Public preview is the changelog line your AE misses
So AWS What's New on August 25: AWS Lambda introduces managed runtimes in public preview for Node.js 26 and Python 3.15. That's the kind of sentence that looks like a footnote until a prospect asks if you're on 26 yet and nobody on the call has seen the post.
Written by Watch Changelog Team
Public preview is the changelog line your AE misses
So AWS What's New on August 25: AWS Lambda introduces managed runtimes in public preview for Node.js 26 and Python 3.15. That's the kind of sentence that looks like a footnote until a prospect asks if you're on 26 yet and nobody on the call has seen the post.
The useful word is preview, not the version numbers.
AWS used to skip this step
To the best of my understanding this is the first time Lambda is shipping a runtime as a public preview. They used to go straight to GA. Once something is GA they cannot break it, so they also could not hear from real workloads while breaking changes were still allowed.
Preview flips that. You can deploy nodejs26.x or python3.15 today. They are not covered by the Lambda SLA or AWS technical support. They should not be in production. Cold starts may be slower on purpose (less optimization, less cache). CloudWatch logs a warning on each cold start so you cannot pretend you did not know.
Partners get a window too. Observability vendors, IaC tools, and deploy frameworks can validate before GA. Upstream Node and Python get a signal from a big cloud while they can still change the language. AWS is calling the whole thing an experiment. They hope previews become the default for future runtimes if this one works.
What you can say on a call
| Public preview | General availability | |
|---|---|---|
| On a sales call | You can talk about it | You can promise it |
| Lambda SLA | No | Yes |
| AWS support | No | Yes |
| Production | Do not | Allowed |
| Breaking changes | Still allowed | Not like this |
| Runtime id | nodejs26.x / python3.15 | Same ids. Functions graduate automatically |
You can talk about it. You cannot promise it. If someone is still selling "we run on whatever AWS GA'd last year," they just got an objection they have not written down.
The sneaky part is the identifier. nodejs26.x in preview is the same nodejs26.x at GA. Functions graduate automatically. No template rewrite. CDK does not even have Runtime.NODEJS_26_X yet. You construct it by string. So an engineer can have 26 in a stack tomorrow and a sales deck can read that as "we support Node 26" when it still means preview.
That is a GTM problem, not a runtime problem. Container images are tagged 26-preview and 3.15-preview for a reason. The tag without preview is not the one you want yet.
How long this stays preview
Timeline:
- 25 Aug 2026: What's New, preview ships
- Oct 2026: upstream languages expected stable (Node Active LTS is the Node gate)
- Nov / Dec 2026 window: Lambda GA targeted within two months after stable
AWS says Node 26 and Python 3.15 are expected to go upstream-stable in October 2026. Lambda GA is targeted within two months after that. For Node they will not GA until it is Active LTS. So you are looking at a late-2026 window, not "it is out so we are on it."
If you pin a function to a specific preview version with Runtime Management Controls, it stays pinned. Those pinned functions are still not under the SLA.
Same week, opposite word
Vercel shipped Security Dashboard generally available on August 26. All plans. A UI plus vercel security check in the CLI. That word, generally available, is the one you can put in a security review. It flags things like missing 2FA, long-lived credentials, and public preview deployments.
Preview and GA showed up in the same two-day window, on two vendors your buyers already run. If you are refreshing blogs by hand you will catch one and miss the other.
We have the AWS line as aws.whats-new and the Vercel line as vercel.changelog. Same JSON shape. Title, date, URL. Raw first. The talking point is the status word. Everything else is decoration.
More from AWS if you want the long version: Introducing public preview runtimes on AWS Lambda.
