Preparing for Amazon Aurora MySQL-Compatible Edition version 2 end of standard support - Amazon Aurora
End of standard support timelineFinding clusters affected by this end-of-life processAmazon RDS Extended SupportPerforming an upgradeUpgrade path for Aurora Serverless v1 DB clusters
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Preparing for Amazon Aurora MySQL-Compatible Edition version 2 end of standard support

Amazon Aurora MySQL-Compatible Edition version 2 (with MySQL 5.7 compatibility) is planned to reach the end of standard support on October 31, 2024. We recommend that you upgrade all clusters running Aurora MySQL version 2 to the default Aurora MySQL version 3 (with MySQL 8.0 compatibility) or higher before Aurora MySQL version 2 reaches the end of its standard support period. On October 31, 2024, Amazon RDS will automatically enroll your databases into Amazon RDS Extended Support. If you're running Amazon Aurora MySQL version 2 (with MySQL 5.7 compatibility) in an Aurora Serverless version 1 cluster, this doesn't apply to you. If you want to upgrade your Aurora Serverless version 1 clusters to Aurora MySQL version 3, see Upgrade path for Aurora Serverless v1 DB clusters.

You can find upcoming end-of-support dates for Aurora major versions in Amazon Aurora versions.

If you have clusters running Aurora MySQL version 2, you will receive periodic notices with the latest information about how to conduct an upgrade as we get closer to the end of standard support date. We will update this page periodically with the latest information.

End of standard support timeline

  1. Now through October 31, 2024 – You can upgrade clusters from Aurora MySQL version 2 (with MySQL 5.7 compatibility) to Aurora MySQL version 3 (with MySQL 8.0 compatibility).

  2. October 31, 2024 – On this date, Aurora MySQL version 2 will reach the end of standard support and Amazon RDS automatically enrolls your clusters into Amazon RDS Extended Support.

We will automatically enroll you in RDS Extended Support. For more information, see Using Amazon RDS Extended Support.

Finding clusters affected by this end-of-life process

To find clusters affected by this end-of-life process, use the following procedures.

Important

Be sure to perform these instructions in every Amazon Web Services Region and for each Amazon Web Services account where your resources are located.

To find an Aurora MySQL version 2 cluster

  1. Sign in to the Amazon Web Services Management Console and open the Amazon RDS console at https://console.amazonaws.cn/rds/.

  2. In the navigation pane, choose Databases.

  3. In the Filter by databases box, enter 5.7.

  4. Check for Aurora MySQL in the engine column.

To find clusters affected by this end-of-life process using the Amazon CLI, call the describe-db-clusters command. You can use the sample script following.

aws rds describe-db-clusters --include-share --query 'DBClusters[?(Engine==`aurora-mysql` && contains(EngineVersion,`5.7.mysql_aurora`))].{EngineVersion:EngineVersion, DBClusterIdentifier:DBClusterIdentifier, EngineMode:EngineMode}' --output table --region us-east-1     
        
        +---------------------------------------------------------------+
        |                      DescribeDBClusters                       |
        +---------------------+---------------+-------------------------+
        |         DBCI        |      EM       |          EV             |
        +---------------------+---------------+-------------------------+
        |    aurora-mysql2    |  provisioned  | 5.7.mysql_aurora.2.11.3 |
        | aurora-serverlessv1 |   serverless  | 5.7.mysql_aurora.2.11.3 |
        +---------------------+---------------+-------------------------+

To find Aurora MySQL DB clusters running Aurora MySQL version 2, use the RDS DescribeDBClusters API operation with the following required parameters:

  • DescribeDBClusters

    • Filters.Filter.N

      • Name

        • engine

      • Values.Value.N

        • ['aurora']

Amazon RDS Extended Support

