4 ms·
The deployment package size limit seems to be 250MB: https://docs.aws.amazon.com/lambda/latest/dg/limits.html https://docs.aws.amazon.com/lambda/latest/dg/limit
by icebraining 8y ago
The deployment package size limit seems to be 250MB: https://docs.aws.amazon.com/lambda/latest/dg/limits.html https://docs.aws.amazon.com/lambda/latest/dg/limits.html
- pplonski86 8y agoThat's the limitation for data related worker tasks. The iron.io can be alternative (they offer 512 MB https://try.iron.io/pricing-worker-monthly/ https://try.iron.io/pricing-worker-monthly/)
- Glowbox 8y agoThere are workarounds for that, f.e. on startup loading code from an s3 bucket (https://hackernoon.com/exploring-the-aws-lambda-deployment-limits-9a8384b0bec3 https://hackernoon.com/exploring-the-aws-lambda-deployment-l...)
- icebraining 8y agoThat workaround is for the 50MB limit on zip files, not for the 250MB limit :)
- zwily 8y agoNo, you get another 500 MB of tmp space you can use at runtime. This workaround does work.
- visarga 8y agoThat would be OK for some ML applications if the framework itself would not be included in the deployment package.