Complete end-of-life dates, support windows, and security status for all Amazon Eks versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.18 | 1.18-eks-13 | Oct 13, 2020 | Aug 15, 2022 | 1363 days past EOL | EOL |
| 1.19 | 1.19-eks-11 | Feb 16, 2021 | Aug 1, 2022 | 1377 days past EOL | EOL |
| 1.20 | 1.20-eks-14 | May 18, 2021 | Nov 1, 2022 | 1285 days past EOL | EOL |
| 1.21 | 1.21-eks-18 | Jul 19, 2021 | Feb 16, 2023 | 1178 days past EOL | EOL |
| 1.22 | 1.22-eks-14 | Apr 4, 2022 | Jun 4, 2023 | 1070 days past EOL | EOL |
| 1.23 | 1.23-eks-30 | Aug 11, 2022 | Oct 11, 2023 | 941 days past EOL | EOL |
| 1.24 | 1.24-eks-45 | Nov 15, 2022 | Jan 31, 2024 | 829 days past EOL | EOL |
| 1.25 | 1.25-eks-48 | Feb 21, 2023 | May 1, 2024 | 738 days past EOL | EOL |
| 1.26 | 1.26-eks-51 | Apr 11, 2023 | Jun 11, 2024 | 697 days past EOL | EOL |
| 1.27 | 1.27-eks-53 | May 24, 2023 | Jul 24, 2024 | 654 days past EOL | EOL |
| 1.28 | 1.28-eks-63 | Sep 26, 2023 | Nov 26, 2024 | 529 days past EOL | EOL |
| 1.29 | 1.29-eks-66 | Jan 23, 2024 | Mar 23, 2025 | 412 days past EOL | EOL |
| 1.30 | 1.30-eks-64 | May 23, 2024 | Jul 23, 2025 | 290 days past EOL | EOL |
| 1.31 | 1.31-eks-56 | Sep 26, 2024 | Nov 26, 2025 | 164 days past EOL | EOL |
| 1.32 | 1.32-eks-40 | Jan 25, 2025 | Mar 23, 2026 | 47 days past EOL | EOL |
| 1.33 | 1.33-eks-33 | May 28, 2025 | Jul 29, 2026 | 81 days remaining | Warning |
| 1.34 | 1.34-eks-19 | Oct 6, 2025 | Dec 2, 2026 | 207 days remaining | Active |
| 1.35 | 1.35-eks-9 | Jan 28, 2026 | Mar 27, 2027 | 322 days remaining | Active |
When a Amazon Eks 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 Eks 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 →