Complete end-of-life dates, support windows, and security status for all Amazon Linux versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2010.11 | 2010.11 | Dec 1, 2010 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2011.09 | 2011.09 | Sep 26, 2011 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2012.03 | 2012.03 | Mar 28, 2012 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2012.09 | 2012.09 | Oct 11, 2012 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2013.03 | 2013.03 | Mar 27, 2013 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2013.09 | 2013.09 | Sep 30, 2013 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2014.03 | 2014.03 | Mar 27, 2014 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2014.09 | 2014.09 | Sep 23, 2014 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2015.03 | 2015.03 | Mar 24, 2015 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2015.09 | 2015.09 | Sep 22, 2015 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2016.03 | 2016.03 | Mar 22, 2016 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2016.09 | 2016.09.1.20161221 | Nov 16, 2016 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2017.03 | 2017.03.1.20170812 | Apr 7, 2017 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2017.09 | 2017.09.1.20180409 | Nov 3, 2017 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2018.03 | 2018.03.0.20231218.0 | Apr 25, 2018 | Dec 31, 2023 | 860 days past EOL | EOL |
| 2 | 2.0.20260504.0 | Jun 26, 2018 | Jun 30, 2026 | 52 days remaining | Warning |
| 2023 | 2023.11.20260505.0 | Mar 1, 2023 | Jun 30, 2029 | 1148 days remaining | Active |
When a Amazon Linux version 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 Amazon Linux 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →