article thumbnail

Using Route 53 Private Hosted Zones for Cross-account Multi-region Architectures

AWS Disaster Recovery

This post was co-written by Anandprasanna Gaitonde, AWS Solutions Architect and John Bickle, Senior Technical Account Manager, AWS Enterprise Support. Many AWS customers have internal business applications spread over multiple AWS accounts and on-premises to support different business units. Introduction. Architecture Overview.

article thumbnail

Disaster Recovery Solutions with AWS-Managed Services, Part 3: Multi-Site Active/Passive

AWS Disaster Recovery

Warm standby with managed services Let’s cover each of the components of this application, as well as how managed services behave in a multisite environment. You would just need to create the records and specify failover for the routing policy. In case of failover, the data plane scales up to meet the workload requirements.

article thumbnail

Journey to Adopt Cloud-Native Architecture Series: #3 – Improved Resilience and Standardized Observability

AWS Disaster Recovery

Minimum business continuity for failover. Our business needs in this scenario required us to build high availability to prevent 30 minutes of continuous downtime (RTO) and prevent persistent user data loss (that is, a few minutes RPO). Centralized cross-account management with Cross-Region copy using AWS Backup.