Remove Account Manager Remove Disaster Recovery Remove Failover Remove High Availability
article thumbnail

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

AWS Disaster Recovery

Welcome to the third post of a multi-part series that addresses disaster recovery (DR) strategies with the use of AWS-managed services to align with customer requirements of performance, cost, and compliance. You would just need to create the records and specify failover for the routing policy.

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

article thumbnail

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

AWS Disaster Recovery

Minimum business continuity for failover. Building disaster recovery (DR) strategies into your system requires you to work backwards from recovery point objective (RPO) and recovery time objective (RTO) requirements. Earlier, we were able to restore from the backup but wanted to improve availability further.