I promised to write an entire article on this topic after struggling for a couple hours to get the graphviz library working in AWS Lambda. In this ...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for the write up. Did you consider using the AWS SAM/LambCI "build" variant containers to avoid installing developer tools? Everyone has this and it follows the "lambci/lambda:build-" naming convention. SAM uses these build variants too. I make heavy use of them not only for layers building (github.com/customink/ruby-vips-lambda) but for local development/test too.
Also, have you seen Michael Hart's yumda project (github.com/lambci/yumda) on LambCI? In some cases it can be useful. I tend to put layer building into 3 buckets.
Hope that helps!
Thanks for reading! I did knew the build images from lambci but wanted to illustrate that for some cases you won't get all the necessary tools and that you could still craft your way into a build image that suits your needs.
It's the first time I read about
yumdabut sounds exactly what I was after originally. I had a similar experience with what you mention about not using layers for code, it was kind of a pain and limits your tree-shaking possibilities in real world projects. It's a super interesting conversation on when it's worth to use a layer and I think binaries are one of those use-cases.I came across the need to use GraphViz in Lambda.
Successfully did it: schemaviz.surge.sh/
There is a working Lambda layer on github: github.com/Nummulith/SchemaViz
I'm happy to answer any questions or receive feedback.
Hi, how did you create the lambda layer? could you help me please?