AWS Lambda provided End of Life Date
AWS Lambda provided end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
| Version | Latest | EOL Date | Status |
|---|---|---|---|
| nodejs | — | Oct 31, 2016 | EOL |
| java8 | — | Mar 3, 2027 | Active |
| python2.7 | — | May 30, 2022 | EOL |
| nodejs4.3 | — | Mar 5, 2020 | EOL |
| dotnetcore1.0 | — | Jul 30, 2019 | EOL |
| nodejs6.10 | — | Aug 12, 2019 | EOL |
| python3.6 | — | Aug 29, 2022 | EOL |
| nodejs4.3-edge | — | Apr 30, 2020 | EOL |
What does AWS Lambda provided end of life mean?
When AWS Lambda provided reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running AWS Lambda provided past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to AWS Lambda ruby4.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.