AWS Lambda's Self-Managed Code Storage Lifts the Account Quota, Not the Function Size Limit
InfoQ, Thursday, July 30th, 2026
AWS Lambda can now load deployment packages from customer-owned S3 buckets, removing the per-Region code storage quota.
AWS has introduced self-managed code storage for Lambda, letting functions reference deployment packages directly in a customer-owned S3 bucket instead of Lambda-managed storage.
The change removes the per-Region code storage quota entirely and raises the default Lambda-managed limit from 75 GB to 300 GB. Per-function package limits are unchanged: 50 MB zipped and 250 MB unzipped for zip functions, and 10 GB for container images.
Costs shift from an invisible Lambda quota to visible S3 billing, while skipping the intermediate package copy can speed up function activation. Infrastructure-as-code support is still catching up, with Terraform waiting on provider enhancements.