← ← Back to all products
All badges & lifecycle API →
Amazon MSKEnd of Life (EOL) Dates & Support Status
Active
MiddlewareLatest Version: 4.2.xLatest Release: Jul 15, 2026
Amazon Managed Streaming for Apache Kafka (MSK) is a fully managed service for Apache Kafka on AWS.
Support summary
Amazon MSK currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
5
0 lts
Versions
19
Latest Version
4.2.x
Active Support
5
EOL
14
Lifecycle Timeline
Oct 26, 2022As of Sep 27, 2026
4.2Active · Date not announced
4.1Active · Date not announced
4.0Active · Date not announced
3.9Active · Date not announced
3.8Active · Date not announced
3.7EOL · Sep 1, 2026
3.6EOL · Jun 1, 2026
3.5EOL · Oct 23, 2025
3.4EOL · Aug 4, 2025
3.3EOL · Sep 11, 2024
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.2 | Jul 15, 2026 | Maintained | Date not announced | 4.2.x | No | Active |
| 4.1 | Oct 15, 2025 | Maintained | Date not announced | 4.1.x | No | Active |
| 4.0 | May 16, 2025 | Maintained | Date not announced | 4.0.x | No | Active |
| 3.9 | Apr 21, 2025 | Maintained | Date not announced | 3.9.x | No | Active |
| 3.8 | Feb 20, 2025 | Maintained | Date not announced | 3.8.x | No | Active |
| 3.7 | May 29, 2024 | Ended | Sep 1, 2026 | 3.7.x | No | EOL |
| 3.6 | Nov 16, 2023 | Ended | Jun 1, 2026 | 3.6.0 | No | EOL |
| 3.5 | Sep 26, 2023 | Ended | Oct 23, 2025 | 3.5.1 | No | EOL |
| 3.4 | May 4, 2023 | Ended | Aug 4, 2025 | 3.4.0 | No | EOL |
| 3.3 | Oct 26, 2022 | Ended | Sep 11, 2024 | 3.3.2 | No | EOL |
| 3.2 | Jun 22, 2022 | Ended | Sep 11, 2024 | 3.2.0 | No | EOL |
| 3.1 | Jun 22, 2022 | Ended | Sep 11, 2024 | 3.1.1 | No | EOL |
| 2.8 | May 19, 2021 | Ended | Jan 14, 2025 | 2.8.2-tiered | No | EOL |
| 2.7 | Dec 29, 2020 | Ended | Sep 11, 2024 | 2.7.2 | No | EOL |
| 2.6 | Oct 21, 2020 | Ended | Sep 11, 2024 | 2.6.3 | No | EOL |
| 2.5 | Sep 30, 2020 | Ended | Jun 8, 2024 | 2.5.1 | No | EOL |
| 2.4 | Dec 19, 2019 | Ended | Jun 8, 2024 | 2.4.1.1 | No | EOL |
| 2.3 | Dec 19, 2019 | Ended | Jun 8, 2024 | 2.3.1 | No | EOL |
| 2.2 | Jul 31, 2019 | Ended | Jun 8, 2024 | 2.2.1 | No | EOL |
Data sources
Embed this badge
Show Amazon MSK's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/amazon-msk/)HTML
<a href="https://eol.wiki/amazon-msk/"><img src="https://eol.wiki/badge/amazon-msk.svg" alt="Amazon MSK end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Amazon MSK have reached end of life?
The following Amazon MSK versions have reached end of life and no longer receive security updates: 3.7, 3.6, 3.5, 3.4, 3.3, 3.2, 3.1, 2.8 (and 6 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Amazon MSK 3.7?
Amazon MSK 3.7 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Amazon MSK?
The latest version of Amazon MSK is 4.2.x, released in the 4.2 release cycle.
How many versions of Amazon MSK are currently supported?
Amazon MSK currently has 5 actively supported version(s): 4.2, 4.1, 4.0, 3.9, 3.8.
When does Amazon MSK 4.2 reach end of life?
Amazon MSK 4.2 does not have a specific end-of-life date announced yet.
What should I do when Amazon MSK reaches end of life?
When a Amazon MSK version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.