1 Answer
- Newest
- Most votes
- Most comments
1
Hello.
The size of your deployment package probably cannot be increased.
So I think you can get around the limitation by mounting EFS from Lambda or creating a custom runtime using Docker containers.
https://docs.aws.amazon.com/lambda/latest/dg/services-efs.html
If you use a custom runtime, you can use up to 10GB.
https://docs.aws.amazon.com/lambda/latest/dg/images-create.html#images-types
Lambda supports a maximum uncompressed image size of 10 GB, including all layers.
Relevant content
asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 years ago
Thanks for your reply.
Why not? The current limit "feels" somewhat arbitrary.
In the same deployment package size quota limit documentation that I referenced, it says "this quota applies to all the files you upload, including layers and custom runtimes." What "custom runtimes" is that referring to if not Docker containers?
I'll look into using EFS or Docker. My concern with those is increased initialization time, on every trigger of a Lambda function, over using the standard AWS base image. How concerned should I be about that? I'll look more at https://docs.aws.amazon.com/lambda/latest/dg/images-create.html.
Actually, moving to container image for larger packages will reduce the startup time compared to zip files.