Amazon MSK End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Amazon MSK versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.2 | 2.2.1 | Jul 31, 2019 | Jun 8, 2024 | 745 days past EOL | EOL |
| 2.3 | 2.3.1 | Dec 19, 2019 | Jun 8, 2024 | 745 days past EOL | EOL |
| 2.4 | 2.4.1.1 | Dec 19, 2019 | Jun 8, 2024 | 745 days past EOL | EOL |
| 2.5 | 2.5.1 | Sep 30, 2020 | Jun 8, 2024 | 745 days past EOL | EOL |
| 2.6 | 2.6.3 | Oct 21, 2020 | Sep 11, 2024 | 650 days past EOL | EOL |
| 2.7 | 2.7.2 | Dec 29, 2020 | Sep 11, 2024 | 650 days past EOL | EOL |
| 2.8 | 2.8.2-tiered | May 19, 2021 | Jan 14, 2025 | 525 days past EOL | EOL |
| 3.1 | 3.1.1 | Jun 22, 2022 | Sep 11, 2024 | 650 days past EOL | EOL |
| 3.2 | 3.2.0 | Jun 22, 2022 | Sep 11, 2024 | 650 days past EOL | EOL |
| 3.3 | 3.3.2 | Oct 26, 2022 | Sep 11, 2024 | 650 days past EOL | EOL |
| 3.4 | 3.4.0 | May 4, 2023 | Aug 4, 2025 | 323 days past EOL | EOL |
| 3.5 | 3.5.1 | Sep 26, 2023 | Oct 23, 2025 | 243 days past EOL | EOL |
| 3.6 | 3.6.0 | Nov 16, 2023 | Jun 1, 2026 | 22 days past EOL | EOL |
| 3.7 | 3.7.x | May 29, 2024 | Sep 1, 2026 | 70 days remaining | Warning |
| 3.8 | 3.8.x | Feb 20, 2025 | TBD | Supported | Active |
| 3.9 | 3.9.x | Apr 21, 2025 | TBD | Supported | Active |
| 4.0 | 4.0.x | May 16, 2025 | TBD | Supported | Active |
| 4.1 | 4.1.x | Oct 15, 2025 | TBD | Supported | Active |
What does Amazon MSK end of life mean for your organization?
When a version of Amazon MSK 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 MSK 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Amazon MSK versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →