Remove Architecture Remove Disaster Recovery Remove Whitepaper
article thumbnail

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

AWS Disaster Recovery

Ultimately, any event that prevents a workload or system from fulfilling its business objectives in its primary location is classified a disaster. This blog post shows how to architect for disaster recovery (DR) , which is the process of preparing for and recovering from a disaster. Architecture of the DR strategies.

article thumbnail

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

AWS Disaster Recovery

In a previous blog post , I introduced you to four strategies for disaster recovery (DR) on AWS. These strategies enable you to prepare for and recover from a disaster. To reduce recovery time, detection should be automated. Using EventBridge to detect and respond to a disaster event. Related information.

Insiders

Sign Up for our Newsletter

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

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. Resilience patterns and trade-offs. P1 – Multi-AZ.

article thumbnail

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

AWS Disaster Recovery

In my first blog post of this series , I introduced you to four strategies for disaster recovery (DR). The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. I use Amazon DynamoDB for the example architecture in Figure 2.

article thumbnail

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

AWS Disaster Recovery

In this blog post, you will learn about two more active/passive strategies that enable your workload to recover from disaster events such as natural disasters, technical failures, or human actions. Previously, I introduced you to four strategies for disaster recovery (DR) on AWS. Related information.

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 does static stability mean with regard to a multi-Region disaster recovery (DR) plan? Testing your disaster recovery plan. Even a simple distributed system may be too complex to operate reliably.

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. Building disaster recovery (DR) strategies into your system requires you to work backwards from recovery point objective (RPO) and recovery time objective (RTO) requirements.