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 reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
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.
✓ Alerts are on — confirmation is in your inbox.
Automating this check?
GET https://api.endoflife.ai/v1/score/amazon-aurora-mysql/3 returns this version's end-of-life date, its source and the EOL Risk Score as JSON.
Get a free API key (150 requests a day, no expiry).
EOL Date
Apr 30, 2028
525 days remaining
Latest Release
3.14
Standard release
Release Date
Nov 23, 2021
Amazon Aurora MySQL 3 (MySQL 8.0) series
Extended Support
Jul 31, 2029
Extended support
Where these dates come from
End of lifeApr 30, 2028endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of extended supportJul 31, 2029endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseNov 23, 2021endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
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.14, published October 26, 2026.
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
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 except under Extended support, until Jul 31, 2029. 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Amazon Aurora MySQL 3 (MySQL 8.0) past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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) reaches end of life on April 30, 2028. That is 525 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 except under Extended support, until Jul 31, 2029. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Amazon Aurora MySQL should migrate immediately or implement compensating controls.