Amazon Msk End of Life Dates
other
Developers working with distributed systems and real-time data processing rely on a robust and scalable solution to manage their messaging queues. Amazon MSK is a managed service that simplifies the deployment, management, and scaling of Apache Kafka clusters in the cloud. Created to address the complexities of building and maintaining Kafka clusters, Amazon MSK is maintained by Amazon Web Services, providing a secure and reliable platform for developers to focus on building their applications. With its ability to handle high-throughput and provide low-latency performance, developers use Amazon MSK to power their real-time analytics, IoT data processing, and machine learning workloads.
The end-of-life landscape for Amazon MSK consists of 18 versions, with 13 already reaching their end-of-life dates. Currently, there are 5 active versions, with the latest stable version being 3.8.x. As the versions progress, the next one to expire is version 3.7, which will reach its end-of-life on 2026-09-01. This is a significant milestone, as it will no longer receive security updates or support after this date. The most recent version to reach its end-of-life was 3.6, which occurred on 2026-06-01. Understanding these timelines is crucial for developers to plan their upgrades and migrations, ensuring their applications remain secure and supported.
Given the current security posture of Amazon MSK, there are no reported Common Vulnerabilities and Exposures, resulting in zero critical CVEs. As a result, there is no most affected version, and the Known Exploited Vulnerabilities catalog does not apply. Despite the lack of known vulnerabilities, developers should remain vigilant and proactive in maintaining their Amazon MSK deployments. This includes regularly reviewing the supported versions, planning upgrades to the latest stable version, and monitoring the official Amazon MSK documentation for any security advisories or updates. By doing so, developers can ensure their applications remain secure, compliant, and continue to operate without interruptions.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 4.2 | Jul 15, 2026 | — | No | — | 4.2.x | — | Active | |
| 4.1 | Oct 15, 2025 | — | No | — | 4.1.x | — | Active | |
| 4.0 | May 16, 2025 | — | No | — | 4.0.x | — | Active | |
| 3.9 | Apr 21, 2025 | — | No | — | 3.9.x | — | Active | |
| 3.8 | Feb 20, 2025 | — | No | — | 3.8.x | — | Active | |
| 3.7 | May 29, 2024 | — | Sep 1, 2026 | in 39d | 3.7.x | — | EOL soon | |
| 3.6 | Nov 16, 2023 | — | Jun 1, 2026 | 53d ago | 3.6.0 | — | EOL | |
| 3.5 | Sep 26, 2023 | — | Oct 23, 2025 | 274d ago | 3.5.1 | — | EOL | |
| 3.4 | May 4, 2023 | — | Aug 4, 2025 | 354d ago | 3.4.0 | — | EOL | |
| 3.3 | Oct 26, 2022 | — | Sep 11, 2024 | 681d ago | 3.3.2 | — | EOL | |
| 3.2 | Jun 22, 2022 | — | Sep 11, 2024 | 681d ago | 3.2.0 | — | EOL | |
| 3.1 | Jun 22, 2022 | — | Sep 11, 2024 | 681d ago | 3.1.1 | — | EOL | |
| 2.8 | May 19, 2021 | — | Jan 14, 2025 | 556d ago | 2.8.2-tiered | — | EOL | |
| 2.7 | Dec 29, 2020 | — | Sep 11, 2024 | 681d ago | 2.7.2 | — | EOL | |
| 2.6 | Oct 21, 2020 | — | Sep 11, 2024 | 681d ago | 2.6.3 | — | EOL | |
| 2.5 | Sep 30, 2020 | — | Jun 8, 2024 | 776d ago | 2.5.1 | — | EOL | |
| 2.4 | Dec 19, 2019 | — | Jun 8, 2024 | 776d ago | 2.4.1.1 | — | EOL | |
| 2.3 | Dec 19, 2019 | — | Jun 8, 2024 | 776d ago | 2.3.1 | — | EOL | |
| 2.2 | Jul 31, 2019 | — | Jun 8, 2024 | 776d ago | 2.2.1 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
