← ← Back to all products
AWS Lambda
Active
Cloud & Platforms Latest Version: ruby4.0 Latest Release: N/A
AWS Lambda is a serverless compute service that runs code in response to events and manages computing resources.
Versions
49
Latest Version
ruby4.0
Active Support
20
EOL
16
Lifecycle Timeline
Today ↓
ruby4.0
ruby4.0
dotnet10
dotnet10
nodejs24.x
nodejs24.x
python3.14
python3.14
java25
java25
ruby3.4
ruby3.4
dotnet9
dotnet9
nodejs22.x
nodejs22.x
python3.13
python3.13
ruby3.3
ruby3.3
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| ruby4.0 | Apr 30, 2026 | Mar 31, 2029 | May 31, 2029 | ruby4.0 | No | Active |
| dotnet10 | Jan 8, 2026 | Nov 14, 2028 | Jan 15, 2029 | dotnet10 | No | Active |
| nodejs24.x | Nov 25, 2025 | Apr 30, 2028 | Jul 1, 2028 | nodejs24.x | No | Active |
| python3.14 | Nov 18, 2025 | Jun 30, 2029 | Aug 31, 2029 | python3.14 | No | Active |
| java25 | Nov 14, 2025 | Jun 30, 2029 | Aug 31, 2029 | java25 | No | Active |
| ruby3.4 | Mar 27, 2025 | Mar 31, 2028 | May 31, 2028 | ruby3.4 | No | Active |
| dotnet9 | Dec 9, 2024 | Nov 10, 2026 | No | dotnet9 | No | Active |
| nodejs22.x | Nov 22, 2024 | Apr 30, 2027 | Jul 1, 2027 | nodejs22.x | No | Active |
| python3.13 | Nov 14, 2024 | Jun 30, 2029 | Aug 31, 2029 | python3.13 | No | Active |
| ruby3.3 | Apr 4, 2024 | Mar 31, 2027 | May 31, 2027 | ruby3.3 | No | Active |
| dotnet8 | Feb 22, 2024 | Nov 10, 2026 | Mar 3, 2027 | dotnet8 | No | Active |
| python3.12 | Dec 14, 2023 | Oct 31, 2028 | Jan 10, 2029 | python3.12 | No | Active |
| java21 | Nov 17, 2023 | Jun 30, 2029 | Aug 31, 2029 | java21 | No | Active |
| nodejs20.x | Nov 15, 2023 | Apr 30, 2026 | Mar 3, 2027 | nodejs20.x | No | Security |
| provided.al2023 | Nov 10, 2023 | Jun 30, 2029 | Aug 31, 2029 | provided.al2023 | No | Active |
| python3.11 | Jul 27, 2023 | Jun 30, 2027 | Aug 31, 2027 | python3.11 | No | Active |
| ruby3.2 | Jun 7, 2023 | Mar 31, 2026 | Mar 3, 2027 | ruby3.2 | No | Security |
| java17 | Apr 27, 2023 | Jun 30, 2027 | Aug 31, 2027 | java17 | No | Active |
| python3.10 | Apr 18, 2023 | Oct 31, 2026 | Mar 3, 2027 | python3.10 | No | Active |
| nodejs18.x | Nov 18, 2022 | Sep 1, 2025 | Mar 3, 2027 | nodejs18.x | No | Security |
| dotnet7 | Nov 15, 2022 | May 14, 2024 | Yes | dotnet7 | No | EOL |
| nodejs16.x | May 12, 2022 | Jun 12, 2024 | Mar 3, 2027 | nodejs16.x | No | Security |
| dotnet6 | Feb 24, 2022 | Dec 20, 2024 | Mar 3, 2027 | dotnet6 | No | Security |
| python3.9 | Aug 16, 2021 | Dec 15, 2025 | Mar 3, 2027 | python3.9 | No | Security |
| nodejs14.x | Feb 3, 2021 | Dec 4, 2023 | Mar 3, 2027 | nodejs14.x | No | Security |
| dotnet5.0 | Dec 2, 2020 | May 10, 2022 | Yes | dotnet5.0 | No | EOL |
| java8.al2 | Aug 12, 2020 | Jun 30, 2027 | Aug 31, 2027 | java8.al2 | No | Active |
| provided.al2 | Aug 12, 2020 | Jul 31, 2026 | Mar 3, 2027 | provided.al2 | No | Active |
| dotnetcore3.1 | Mar 31, 2020 | Apr 3, 2023 | May 3, 2023 | dotnetcore3.1 | No | EOL |
| ruby2.7 | Feb 19, 2020 | Dec 7, 2023 | Mar 3, 2027 | ruby2.7 | No | Security |
| nodejs12.x | Nov 18, 2019 | Mar 31, 2023 | Apr 30, 2023 | nodejs12.x | No | EOL |
| python3.8 | Nov 18, 2019 | Oct 14, 2024 | Mar 3, 2027 | python3.8 | No | Security |
| java11 | Nov 18, 2019 | Jun 30, 2027 | Aug 31, 2027 | java11 | No | Active |
| nodejs10.x | May 15, 2019 | Jul 30, 2021 | Feb 14, 2022 | nodejs10.x | No | EOL |
| ruby2.5 | Nov 29, 2018 | Jul 30, 2021 | Mar 31, 2022 | ruby2.5 | No | EOL |
| provided | Nov 29, 2018 | Jan 8, 2024 | Mar 3, 2027 | provided | No | Security |
| python3.7 | Nov 19, 2018 | Dec 4, 2023 | Mar 3, 2027 | python3.7 | No | Security |
| dotnetcore2.1 | Jul 9, 2018 | Jan 5, 2022 | Apr 13, 2022 | dotnetcore2.1 | No | EOL |
| nodejs8.10 | Apr 2, 2018 | Mar 6, 2020 | Mar 6, 2020 | nodejs8.10 | No | EOL |
| dotnetcore2.0 | Jan 15, 2018 | May 30, 2019 | May 30, 2019 | dotnetcore2.0 | No | EOL |
| go1.x | Jan 15, 2018 | Jan 8, 2024 | Mar 3, 2027 | go1.x | No | Security |
| nodejs4.3-edge | Jul 17, 2017 | Mar 5, 2020 | Apr 30, 2020 | nodejs4.3-edge | No | EOL |
| python3.6 | Apr 18, 2017 | Jul 18, 2022 | Aug 29, 2022 | python3.6 | No | EOL |
| nodejs6.10 | Mar 22, 2017 | Aug 12, 2019 | Aug 12, 2019 | nodejs6.10 | No | EOL |
| dotnetcore1.0 | Dec 1, 2016 | Jun 27, 2019 | Jul 30, 2019 | dotnetcore1.0 | No | EOL |
| nodejs4.3 | Apr 7, 2016 | Mar 5, 2020 | Mar 5, 2020 | nodejs4.3 | No | EOL |
| python2.7 | Oct 8, 2015 | Jul 15, 2021 | May 30, 2022 | python2.7 | No | EOL |
| java8 | Jun 15, 2015 | Jan 8, 2024 | Mar 3, 2027 | java8 | No | Security |
| nodejs | Nov 13, 2014 | Aug 30, 2016 | Oct 31, 2016 | nodejs | No | EOL |
Frequently Asked Questions
Which versions of AWS Lambda have reached end of life?
The following AWS Lambda versions have reached end of life and no longer receive security updates: dotnet7, dotnet5.0, dotnetcore3.1, nodejs12.x, nodejs10.x, ruby2.5, dotnetcore2.1, nodejs8.10 (and 8 more). It is recommended to upgrade to a supported version.
Is it safe to continue using AWS Lambda dotnet7?
AWS Lambda dotnet7 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of AWS Lambda?
The latest version of AWS Lambda is ruby4.0, released in the ruby4.0 release cycle.
How many versions of AWS Lambda are currently supported?
AWS Lambda currently has 33 actively supported version(s): ruby4.0, dotnet10, nodejs24.x, python3.14, java25, ruby3.4, dotnet9, nodejs22.x, python3.13, ruby3.3, dotnet8, python3.12, java21, nodejs20.x, provided.al2023, python3.11, ruby3.2, java17, python3.10, nodejs18.x, nodejs16.x, dotnet6, python3.9, nodejs14.x, java8.al2, provided.al2, ruby2.7, python3.8, java11, provided, python3.7, go1.x, java8.
When does AWS Lambda ruby4.0 reach end of life?
AWS Lambda ruby4.0 is scheduled to reach end of life on May 31, 2029.
What should I do when AWS Lambda reaches end of life?
When a AWS Lambda version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.