Amazon RDS for MySQL End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Amazon RDS for MySQL versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.6 | 5.6 | Jul 1, 2013 | Mar 1, 2022 | 1575 days past EOL | EOL |
| 5.7 | 5.7.44 | Feb 22, 2016 | Feb 29, 2024 | 845 days past EOL | EOL |
| 8.0 | 8.0.46 | Oct 23, 2018 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.0.40 | 8.0.40 | Oct 15, 2024 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.4.3 | 8.4.3 | Oct 15, 2024 | Jul 31, 2029 | 1134 days remaining | Active |
| 8.4 | 8.4.9 | Nov 21, 2024 | Jul 31, 2029 | 1134 days remaining | Active |
| 8.0.41 | 8.0.41 | Jan 21, 2025 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.4.4 | 8.4.4 | Jan 21, 2025 | Jul 31, 2029 | 1134 days remaining | Active |
| 8.0.42 | 8.0.42 | Apr 15, 2025 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.4.5 | 8.4.5 | Apr 15, 2025 | Jul 31, 2029 | 1134 days remaining | Active |
| 8.0.43 | 8.0.43 | Jul 22, 2025 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.4.6 | 8.4.6 | Jul 22, 2025 | Jul 31, 2029 | 1134 days remaining | Active |
| 8.0.44 | 8.0.44 | Oct 21, 2025 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.4.7 | 8.4.7 | Oct 21, 2025 | Jul 31, 2029 | 1134 days remaining | Active |
| 8.0.45 | 8.0.45 | Jan 20, 2026 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.4.8 | 8.4.8 | Jan 20, 2026 | Jul 31, 2029 | 1134 days remaining | Active |
| 8.0.46 | 8.0.46 | Apr 21, 2026 | Jul 31, 2026 | 38 days remaining | Warning |
| 8.4.9 | 8.4.9 | Apr 21, 2026 | Jul 31, 2029 | 1134 days remaining | Active |
What does Amazon RDS for MySQL end of life mean for your organization?
When a version of Amazon RDS for MySQL 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 RDS for MySQL 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 RDS for MySQL 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 →