Amazon Aurora Global Database is designed for globally distributed applications, allowing a single Amazon Aurora database to span multiple AWS regions. It replicates your data with no impact on database performance, enables fast local reads with low latency in each region, and provides disaster recovery from region-wide outages. In disaster recovery situations, you can promote a secondary region to take full read-write responsibilities in under a minute.

With an Aurora global database, there are two different approaches to failover depending on the scenario.

Manual unplanned failover (“detach and promote”) – To recover from an unplanned outage or to do disaster recovery (DR) testing, perform a cross-Region failover to one of the secondaries in your Aurora global database. The RTO for this manual process depends on how quickly you can perform the tasks listed in Recovering an Amazon Aurora global database from an unplanned outage. The RPO is typically measured in seconds, but this depends on the Aurora storage replication lag across the network at the time of the failure.

Managed planned failover – This feature is intended for controlled environments, such as operational maintenance and other planned operational procedures. By using managed planned failover, you can relocate the primary DB cluster of your Aurora global database to one of the secondary Regions. Because this feature synchronizes secondary DB clusters with the primary before making any other changes, RPO is 0 (no data loss). To learn more, see Performing managed planned failovers for Amazon Aurora global databases.

Managed planned failover, is showcased in Module 3: Warm Standby.

For this workshop we will be doing a Managed Unplanned Failover.

Promote Aurora secondary database

1.1 Click RDS to navigate to the dashboard in the N. California (us-west-1) region.

1.2 Look at the hot-global Global database. Notice how we have hot-primary a Primary cluster in us-east-1 which has our Writer instance and hot-secondary a Secondary cluster in us-west-1 which has our Reader instance.

1.3 Select hot-secondary instance and click Actions. Next click the Remove from global database option to promote the instance to a standalone database.

1.4 Click Remove and Promote to confirm the database promotion.

You will need to wait for the database to be successfully promoted before moving on to the next step. This can take several minutes.

1.5 Notice the changes. Hot-secondary has been removed from the Global database and is now a Regional cluster with its own Writer instance. You may need to click the Refresh button to see the changes.