You can use Amazon RDS Extended Support over community MySQL 5.7 at no charge until the end of support date, October 31, 2024. On October 31, 2024, Amazon RDS automatically enrolls your databases into RDS Extended Support for Aurora MySQL version 2. RDS Extended Support for Aurora is a paid service that provides up to 28 additional months of support for Aurora MySQL version 2 until the end of RDS Extended Support in February 2027. RDS Extended Support will only be offered for Aurora MySQL minor versions 2.11 and 2.12. To use Amazon Aurora MySQL version 2 past the end of standard support, plan to run your databases on one of these minor versions before October 31, 2024.

For more information about RDS Extended Support, such as charges and other considerations, see Using Amazon RDS Extended Support.

Performing an upgrade

Upgrading between major versions requires more extensive planning and testing than for a minor version. The process can take substantial time. We want to look at the upgrade as a three-step process, with activities before the upgrade, for the upgrade, and after the upgrade.

Before the upgrade:

Before the upgrade, we recommend that you check for application compatibility, performance, maintenance procedures, and similar considerations for the upgraded cluster, thereby confirming that post-upgrade your applications will work as expected. Here are five recommendations that will help provide you a better upgrade experience.

If you have any questions or concerns, the Amazon Support Team is available on the community forums and Premium Support.

Doing the upgrade:

You can use one of the following upgrade techniques. The amount of downtime your system will experience depends on the technique chosen.

  • Blue/Green Deployments – For situations where the top priority is to reduce application downtime, you can use Amazon RDS Blue/Green Deployments for performing the major version upgrade in provisioned Amazon Aurora DB clusters. A blue/green deployment creates a staging environment that copies the production environment. You can make certain changes to the Aurora DB cluster in the green (staging) environment without affecting production workloads. The switchover typically takes under a minute with no data loss. For more information, see Overview of Amazon RDS Blue/Green Deployments for Aurora. This minimizes downtime, but requires you to run additional resources while performing the upgrade.

  • In-place upgrades – You can perform an in-place upgrade where Aurora automatically performs a precheck process for you, takes the cluster offline, backs up your cluster, performs the upgrade, and puts your cluster back online. An in-place major version upgrade can be performed in a few clicks, and doesn't involve other coordination or failovers with other clusters, but does involve downtime. For more information, see How to perform an in-place upgrade

  • Snapshot restore – You can upgrade your Aurora MySQL version 2 cluster by restoring from an Aurora MySQL version 2 snapshot into an Aurora MySQL version 3 cluster. To do this, you should follow the process for taking a snapshot and restoring from it. This process involves database interruption because you're restoring from a snapshot.

After the upgrade:

After the upgrade, you need to closely monitor your system (application and database) and make fine-tuning changes if necessary. Following the pre-upgrade steps closely will minimize the required changes needed. For more information, see Troubleshooting Amazon Aurora MySQL database performance.

To learn more about the methods, planning, testing, and troubleshooting of Aurora MySQL major version upgrades, be sure to thoroughly read Upgrading the major version of an Amazon Aurora MySQL DB cluster, including Troubleshooting for Aurora MySQL in-place upgrade. Also, note that some instance types aren't supported for Aurora MySQL version 3. For more information, see Aurora DB instance classes.

Upgrade path for Aurora Serverless v1 DB clusters

Upgrading between major versions requires more extensive planning and testing than for a minor version. The process can take substantial time. We want to look at the upgrade as a three-step process, with activities before the upgrade, for the upgrade, and after the upgrade.

Aurora MySQL version 2 (with MySQL 5.7 compatibility) will continue to receive standard support for Aurora Serverless v1 clusters.

If you want to upgrade to Amazon Aurora MySQL 3 (with MySQL 8.0 compatibility) and continue running Aurora Serverless, you can use Amazon Aurora Serverless v2. To understand the differences between Aurora Serverless v1 and Aurora Serverless v2, see Comparison of Aurora Serverless v2 and Aurora Serverless v1.

Upgrade to Aurora Serverless v2: You can upgrade an Aurora Serverless v1 cluster to Aurora Serverless v2. For more information, see Upgrading from an Aurora Serverless v1 cluster to Aurora Serverless v2.