--- title: AWS Lambda now supports SnapStart for container image... description: AWS Lambda now supports SnapStart for container image-packaged functions, cutting cold start times from several seconds down to sub-second. SnapStart works by... canonical: https://daily.dev/posts/aws-lambda-now-supports-snapstart-for-container-image-functions-ssafmfewu twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: AWS Lambda now supports SnapStart for container image functions | daily.dev og:description: AWS Lambda now supports SnapStart for container image-packaged functions, cutting cold start times from several seconds down to sub-second. SnapStart works by... og:url: https://daily.dev/posts/aws-lambda-now-supports-snapstart-for-container-image-functions-ssafmfewu og:image: https://api.daily.dev/og/posts/SSafMFeWU.png og:image:alt: AWS Lambda now supports SnapStart for container image functions 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 now supports SnapStart for container image functions **[AWS](https://daily.dev/sources/aws)** · 2 min read · 0 upvotes · 0 comments ## Summary AWS Lambda now supports SnapStart for container image-packaged functions, cutting cold start times from several seconds down to sub-second. SnapStart works by snapshotting the initialized execution environment at deployment and resuming from it on invocation instead of cold-initializing. Previously limited to managed runtimes (Python, .NET, Java), it now extends to container images, useful for latency-sensitive workloads like ML inference and interactive APIs. It's available in all commercial AWS regions except Asia Pacific (New Zealand) and Asia Pacific (Taipei), and can be enabled via the Lambda API, Console, CLI, CloudFormation, SAM, SDK, or CDK. ## 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 SnapStart work with container image functions? Yes, AWS Lambda now supports SnapStart for functions packaged as container images, reducing startup times from several seconds to as low as sub-second. Previously SnapStart only worked with managed runtimes (Python, .NET, and Java). It is available in all commercial AWS Regions except Asia Pacific (New Zealand) and Asia Pacific (Taipei), and can be enabled via the Lambda API, Console, CLI, CloudFormation, SAM, SDK, or CDK. _Teams tuning Lambda cold starts for container-based deployments can track serverless updates like this on daily.dev._ ### How does AWS Lambda SnapStart reduce cold start times for container images? SnapStart takes a snapshot of the initialized execution environment during function deployment, caches it, and resumes from that snapshot on invocation instead of initializing from scratch. This avoids the delay of downloading image layers and initializing the runtime and application code each time, which is especially useful for latency-sensitive workloads like ML inference and interactive APIs. _Engineers optimizing latency-sensitive Lambda workloads can follow serverless performance changes via daily.dev._ ### Do I need to change my code to use SnapStart with a Node.js or Ruby Lambda container image? It depends on the base image. If using an AWS base image for Lambda with Java (version 11+), Python (version 3.12+), or .NET (version 8+), the SnapStart experience is the same as with .zip archive deployments. For other AWS base images like Node.js or Ruby, or custom base images, you need to follow the runtime hooks guidance in the Lambda developer documentation. _Developers migrating container-based Lambda functions can keep up with runtime-specific caveats through daily.dev._ --- Tags: [#aws](https://daily.dev/tags/aws), [#docker](https://daily.dev/tags/docker), [#serverless](https://daily.dev/tags/serverless), [#aws-lambda](https://daily.dev/tags/aws-lambda) [View this post on daily.dev](https://daily.dev/posts/aws-lambda-now-supports-snapstart-for-container-image-functions-ssafmfewu) ```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 now supports SnapStart for container image functions","url":"https://daily.dev/posts/aws-lambda-now-supports-snapstart-for-container-image-functions-ssafmfewu","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/aws-lambda-now-supports-snapstart-for-container-image-functions-ssafmfewu"},"datePublished":"2026-09-02T15:07:13.387Z","dateModified":"2026-09-13T21:25:17.607Z","description":"AWS Lambda now supports SnapStart for container image-packaged functions, cutting cold start times from several seconds down to sub-second. SnapStart works by...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2d99c2aecc14a73a5cba88addc902c88?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2d99c2aecc14a73a5cba88addc902c88?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"AWS","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":"AWS","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/aws","url":"https://daily.dev/sources/aws"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/aws-lambda-now-supports-snapstart-for-container-image-functions-ssafmfewu","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,docker,serverless,aws-lambda","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS","item":"https://daily.dev/sources/aws"},{"@type":"ListItem","position":3,"name":"AWS Lambda now supports SnapStart for container image functions"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/aws-lambda-now-supports-snapstart-for-container-image-functions-ssafmfewu#faq","mainEntity":[{"@type":"Question","name":"Does AWS Lambda SnapStart work with container image functions?","acceptedAnswer":{"@type":"Answer","text":"Yes, AWS Lambda now supports SnapStart for functions packaged as container images, reducing startup times from several seconds to as low as sub-second. Previously SnapStart only worked with managed runtimes (Python, .NET, and Java). It is available in all commercial AWS Regions except Asia Pacific (New Zealand) and Asia Pacific (Taipei), and can be enabled via the Lambda API, Console, CLI, CloudFormation, SAM, SDK, or CDK. Teams tuning Lambda cold starts for container-based deployments can track serverless updates like this on daily.dev."}},{"@type":"Question","name":"How does AWS Lambda SnapStart reduce cold start times for container images?","acceptedAnswer":{"@type":"Answer","text":"SnapStart takes a snapshot of the initialized execution environment during function deployment, caches it, and resumes from that snapshot on invocation instead of initializing from scratch. This avoids the delay of downloading image layers and initializing the runtime and application code each time, which is especially useful for latency-sensitive workloads like ML inference and interactive APIs. Engineers optimizing latency-sensitive Lambda workloads can follow serverless performance changes via daily.dev."}},{"@type":"Question","name":"Do I need to change my code to use SnapStart with a Node.js or Ruby Lambda container image?","acceptedAnswer":{"@type":"Answer","text":"It depends on the base image. If using an AWS base image for Lambda with Java (version 11+), Python (version 3.12+), or .NET (version 8+), the SnapStart experience is the same as with .zip archive deployments. For other AWS base images like Node.js or Ruby, or custom base images, you need to follow the runtime hooks guidance in the Lambda developer documentation. Developers migrating container-based Lambda functions can keep up with runtime-specific caveats through daily.dev."}}]} ```