1.1 End-Of-Life (EOL) Notice

December 23rd, 2025

ACHE effectively has an EOL that corresponds with the upstream release. In this case, CentOS 8.3 which reaches EOL at the end of December 2025.

Always check the release notes for superseded EOL dates. Mitigating circumstances at the time of release may indicate a longer or shorter EOL than the underlying base release.

1.1.1 Implications of Running ACHE Beyond EOL

AC do not follow common practice or recommendations by other vendors to constantly update the base release. Security considerations should be mitigated as required by the system administrator but based on real world threats in the specific use-case rather than blind adherence to published CVE1s.

AC take a different view of risk based primarily on real threats. A primary source of failure and downtime is unintended impact from changes to base releases and frequent poorly tested updates.

For these reasons, running ACHE for legacy applications well beyond EOL carries no specific warning or counter-recommendation. In fact, it may be preferable from a business continuity perspective to run a specific deployment well beyond EOL.

Users should, of course, be wary of the end of any support license they may have had with the upstream vendor such as RedHat. In addition, consideration should also be given to the impact on security audits.

The AC approach to resiliency and security may not meet audit requirements that have a high security "tick box" focus on addressing CVEs regardless of real exposure. Users can meet such requirements by applying updates from the base release until the EOL period.