Lambda code storage default limit increased to 300GB. Exceeded the old 75GB limit without requesting a quota increase.
This page has been translated by machine translation. View original
Introduction
On July 15, 2026, the default limit for AWS Lambda managed code storage was increased.
| Item | Old Default | New Default |
|---|---|---|
| Managed code storage limit | 75 GB | 300 GB |
Previously, the initial value was 75 GB per region, and a quota increase request was required if that was exceeded. With this change, you can use up to 300 GB without submitting a request.
Verification Details
Verification Environment
| Item | Value |
|---|---|
| Region | ap-northeast-1 |
| Quota increase request | None |
| Existing Lambda functions | 17 |
| Dummy zip size | 209,715,368 bytes (approx. 200 MB) |
| Number of layers created | 390 |
| Layer compatible runtime | python3.12 |
Checking with get-account-settings
First, I checked the current limit value using get-account-settings.
aws lambda get-account-settings --region ap-northeast-1
{
"AccountLimit": {
"TotalCodeSize": 322122547200,
"CodeSizeUnzipped": 262144000,
"CodeSizeZipped": 52428800,
"ConcurrentExecutions": 1000,
"UnreservedConcurrentExecutions": 1000
},
"AccountUsage": {
"TotalCodeSize": 68507563,
"FunctionCount": 17
}
}
AccountLimit.TotalCodeSize is 322,122,547,200 bytes (300 GB). This has been increased from the previous default of 80,530,636,800 bytes (75 GB). The size limits for individual functions, such as CodeSizeUnzipped (250 MB) and CodeSizeZipped (50 MB), have not changed.
At the start of verification, the usage (AccountUsage.TotalCodeSize) was 68,507,563 bytes (approximately 65 MB).
Demonstrating Exceeding 75 GB
I created a dummy zip file of approximately 200 MB. I generated 200 MB of random data from /dev/urandom and archived it using zip -0 (uncompressed store).
dd if=/dev/urandom of=dummy.bin bs=1M count=200
zip -0 dummy.zip dummy.bin
Upload the created zip to S3.
aws s3 cp dummy.zip s3://<BUCKET_NAME>/<OBJECT_KEY>
Create a layer referencing the zip on S3. The following is an example of a single execution.
aws lambda publish-layer-version \
--layer-name dummy-layer-001 \
--content S3Bucket=<BUCKET_NAME>,S3Key=<OBJECT_KEY> \
--compatible-runtimes python3.12 \
--region ap-northeast-1
Using this approach, I created 390 layers. In practice, they were executed all at once using a shell loop.
for i in $(seq -w 1 390); do
aws lambda publish-layer-version \
--layer-name "dummy-layer-$i" \
--content S3Bucket=<BUCKET_NAME>,S3Key=<OBJECT_KEY> \
--compatible-runtimes python3.12 \
--region ap-northeast-1 &
done
wait
The time required for layer creation alone was approximately 7 minutes.
| Timing | TotalCodeSize | Notes |
|---|---|---|
| Before layer creation | 68,507,563 bytes (≒ 65 MB) | Existing 17 functions |
| After creating 390 layers | 81,857,501,083 bytes (≒ 76.24 GB) | Exceeded old limit of 75 GB, no error |
| After cleanup | 68,507,563 bytes (≒ 65 MB) | Usage returned to original value |
The old default limit of 75 GB (80,530,636,800 bytes) was exceeded by approximately 1.24 GB, but CodeStorageExceededException did not occur. All layer creations completed successfully. After the verification, all dummy layers were deleted and the usage returned to its original value.
Note that when uploading directly with publish-layer-version using --zip-file, the CodeSizeZipped (50 MB) limit will be hit. Via S3 (--content S3Bucket=...,S3Key=...), a 200 MB zip can be used to create a layer without issues. However, even via S3, the post-extraction limit of 250 MB (CodeSizeUnzipped) still applies.
Summary
The default limit for AWS Lambda managed code storage has been increased from 75 GB to 300 GB.
In this verification, I created 390 dummy layers on an account without a quota increase request and confirmed that usage could be increased to approximately 76.24 GB, exceeding the old limit equivalent of 75 GB. Even after exceeding 75 GB, CodeStorageExceededException did not occur, and layer creation completed successfully.
Previously, a quota increase request was required before exceeding 75 GB, but going forward, up to 300 GB can be used without a request. For environments deploying large numbers of functions and layers, this reduces the effort of submitting requests and allows for more comfortable code management. Note that this 300 GB quota is currently not increasable.
If 300 GB is still insufficient, REFERENCE mode, which does not count toward code storage, is also available. For details, please refer to the following article.
