Amazon Aurora Mysql 3 (MySQL 8.0) · Version Status

Amazon Aurora Mysql 3 (MySQL 8.0) End of Life Date

Amazon Aurora Mysql 3 (MySQL 8.0) end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Amazon Aurora Mysql 3 (MySQL 8.0) is actively supported. EOL date: April 30, 2028.
📅 Get reminded before Amazon Aurora Mysql 3 (MySQL 8.0) reaches EOL on April 30, 2028 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Apr 30, 2028
616 days remaining
Latest Release
3.12
Standard release
Release Date
Nov 23, 2021
Amazon Aurora Mysql 3 (MySQL 8.0) series
Extended Support
Jul 31, 2029
Extended support
Lifecycle detail

Amazon Aurora Mysql 3 was released on November 23, 2021 and support is scheduled to end on April 30, 2028 — a planned supported lifespan of 6 years and 5 months, in line with the 6 years and 9 months median for Amazon Aurora Mysql releases. Its most recent patch is 3.12, published February 17, 2026.

← Amazon Aurora Mysql 2 (MySQL 5.7) All Amazon Aurora Mysql versions Amazon Aurora Mysql 8.4 →
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Amazon Aurora Mysql Versions
VersionLatestEOL DateStatus
1 (MySQL 5.6) 1.23.4 Feb 28, 2023 EOL
2 (MySQL 5.7) 2.12 Oct 31, 2024 EOL
3 (MySQL 8.0) 3.12 Apr 30, 2028 Active
8.4 8.4.7 Apr 30, 2032 Active

What does Amazon Aurora Mysql 3 (MySQL 8.0) end of life mean?

When Amazon Aurora Mysql 3 (MySQL 8.0) reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Amazon Aurora Mysql 3 (MySQL 8.0) past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Amazon Aurora Mysql 8.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Amazon Aurora Mysql 3 (MySQL 8.0) reach end of life?
Amazon Aurora Mysql 3 (MySQL 8.0) reached end of life on April 30, 2028. That is 616 days remaining.
Is Amazon Aurora Mysql 3 (MySQL 8.0) still supported?
Yes, Amazon Aurora Mysql 3 (MySQL 8.0) is currently supported. The EOL date is April 30, 2028.
What should I upgrade to from Amazon Aurora Mysql 3 (MySQL 8.0)?
The recommended upgrade from Amazon Aurora Mysql 3 (MySQL 8.0) is Amazon Aurora Mysql 8.4 — the latest actively supported version. Check the Amazon Aurora Mysql full timeline for all supported versions.
What are the security risks of running Amazon Aurora Mysql 3 (MySQL 8.0) past EOL?
When Amazon Aurora Mysql 3 (MySQL 8.0) reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Amazon Aurora Mysql should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →