Streams for Apache Kafka (Red Hat AMQ Streams) End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Streams for Apache Kafka (Red Hat AMQ Streams) versions. Dates read at the vendor's own lifecycle pages (access.redhat.com). Updated at every deploy.
Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 is supported until November 30, 2027, its end-of-support date. Active support for Streams for Apache Kafka (Red Hat AMQ Streams) 3.2 ends on May 31, 2027. The next Streams for Apache Kafka (Red Hat AMQ Streams) version to reach end of life is 2.9, on October 31, 2026. 3 of 5 tracked Streams for Apache Kafka (Red Hat AMQ Streams) versions are past end of life; the most recent to reach it, 3.1, did so on May 4, 2026. The full Streams for Apache Kafka (Red Hat AMQ Streams) lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.9 | — | — | Oct 31, 2026 | 12 days remaining | Warning |
| 1.8 | — | — | Jan 31, 2022 | 1722 days past EOL | EOL |
| 3.2 | — | May 4, 2026 | Nov 30, 2027 | 407 days remaining | Active |
| 3.1 | — | Dec 16, 2025 | May 4, 2026 | 168 days past EOL | EOL |
| 3.0 | — | Jul 31, 2025 | Dec 16, 2025 | 307 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/redhat-amq-streams)
Streams for Apache Kafka (Red Hat AMQ Streams) lifecycle status — the real story
Streams for Apache Kafka (formerly Red Hat AMQ Streams) is Red Hat's supported Kafka distribution for OpenShift and RHEL. Red Hat gives long-term lines (2.9 for 2.x, 3.2 for 3.x) Full and Maintenance support; the other minors get Full support only until the next minor ships. No Extended Life Cycle Support is offered. The 2.9 row carries the 2.x family's first release date, so no release date is shown for it.
Streams for Apache Kafka (Red Hat AMQ Streams) release and support pattern
Across the 3 release lines with a published release date, Streams for Apache Kafka (Red Hat AMQ Streams) has shipped a new line roughly every 5 months (median interval). A line typically stays supported for about 5 months from its release to its end-of-life date (measured on the 3 lines with both dates published).
Of the 5 release lines tracked, 3 are past end of life and 2 are still within support. The newest line, 3.0, was released July 31, 2025. The next scheduled end of life is 2.9 on October 31, 2026 — 11 days from this build. The longest-supported line currently published is 3.2, to November 30, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Streams for Apache Kafka (Red Hat AMQ Streams) end of life mean for your organization?
When a version of Streams for Apache Kafka (Red Hat AMQ Streams) 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Streams for Apache Kafka (Red Hat AMQ Streams) 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.
Your options when Streams for Apache Kafka (Red Hat AMQ Streams) reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Streams for Apache Kafka (Red Hat AMQ Streams) version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Streams for Apache Kafka (Red Hat AMQ Streams) has 3 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Streams for Apache Kafka (Red Hat AMQ Streams) is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."