---
slug: "aws-aurora-mysql-version-8-4-end-of-support"
title: "Amazon Aurora MySQL: version 8.4 end of standard support"
summary: "Aurora end of standard support date for Amazon Aurora MySQL version 8.4: Apr 2032. AWS states that a major version can keep running past this date under RDS Extended Support, for a fee."
cloud: "aws"
service: "Amazon Aurora MySQL"
service_slug: "aurora-mysql"
category: "database"
type: "end_of_support"
announced_date: null
effective_date: "2032-04-01"
effective_precision: "month"
replacement: null
affected_versions: ["8.4"]
source_url: "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html"
extra_source_urls: ["https://endoflife.date/amazon-aurora-mysql"]
vendor_ref: "amazon-aurora-mysql@8.4"
last_checked_at: "2026-11-12T09:55:40.805Z"
created_at: "2026-11-13T13:36:44.208Z"
updated_at: "2026-11-13T13:36:44.208Z"
url: "https://eolwatch.dev/items/aws-aurora-mysql-version-8-4-end-of-support"
short_url: "https://eolwatch.dev/i/e4"
markdown_url: "https://eolwatch.dev/items/aws-aurora-mysql-version-8-4-end-of-support.md"
json_url: "https://eolwatch.dev/items/aws-aurora-mysql-version-8-4-end-of-support.json"
---

# Amazon Aurora MySQL: version 8.4 end of standard support

Aurora end of standard support date for Amazon Aurora MySQL version 8.4: Apr 2032. AWS states that a major version can keep running past this date under RDS Extended Support, for a fee.

- Effective date: Apr 2032 (month precision: the vendor gives no day)
- Cloud: [AWS](https://eolwatch.dev/cloud/aws.md)
- Service: [Amazon Aurora MySQL](https://eolwatch.dev/services/aws/aurora-mysql.md)
- Type: End of support
- Category: [Database](https://eolwatch.dev/categories/databases.md)
- Affected versions: 8.4
- Replacement: Not stated by vendor
- Announced: Not stated by vendor
- Official source: [docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html)
- Last checked: 12 Nov 2026

## What breaks

AWS states that a major version can keep running past its standard support end date under RDS Extended Support, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html). The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html#AuroraMySQL.release-calendars.major) lists Extended Support dates and eligible minor versions; some are "To be determined".

- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.
- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.
- Charges apply only to certain minor versions.
- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.

## Who is affected

### Affected versions

- `8.4`

### Matching resource types

- `aws_rds_cluster`

### Fields the check reads

- `engine`
- `engine_version_actual`
- `engine_version`

### Detected by the estate check from

- Terraform state or plan (JSON)

## What to do

1. Look up your type and version of cluster in [Aurora MySQL major version upgrade paths](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Compatibility). The table says whether the cluster can use the in-place upgrade mechanism and which action applies.
2. Where the table points to a major version upgrade, plan it with [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). A major version upgrade needs more planning and testing than a minor version upgrade.
3. Before an in-place upgrade, create a clone of the original cluster, perform an in-place upgrade of the clone immediately after creating it, and test application compatibility, performance and administration procedures on it.
4. When the test cluster works properly, perform the in-place upgrade for the production cluster. See [How to perform an in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Upgrading.Procedure.html).
5. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).

## Replacement

Not stated by vendor.

## Sources

- [Official source](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html) (docs.aws.amazon.com, Official)
- [Additional source](https://endoflife.date/amazon-aurora-mysql) (endoflife.date, Via endoflife.date)

Last checked against the first source in this list on 12 Nov 2026.

Page: https://eolwatch.dev/items/aws-aurora-mysql-version-8-4-end-of-support | JSON: https://eolwatch.dev/items/aws-aurora-mysql-version-8-4-end-of-support.json

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published.