AWS Disaster Recovery
JUNE 23, 2021
My subsequent posts shared details on the backup and restore , pilot light, and warm standby active/passive strategies. 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.
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. DR strategies: Choosing backup and restore. Implementing backup and restore.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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). Earlier, we were able to restore from the backup but wanted to improve availability further. Related information.
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.
AWS Disaster Recovery
JANUARY 25, 2022
The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. In the simplest case, we’ve deployed an application in a primary Region and a backup Region. First, Route 53, our DNS service, has to be available.
Expert insights. Personalized for you.
63 
Let's personalize your content