|
|
The AWS Cloud spans 36 Regions and 114 Availability Zones worldwide, with plans for 13 more AZs and 4 new Regions (New Zealand, Saudi Arabia, Taiwan, European Sovereign Cloud). AWS delivers services through a global network of 700+ Edge Locations and 13 Regional Edge Caches, serving 245 countries and territories.
Regions (Availability Zones): N. California (3), Oregon (4), Ohio (3), N. Virginia (6), Canada Central (3), US GovCloud-West (3), US GovCloud-East (3)
Edge Locations: Ashburn, VA (3); Atlanta, GA (3); Boston, MA; Chicago, IL (2); Dallas/Fort Worth, TX (5); Denver, CO (2); Hayward, CA; Jacksonville, FL; Los Angeles, CA (4); Miami, FL (3); Minneapolis, MN; Montreal, QC; New York, NY (3); Newark, NJ (3); Palo Alto, CA; Phoenix, AZ; Philadelphia, PA; San Jose, CA (2); Seattle, WA (3); South Bend, IN; St. Louis, MO; Toronto, ON
Regional Edge Caches: Northern Virginia; Ohio; Oregon
| Short name | Full name | Code name | AZ's | Launched |
|---|---|---|---|---|
| Oregon | US West (Oregon) | us-west-2 | 4 | 2011 |
| N. California | US West (N. California) | us-west-1 | 3 | 2009 |
| US GovCloud-West | AWS GovCloud (US-West) | us-gov-west-1 | 3 | 2011 |
| US GovCloud-East | AWS GovCloud (US-East) | us-gov-east-1 | 3 | 2018 |
| Ohio | US East (Ohio) | us-east-2 | 3 | 2016 |
| N. Virginia | US East (N. Virginia) | us-east-1 | 6 | 2006 |
| Canada | Canada (Central) | ca-central-1 | 3 | 2016 |
Regions (Availability Zones): São Paulo (3)
Edge Locations: Rio de Janeiro (2), Sao Paulo (2)
Regional Edge Cache: Sao Paulo
| Short name | Full name | Code name | AZ's | Launched |
|---|---|---|---|---|
| São Paulo | South America (São Paulo) | sa-east-1 | 3 | 2011 |
Regions (Availability Zones): Frankfurt (3), Ireland (3), London (3), Paris (3), Stockholm (3), Bahrain (3)
Edge Locations: Amsterdam (2); Berlin; Cape Town; Dublin; Frankfurt (8); Helsinki; Johannesburg; London (7); Madrid (2); Manchester; Marseille; Milan; Munich; Palermo; Paris (3); Prague; Stockholm (3); Vienna; Warsaw; Zurich; Lisbon
Regional Edge Caches: Frankfurt; London
| Short name | Full name | Code name | AZ's | Launched |
|---|---|---|---|---|
| Bahrain | Middle East (Bahrain) | me-south-1 | 3 | 2019 |
| Paris | EU (Paris) | eu-west-3 | 3 | 2017 |
| London | EU (London) | eu-west-2 | 3 | 2016 |
| Ireland | EU (Ireland) | eu-west-1 | 3 | 2007 |
| Stockholm | EU (Stockholm) | eu-north-1 | 3 | 2018 |
| Frankfurt | EU (Frankfurt) | eu-central-1 | 3 | 2014 |
Regions (Availability Zones): Hong Kong SAR (3), Mumbai (3), Seoul (3), Singapore (3), Sydney (3), Tokyo (4), Hyderabad (3), Jakarta (3), Melbourne (3), Osaka (3), Kuala Lumpur (3), Tel Aviv (3), Mexico Central (3)
Edge Locations: Bangalore (3); Chennai (2); Hong Kong (3); Hyderabad (4); Kuala Lumpur; Mumbai (2); Manila; New Delhi (5); Osaka; Seoul (4); Singapore (3); Taipei (3); Tokyo (12); Melbourne; Perth; Sydney (2); Beijing (1); Shanghai (1); Zhongwei (1); Shenzhen (1)
Regional Edge Caches: Mumbai; Singapore; Seoul; Tokyo; Sydney
| Short name | Full name | Code name | AZ's | Launched |
|---|---|---|---|---|
| Ningxia | China (Ningxia) | cn-northwest-1 | 3 | 2017 |
| Beijing | China (Beijing) | cn-north-1 | 3 | 2014 |
| Sydney | Asia Pacific (Sydney) | ap-southeast-2 | 3 | 2012 |
| Singapore | Asia Pacific (Singapore) | ap-southeast-1 | 3 | 2010 |
| Mumbai | Asia Pacific (Mumbai) | ap-south-1 | 3 | 2016 |
| Osaka | Asia Pacific (Osaka) | ap-northeast-3 | 3 | 2021 |
| Seoul | Asia Pacific (Seoul) | ap-northeast-2 | 3 | 2016 |
| Tokyo | Asia Pacific (Tokyo) | ap-northeast-1 | 4 | 2011 |
| Hong Kong | Asia Pacific (Hong Kong) | ap-east-1 | 3 | 2019 |
Edge Locations: Over 700 globally, providing content caching and low-latency delivery.
Regional Edge Caches: 13, acting as larger cache layers between origins and edge locations.
Edge locations are not tied to regions/AZs and support both read and write operations.
43 AWS Local Zones extend AWS services to metro areas for ultra-low latency (5-20 ms). Ideal for real-time gaming, media, and ML inference.
AWS Outposts bring fully managed AWS infrastructure, services, APIs, and tools to customer data centers or co-location spaces, enabling true hybrid cloud with local data residency and low-latency needs.
Key difference: Outposts are on-premises, Local Zones are AWS-managed in metro areas.