AWS Security ChangesHomeSearch

AWS lambda documentation change

Service: lambda · 2026-07-01 · Documentation low

File: lambda/latest/dg/troubleshooting-deployment.md

Summary

Updated code storage limit from 75GB to 300GB and added self-managed S3 storage option

Security assessment

Changes are operational improvements without security implications. Self-managed storage option doesn't introduce new security features.

Diff

diff --git a/lambda/latest/dg/troubleshooting-deployment.md b/lambda/latest/dg/troubleshooting-deployment.md
index 4c7da0ad1..857398f39 100644
--- a//lambda/latest/dg/troubleshooting-deployment.md
+++ b//lambda/latest/dg/troubleshooting-deployment.md
@@ -138 +138 @@ For some languages, Lambda provides a library with an interface that expects a h
-Lambda stores your function code in an internal S3 bucket that's private to your account. Each AWS account is allocated 75 GB of storage in each Region. Code storage includes the total storage used by both Lambda functions and layers. If you reach the quota, you receive a _CodeStorageExceededException_ when you attempt to deploy new functions.
+Lambda stores a copy of your function code in an internal S3 bucket that's private to your account. Each AWS account is allocated 300 GB of code storage (unzipped) in each Region. Code storage includes the total storage used by both Lambda functions and layers. If you reach the quota, you receive a _CodeStorageExceededException_ when you attempt to deploy new functions.
@@ -140 +140,3 @@ Lambda stores your function code in an internal S3 bucket that's private to your
-Manage the storage space available by cleaning up old versions of functions, removing unused code, or using Lambda layers. In addition, it's good practice to [use separate AWS accounts for separate workloads](./concepts-application-design.html#multiple-accounts) to help manage storage quotas.
+To resolve this issue, you can clean up old versions of functions, remove unused code, or use Lambda layers to de-duplicate common code shared between functions. In addition, it's good practice to [use separate AWS accounts for separate workloads](./concepts-application-design.html#multiple-accounts) to help manage storage quotas.
+
+Alternatively, you can configure your functions and layers to use [self-managed S3 code storage](./configuration-self-managed-storage.html). With self-managed S3 code storage, Lambda references your code directly from your S3 bucket, which does not count against your storage quota.