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

4 minute read

I want to upgrade my Amazon Aurora MySQL-Compatible Edition and my Amazon Aurora PostgreSQL-Compatible Edition 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

Aurora MySQL-Compatible

Note: For minor version upgrades, you must upgrade all secondary clusters before you upgrade the primary cluster. For some Aurora MySQL versions, you must delete the secondary cluster and upgrade the primary cluster by itself. After that's completed, you can rebuild the secondary cluster on the new version.

If this error occurs, then you receive the following error when you try to perform the in-place upgrade on your secondary cluster:

"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."

To upgrade your Aurora MySQL global cluster, use either the AWS CLI or Amazon Relational Database (Amazon RDS) console to modify the engine version.

For a minor upgrade to Aurora MySQL version 2.12.0 or 3.03.0 or later, see the Note in Upgrading Aurora MySQL by modifying the engine version.

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 cluster, the Enable minor version upgrade option is turned on by default so clusters automatically get minor upgrades. 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.

To perform a major version upgrade for an Amazon Aurora MySQL global database, see Upgrading an Amazon Aurora global database. Make sure to select the global cluster and not one of the individual clusters. When you select the global cluster, all your clusters are upgraded 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 command.

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

Note: The upgrade is permanent and can't be reversed.

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, confirm that you set a recovery point object (RPO) for the rds.global_db_rpo parameter for the cluster. This parameter is turned off by default, but to perform a major upgrade you must turn it on.

After you meet all of the preceding prerequisites, upgrade your Aurora PostgreSQL global cluster.