Amazon Eks End of Life Dates
other
Developers rely on Amazon Eks to manage containerized applications, and this platform has been a cornerstone of cloud-based development since its introduction. Maintained by Amazon, Amazon Eks provides a scalable and secure way to deploy and manage applications. The need for a reliable and up-to-date tracking system for Amazon Eks end-of-life dates has become increasingly important, given the ever-evolving landscape of cloud computing and the potential security risks associated with outdated software. With 19 total versions, the complexity of managing and upgrading Amazon Eks can be daunting, which is why tracking supported versions and security patch timelines is crucial for developers.
The end-of-life landscape for Amazon Eks is characterized by a significant number of versions that are no longer supported, with 15 versions having reached their end-of-life. Currently, only 4 versions remain active, with the latest stable version being 1.36-eks-3. Notably, version 1.33 is next in line to expire, with its end-of-life date set for 2026-07-29. This means that developers who are still using this version must plan their upgrades accordingly to avoid potential security risks and disruptions to their applications. The most recent version to reach end-of-life was 1.32, which expired on 2026-03-23, highlighting the importance of staying up-to-date with the latest versions and security patches.
Given the potential security risks associated with outdated software, it is essential for developers to stay informed about the security picture for Amazon Eks. Fortunately, there are currently no known CVEs or critical CVEs affecting Amazon Eks, which is a testament to the platform's robust security. As a result, there is no most affected version, and no action is required to address specific security vulnerabilities. However, developers should still prioritize upgrading to the latest stable version to ensure they have access to the latest security patches and features, and to avoid potential issues when older versions eventually reach their end-of-life.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.37 | Oct 1, 2026 | — | Dec 1, 2027 | in 404d | 1.37-eks-4 | — | Active | |
| 1.36 | Jun 2, 2026 | — | Aug 2, 2027 | in 283d | 1.36-eks-13 | — | Active | |
| 1.35 | Jan 28, 2026 | — | Mar 27, 2027 | in 155d | 1.35-eks-23 | — | Active | |
| 1.34 | Oct 6, 2025 | — | Dec 2, 2026 | in 40d | 1.34-eks-33 | — | EOL soon | |
| 1.33 | May 28, 2025 | — | Jul 29, 2026 | 86d ago | 1.33-eks-47 | — | EOL | |
| 1.32 | Jan 25, 2025 | — | Mar 23, 2026 | 214d ago | 1.32-eks-54 | — | EOL | |
| 1.31 | Sep 26, 2024 | — | Nov 26, 2025 | 331d ago | 1.31-eks-70 | — | EOL | |
| 1.30 | May 23, 2024 | — | Jul 23, 2025 | 457d ago | 1.30-eks-76 | — | EOL | |
| 1.29 | Jan 23, 2024 | — | Mar 23, 2025 | 579d ago | 1.29-eks-66 | — | EOL | |
| 1.28 | Sep 26, 2023 | — | Nov 26, 2024 | 696d ago | 1.28-eks-63 | — | EOL | |
| 1.27 | May 24, 2023 | — | Jul 24, 2024 | 821d ago | 1.27-eks-53 | — | EOL | |
| 1.26 | Apr 11, 2023 | — | Jun 11, 2024 | 864d ago | 1.26-eks-51 | — | EOL | |
| 1.25 | Feb 21, 2023 | — | May 1, 2024 | 905d ago | 1.25-eks-48 | — | EOL | |
| 1.24 | Nov 15, 2022 | — | Jan 31, 2024 | 996d ago | 1.24-eks-45 | — | EOL | |
| 1.23 | Aug 11, 2022 | — | Oct 11, 2023 | 1108d ago | 1.23-eks-30 | — | EOL | |
| 1.22 | Apr 4, 2022 | — | Jun 4, 2023 | 1237d ago | 1.22-eks-14 | — | EOL | |
| 1.21 | Jul 19, 2021 | — | Feb 16, 2023 | 1345d ago | 1.21-eks-18 | — | EOL | |
| 1.20 | May 18, 2021 | — | Nov 1, 2022 | 1452d ago | 1.20-eks-14 | — | EOL | |
| 1.19 | Feb 16, 2021 | — | Aug 1, 2022 | 1544d ago | 1.19-eks-11 | — | EOL | |
| 1.18 | Oct 13, 2020 | — | Aug 15, 2022 | 1530d ago | 1.18-eks-13 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
