AWS Availability Zones
Availability Zones are isolated locations within an AWS Region, with independent power, cooling, and networking connected through high-bandwidth, low-latency links.
AWS regions with Availability Zones
Zone names come from the current public region dataset and can map to different physical zones across AWS accounts. Use Availability Zone IDs when consistent physical-zone mapping is required.
On smaller screens, scroll horizontally to view all columns.
| Geography | Region code | Region name | Availability Zones | Zone names |
|---|---|---|---|---|
| South Africa | af-south-1 | Africa (Cape Town) | 3 | af-south-1a af-south-1b af-south-1c |
| Hong Kong | ap-east-1 | Asia Pacific (Hong Kong) | 3 | ap-east-1a ap-east-1b ap-east-1c |
| India | ap-south-2 | Asia Pacific (Hyderabad) | 3 | ap-south-2a ap-south-2b ap-south-2c |
| Indonesia | ap-southeast-3 | Asia Pacific (Jakarta) | 3 | ap-southeast-3a ap-southeast-3b ap-southeast-3c |
| Malaysia | ap-southeast-5 | Asia Pacific (Malaysia) | 3 | ap-southeast-5a ap-southeast-5b ap-southeast-5c |
| Australia | ap-southeast-4 | Asia Pacific (Melbourne) | 3 | ap-southeast-4a ap-southeast-4b ap-southeast-4c |
| India | ap-south-1 | Asia Pacific (Mumbai) | 3 | ap-south-1a ap-south-1b ap-south-1c |
| New Zealand | ap-southeast-6 | Asia Pacific (New Zealand) | 3 | ap-southeast-6a ap-southeast-6b ap-southeast-6c |
| Japan | ap-northeast-3 | Asia Pacific (Osaka) | 3 | ap-northeast-3a ap-northeast-3b ap-northeast-3c |
| South Korea | ap-northeast-2 | Asia Pacific (Seoul) | 4 | ap-northeast-2a ap-northeast-2b ap-northeast-2c ap-northeast-2d |
| Singapore | ap-southeast-1 | Asia Pacific (Singapore) | 3 | ap-southeast-1a ap-southeast-1b ap-southeast-1c |
| Australia | ap-southeast-2 | Asia Pacific (Sydney) | 3 | ap-southeast-2a ap-southeast-2b ap-southeast-2c |
| Taiwan | ap-east-2 | Asia Pacific (Taipei) | 3 | ap-east-2a ap-east-2b ap-east-2c |
| Thailand | ap-southeast-7 | Asia Pacific (Thailand) | 3 | ap-southeast-7a ap-southeast-7b ap-southeast-7c |
| Japan | ap-northeast-1 | Asia Pacific (Tokyo) | 3 | ap-northeast-1a ap-northeast-1c ap-northeast-1d |
| Canada | ca-central-1 | Canada (Central) | 3 | ca-central-1a ca-central-1b ca-central-1d |
| Canada | ca-west-1 | Canada West (Calgary) | 3 | ca-west-1a ca-west-1b ca-west-1c |
| Germany | eu-central-1 | Europe (Frankfurt) | 3 | eu-central-1a eu-central-1b eu-central-1c |
| Ireland | eu-west-1 | Europe (Ireland) | 3 | eu-west-1a eu-west-1b eu-west-1c |
| United Kingdom | eu-west-2 | Europe (London) | 4 | eu-west-2a eu-west-2b eu-west-2c eu-west-2d |
| Italy | eu-south-1 | Europe (Milan) | 3 | eu-south-1a eu-south-1b eu-south-1c |
| France | eu-west-3 | Europe (Paris) | 3 | eu-west-3a eu-west-3b eu-west-3c |
| Spain | eu-south-2 | Europe (Spain) | 3 | eu-south-2a eu-south-2b eu-south-2c |
| Sweden | eu-north-1 | Europe (Stockholm) | 3 | eu-north-1a eu-north-1b eu-north-1c |
| Switzerland | eu-central-2 | Europe (Zurich) | 3 | eu-central-2a eu-central-2b eu-central-2c |
| Israel | il-central-1 | Israel (Tel Aviv) | 3 | il-central-1a il-central-1b il-central-1c |
| Mexico | mx-central-1 | Mexico (Central) | 3 | mx-central-1a mx-central-1b mx-central-1c |
| Bahrain | me-south-1 | Middle East (Bahrain) | 3 | |
| United Arab Emirates | me-central-1 | Middle East (UAE) | 3 | me-central-1a me-central-1b me-central-1c |
| Brazil | sa-east-1 | South America (Sao Paulo) | 3 | sa-east-1a sa-east-1b sa-east-1c |
| United States | us-east-1 | US East (N. Virginia) | 6 | us-east-1a us-east-1b us-east-1c us-east-1d us-east-1e us-east-1f |
| United States | us-east-2 | US East (Ohio) | 3 | us-east-2a us-east-2b us-east-2c |
| United States | us-west-1 | US West (N. California) | 2 | us-west-1a us-west-1b |
| United States | us-west-2 | US West (Oregon) | 4 | us-west-2a us-west-2b us-west-2c us-west-2d |
Availability Zone statistics
Additional resources
Use these references to plan resilient architectures across AWS Availability Zones.
Regions and Availability Zones
Review AWS infrastructure concepts and the current global footprint.
Read guidanceAvailability Zone IDs
Learn how zone names and account-independent zone IDs map to physical locations.
Read zone ID guidanceAWS Well-Architected
Review reliability guidance for multi-AZ and multi-region workload design.
Read reliability guidanceFrequently asked questions
How are AWS Availability Zones isolated?
Availability Zones use separate facilities and infrastructure to reduce correlated failures while remaining connected through private, high-bandwidth, low-latency networking.
Are zone names the same for every AWS account?
Zone names such as us-east-1a can map differently between accounts. Use Availability Zone IDs when workloads in multiple accounts must refer to the same physical zone.
Does every AWS service support multi-AZ deployment?
No. Availability Zone support and deployment behavior vary by service and region. Review the service documentation and test the workload's failure behavior before production use.