High Availability and Disaster Recovery
Design highly available and fault-tolerant architectures: Availability Zones and Regions, Multi-AZ patterns, database replication options, Route 53 routing and failover, backups, and the four disaster recovery strategies.
Availability Zones and Regions
A Region is a geographic area (such as us-east-1). Each Region has multiple Availability Zones (AZs): one or more data centers with independent power, cooling, and networking, connected by low-latency links.
- High availability (HA) means the system keeps working when a component or an AZ fails. On AWS, that almost always means Multi-AZ.
- Fault tolerance goes a step further: the failure causes no user-visible interruption, usually because redundant capacity is already running.
- Disaster recovery (DR) is how you recover from a larger event, such as the loss of a whole Region, a bad deployment, or deleted data.
Read the question carefully. If it says “highly available,” Multi-AZ is usually enough. Multi-Region is the answer only when the question mentions Regional outages, global users, or a very low RTO/RPO across Regions.
The Multi-AZ Pattern
The pattern: spread every tier across at least two AZs, size each AZ so the others can carry the load if one fails, and use services that are already Multi-AZ (S3, DynamoDB, SQS, Lambda, EFS) wherever you can.
Database Resilience Options
| Option | What it does | Readable? | Use it for |
|---|---|---|---|
| RDS Multi-AZ (instance) | Synchronous standby in another AZ; automatic failover, usually in a minute or two | No, standby only | High availability |
| RDS Multi-AZ DB cluster | One writer and two readable standbys in three AZs | Yes | HA plus read capacity, faster failover |
| RDS read replicas | Asynchronous copies, in-Region or cross-Region; can be promoted | Yes | Scaling reads; cross-Region DR |
| Aurora | Storage keeps six copies across three AZs; up to 15 low-lag replicas; fast failover | Yes | HA and read scaling with less to manage |
| Aurora Global Database | Replicates to other Regions, typically with under a second of lag | Yes, in secondary Regions | Low-RPO cross-Region DR and local global reads |
| DynamoDB global tables | Multi-Region, multi-active replication | Yes, read and write in every Region | Global apps that write in many Regions |
The two features people mix up most often, side by side:
Remember the difference: Multi-AZ is for availability, and read replicas are for read scaling (plus cross-Region DR). Exam answers that use a read replica for automatic failover, or a classic Multi-AZ standby to serve reads, are wrong.
Route 53: Routing and Failover
| Routing policy | Use it when |
|---|---|
| Simple | One resource, no health checks |
| Failover | Active-passive: send traffic to the secondary when the primary’s health check fails |
| Weighted | Split traffic by percentage (canary or blue/green releases) |
| Latency | Send users to the Region with the lowest latency for them |
| Geolocation | Route by the user’s country or continent (compliance, localized content) |
| Geoproximity | Route by distance, with a bias to shift traffic between Regions |
| Multivalue answer | Return several healthy IPs for simple client-side load spreading |
| IP-based | Route by the client’s IP range |
Alias records point a domain name (including the zone apex, like example.com) at AWS resources such as an ALB, CloudFront distribution, or S3 website, at no query charge.
Backups and the Four DR Strategies
AWS Backup centralizes backup policies across EBS, RDS, Aurora, DynamoDB, EFS, FSx, S3, and more, including cross-Region and cross-account copies. Copies in a separate account protect you from someone deleting both the data and its backups.
DR strategies, from cheapest and slowest to most expensive and fastest:
| Strategy | What runs in the DR Region | RTO / RPO |
|---|---|---|
| Backup and restore | Nothing but backups | Hours |
| Pilot light | Data is replicated and live; servers are off or minimal | Tens of minutes |
| Warm standby | A scaled-down but fully working copy of production | Minutes |
| Multi-site active/active | Full production in more than one Region, serving traffic | Near zero |
Choose the cheapest strategy that meets the RTO and RPO in the question.
Common mistake: the design says “nightly snapshots” and stops there.
An untested backup is a hope, not a plan. Real DR plans include restore tests, documented runbooks, and the service quotas needed in the recovery Region. Exam questions also test the time dimension: a nightly backup can’t meet a 15-minute RPO.
Key Takeaway
Multi-AZ is the default for high availability; go multi-Region only when Regional failure or global users are part of the requirement. Know which database feature gives failover (Multi-AZ) and which gives read scaling (read replicas), how Route 53 failover works with health checks, and pick the cheapest DR strategy that meets the RTO and RPO.
For each scenario, pick a DR strategy and the main services. Then compare with the suggested answers.
- An internal reporting app. RTO 24 hours, RPO 24 hours.
- An e-commerce checkout. RTO 15 minutes, RPO 1 minute.
- A global trading platform. RTO and RPO near zero.
Suggested answers: (1) backup and restore with AWS Backup cross-Region copies; (2) warm standby with Aurora Global Database and a scaled-down ASG plus Route 53 failover; (3) multi-site active/active with DynamoDB global tables or Aurora Global Database, latency-based routing, and full capacity in each Region.
1. A company needs its RDS for MySQL database to fail over automatically if an AZ fails. What should they enable?
Multi-AZ keeps a synchronous standby in another AZ and fails over automatically.
2. Users report slow reads from an RDS database during reporting hours. Writes are fine. What is the MOST appropriate fix?
Read replicas add read capacity. A classic Multi-AZ standby does not serve reads.
3. Which Route 53 routing policy sends all traffic to a primary site and switches to a secondary when a health check fails?
Failover routing implements active-passive with health checks.
4. A workload needs an RTO of a few minutes after a Regional outage and the company wants to keep costs down. Which DR strategy fits BEST?
Warm standby runs a smaller working copy that can scale up in minutes, for less than active/active. Backup and restore takes hours.