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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| nodejs | — | Nov 13, 2014 | Oct 31, 2016 | 3540 days past EOL | EOL |
| java8 | — | Jun 15, 2015 | Mar 3, 2027 | 235 days remaining | Active |
| python2.7 | — | Oct 8, 2015 | May 30, 2022 | 1503 days past EOL | EOL |
| nodejs4.3 | — | Apr 7, 2016 | Mar 5, 2020 | 2319 days past EOL | EOL |
| dotnetcore1.0 | — | Dec 1, 2016 | Jul 30, 2019 | 2538 days past EOL | EOL |
| nodejs6.10 | — | Mar 22, 2017 | Aug 12, 2019 | 2525 days past EOL | EOL |
| python3.6 | — | Apr 18, 2017 | Aug 29, 2022 | 1412 days past EOL | EOL |
| nodejs4.3-edge | — | Jul 17, 2017 | Apr 30, 2020 | 2263 days past EOL | EOL |
| go1.x | — | Jan 15, 2018 | Mar 3, 2027 | 235 days remaining | Active |
| dotnetcore2.0 | — | Jan 15, 2018 | May 30, 2019 | 2599 days past EOL | EOL |
| nodejs8.10 | — | Apr 2, 2018 | Mar 6, 2020 | 2318 days past EOL | EOL |
| dotnetcore2.1 | — | Jul 9, 2018 | Apr 13, 2022 | 1550 days past EOL | EOL |
| python3.7 | — | Nov 19, 2018 | Mar 3, 2027 | 235 days remaining | Active |
| provided | — | Nov 29, 2018 | Mar 3, 2027 | 235 days remaining | Active |
| ruby2.5 | — | Nov 29, 2018 | Mar 31, 2022 | 1563 days past EOL | EOL |
| nodejs10.x | — | May 15, 2019 | Feb 14, 2022 | 1608 days past EOL | EOL |
| java11 | — | Nov 18, 2019 | Aug 31, 2027 | 416 days remaining | Active |
| python3.8 | — | Nov 18, 2019 | Mar 3, 2027 | 235 days remaining | Active |
| nodejs12.x | — | Nov 18, 2019 | Apr 30, 2023 | 1168 days past EOL | EOL |
| ruby2.7 | — | Feb 19, 2020 | Mar 3, 2027 | 235 days remaining | Active |
| dotnetcore3.1 | — | Mar 31, 2020 | May 3, 2023 | 1165 days past EOL | EOL |
| provided.al2 | — | Aug 12, 2020 | Mar 3, 2027 | 235 days remaining | Active |
| java8.al2 | — | Aug 12, 2020 | Aug 31, 2027 | 416 days remaining | Active |
| dotnet5.0 | — | Dec 2, 2020 | No EOL date | Supported | Active |
| nodejs14.x | — | Feb 3, 2021 | Mar 3, 2027 | 235 days remaining | Active |
| python3.9 | — | Aug 16, 2021 | Mar 3, 2027 | 235 days remaining | Active |
| dotnet6 | — | Feb 24, 2022 | Mar 3, 2027 | 235 days remaining | Active |
| nodejs16.x | — | May 12, 2022 | Mar 3, 2027 | 235 days remaining | Active |
| dotnet7 | — | Nov 15, 2022 | No EOL date | Supported | Active |
| nodejs18.x | — | Nov 18, 2022 | Mar 3, 2027 | 235 days remaining | Active |
| python3.10 | — | Apr 18, 2023 | Mar 3, 2027 | 235 days remaining | Active |
| java17 | — | Apr 27, 2023 | Aug 31, 2027 | 416 days remaining | Active |
| ruby3.2 | — | Jun 7, 2023 | Mar 3, 2027 | 235 days remaining | Active |
| python3.11 | — | Jul 27, 2023 | Aug 31, 2027 | 416 days remaining | Active |
| provided.al2023 | — | Nov 10, 2023 | Aug 31, 2029 | 1147 days remaining | Active |
| nodejs20.x | — | Nov 15, 2023 | Mar 3, 2027 | 235 days remaining | Active |
| java21 | — | Nov 17, 2023 | Aug 31, 2029 | 1147 days remaining | Active |
| python3.12 | — | Dec 14, 2023 | Jan 10, 2029 | 914 days remaining | Active |
| dotnet8 | — | Feb 22, 2024 | Mar 3, 2027 | 235 days remaining | Active |
| ruby3.3 | — | Apr 4, 2024 | May 31, 2027 | 324 days remaining | Active |
| python3.13 | — | Nov 14, 2024 | Aug 31, 2029 | 1147 days remaining | Active |
| nodejs22.x | — | Nov 22, 2024 | Jul 1, 2027 | 355 days remaining | Active |
| dotnet9 | — | Dec 9, 2024 | TBD | Supported | Active |
| ruby3.4 | — | Mar 27, 2025 | May 31, 2028 | 690 days remaining | Active |
| java25 | — | Nov 14, 2025 | Aug 31, 2029 | 1147 days remaining | Active |
| python3.14 | — | Nov 18, 2025 | Aug 31, 2029 | 1147 days remaining | Active |
| nodejs24.x | — | Nov 25, 2025 | Jul 1, 2028 | 721 days remaining | Active |
| dotnet10 | — | Jan 8, 2026 | Jan 15, 2029 | 919 days remaining | Active |
| ruby4.0 | — | Apr 30, 2026 | May 31, 2029 | 1055 days remaining | Active |
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.
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 14 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →