Topic lessonTopic: Audit coverage and recovery design
AWS fault domains: choosing between Multi-AZ and Multi-Region
Start with what can fail together. Trace a fictional image submission through compute and storage to see which business routes survive a failure.
Trace dependencies for the business transaction and evaluate which routes survive an AZ-wide or Region-wide outage.
This is a fixed architecture exercise. The scenario does not estimate actual AWS recovery time or interpret service guarantees.
Find the dependencies shared by redundant paths
AWS provides isolation across Availability Zones and, when necessary, across Regions. Whether a surviving path completes the transaction still depends on placement, capacity and shared dependencies.
- Worker A → Shared databaseA uses shared data
- Worker B → Shared databaseB uses shared data
- Shared database → Business checkCheck the outcome
- Worker A
- East Region, AZ A
- Worker B
- Same Region, AZ B
- Shared database
- Both use storage in AZ A
- Business check
- Submit and read back
An entry point survives but the write path does not
| Outage | What remains | Business status |
|---|---|---|
| AZ B unavailable | Worker A and database | May continue if A can handle the load |
| AZ A unavailable | Worker B | Cannot write to shared database |
| East Region unavailable | Only the static page is in West | Submissions cannot continue |
| Surviving capacity unmeasured | A complete route exists | Peak-load operation remains unverified |
A second Region does not remove a dependency on the original Region when, for example, the write target or a startup dependency remains there.
Choose isolation that matches the requirement
Name the business outcome. List viewing, submitting and delayed processing separately. Give each outcome its own observable pass condition.
Follow the whole route. For each failure scope, inspect entry points, compute, data, identity and external dependencies. Check the capacity of the paths that remain.
Record deployment and capacity evidence. Keep normal synthetic results separate from the measured capacity of the surviving system during a fault.
Check your decision
Choose an option to see the result and explanation.
Check, then explain in your own words
- Define the business outcome.
- Trace dependencies for each failure scope.
- Measure surviving capacity and completed transactions.
Check your understanding: Why do compute resources in two AZs leave availability uncertain?
Both paths may depend on the same data or service.
Availability depends on isolation of the resources needed to complete the work.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsFault isolation across AZs and Regions, including dependencies.
Used in this lessonFind the dependencies shared by redundant paths An entry point survives but the write path does not Choose isolation that matches the requirement