A county constituent portal must remain available if an entire AWS…

Question

A county constituent portal must remain available if an entire AWS Region fails. Architects currently run Multi-AZ inside one Region and assume that covers regional outages. What should they redesign for Region-level disruption?

Accepted Answer

Implement a multi-Region architecture with cross-Region data replication and Route 53 (or equivalent) failover/health-based routing so application and infrastructure can recover outside the disrupted Region. — Multi-AZ is a neighborhood generator backup—great when one block goes dark, useless when the whole town loses power. Region failure needs another Region, replicated data, and DNS that knows when to move traffic.

Answer

Keep a single-AZ deployment because Multi-AZ already implies multi-Region failover.

Answer

Disable health checks so DNS never fails away from the primary Region during an outage.

Answer

Rely solely on Amazon S3 same-Region versioning and expect the portal to stay online when the Region is unavailable.

A county constituent portal must remain available if an entire AWS Region fails. Architects currently run Multi-AZ inside one Region and assume that covers regional outages. What should they redesign for Region-level disruption?

Short Explanation

Full Explanation