AWS Lambda Introduces Self-Managed Code Storage, Increasing Account-Level Quotas

New Self-Managed Code Storage Option

AWS has introduced self-managed code storage for Lambda, allowing users to store function and layer deployment packages in their own S3 buckets. This means Lambda functions can directly reference these packages, shifting storage management to the customer's S3 account.

Removal of Account-Level Storage Quotas

A key change is the removal of the per-Region code storage quota that previously limited large deployments. For those still using Lambda-managed storage, the default quota has been raised from 75 GB to 300 GB. This addresses a common pain point for teams with extensive function fleets.

Individual Function Size Limits Unchanged

Despite the increased account-level storage, the individual function package size limits remain the same. Zip-based functions are still capped at 50 MB zipped and 250 MB unzipped, while container images have a 10 GB limit. This distinction is important as the change primarily affects aggregate storage, not the size of single functions.

Operational Impact and Cost Implications

Operationally, self-managed storage eliminates an intermediate copy step, potentially speeding up function activation after creation or updates. While there are no additional Lambda charges for this feature, customers will incur standard S3 storage and any cross-Region transfer costs, making storage expenses visible on their S3 bill.