Legacy ImageMagick Discussions Archive

Hi,

I am trying to bundle ImageMagick 7 in an AWS lambda function. I build ImageMagick from source with support for jpeg, png, webp, tiff, openjp2 and jbig. The library compiled fine and both magick and identify worked with no issues.

I copied the binaries, libraries along with the coders, filters and configuration xml files each to its own directory, packaged them all in my lambda function zip archive.

I then set the environment variables for each path from the AWS lambda console as such:

MAGICK_CODER_FILTER_PATH => /var/task/imagemagick/filters
MAGICK_CODER_MODULE_PATH => /var/task/imagemagick/coders
MAGICK_CONFIGURE_PATH => /var/task/imagemagick/config
LD_LIBRARY_PATH => /var/task/imagemagick/lib

I can verify that each of the directories mentioned above do exist on the lambda function environment as I started listing the files inside each one of those directories and indeed they are there with all their files.


Then I tried to execute this simple command [/b] and I got the following:
I tried running from the code and indeed the file does exist: What am I missing here?

I know nothing about "AWS lambda function". Is it a permissions problem?

snibgo wrote: ↑2017-12-05T07:58:48-07:00 I know nothing about "AWS lambda function". Is it a permissions problem?

I don't think its a permission problem. I opened a linux EC2 instance and copied the package binaries, libs and files. set the environment variables as mentioned in the original post and I get the same error. As for AWS Lambda, you can think of it as a container if you will.