Red Hat Ansible Automation Platform End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Red Hat Ansible Automation Platform versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
Red Hat Ansible Automation Platform 2.7 is supported until June 2, 2029, its end-of-support date. Active support for Red Hat Ansible Automation Platform 2.7 ends on June 2, 2027; security fixes continue until that end-of-life date. The next Red Hat Ansible Automation Platform version to reach end of life is 2.5, on October 2, 2027. 2 of 5 tracked Red Hat Ansible Automation Platform versions are past end of life; the most recent to reach it, 2.4, did so on June 30, 2026. The full Red Hat Ansible Automation Platform 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 | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 2.3 | — | Nov 29, 2022 | May 31, 2024 | — | 890 days past EOL | EOL |
| 2.4 | — | Jun 27, 2023 | Jun 30, 2026 | Jun 30, 2028 Extended support |
130 days past EOL | EOL |
| 2.5 | — | Sep 30, 2024 | Oct 2, 2027 | — | 329 days remaining | Active |
| 2.6 | — | Oct 1, 2025 | Oct 1, 2028 | — | 694 days remaining | Active |
| 2.7 | — | Jun 2, 2026 | Jun 2, 2029 | — | 938 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/red-hat-ansible-automation-platform)
Red Hat Ansible Automation Platform lifecycle status — the real story
Red Hat supports each Ansible Automation Platform release in three production phases: Full Support, then Maintenance Support 1 (Critical and Important security fixes, Critical bug fixes only), then Maintenance Support 2 (Critical security fixes only, no bug fixes). The paid Extended Life-cycle Support add-on and, for 2.4, purchased Extended Update Support can run beyond that.
On this site the active support date is the end of Full Support and the end of life date is the end of Maintenance Support 2, the last phase in which Red Hat ships fixes under a standard subscription. The extended support column shows a purchased extension only where Red Hat lists one for that release.
Verified against the vendor's lifecycle documentation on October 17, 2026.
Red Hat Ansible Automation Platform release and support pattern
Across the 5 release lines with a published release date, Red Hat Ansible Automation Platform has shipped a new line roughly every 10 months (median interval). A line typically stays in standard support for about 3 years from its release to its standard-support end date.
Of the 5 release lines tracked, 2 are past end of life and 3 are still within support. The newest line, 2.7, was released June 2, 2026. The next scheduled end of life is 2.5 on October 2, 2027 — 328 days from this build. The longest-supported line currently published is 2.7, to June 2, 2029. Upstream also publishes an extended-support phase for 1 line, shown in the table above.
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 Red Hat Ansible Automation Platform end of life mean for your organization?
When a version of Red Hat Ansible Automation Platform 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 Red Hat Ansible Automation Platform 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 Red Hat Ansible Automation Platform 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 Red Hat Ansible Automation Platform version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Red Hat Ansible Automation Platform has 2 versions past end of life — standard security patches have stopped; 1 of them is still covered by Extended support, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Red Hat Ansible Automation Platform 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."