Remove Failover Remove Resilience Remove Whitepaper
article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part I: Strategies for Recovery in the Cloud

AWS Disaster Recovery

As lead solutions architect for the AWS Well-Architected Reliability pillar , I help customers build resilient workloads on AWS. Figure 2 shows the four strategies for DR that are highlighted in the DR whitepaper. All requests are now switched to be routed there in a process called “failover.” Multi-site active/active.

article thumbnail

Minimizing Dependencies in a Disaster Recovery Plan

AWS Disaster Recovery

The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. What if the very tools that we rely on for failover are themselves impacted by a DR event? Failover plan dependencies and considerations. What are the dependencies that we’ve baked into this failover plan?

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

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

AWS Disaster Recovery

In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. Increase resiliency. In the following sections, we show you the steps we took to improve system resiliency for our example company. Conclusion.

article thumbnail

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

AWS Disaster Recovery

This architecture pattern follows the option of the “Multi-Account Decentralized” model as described in the whitepaper Hybrid Cloud DNS options for Amazon VPC. This architecture provides the following benefits: Resilient and scalable. Failover routing policy is set up in the PHZ and failover records are created.