EOLCanaryEOLCanary
← Explore

Aws Lambda End of Life Dates

other

Developers rely on Aws Lambda to build scalable and secure serverless applications, and the platform has been a cornerstone of cloud development since its introduction. Created to simplify the process of deploying code without provisioning or managing servers, Aws Lambda has become a crucial tool for many organizations. The platform is actively maintained by Amazon, with a strong focus on security and performance. By tracking the end-of-life dates of Aws Lambda, developers can ensure their applications remain secure and up-to-date, avoiding potential vulnerabilities that can arise from using unsupported versions.

With a total of 49 versions released, Aws Lambda has a complex landscape of supported and unsupported releases. Currently, 16 versions have reached their end-of-life, while 33 remain active and supported. The next version to expire is dotnet6, which will reach its end-of-life on 2027-03-03, giving developers ample time to plan their upgrades. The most recent version to reach end-of-life was dotnetcore3.1, which expired on 2023-05-03. By staying on top of these end-of-life dates, developers can ensure a smooth transition to newer versions and avoid potential security risks.

The security picture for Aws Lambda is currently very positive, with a total of 0 CVEs tracked and 0 critical vulnerabilities. This indicates that the platform is highly secure, and developers can have confidence in its ability to protect their applications. Since there are no known vulnerabilities, there is no most affected version, and no action is required to address specific security concerns. However, it is still essential for developers to stay up-to-date with the latest versions and security patches to ensure their applications remain secure and compliant with industry standards. By tracking the end-of-life dates and security timelines for Aws Lambda, developers can ensure their applications remain secure and performant.

Last updated: Sep 7, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
java8.al2023 Jul 31, 2026Jun 30, 2029Aug 31, 2029in 1088d——Active
java11.al2023 Jul 31, 2026Jun 30, 2029Aug 31, 2029in 1088d——Active
java17.al2023 Jul 31, 2026Jun 30, 2029Aug 31, 2029in 1088d——Active
ruby4.0 Apr 30, 2026Mar 31, 2029May 31, 2029in 996d——Active
dotnet10 Jan 8, 2026Nov 14, 2028Jan 15, 2029in 860d——Active
nodejs24.x Nov 25, 2025Apr 30, 2028Jul 1, 2028in 662d——Active
python3.14 Nov 18, 2025Jun 30, 2029Aug 31, 2029in 1088d——Active
java25 Nov 14, 2025Jun 30, 2029Aug 31, 2029in 1088d——Active
ruby3.4 Mar 27, 2025Mar 31, 2028May 31, 2028in 631d——Active
dotnet9 Dec 9, 2024Nov 10, 2026No———Active
nodejs22.x Nov 22, 2024Apr 30, 2027Jul 1, 2027in 296d——Active
python3.13 Nov 14, 2024Jun 30, 2029Aug 31, 2029in 1088d——Active
ruby3.3 Apr 4, 2024Mar 31, 2027May 31, 2027in 265d——Active
dotnet8 Feb 22, 2024Nov 10, 2026Mar 3, 2027in 176d——Active
python3.12 Dec 14, 2023Oct 31, 2028Jan 10, 2029in 855d——Active
java21 Nov 17, 2023Jun 30, 2029Aug 31, 2029in 1088d——Active
nodejs20.x Nov 15, 2023Apr 30, 2026Mar 3, 2027in 176d——Active
provided.al2023 Nov 10, 2023Jun 30, 2029Aug 31, 2029in 1088d——Active
python3.11 Jul 27, 2023Jun 30, 2027Aug 31, 2027in 357d——Active
ruby3.2 Jun 7, 2023Mar 31, 2026Mar 3, 2027in 176d——Active
java17 Apr 27, 2023Jun 30, 2027Aug 31, 2027in 357d——Active
python3.10 Apr 18, 2023Oct 31, 2026Mar 3, 2027in 176d——Active
nodejs18.x Nov 18, 2022Sep 1, 2025Mar 3, 2027in 176d——Active
dotnet7 Nov 15, 2022May 14, 2024Yes———EOL
nodejs16.x May 12, 2022Jun 12, 2024Mar 3, 2027in 176d——Active
dotnet6 Feb 24, 2022Dec 20, 2024Mar 3, 2027in 176d——Active
python3.9 Aug 16, 2021Dec 15, 2025Mar 3, 2027in 176d——Active
nodejs14.x Feb 3, 2021Dec 4, 2023Mar 3, 2027in 176d——Active
dotnet5.0 Dec 2, 2020May 10, 2022Yes———EOL
java8.al2 Aug 12, 2020Jun 30, 2027Aug 31, 2027in 357d——Active
provided.al2 Aug 12, 2020Jul 31, 2026Mar 3, 2027in 176d——Active
dotnetcore3.1 Mar 31, 2020Apr 3, 2023May 3, 20231224d ago——EOL
ruby2.7 Feb 19, 2020Dec 7, 2023Mar 3, 2027in 176d——Active
java11 Nov 18, 2019Jun 30, 2027Aug 31, 2027in 357d——Active
nodejs12.x Nov 18, 2019Mar 31, 2023Apr 30, 20231227d ago——EOL
python3.8 Nov 18, 2019Oct 14, 2024Mar 3, 2027in 176d——Active
nodejs10.x May 15, 2019Jul 30, 2021Feb 14, 20221667d ago——EOL
ruby2.5 Nov 29, 2018Jul 30, 2021Mar 31, 20221622d ago——EOL
provided Nov 29, 2018Jan 8, 2024Mar 3, 2027in 176d——Active
python3.7 Nov 19, 2018Dec 4, 2023Mar 3, 2027in 176d——Active
dotnetcore2.1 Jul 9, 2018Jan 5, 2022Apr 13, 20221609d ago——EOL
nodejs8.10 Apr 2, 2018Mar 6, 2020Mar 6, 20202377d ago——EOL
dotnetcore2.0 Jan 15, 2018May 30, 2019May 30, 20192658d ago——EOL
go1.x Jan 15, 2018Jan 8, 2024Mar 3, 2027in 176d——Active
nodejs4.3-edge Jul 17, 2017Mar 5, 2020Apr 30, 20202322d ago——EOL
python3.6 Apr 18, 2017Jul 18, 2022Aug 29, 20221471d ago——EOL
nodejs6.10 Mar 22, 2017Aug 12, 2019Aug 12, 20192584d ago——EOL
dotnetcore1.0 Dec 1, 2016Jun 27, 2019Jul 30, 20192597d ago——EOL
nodejs4.3 Apr 7, 2016Mar 5, 2020Mar 5, 20202378d ago——EOL
python2.7 Oct 8, 2015Jul 15, 2021May 30, 20221562d ago——EOL
java8 Jun 15, 2015Jan 8, 2024Mar 3, 2027in 176d——Active
nodejs Nov 13, 2014Aug 30, 2016Oct 31, 20163599d ago——EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions