Skip to content

Feature request: use Lambda Layers for python packages #299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
str3tch opened this issue Dec 5, 2018 · 2 comments
Closed

Feature request: use Lambda Layers for python packages #299

str3tch opened this issue Dec 5, 2018 · 2 comments

Comments

@str3tch
Copy link

str3tch commented Dec 5, 2018

I am flat out and have no time to do this, so I'll write it here in case someone else does - or at least start a conversation about it.

Now that Lambda has the concept of Layers, it would be great if we can utilise them for common python dependencies

https://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html#configuration-layers-path

If the user is not packaging individually, then we can create one Lambda Layer with the python requirements, and the functions just use that layer, rather than having to have the packages in each function deployment.

If they are packaging individually, then maybe there's the option of specifying which ones are common and therefore can go into a layer. This will make the package and upload process faster, and also resulting lambda deployment package smaller (as they will share the layer)

whilst I write this I spotted a blog of someone else doing this:

https://nordcloud.com/lambda-layers-for-python-runtime/

so.. what you reckon?

@str3tch
Copy link
Author

str3tch commented Dec 5, 2018

serverless framework supports layers: https://serverless.com/blog/publish-aws-lambda-layers-serverless-framework/

@dschep
Copy link
Contributor

dschep commented Dec 5, 2018

Duplicate of #295

@dschep dschep marked this as a duplicate of #295 Dec 5, 2018
@dschep dschep closed this as completed Dec 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants