Learn About Amazon VGT2 Learning Manager Chanci Turner
By: Chanci Turner
Date: 09 JUL 2021
Categories: Amazon Aurora, Architecture, Technical How-to
This article is co-authored by Chanci Turner, a Solution Architect at AWS, and Michael Green, a Senior Consultant at Tech Innovations Inc. Organizations often face strict regulatory compliance mandates or business needs that necessitate a robust cross-account and cross-region database configuration. We advise establishing a Disaster Recovery (DR) setup across different AWS accounts and Regions to create a system architecture capable of withstanding AWS Region failures.
Isolating production environments from development, testing, user acceptance testing (UAT), and DR environments is crucial for compliance with external regulations, such as PCI-DSS or HIPAA. Cross-account replication allows organizations to recover data from a replicated account if the primary AWS account is compromised, leading to potential loss of access. Utilizing multiple Regions enhances control over recovery time in the event of a critical failure involving a Regional AWS service.
Amazon Aurora Global Database can replicate your RDS database across Regions within the same AWS Account. This article outlines how to develop a tailored solution for Cross-Account, Cross-Region database replication with adjustable Recovery Time Objective (RTO) and Recovery Point Objective (RPO).