--- title: AWS Lambda's Self-Managed Code Storage Lifts the Account... description: AWS Lambda now supports self-managed code storage, allowing functions and layers to reference deployment packages directly from customer-owned S3 buckets. This... canonical: https://daily.dev/posts/aws-lambda-s-self-managed-code-storage-lifts-the-account-quota-not-the-function-size-limit-mhc0xpwoy twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: AWS Lambda's Self-Managed Code Storage Lifts the Account Quota, Not the Function Size Limit | daily.dev og:description: AWS Lambda now supports self-managed code storage, allowing functions and layers to reference deployment packages directly from customer-owned S3 buckets. This... og:url: https://daily.dev/posts/aws-lambda-s-self-managed-code-storage-lifts-the-account-quota-not-the-function-size-limit-mhc0xpwoy og:image: https://api.daily.dev/og/posts/mHC0xpWOy.png og:image:alt: AWS Lambda's Self-Managed Code Storage Lifts the Account Quota, Not the Function Size Limit og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # AWS Lambda's Self-Managed Code Storage Lifts the Account Quota, Not the Function Size Limit **[InfoQ](https://daily.dev/sources/infoq)** · 3 min read · 1 upvotes · 0 comments ## Summary AWS Lambda now supports self-managed code storage, allowing functions and layers to reference deployment packages directly from customer-owned S3 buckets. This removes the per-Region code storage quota and raises the Lambda-managed default from 75 GB to 300 GB. Importantly, per-function package size limits remain unchanged (50 MB zipped, 250 MB unzipped for zip-based; 10 GB for containers). Lambda no longer creates an intermediate copy of the package, which can speed up function activation. Storage costs shift from an invisible Lambda quota to visible S3 billing. The deployment workflow still requires calling UpdateFunctionCode after replacing an S3 object. Terraform provider support is not yet available and remains an open enhancement request. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Does AWS Lambda's new self-managed code storage let me deploy larger function packages? No, per-function package size limits remain unchanged: 50 MB zipped and 250 MB unzipped for zip-based functions, and 10 GB for container images. Self-managed storage only removes the aggregate per-Region account quota for total code storage and raises the Lambda-managed default from 75 GB to 300 GB; individual function size ceilings still apply exactly as before. _Teams sizing Lambda packages can track AWS service limit changes like this on daily.dev before they hit a wall._ ### Do I still need to call UpdateFunctionCode after changing my Lambda deployment package in S3 with self-managed storage? Yes, UpdateFunctionCode still must be called after replacing the object in S3 because the code reference resolves at update time rather than continuously, so pointing Lambda at a bucket does not turn it into a live code feed. The deployment workflow itself is otherwise unchanged from before this feature. _Anyone automating Lambda deployments can follow serverless workflow changes like this via daily.dev._ ### Does Terraform support AWS Lambda's new self-managed S3 code storage option? Not yet: a Terraform provider enhancement request filed July 15 asking for an s3_object_storage_mode attribute on aws_lambda_function remains open with no implementation. Teams standardized on Terraform currently need to use the AWS CLI or SDKs instead, where the parameter is already available. _Infrastructure-as-code teams weighing Terraform gaps against CLI workarounds can track updates like this on daily.dev._ ## Similar posts on daily.dev - [AWS Lambda announces self-managed code storage](https://daily.dev/posts/aws-lambda-announces-self-managed-code-storage-jb2c0qruw) · AWS · 0 upvotes · 0 comments - [AWS Lambda supports up to 32 GB of memory and 16 vCPUs for Lambda Managed Instances](https://daily.dev/posts/aws-lambda-supports-up-to-32-gb-of-memory-and-16-vcpus-for-lambda-managed-instances-jp3xptauv) · AWS · 0 upvotes · 0 comments - [AWS Lambda Pushes Serverless Toward Long-Running Workloads](https://daily.dev/posts/aws-lambda-pushes-serverless-toward-long-running-workloads-2zbrcptyu) · InfoQ · 0 upvotes · 0 comments - [Vercel Functions can now be up to 5GB in package size](https://daily.dev/posts/vercel-functions-can-now-be-up-to-5gb-in-package-size-xblhhizuh) · Vercel · 7 upvotes · 1 comments --- Tags: [#cloud](https://daily.dev/tags/cloud), [#serverless](https://daily.dev/tags/serverless), [#terraform](https://daily.dev/tags/terraform), [#aws-lambda](https://daily.dev/tags/aws-lambda), [#aws-s3](https://daily.dev/tags/aws-s3) [View this post on daily.dev](https://daily.dev/posts/aws-lambda-s-self-managed-code-storage-lifts-the-account-quota-not-the-function-size-limit-mhc0xpwoy) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"AWS Lambda's Self-Managed Code Storage Lifts the Account Quota, Not the Function Size Limit","url":"https://daily.dev/posts/aws-lambda-s-self-managed-code-storage-lifts-the-account-quota-not-the-function-size-limit-mhc0xpwoy","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/aws-lambda-s-self-managed-code-storage-lifts-the-account-quota-not-the-function-size-limit-mhc0xpwoy"},"datePublished":"2026-07-30T08:03:55.993Z","dateModified":"2026-09-14T09:11:15.743Z","description":"AWS Lambda now supports self-managed code storage, allowing functions and layers to reference deployment packages directly from customer-owned S3 buckets. This...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c6272c88cbaf8d885b2b4a4116900744?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c6272c88cbaf8d885b2b4a4116900744?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoQ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoQ","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/afc3bced3e1e4b188dd9127017a60e0c","url":"https://daily.dev/sources/infoq"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/aws-lambda-s-self-managed-code-storage-lifts-the-account-quota-not-the-function-size-limit-mhc0xpwoy","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cloud,serverless,terraform,aws-lambda,aws-s3","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoQ","item":"https://daily.dev/sources/infoq"},{"@type":"ListItem","position":3,"name":"AWS Lambda's Self-Managed Code Storage Lifts the Account Quota, Not the Function Size Limit"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/aws-lambda-s-self-managed-code-storage-lifts-the-account-quota-not-the-function-size-limit-mhc0xpwoy#faq","mainEntity":[{"@type":"Question","name":"Does AWS Lambda's new self-managed code storage let me deploy larger function packages?","acceptedAnswer":{"@type":"Answer","text":"No, per-function package size limits remain unchanged: 50 MB zipped and 250 MB unzipped for zip-based functions, and 10 GB for container images. Self-managed storage only removes the aggregate per-Region account quota for total code storage and raises the Lambda-managed default from 75 GB to 300 GB; individual function size ceilings still apply exactly as before. Teams sizing Lambda packages can track AWS service limit changes like this on daily.dev before they hit a wall."}},{"@type":"Question","name":"Do I still need to call UpdateFunctionCode after changing my Lambda deployment package in S3 with self-managed storage?","acceptedAnswer":{"@type":"Answer","text":"Yes, UpdateFunctionCode still must be called after replacing the object in S3 because the code reference resolves at update time rather than continuously, so pointing Lambda at a bucket does not turn it into a live code feed. The deployment workflow itself is otherwise unchanged from before this feature. Anyone automating Lambda deployments can follow serverless workflow changes like this via daily.dev."}},{"@type":"Question","name":"Does Terraform support AWS Lambda's new self-managed S3 code storage option?","acceptedAnswer":{"@type":"Answer","text":"Not yet: a Terraform provider enhancement request filed July 15 asking for an s3_object_storage_mode attribute on aws_lambda_function remains open with no implementation. Teams standardized on Terraform currently need to use the AWS CLI or SDKs instead, where the parameter is already available. Infrastructure-as-code teams weighing Terraform gaps against CLI workarounds can track updates like this on daily.dev."}}]} ```