Skip to content
Cloud

AWS Lambda Releases

Track every AWS Lambda runtime, from latest supported to end-of-life. Runtime version timelines, EOL dates, deprecation schedules, and migration guidance.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Embed Badges

Add live AWS Lambda status badges to your README, docs, or dashboard.

Health Status

Overall support health

AWS Lambda Health Status
![AWS Lambda Health Status](https://img.releaserun.com/badge/health/aws-lambda.svg)

EOL Countdown

Next end-of-life date

AWS Lambda EOL Countdown
![AWS Lambda EOL Countdown](https://img.releaserun.com/badge/eol/aws-lambda.svg)

Latest Version

Current stable release

AWS Lambda Latest Version
![AWS Lambda Latest Version](https://img.releaserun.com/badge/v/aws-lambda.svg)

CVE Status

Known vulnerabilities

AWS Lambda CVE Status
![AWS Lambda CVE Status](https://img.releaserun.com/badge/cve/aws-lambda.svg)

Frequently Asked Questions

Common questions about AWS Lambda releases and lifecycle.

How does AWS Lambda runtime deprecation work?
AWS announces runtime deprecation about 60 days before Phase 1, when you can no longer create new functions. Phase 2 follows, blocking updates to existing functions. Phase 3 eventually blocks invocations. Always migrate before Phase 1 hits.
Which Lambda runtimes are currently supported?
Check the version table above for current status. AWS supports runtimes for Node.js, Python, Java, .NET, Ruby, and Go. Custom runtimes via Amazon Linux have their own lifecycle.
How do I know when my Lambda runtime is being deprecated?
AWS sends email notifications and posts to the AWS Lambda blog. You can also check the Health Dashboard and this tracker for early warnings.
What happens if I do not upgrade a deprecated Lambda runtime?
After Phase 2 deprecation, you cannot update function code or configuration. After Phase 3, invocations will fail. AWS does not auto-migrate your functions to newer runtimes.

Related Tools