How do I upgrade my Aurora MySQL-Compatible and Aurora PostgreSQL-Compatible global databases?

Resolution

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.

You can perform either a minor or a major version upgrade to the Amazon Aurora clusters in your global database configuration.

Minor version upgrade

Automatic minor version upgrades don't apply to Aurora MySQL-Compatible and Aurora PostgreSQL-Compatible clusters that are part of a global database.

Aurora MySQL-Compatible

When you try to perform an in-place upgrade on your secondary cluster, you might receive the following error message:

"In-place minor version upgrade of Aurora MySQL global database cluster 'cluster-name' to Aurora MySQL engine version 8.0.mysql_aurora.3.0x.x isn't supported. The selected target version 8.0.mysql_aurora.3.0x.x supports a higher version of community MySQL that introduces changes incompatible with previous minor versions of Aurora MySQL. See the Aurora documentation for how to perform a minor version upgrade on global database clusters."

For minor version upgrades, you must upgrade all secondary clusters before you upgrade the primary cluster. However, for some Aurora MySQL-Compatible versions, you must delete the secondary cluster and then upgrade the primary cluster. After you upgrade the primary cluster, you can rebuild the secondary cluster on the new version. To upgrade your Aurora MySQL-Compatible global cluster engine version, you must modify the DB cluster.

For a minor upgrade to Aurora MySQL-Compatible version 2.12.*, 3.04.*, or later, remove all secondary Regions from the global cluster. Upgrade the engine version of the primary Region to one of the Aurora MySQL-Compatible versions. Then, add secondary Regions to the global cluster.

For more information, see Upgrading the minor version or patch level of an Aurora MySQL DB cluster.

Aurora PostgreSQL-Compatible

When you create a new Aurora PostgreSQL-Compatible global cluster, automatic minor upgrades don't occur. You must manually upgrade all the secondary clusters, and then upgrade the primary cluster.

You might experience brief outages during the upgrade because the zero-downtime patching feature isn't available for global clusters. For more information, see How to perform minor version upgrades and apply patches.

Major version upgrade

Aurora MySQL-Compatible

A major version upgrade of an Amazon Aurora global database updates the global database cluster instead of the individual clusters that it contains.

Note: After you upgrade the global database, you can't reverse the upgrade.

To perform a major version upgrade for an Amazon Aurora MySQL-Compatible global database, see In-place major upgrades for global databases. Make sure that you select the global cluster and not one of the individual clusters. When you select the global cluster, all your clusters upgrade at the same time. If you use the Amazon RDS console to perform the upgrade, then choose the item with a Global database role. If you use the AWS CLI, then run the modify-global-cluster command instead of the modify-db-cluster.

For more information about major upgrades for Aurora MySQL, see How the Aurora MySQL in-place major version upgrade works.

To troubleshoot issues with your upgrade, see Troubleshooting for Aurora MySQL in-place upgrade.

Aurora PostgreSQL-Compatible

When you perform a major upgrade on an Aurora PostgreSQL cluster, it's a best practice to test your applications on the upgraded version.

Before you perform the upgrade, you must reset a recovery point object (RPO) for the rds.global_db_rpo parameter for the cluster. Then, upgrade your Aurora PostgreSQL global database.

Related information

Using Amazon Aurora Global Database

Upgrade to Amazon Aurora MySQL version 3 (with MySQL 8.0 compatibility)

Make the most of your upgrade to Amazon Aurora MySQL version 3 | The Data Dive on AWS OnAir S01 on the YouTube website