AWS AWSEC2 documentation change
Summary
Restructured documentation about AWS regions and availability zones. Removed detailed region/zone tables and technical implementation details, replaced with simplified explanations and external references. Reordered sections about Wavelength Zones/Outposts and updated instance placement guidance.
Security assessment
Changes focus on content reorganization, simplification, and removing redundant technical details. No references to security vulnerabilities, patches, or security-specific features. Updates about fault tolerance and zone isolation are general reliability practices, not direct security fixes.
Diff
diff --git a/AWSEC2/latest/UserGuide/using-regions-availability-zones.md index 63663615f..bba576d4d 100644 --- a/AWSEC2/latest/UserGuide/using-regions-availability-zones.md +++ b/AWSEC2/latest/UserGuide/using-regions-availability-zones.md @@ -11 +11 @@ Amazon EC2 is hosted in multiple locations world-wide. These locations are compo - * Each Region is a separate geographic area. + * Regions are separate geographic areas. @@ -17 +17 @@ Amazon EC2 is hosted in multiple locations world-wide. These locations are compo - * AWS Outposts brings native AWS services, infrastructure, and operating models to virtually any data center, co-location space, or on-premises facility. + * Wavelength Zones allow you to build applications that deliver ultra-low latencies to 5G devices and end users. Wavelength deploys standard AWS compute and storage services to the edge of telecommunication carriers' 5G networks. @@ -19 +19 @@ Amazon EC2 is hosted in multiple locations world-wide. These locations are compo - * Wavelength Zones allow developers to build applications that deliver ultra-low latencies to 5G devices and end users. Wavelength deploys standard AWS compute and storage services to the edge of telecommunication carriers' 5G networks. + * AWS Outposts brings native AWS services, infrastructure, and operating models to virtually any data center, co-location space, or on-premises facility. @@ -30,29 +30 @@ For more information, see [AWS Global Infrastructure](https://aws.amazon.com/abo - * [Regions](./using-regions-availability-zones.html#concepts-regions) - * [Available Regions](./using-regions-availability-zones.html#concepts-available-regions) - * [Regional endpoints](./using-regions-availability-zones.html#using-regions-endpoints) - * [Availability Zones](./using-regions-availability-zones.html#concepts-availability-zones) - * [AZ IDs](./using-regions-availability-zones.html#az-ids) - * [Available Availability Zones](./using-regions-availability-zones.html#available-availability-zones) - * [Instances in Availability Zones](./using-regions-availability-zones.html#using-regions-availability-zones-launching) - * [Local Zones](./using-regions-availability-zones.html#concepts-local-zones) - * [Available Local Zones](./using-regions-availability-zones.html#available-local-zones) - * [Instances in Local Zones](./using-regions-availability-zones.html#local-zones-launching) - * [Wavelength Zones](./using-regions-availability-zones.html#concepts-wavelength-zones) - * [Available Wavelength Zones](./using-regions-availability-zones.html#available-wavelength-zones) - * [Instances in Wavelength Zones](./using-regions-availability-zones.html#wavelength-zones-launching) - * [AWS Outposts](./using-regions-availability-zones.html#concepts-outposts) - * [Instances on an Outpost](./using-regions-availability-zones.html#outposts-instances) - * [Volumes on an Outposts rack](./using-regions-availability-zones.html#outposts-rack-volumes) - * [Volumes on an Outposts server](./using-regions-availability-zones.html#outposts-server-volumes) - - - -## Regions - -Each Region is designed to be isolated from the other Regions. This achieves the greatest possible fault tolerance and stability. - -When you view your resources, you see only the resources that are tied to the Region that you specified. This is because Regions are isolated from each other, and we don't automatically replicate resources across Regions. - -When you launch an instance, you must select an AMI that's in the same Region. If the AMI is in another Region, you can copy the AMI to the Region you're using. For more information, see [Copy an Amazon EC2 AMI](./CopyingAMIs.html). - -Note that there is a charge for data transfer between Regions. For more information, see [Amazon EC2 Pricing - Data Transfer](https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer). + * Regions @@ -60,3 +32 @@ Note that there is a charge for data transfer between Regions. For more informat -### Available Regions - -Your account determines the Regions that are available to you. + * Availability Zones @@ -64 +34 @@ Your account determines the Regions that are available to you. - * An AWS account provides multiple Regions so that you can launch Amazon EC2 instances in locations that meet your requirements. For example, you might want to launch instances in Europe to be closer to your European customers or to meet legal requirements. + * Local Zones @@ -66 +36 @@ Your account determines the Regions that are available to you. - * An AWS GovCloud (US-West) account provides access to the AWS GovCloud (US-West) Region and the AWS GovCloud (US-East) Region. For more information, see [AWS GovCloud (US)](https://aws.amazon.com/govcloud-us/). + * Wavelength Zones @@ -68 +38 @@ Your account determines the Regions that are available to you. - * An Amazon AWS (China) account provides access to the Beijing and Ningxia Regions only. For more information, see [Amazon Web Services in China](https://www.amazonaws.cn/about-aws/china/). + * AWS Outposts @@ -73,3 +43 @@ Your account determines the Regions that are available to you. -You can't describe or access additional Regions from an AWS account, such as the AWS GovCloud (US) Regions or the China Regions. - -The following table lists the Regions provided by an AWS account. Alternatively, call the [list-regions](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/account/list-regions.html) command. +## Regions @@ -77,36 +45 @@ The following table lists the Regions provided by an AWS account. Alternatively, -Code | Name | Opt-in status ----|---|--- -us-east-1 | US East (N. Virginia) | Not required -us-east-2 | US East (Ohio) | Not required -us-west-1 | US West (N. California) | Not required -us-west-2 | US West (Oregon) | Not required -af-south-1 | Africa (Cape Town) | Required -ap-east-1 | Asia Pacific (Hong Kong) | Required -ap-south-2 | Asia Pacific (Hyderabad) | Required -ap-southeast-3 | Asia Pacific (Jakarta) | Required -ap-southeast-5 | Asia Pacific (Malaysia) | Required -ap-southeast-4 | Asia Pacific (Melbourne) | Required -ap-south-1 | Asia Pacific (Mumbai) | Not required -ap-northeast-3 | Asia Pacific (Osaka) | Not required -ap-northeast-2 | Asia Pacific (Seoul) | Not required -ap-southeast-1 | Asia Pacific (Singapore) | Not required -ap-southeast-2 | Asia Pacific (Sydney) | Not required -ap-southeast-7 | Asia Pacific (Thailand) | Required -ap-northeast-1 | Asia Pacific (Tokyo) | Not required -ca-central-1 | Canada (Central) | Not required -ca-west-1 | Canada West (Calgary) | Required -cn-north-1 | China (Beijing) | Not required -cn-northwest-1 | China (Ningxia) | Not required -eu-central-1 | Europe (Frankfurt) | Not required -eu-west-1 | Europe (Ireland) | Not required -eu-west-2 | Europe (London) | Not required -eu-south-1 | Europe (Milan) | Required -eu-west-3 | Europe (Paris) | Not required -eu-south-2 | Europe (Spain) | Required -eu-north-1 | Europe (Stockholm) | Not required -eu-central-2 | Europe (Zurich) | Required -il-central-1 | Israel (Tel Aviv) | Required -mx-central-1 | Mexico (Central) | Required -me-south-1 | Middle East (Bahrain) | Required -me-central-1 | Middle East (UAE) | Required -sa-east-1 | South America (São Paulo) | Not required +Each Region is designed to be isolated from the other Regions. This achieves the greatest possible fault tolerance and stability. @@ -114 +47 @@ sa-east-1 | South America (São Paulo) | Not required -To use a Region introduced after March 20, 2019, you must enable the Region. For more information, see [Enable or disable AWS Regions in your account](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html) in the _AWS Account Management Reference Guide_. +When you launch an instance, select a Region that puts your instances close to specific customers, or that meets the legal or other requirements that you have. You can launch instances in multiple Regions. @@ -116 +49 @@ To use a Region introduced after March 20, 2019, you must enable the Region. For -To get the name of a Region, use the following [get-parameters-by-path](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ssm/get-parameters-by-path.html) command. Replace `region-code` with the code for the Region. You might need to modify the quotes to get the example to work with your terminal. +When you view your resources, you see only the resources that are tied to the Region that you specified. This is because Regions are isolated from each other, and we don't automatically replicate resources across Regions. @@ -117,0 +51 @@ To get the name of a Region, use the following [get-parameters-by-path](https:// +### Available Regions @@ -119,4 +53 @@ To get the name of a Region, use the following [get-parameters-by-path](https:// - aws ssm get-parameters-by-path \ - --path /aws/service/global-infrastructure/regions/region-code \ - --query 'Parameters[?Name.contains(@,`longName`)].Value' \ - --output text +For the list of available Regions, see [AWS Regions](https://docs.aws.amazon.com/global-infrastructure/latest/regions/aws-regions.html). @@ -124 +55 @@ To get the name of a Region, use the following [get-parameters-by-path](https:// -### Regional endpoints +### Regional endpoints for Amazon EC2 @@ -128,2 +58,0 @@ When you work with an instance using the command line interface or API actions, -For more information about endpoints and protocols in AWS GovCloud (US-West), see [Service Endpoints](https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/using-govcloud-endpoints.html) in the _AWS GovCloud (US) User Guide_. - @@ -134 +63 @@ Each Region has multiple, isolated locations known as _Availability Zones_. The -When you launch an instance, you select a Region and a virtual private cloud (VPC), and then you can either select a subnet from one of the Availability Zones or let us choose one for you. If you distribute your instances across multiple Availability Zones and one instance fails, you can design your application so that an instance in another Availability Zone can handle requests. You can also use Elastic IP addresses to mask the failure of an instance in one Availability Zone by rapidly remapping the address to an instance in another Availability Zone. +By launching EC2 instances in multiple Availability Zones, you can protect your applications from the failure of a single location in the Region. @@ -136 +65 @@ When you launch an instance, you select a Region and a virtual private cloud (VP -The following diagram illustrates multiple Availability Zones in an AWS Region. Availability Zone A and Availability Zone B each have one subnet, and each subnet has instances. Availability Zone C has no subnets, therefore you can't launch instances into this Availability Zone. +The following diagram illustrates multiple Availability Zones in an AWS Region. Availability Zone A and Availability Zone B each have one subnet, and each subnet has EC2 instances. Availability Zone C has no subnets, therefore you can't launch instances into this Availability Zone. @@ -140,87 +69 @@ The following diagram illustrates multiple Availability Zones in an AWS Region. -As Availability Zones grow over time, our ability to expand them can become constrained. If this happens, we might restrict you from launching an instance in a constrained Availability Zone unless you already have an instance in that Availability Zone. Eventually, we might also remove the constrained Availability Zone from the list of Availability Zones for new accounts. Therefore, your account might have a different number of available Availability Zones in a Region than another account. - -### AZ IDs - -To ensure that resources are distributed across the Availability Zones for a Region, we independently map Availability Zones to codes for each AWS account in our oldest Regions. For example, the `us-east-1a` for your AWS account might not be the same physical location as the `us-east-1a` for another AWS account. - -To coordinate Availability Zones across accounts in all Regions even those that map Availability Zones, use the _AZ IDs_ , which are unique and consistent identifiers for an Availability Zone. For example, `use1-az1` is an AZ ID for the `us-east-1` Region, and it has the same physical location in every AWS account. You can view the AZ IDs for your account to determine the physical location of your resources relative to the resources in another account. For example, if you share a subnet in the Availability Zone with the AZ ID `use1-az2` with another account, this subnet is available to that account in the Availability Zone whose AZ ID is also `use1-az2`. - -To view the AZ IDs for your account, check the **Service health** panel on the [EC2 Dashboard](https://console.aws.amazon.com/ec2/) or use the [describe-availability-zones](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-availability-zones.html) AWS CLI command. - -The following diagram illustrates two accounts with different mappings of Availability Zone code to AZ ID. - - - -### Available Availability Zones - -Each Region has multiple Availability Zones, as shown in the following list. - - * US East (N. Virginia) – `use1-az1` | `use1-az2` | `use1-az3` | `use1-az4` | `use1-az5` | `use1-az6` - - * US East (Ohio) – `use2-az1` | `use2-az2` | `use2-az3` - - * US West (N. California) – `usw1-az1` | `usw1-az2` | `usw1-az3` † - - * US West (Oregon) – `usw2-az1` | `usw2-az2` | `usw2-az3` | `usw2-az4` - - * Africa (Cape Town) – `afs1-az1` | `afs1-az2` | `afs1-az3` - - * Asia Pacific (Hong Kong) – `ape1-az1` | `ape1-az2` | `ape1-az3` - - * Asia Pacific (Hyderabad) – `aps2-az1` | `aps2-az2` | `aps2-az3` - - * Asia Pacific (Jakarta) – `apse3-az1` | `apse3-az2` | `apse3-az3` - - * Asia Pacific (Malaysia) – `apse5-az1` | `apse5-az2` | `apse5-az3` - - * Asia Pacific (Melbourne) – `apse4-az1` | `apse4-az2` | `apse4-az3` - - * Asia Pacific (Mumbai) – `aps1-az1` | `aps1-az2` | `aps1-az3` - - * Asia Pacific (Osaka) – `apne3-az1` | `apne3-az2` | `apne3-az3` - - * Asia Pacific (Seoul) – `apne2-az1` | `apne2-az2` | `apne2-az3` | `apne2-az4` - - * Asia Pacific (Singapore) – `apse1-az1` | `apse1-az2` | `apse1-az3` - - * Asia Pacific (Sydney) – `apse2-az1` | `apse2-az2` | `apse2-az3` - - * Asia Pacific (Thailand) – `apse7-az1` | `apse7-az2` | `apse7-az3` - - * Asia Pacific (Tokyo) – `apne1-az1` | `apne1-az2` | `apne1-az3` | `apne1-az4` - - * Canada (Central) – `cac1-az1` | `cac1-az2` | `cac1-az4` - - * Canada West (Calgary) – `caw1-az1` | `caw1-az2` | `caw1-az3` - - * Europe (Frankfurt) – `euc1-az1` | `euc1-az2` | `euc1-az3` - - * Europe (Ireland) – `euw1-az1` | `euw1-az2` | `euw1-az3` - - * Europe (London) – `euw2-az1` | `euw2-az2` | `euw2-az3` - - * Europe (Milan) – `eus1-az1` | `eus1-az2` | `eus1-az3` - - * Europe (Paris) – `euw3-az1` | `euw3-az2` | `euw3-az3` - - * Europe (Spain) – `eus2-az1` | `eus2-az2` | `eus2-az3` - - * Europe (Stockholm) – `eun1-az1` | `eun1-az2` | `eun1-az3` - - * Europe (Zurich) – `euc2-az1` | `euc2-az2` | `euc2-az3` -