article thumbnail

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

AWS Disaster Recovery

Figure 2 shows the four strategies for DR that are highlighted in the DR whitepaper. Architecture of the DR strategies. Backup and restore DR architecture. Pilot light DR architecture. Warm standby DR architecture. Multi-site active/active DR architecture. Backup and restore. Pilot light. Warm standby.

article thumbnail

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

AWS Disaster Recovery

Route 53 Private Hosted Zones (PHZs) and Resolver endpoints on AWS create an architecture best practice for centralized DNS in hybrid cloud environment. This blog presents an architecture that provides a unified view of the DNS while allowing different AWS accounts to manage subdomains. Architecture Overview.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part II: Backup and Restore with Rapid Recovery

AWS Disaster Recovery

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. Disaster Recovery (DR) Architecture on AWS, Part I: Strategies for Recovery in the Cloud.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part IV: Multi-site Active/Active

AWS Disaster Recovery

The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. To maintain low latencies and reduce the potential for network error, serve all read and write requests from the local Region of your multi-Region active/active architecture. DR strategies.

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. Due to its monolithic architecture, the application didn’t scale quickly with sudden increases in traffic because of its high bootstrap time. Predictive scaling for EC2.

article thumbnail

Disaster Recovery (DR) Architecture on AWS, Part III: Pilot Light and Warm Standby

AWS Disaster Recovery

In a previous blog post , I showed how quick detection is essential for low RTO, and I shared a serverless architecture to achieve this. Disaster Recovery (DR) Architecture on AWS, Part I: Strategies for Recovery in the Cloud. Disaster Recovery (DR) Architecture on AWS, Part II: Backup and Restore with Rapid Recovery.

article thumbnail

Understand resiliency patterns and trade-offs to architect efficiently in the cloud

AWS Disaster Recovery

Firms designing for resilience on cloud often need to evaluate multiple factors before they can decide the most optimal architecture for their workloads. This will help you achieve varying levels of resiliency and make decisions about the most appropriate architecture for your needs. Looking for more architecture content?