AWS Platform Architecture
AWS maintains data centers for its physical servers around the world. Because the centers are so widely distributed, you can reduce your own services' network transfer latency by hosting your workloads geographically close to your users. It can also help you manage compliance with regulations requiring you to keep data within a particular legal jurisdiction.
Data centers exist within AWS regions, of which there are currently 21—not including private U.S. government AWS GovCloud regions—although this number is constantly growing. It's important to always be conscious of the region you have selected when you launch new AWS resources; pricing and service availability can vary from one to the next. Table 1.3 shows a list of all 21 (nongovernment) regions along with each region's name and core endpoint addresses. Note that accessing and authenticating to the two Chinese regions requires unique protocols.
TABLE 1.3 A list of publicly accessible AWS regions
| Region name | Region | Endpoint |
|---|---|---|
| US East (Ohio) |
us‐east‐2
|
us-east-2.amazonaws.com
|
| US West (N. California) |
us‐west‐1
|
us-west-1.amazonaws.com
|
| US West (Oregon) |
us‐west‐2
|
us-west-2.amazonaws.com
|
| Asia Pacific (Hong Kong) |
ap‐east‐1
|
ap-east-1.amazonaws.com
|
| Asia Pacific (Mumbai) |
ap‐south‐1
|
ap-south-1.amazonaws.com
|
| Asia Pacific (Seoul) |
ap‐northeast‐2
|
ap-northeast-2.amazonaws.com
|
| Asia Pacific (Osaka‐Local) |
ap‐northeast‐3
|
ap-northeast-3.amazonaws.com
|
| Asia Pacific (Singapore) |
ap‐southeast‐1
|
ap-southeast-1.amazonaws.com
|
| Asia Pacific (Sydney) |
ap‐southeast‐2
|
ap-southeast-2.amazonaws.com
|
| Asia Pacific (Tokyo) |
ap‐northeast‐1
|
ap-northeast-1.amazonaws.com
|
| Canada (Central) |
ca‐central‐1
|
ca-central-1.amazonaws.com
|
| China (Beijing) |
cn‐north‐1
|
cn-north-1.amazonaws.com.cn
|
| China (Ningxia) |
cn‐northwest‐1
|
cn-northwest-1.amazonaws.com.cn
|
| EU (Frankfurt) |
eu‐central‐1
|
eu-central-1.amazonaws.com
|
| EU (Ireland) |
eu‐west‐1
|
