# AWS Lambda adds a pre-GA runtime channel for Node.js and Python Lambda can now run Node.js 26 and Python 3.15 before their stable releases, giving application teams and tooling vendors a real AWS environment for compatibility testing while breaking changes are still allowed. AWS is changing how Lambda introduces managed runtimes: Node.js 26 and Python 3.15 are available in public preview before GA, with normal runtime identifiers that automatically graduate when the runtimes become production-ready. - Status: Active - Published: 2026-09-01T06:27:01+12:00 - Updated: 2026-09-01T06:27:01+12:00 - Categories: Web Development, Cloud & Infrastructure, Cloud Platforms, JavaScript, Deployment & DevOps - Tags: AWS, AWS Lambda, Node.js, Python, serverless - Canonical HTML: https://beyondthe.news/dossiers/aws-lambda-public-preview-runtimes-nodejs-26-python-315 ## What changed AWS Lambda has introduced managed runtimes in public preview for the first time, beginning with Node.js 26 and Python 3.15. Previously, new Lambda runtimes launched directly at general availability. The preview channel lets customers, infrastructure-as-code frameworks, deployment tools, observability vendors and upstream language communities run real workloads before GA while AWS can still make breaking changes. Preview functions use the eventual GA identifiers, `nodejs26.x` and `python3.15`, so they graduate automatically when AWS moves the runtimes to GA. ## Why it matters The change creates an earlier compatibility window around one of serverless computing’s most important managed-runtime boundaries. Teams can test dependencies, cold starts, native modules, instrumentation and deployment tooling before a language version becomes production-supported. It also shifts some risk onto testers: preview runtimes can break, are outside the Lambda SLA and AWS Technical Support, and AWS explicitly recommends against production use. ## This is a new release process, not just two new language versions AWS says Lambda historically launched managed runtimes directly at GA. The new preview stage is intended to expose compatibility problems while AWS and upstream language projects can still make breaking changes. AWS says it hopes previews can become the default pattern for future runtime launches if the experiment succeeds. ## Existing deployment tools can target the preview identifiers The runtimes are available through the console, CLI, CloudFormation, SAM and CDK using the same identifiers that will be used at GA. That makes it possible to test normal infrastructure definitions rather than maintaining a separate preview-only deployment model. ## The preview is deliberately outside the production support boundary AWS does not cover these runtimes under the Lambda SLA or AWS Technical Support and warns against production workloads. Performance can also differ from GA, including slower cold starts while optimization and internal caching mature. ## Functions graduate automatically at GA Because the identifier remains unchanged, an unpinned preview function moves onto the GA runtime without a configuration migration. Teams that pin a specific runtime version retain that pin and therefore need to manage the transition themselves. ## Key details - Node.js 26 and Python 3.15 are Lambda’s first managed runtimes released through a public-preview phase. - Preview runtimes may receive breaking changes and are not covered by the Lambda SLA or AWS Technical Support. - They are available across commercial, GovCloud and China Regions at standard Lambda pricing. - Runtime identifiers are `nodejs26.x` and `python3.15`, the same identifiers planned for GA. - AWS documentation targets November 2026 for the managed-runtime launches, subject to upstream release timing. - AWS says preview runtimes are an experiment it may extend to future runtime releases. ## Builder takeaways - Use the preview to run CI and representative workloads, not production traffic. - Test native dependencies, observability agents, frameworks and IaC definitions before GA instead of waiting for the production cutoff. - Avoid pinning a pre-GA runtime version unless you have a specific reproducibility reason and a plan to unpin it. - Track AWS’s dedicated feedback channels because breaking changes during preview are expected rather than exceptional. - Treat any preview performance measurement as provisional until AWS completes GA optimization. ## What to watch - Whether AWS makes public previews standard for future Lambda runtimes. - Breaking changes or performance improvements during the Node.js 26 and Python 3.15 preview periods. - Final GA timing after the upstream language releases. - Compatibility updates from major serverless frameworks and observability vendors. ## Uncertainties - The preview runtimes can change before GA. - AWS’s target GA dates are indicative and depend partly on upstream language release schedules. - Performance and operational behavior during preview may not represent the final GA runtimes. ## Sources - [AWS Lambda introduces managed runtimes in public preview for Node.js 26 and Python 3.15](https://aws.amazon.com/about-aws/whats-new/2026/08/aws-lambda-node-js-python-public-preview/) — Amazon Web Services · primary announcement · 2026-08-25T00:00:00+12:00. Primary launch details, support limits, identifiers, regions and pricing. - [Introducing public preview runtimes on AWS Lambda, starting with Node.js 26 and Python 3.15](https://aws.amazon.com/blogs/compute/introducing-public-preview-runtimes-on-aws-lambda-starting-with-node-js-26-and-python-3-15/) — Amazon Web Services · official engineering blog · 2026-08-15T00:00:00+12:00. Detailed rationale, expected preview behavior and transition-to-GA model. - [Lambda runtimes](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html) — Amazon Web Services · primary documentation. Current runtime status and projected release/deprecation information.