AWS Elastic Disaster Recovery

AWS Elastic Disaster Recovery is a service that continuously replicates block-level data from source physical, virtual, or cloud servers into a staging area in AWS and orchestrates recovery to Amazon EC2. It operates by installing a lightweight replication agent or appliance at the source, sending replication data to staging resources in a target AWS account, and providing tooling to test, launch, and manage recovery instances.

🗂 Resource Category

Migration and Transfer • Management and Governance

🧠 Exam Memory Hook

Think: "Continuous block replication + orchestrated failover to AWS + agent/appliance = AWS Elastic Disaster Recovery"

📖 Ownership

Classification: Shared Responsibility Service

AWS responsibilities: AWS operates and maintains the Elastic Disaster Recovery control plane, service APIs, and underlying AWS infrastructure, and secures and patches AWS-owned infrastructure components (physical hosts, network fabric, and the managed control plane). AWS provides the console, APIs, and service updates used to orchestrate replication, staging, and recovery workflows.

Customer responsibilities: The customer installs and configures replication agents or appliances on source systems, configures replication settings, network connectivity (VPN/Direct Connect), VPCs, subnets, security groups, and IAM roles in the target account, monitors replication health, performs recovery tests, and executes failover and failback runbooks; the customer also manages data consistency, access controls, and operational procedures for recovery.

Patching responsibilities: AWS patches and maintains the physical infrastructure, hypervisor, and the Elastic Disaster Recovery service control plane and managed service components. The customer is responsible for patching guest operating systems, application runtimes, libraries, dependencies, and any EC2 instances launched in their account (including recovery or replication instances unless a specific managed option states otherwise); if a particular replication-server AMI patching responsibility is required, Information not available.

🏗 Typical Architecture

💡 Top 5 Features

Continuous block-level replication of source servers to a staging area in AWS.
Orchestrated recovery workflows to launch, test, and perform failover to Amazon EC2.
Non-disruptive recovery testing using isolated networks or staging configurations.
Service console and APIs that expose replication metrics, health, and recovery job orchestration.
Agent- or appliance-based replication support for physical and virtual server sources.

✅ Top 5 Use Cases

Disaster recovery to AWS for on-premises or cloud-hosted servers by continuously replicating working server volumes and enabling orchestrated failover.
Non-disruptive DR testing for compliance or audit requirements using isolated test networks in AWS.
Lift-and-shift migrations where block-level replication is used to synchronize servers prior to cutover.
Protecting legacy physical or virtual servers where replatforming is not feasible by maintaining a recovery copy in AWS.
Orchestrated recovery of multi-tier applications requiring coordinated ordering, networking, and boot sequencing in AWS.

🏗 Architecture Placement

AWS Elastic Disaster Recovery is deployed into the customer’s target AWS account and operates at a regional level for the selected recovery region; it receives replication data from source-side agents or appliances over secure network connectivity. The service creates or uses staging resources (replication servers and storage) within a VPC and launches Amazon EC2 recovery instances when testing or performing failover. It normally connects to IAM for permissions, VPC networking for isolation, and customer storage for staged data.

🎯 Commonly Used With

- Amazon EC2
- Amazon VPC
- AWS Identity and Access Management
- Amazon CloudWatch
- Amazon S3

🌍 5 Real-World Examples

A bank replicates critical transaction servers to AWS to run isolated recovery tests for regulatory resilience exercises.
A healthcare provider maintains replicated imaging and archive servers in AWS to perform non-disruptive DR tests before planned datacenter maintenance.
A retail chain replicates point-of-sale and inventory servers to AWS to enable a coordinated failover during a datacenter outage.
A government agency uses replication to preserve operational copies of case-management servers in AWS to maintain continuity during infrastructure upgrades.
A software company performs lift-and-shift migrations of development and test VMs by continuously replicating source machines to AWS and performing controlled cutovers.

🎓 AWS Exam Clues

Used when requirements call for continuous block-level replication and orchestrated failover to AWS.
Appropriate when non-disruptive recovery testing in isolated networks is required for compliance or validation.
Consider alternative migration tools if application-level replatforming or transformation is required during migration.
Requires secure network connectivity, VPC configuration, IAM roles, and staging resources in the target AWS account as part of deployment.
Operational responsibility: customer patches source OS and recovered EC2 instances; AWS manages the service control plane and underlying AWS infrastructure.

📝 Quick Revision

AWS Elastic Disaster Recovery continuously replicates source servers at block level into a staging area in a target AWS account and provides orchestration for testing and failover to EC2. Use it for DR and lift-and-shift scenarios; important considerations are network connectivity, staging resource configuration, IAM permissions, monitoring, and customer responsibility for guest OS and application patching.

🏷 Keywords

block-level replication • replication agent • staging area • replication server • recovery instance • orchestrated failover • non-disruptive testing • cutover • recovery runbook • staging storage • continuous replication • recovery point objective