The AMI amzn2-ami-hvm-0313-x86_64-gp2 was used for this compilation. ImageMagickīefore proceeding, set up a Lambda Execution Environment. Updated instructions for nodejs10.x runtime Did you do this also? Or is this using Node8.10 and using the preinstalled IM libs? I found when using Lambda Node10.x I then also had to copy across many of the missing libs & config xmls like delegate.xml. In which case - why not just use the ImageMagick 6.7.8.9 already in Lambda/Node8.10 - thanks for the detailed tips on GS / PDF / gslib config. with your script above, I'm pretty sure that won't give you extras such as PDF support, and will rely on the libs / modules included in the Lambda AMI for Node8.10. (I'm not sure if this was a recent change?) But convert & identify etc work natively out of the box, however it doesn't include PDF support. What caught me out during this journey is that Lambda/Node8.10 actually has ImageMagick 6.7.8.9-15.21.amzn1 RPM already installed. However it's also left me some questions - did AWS say why they removed the convert modules? And do we mean the modules like /usr/lib64/ImageMagick-6.7.8/modules-Q16/coders/pdf.la ? This thread has been super helpful - in that I now finally have a working version of IM with PDF support running on Lambda / Node v10.x Then in our Lambda function, above the handler definition, we include the following: Ensure the bin/gs binary is executable via chmod +x bin/gs.Copy the gs-*-linux-x86_64 executable to bin/gs in your repository.Download the latest version of Ghostscript for Linux x86 (64 bit) from. In the instructions above, ensure use of -with-gslib=no.To work around that, we did the following: We also had issues working with PDF files. If building ImageMagick 7, symlinks are present in the bin directory, so be sure to preserve symlinks using zip -symlinks or tar zcf.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |