AWS Lambda End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all AWS Lambda versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Node.js 0.10 | — | Nov 13, 2014 | Oct 31, 2016 | 3569 days past EOL | EOL |
| Java 8 (AL1) | — | Jun 15, 2015 | Mar 3, 2027 | 206 days remaining | Active |
| Python 2.7 | — | Oct 8, 2015 | May 30, 2022 | 1532 days past EOL | EOL |
| Node.js 4.3 | — | Apr 7, 2016 | Mar 5, 2020 | 2348 days past EOL | EOL |
| .NET Core 1.0 | — | Dec 1, 2016 | Jul 30, 2019 | 2567 days past EOL | EOL |
| Node.js 6.10 | — | Mar 22, 2017 | Aug 12, 2019 | 2554 days past EOL | EOL |
| Python 3.6 | — | Apr 18, 2017 | Aug 29, 2022 | 1441 days past EOL | EOL |
| Node.js 4.3 edge | — | Jul 17, 2017 | Apr 30, 2020 | 2292 days past EOL | EOL |
| Go 1.x | — | Jan 15, 2018 | Mar 3, 2027 | 206 days remaining | Active |
| .NET Core 2.0 | — | Jan 15, 2018 | May 30, 2019 | 2628 days past EOL | EOL |
| Node.js 8.10 | — | Apr 2, 2018 | Mar 6, 2020 | 2347 days past EOL | EOL |
| .NET Core 2.1 | — | Jul 9, 2018 | Apr 13, 2022 | 1579 days past EOL | EOL |
| Python 3.7 | — | Nov 19, 2018 | Mar 3, 2027 | 206 days remaining | Active |
| Custom Runtime (AL1) | — | Nov 29, 2018 | Mar 3, 2027 | 206 days remaining | Active |
| Ruby 2.5 | — | Nov 29, 2018 | Mar 31, 2022 | 1592 days past EOL | EOL |
| Node.js 10 | — | May 15, 2019 | Feb 14, 2022 | 1637 days past EOL | EOL |
| Java 11 | — | Nov 18, 2019 | Aug 31, 2027 | 387 days remaining | Active |
| Python 3.8 | — | Nov 18, 2019 | Mar 3, 2027 | 206 days remaining | Active |
| Node.js 12 | — | Nov 18, 2019 | Apr 30, 2023 | 1197 days past EOL | EOL |
| Ruby 2.7 | — | Feb 19, 2020 | Mar 3, 2027 | 206 days remaining | Active |
| .NET Core 3.1 | — | Mar 31, 2020 | May 3, 2023 | 1194 days past EOL | EOL |
| Custom Runtime (AL2) | — | Aug 12, 2020 | Mar 3, 2027 | 206 days remaining | Active |
| Java 8 (AL2) | — | Aug 12, 2020 | Aug 31, 2027 | 387 days remaining | Active |
| .NET 5 (container-only) | — | Dec 2, 2020 | Not published | Past EOL | EOL |
| Node.js 14 | — | Feb 3, 2021 | Mar 3, 2027 | 206 days remaining | Active |
| Python 3.9 | — | Aug 16, 2021 | Mar 3, 2027 | 206 days remaining | Active |
| .NET 6 | — | Feb 24, 2022 | Mar 3, 2027 | 206 days remaining | Active |
| Node.js 16 | — | May 12, 2022 | Mar 3, 2027 | 206 days remaining | Active |
| .NET 7 (container-only) | — | Nov 15, 2022 | Not published | Past EOL | EOL |
| Node.js 18 | — | Nov 18, 2022 | Mar 3, 2027 | 206 days remaining | Active |
| Python 3.10 | — | Apr 18, 2023 | Mar 3, 2027 | 206 days remaining | Active |
| Java 17 | — | Apr 27, 2023 | Aug 31, 2027 | 387 days remaining | Active |
| Ruby 3.2 | — | Jun 7, 2023 | Mar 3, 2027 | 206 days remaining | Active |
| Python 3.11 | — | Jul 27, 2023 | Aug 31, 2027 | 387 days remaining | Active |
| Custom Runtime (AL2023) | — | Nov 10, 2023 | Aug 31, 2029 | 1118 days remaining | Active |
| Node.js 20 | — | Nov 15, 2023 | Mar 3, 2027 | 206 days remaining | Active |
| Java 21 | — | Nov 17, 2023 | Aug 31, 2029 | 1118 days remaining | Active |
| Python 3.12 | — | Dec 14, 2023 | Jan 10, 2029 | 885 days remaining | Active |
| .NET 8 | — | Feb 22, 2024 | Mar 3, 2027 | 206 days remaining | Active |
| Ruby 3.3 | — | Apr 4, 2024 | May 31, 2027 | 295 days remaining | Active |
| Python 3.13 | — | Nov 14, 2024 | Aug 31, 2029 | 1118 days remaining | Active |
| Node.js 22 | — | Nov 22, 2024 | Jul 1, 2027 | 326 days remaining | Active |
| .NET 9 (container only) | — | Dec 9, 2024 | TBD | Supported | Active |
| Ruby 3.4 | — | Mar 27, 2025 | May 31, 2028 | 661 days remaining | Active |
| Java 25 | — | Nov 14, 2025 | Aug 31, 2029 | 1118 days remaining | Active |
| Python 3.14 | — | Nov 18, 2025 | Aug 31, 2029 | 1118 days remaining | Active |
| Node.js 24 | — | Nov 25, 2025 | Jul 1, 2028 | 692 days remaining | Active |
| .NET 10 | — | Jan 8, 2026 | Jan 15, 2029 | 890 days remaining | Active |
| Ruby 4.0 | — | Apr 30, 2026 | May 31, 2029 | 1026 days remaining | Active |
| Java 8 (AL2023) | — | Jul 31, 2026 | TBD | Supported | Active |
| Java 11 (AL2023) | — | Jul 31, 2026 | TBD | Supported | Active |
| Java 17 (AL2023) | — | Jul 31, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/aws-lambda)
What does AWS Lambda end of life mean for your organization?
When a version of AWS Lambda reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL AWS Lambda should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when AWS Lambda reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL AWS Lambda versions. This is a bridge, not a permanent solution — plan your migration in parallel.
AWS Lambda has 16 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for AWS Lambda exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.