Deploy the solution
After you set up the prerequisites, follow the instructions in the DR Orchestrator Framework pattern. Instructions are included for Amazon RDSAurora, and Amazon ElastiCache. To test the solution, review the prerequisites and limitations, and deploy example databases on AWS.
Prerequisites
-
An active AWS account
to deploy this solution. -
Permissions to create Amazon Simple Storage Service (Amazon S3) buckets and the resources used in the AWS CloudFormation templates.
-
Before you run the
DR Orchestrator FAILBACKstate machine:-
Manually modify the RDS instance or modify the Amazon Aurora DB Cluster, and disable
DeletionProtection. -
Take a DB snapshot before deleting the Amazon RDS instance or Aurora cluster if you plan to perform root cause analysis (RCA).
-
Limitations
-
Feature availability and support vary across specific versions of each database engine and across AWS Regions. For more information on feature and Region availability for cross-Region replication, see Cross-Region read replicas.
-
This solution has been tested using a primary database instance with one read replica. If you want to use more than one read replica, test the solution thoroughly before implementing it in a production environment.
-
For Amazon RDS, the solution supports only the following engines: Amazon RDS for MySQL, Amazon RDS for PostgreSQL, and Amazon RDS for MariaDB.
Deploy example databases on AWS
To demonstrate the cross-Region DR solution for databases on AWS, you can deploy Amazon RDS for MySQL, Amazon Aurora MySQL-Compatible Edition, and Amazon ElastiCache (Redis OSS) - Global Datastore.
Use the instructions in the App-Stack
README file of the aws-cross-region-dr-databasesus-east-1, and the secondary Region is us-west-2.
The application stack uses the AWS CloudFormation Outputs section to export the parameters that are used by DR Orchestrator Framework to automate the failover and failback of AWS databases.
