7 ms·
Everyone complains about the 15 minutes problem on lambda, but am I the only that have a problem with the 250MB deployment size limit?
by RavlaAlvar 4y ago
Everyone complains about the 15 minutes problem on lambda, but am I the only that have a problem with the 250MB deployment size limit?
- killyourcar 4y agoWhat are you publishing that has a binary that big but can't use a container image?
- cbsmith 4y agoSure you can get around that with proper use of Layers.
- rlayton2 4y agoTotal layer size is also restricted.
- cbsmith 4y agoRestricted to 10GB. I'm sorry, but if you need more than that, you probably shouldn't be using Lambdas the way you are using Lambdas.
- ManWith2Plans 4y agoThis isn't true. 10GB is the limit on docker backed lambda function sizes. Layers are capped to 256MB just like lambda functions. A couple of weeks ago, I tried to deploy a lambda function that created Azure Subnets in python, and the Azure client was 265GB alone. My layer creation api call failed because of this.
- cbsmith 4y agoYou're right. I forgot it was docker backed lambda rather than layers. Out of curiosity, why didn't you use an Azure docker image to back your lambda function?
- scarface74 4y agoYou can use Lambda to run Docker containers of sizes up to 10GB https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/ https://aws.amazon.com/blogs/aws/new-for-aws-lambda-containe...