A web service should continue if one Availability Zone fails.
Increase availability within the same Region.
Which design is appropriate?
Distribute application resources across multiple Availability Zones and combine them with traffic distribution and data protection.
Detailed explanation
IAM identities are not placed in an AZ and do not provide application redundancy.
IAM identities are not placed in an AZ and do not provide application redundancy.
A single AZ remains a single failure domain.
A single AZ remains a single failure domain.
Encryption does not remove a physical AZ failure domain.
Encryption does not remove a physical AZ failure domain.
Multiple AZs separate failure domains and allow the service to continue when one AZ has an issue.
Multiple AZs separate failure domains and allow the service to continue when one AZ has an issue.
Check official documentation
Compare the following points with the official documentation.
AWS Regions and Availability Zones User GuideのAvailability Zonesの説明を確認する。
What to confirm
1つのAZが利用できない場合にも、別AZのリソースでサービスを継続できる構成を検討できる。
Key points
- Availability Zone
- High availability
- Failure isolation
Notes
- Environment: AWS公式Global Infrastructureドキュメントの確認
- AWS global infrastructure and service availability can change; verify current details in official AWS documentation.
Foundation review
Benefit versus implementation
Agility and elasticity describe cloud capabilities; a particular Region or AZ is an implementation choice that must satisfy other constraints.
Availability and proximity
Use multiple AZs for failure isolation and suitable Regions or Local Zones for geographic proximity and latency.