AWS Disaster Recovery

JANUARY 20, 2021

It utilizes PHZs with overlapping namespaces and cross-account multi-region VPC association for PHZs to create an efficient, scalable, and highly available architecture for DNS. This architecture pattern follows the option of the “Multi-Account Decentralized” model as described in the whitepaper Hybrid Cloud DNS options for Amazon VPC.

Architecture 68

Architecture Failover High Availability Application 68

AWS Disaster Recovery

APRIL 26, 2021

By using the best practices provided in the AWS Well-Architected Reliability Pillar whitepaper to design your DR strategy, your workloads can remain available despite disaster events such as natural disasters, technical failures, or human actions. Every AWS Region consists of multiple Availability Zones (AZs).

Disaster Recovery 75

Disaster Recovery Architecture Backup Failover 75

AWS Disaster Recovery

JANUARY 25, 2022

The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. The AWS Identity and Access Management (IAM) data plane is highly available in each Region, so you can authorize the creation of new resources as long as you’ve already defined the roles.

Disaster Recovery 78

Disaster Recovery Failover Outage Application 78

AWS Disaster Recovery

JUNE 23, 2021

Each Region hosts a highly available, multi- Availability Zone (AZ) workload stack. Figure 2 shows Amazon Route 53 , a highly available and scalable cloud Domain Name System (DNS) , used for routing. Disaster recovery options in the cloud whitepaper. Only two Regions are shown, which is common, but more may be used.

Activation 63

Activation Disaster Recovery Architecture Failover 63

AWS Disaster Recovery

APRIL 27, 2021

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

Architecture 74

Architecture Resilience Application Backup 74