AWS ships self-managed S3 buckets for Lambda function code, removing 75GB quota

AWS quietly shipped a change that matters to teams running serverless at scale: Lambda can now read function code directly from customer-owned S3 buckets, eliminating the long-standing 75GB per-region code storage quota. For organizations with hundreds or thousands of Lambda functions — increasingly common as agentic and event-driven AI workloads proliferate — that quota was a real operational ceiling.

Beyond raw scale, the feature addresses security and governance. By keeping deployment artifacts in a bucket the customer controls, teams can apply their own encryption, access policies, versioning and audit logging to the code that runs in Lambda, rather than relying on AWS's opaque internal storage. That's meaningful for regulated industries and security-conscious platform teams who want provenance and control over exactly what code executes.

The timing fits AWS's broader push to make its serverless and agentic infrastructure enterprise-grade — the same week it detailed Bedrock AgentCore's growth, HyperPod topology improvements for training clusters, and cross-cloud security scanning. Individually minor, collectively these signal AWS grinding on the governance and scale primitives that large customers demand.

The caveat: this is plumbing, not a headline AI feature, and it primarily benefits organizations that have already hit the code-storage ceiling. But for those teams, removing an artificial quota and handing back control of deployment artifacts is exactly the kind of unglamorous improvement that keeps large customers on the platform — and it reflects how much of the 'AI infrastructure' race is really about mundane operational limits.