AWS Lambda Custom Runtime (AL2) End of Life Date
AWS Lambda Custom Runtime (AL2) end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
AWS Lambda provided.al2 was released on August 12, 2020 and support is scheduled to end on March 3, 2027 — a planned supported lifespan of 6 years and 7 months, longer than the 3 years and 10 months median for AWS Lambda releases.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| Node.js 0.10 | — | Oct 31, 2016 | EOL |
| Java 8 (AL1) | — | Mar 3, 2027 | Warning |
| Python 2.7 | — | May 30, 2022 | EOL |
| Node.js 4.3 | — | Mar 5, 2020 | EOL |
| .NET Core 1.0 | — | Jul 30, 2019 | EOL |
| Node.js 6.10 | — | Aug 12, 2019 | EOL |
| Python 3.6 | — | Aug 29, 2022 | EOL |
| Node.js 4.3 edge | — | Apr 30, 2019 | EOL |
What does AWS Lambda Custom Runtime (AL2) end of life mean?
When AWS Lambda Custom Runtime (AL2) 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 Custom Runtime (AL2) past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to AWS Lambda Java 17 (AL2023) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.