Announcement: Amazon Aurora MySQL 2.x end of standard support is on October 31, 2024

On October 31, 2024, Amazon Aurora MySQL 2.x (compatible with MySQL 5.7.* ) will reach the end of standard support. We recommend that you proactively test and upgrade your databases running Amazon Aurora MySQL major version 2.x to default version of Amazon Aurora MySQL 3 (compatible with MySQL 8.0) or higher at your convenience before October 31, 2024. Refer to Amazon Aurora Versioning Policy [1]

Starting on or after October 31, 2024, if you do not upgrade your database running Aurora MySQL 2.x to a newer default version or higher on Amazon Aurora MySQL 3.x, we will enroll your Amazon Aurora MySQL 2.x databases into RDS Extended Support. RDS Extended Support supports Amazon Aurora MySQL versions 2.11.x and 2.12.x and charges will start on December 1, 2024 regardless of what 2.x version your database is running. You do not have to use the AWS console or APIs to opt-in to Amazon RDS Extended Support manually and you can continue to run 2.11.x or 2.12.x. databases on RDS Extended Support for up to three years (i.e. February 28, 2027). Extended Support charges will continue until you upgrade to a newer major version.

Please be aware of the following timeline:

• October 31, 2024: Amazon Aurora MySQL 2.x will reach the end of standard support
• October 31, 2024: Amazon Aurora automatically enrolls Aurora MySQL 2.x clusters in RDS Extended Support, which ONLY supports 2.11, 2.12 minor versions. To use Amazon Aurora MySQL 2.x past the end of standard support, you should plan to run your databases on one of these minor versions before October 31, 2024.
• December 1, 2024: Amazon Aurora automatically charges you for RDS Extended Support.
• February 28, 2027: End of RDS Extended Support for Aurora MySQL 2.x.

How to Determine Which Instances are Running Aurora MySQL 2.x? To find clusters affected by this end of standard support process, use the following procedures:

• Sign in to the AWS Management Console and open the AWS Health Dashboard console at https://health.console.aws.amazon.com/health/home#/account/dashboard/open-issues
• In the navigation pane, choose Open and recent issues.
• Choose Scheduled Changes tab
• In Event tab, choose RDS planned lifecycle event with the Start time of October 31, 2024. Each region which has Aurora MySQL 2.x running will have a separate Health event.
• Choose Affected resources tab

You can also find affected cluster/s using RDS Console, AWS CLI and AWS API [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57.EOL.html#find-cluster].

Upgrading to a New Major Version Upgrading from Aurora MySQL v2 to v3 requires extensive functional and performance testing and planning. We want you to look at the upgrade as a three-step process, with activities before the upgrade, during the upgrade, and after the upgrade. Please refer to our public documentation [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57.EOL.html#Aurora-Performing-an-Upgrade] to understand more about upgrade best practices, checklists, methods, testing, and troubleshooting. To avoid any unplanned unavailability outside your maintenance window, we recommend that you first take a snapshot [3] or a fast database clone [4] of your database and test the upgrade to get an estimate of the duration. To learn more about upgrading Aurora MySQL major versions, review the Upgrading Database Versions page [5] and [6].

Availability of RDS Extended Support: Amazon RDS Extended Support [7] allows you to continue to use Aurora MySQL major versions after the community end-of-life. During this time, AWS provides fixes for critical security issues and bugs through patch releases, giving you more time, up to February 28, 2027, to upgrade to a new major version to help you meet your business requirements. For provisioned instances on Amazon Aurora, Amazon RDS Extended Support is priced per vCPU per hour [8].

How to estimate RDS Extended Support charges? To estimate the charges for Amazon RDS Extended Support, you can use the AWS Pricing Calculator [https://calculator.aws/#/createCalculator/AuroraMySQL] and follow this blog [https://aws.amazon.com/blogs/aws-cloud-financial-management/estimating-the-charges-for-amazon-rds-extended-support/]. The additional charges for RDS Extended Support automatically stops when you take one of the following actions. Refer to our public documentation [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html] for more details. .

• Upgrade your cluster/s to Aurora MySQL 3 (compatible with MySQL 8.0)
• Delete or stop the database Aurora MySQL 2 (compatible with MySQL 5.7)

For information on creating or restoring Aurora MySQL 2.x clusters after the end of standard support (October 31, 2024), please refer to the following documentation:

• https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-creating-db-instance.html
• https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-creating-db-instance.html

If you have any questions or concerns, the AWS Support Team is available on AWS re:Post and via Premium Support [9]

[1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.html

[2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/accessing-monitoring.html

[3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html

[4] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Clone.html

[5] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html

[6] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57.EOL.html#Aurora-Performing-an-Upgrade

[7] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support.html

[8] https://aws.amazon.com/rds/aurora/pricing/#Amazon_RDS_Extended_Support_costs

[9] https://aws.amazon.com/support