AWS local-zones documentation change
Summary
Updated documentation to replace 'Opt-in' terminology with 'Enable' for Local Zones, changed console references from AWS Global View to Amazon EC2, added explicit warning about SSH key pair requirement for EC2 instances, and streamlined procedural steps.
Security assessment
The change adds a security-related warning advising users not to launch instances without a key pair ('Do not choose Proceed without a key pair'). This explicitly documents security best practices for EC2 instance access control. However, there is no evidence of addressing a specific security vulnerability or incident.
Diff
diff --git a/local-zones/latest/ug/getting-started.md b/local-zones/latest/ug/getting-started.md index 037efff1f..03b69c2e2 100644 --- a//local-zones/latest/ug/getting-started.md +++ b//local-zones/latest/ug/getting-started.md @@ -5 +5 @@ -Step 1: Opt-in to a Local ZoneStep 2: Create a Local Zone subnetStep 3: Create a resource in your Local Zone subnetStep 4: Clean up +Step 1: Enable a Local ZoneStep 2: Create a Local Zone subnetStep 3: Create a resource in your Local Zone subnetStep 4: Clean up @@ -9 +9 @@ Step 1: Opt-in to a Local ZoneStep 2: Create a Local Zone subnetStep 3: Create a -To get started with AWS Local Zones, you must first opt-in to a Local Zone through the AWS Global View console or the AWS CLI. Next, create a subnet in a VPC in the parent Region, specifying the Local Zone when you create it. Finally, create AWS resources in the Local Zone subnet. +To get started with AWS Local Zones, you must first enable a Local Zone through the Amazon EC2 console or the AWS CLI. Next, create a subnet in a VPC in the parent Region, specifying the Local Zone when you create it. Finally, create AWS resources in the Local Zone subnet. @@ -13 +13 @@ To get started with AWS Local Zones, you must first opt-in to a Local Zone throu - * Step 1: Opt-in to a Local Zone + * Step 1: Enable a Local Zone @@ -24 +24 @@ To get started with AWS Local Zones, you must first opt-in to a Local Zone throu -## Step 1: Opt-in to a Local Zone +## Step 1: Enable a Local Zone @@ -26 +26 @@ To get started with AWS Local Zones, you must first opt-in to a Local Zone throu -You can use the AWS Global View console or a command line interface to determine which Local Zones are available for your account. Then opt in to the Local Zone that you want to use. +You can use the Amazon EC2 console or a command line interface to determine which Local Zones are available for your account, and then enable the Local Zone that you want to use. @@ -28 +28 @@ You can use the AWS Global View console or a command line interface to determine -AWS Global View console +###### To enable a Local Zone using the console @@ -29,0 +30 @@ AWS Global View console + 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). @@ -31,9 +32 @@ AWS Global View console -###### To opt in to a Local Zone - - 1. Sign in to the [AWS Global View console](https://console.aws.amazon.com/ec2globalview/home#RegionsAndZones). - - 2. From the navigation pane, choose **Regions and Zones**. - - 3. Choose the **Local Zones** tab. - - 4. Find the Local Zone that you want to enable. You can scroll down the list or enter a term in the Search field. + 2. From the navigation bar, choose the **Regions** selector and then choose the parent Region. @@ -41 +34 @@ AWS Global View console - 5. Select the row for the Local Zone. + 3. From the Amazon EC2 console dashboard, in the **Account attributes** box, choose **Zones**. @@ -43 +36 @@ AWS Global View console - 6. Choose **Opt-in**. + 4. (Optional) To filter the list of zones, choose the **All Zones** filter and then **Local Zones**. @@ -45 +38 @@ AWS Global View console - 7. You will be asked to enable the parent Region of the Local Zone. Choose **Enable Region**. + 5. Select the row of the Local Zone that you want to use. @@ -47 +40 @@ AWS Global View console - 8. On the **Enable Region** pop-up, choose **Enable Region**. + 6. Choose **Actions** , **Manage Zone group**. @@ -49 +42 @@ AWS Global View console - 9. From the **Local Zones** tab on the **Regions and Zones** page, select the Local Zone and choose **Opt-in**. + 7. On the **Manage zone group** pop-up, select **Enable**. @@ -51 +44 @@ AWS Global View console - 10. On the **Opt-in Zone group** pop-up, choose **Opt-in Zone group**. + 8. Choose **Update**. @@ -53 +46 @@ AWS Global View console -You can now use the Local Zone. + 9. To confirm that you want to enable the Local Zone, enter **Enable**. @@ -54,0 +48 @@ You can now use the Local Zone. + 10. Choose **Enable zone group**. @@ -58 +51,0 @@ You can now use the Local Zone. -AWS CLI @@ -59,0 +53 @@ AWS CLI +###### To enable a Local Zone using the AWS CLI @@ -61 +55 @@ AWS CLI -###### To opt in to a Local Zone +Use the [describe-availability-zones](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-availability-zones.html) command as follows to describe all Local Zones in the specified Region. @@ -63 +56,0 @@ AWS CLI - 1. Use the [describe-availability-zones](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-availability-zones.html) command as follows to describe all Local Zones in the specified Region. @@ -70 +63,2 @@ AWS CLI - 2. Use the [modify-availability-zone-group](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-availability-zone-group.html) command as follows to enable a specific Local Zone. +Use the [modify-availability-zone-group](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/modify-availability-zone-group.html) command as follows to enable a specific Local Zone. + @@ -84,4 +75 @@ When you add a subnet, you must specify an IPv4 CIDR block for the subnet from t -Console - - -###### To add a Local Zone subnet to a VPC +###### To add a Local Zone subnet to a VPC using the console @@ -114,4 +102 @@ Console -AWS CLI - - -###### To add a Local Zone subnet to a VPC +###### To add a Local Zone subnet to a VPC using the AWS CLI @@ -119 +104 @@ AWS CLI -Use the [create-subnet](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-subnet.html) command as follows to create a subnet for the specified VPC in the specified Local Zone. +Use the [create-subnet](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-subnet.html) command as follows to create a subnet for the specified VPC in the specified Local Zone. @@ -131,4 +116 @@ After you create a subnet in a Local Zone, you can deploy AWS resources in the L -Console - - -###### To launch an Amazon EC2 instance in a Local Zone subnet +###### To launch an Amazon EC2 instance in a Local Zone subnet using the console @@ -138,5 +120 @@ Console - 2. In the navigation pane, under **Instances** , choose **Instance Types**. - - 3. In the search field, choose **Availability zones** , choose **Contains** , and then enter the zone name (for example, `us-west-2-lax-1`.) Select the first item, or whichever item has just this zone ID and the Availability Zones for the parent Region. - - 4. Select one of the instance types, and then choose **Actions** , **Launch instance**. + 2. From the Amazon EC2 console dashboard, in the **Launch instance** box, choose **Launch instance**. @@ -144 +122 @@ Console - 5. Under **Name and tags** , enter a descriptive name for the instance (for example, _my-lz-instance_). Doing so creates a tag with a key of `Name` and the value that you specify. + 3. Under **Name and tags** , enter a descriptive name for the instance (for example, _my-lz-instance_). Doing so creates a tag with a key of `Name` and the value that you specify. @@ -146 +124 @@ Console - 6. Under **Application and OS Images (Amazon Machine Image)** , do the following: + 4. Under **Application and OS Images (Amazon Machine Image)** , do the following: @@ -154 +132,7 @@ Console - 7. Under **Key pair (login)** , choose an existing key pair or create a new one. This is required if you want to connect to your EC2 instance. + 5. Under **Instance type** , from the **Instance type** list, select the hardware configuration for your instance that's supported in a Local Zone. For example, the `t3.micro` instance type. + + 6. Under **Key pair (login)** , choose an existing key pair or create a new one. + +###### Warning + +Do not choose **Proceed without a key pair (Not recommended)**. If you launch your instance without a key pair, then you can't connect to it. @@ -156 +140 @@ Console - 8. Next to **Network settings** , choose **Edit** , and then: + 7. Next to **Network settings** , choose **Edit** , and then: @@ -166,11 +150 @@ Console - 9. You can keep the default selections for the other configuration settings for your instance. To determine the storage types that are supported, see the _Compute and storage_ section in [AWS Local Zones features](https://aws.amazon.com/about-aws/global-infrastructure/localzones/features/). - - 10. Review a summary of your instance configuration in the **Summary** panel, and when you're ready, choose **Launch instance**. - - 11. A confirmation page lets you know that your instance is launching. Choose **View all instances** to close the confirmation page and return to the console. - - 12. On the **Instances** screen, you can view the status of the launch. It takes a short time for an instance to launch. When you launch an instance, its initial state is `pending`. After the instance starts, its state changes to `running` and it receives a public DNS name. If the **Public IPv4 DNS** column is hidden, choose the settings icon (  ) in the top-right corner, turn on **Public IPv4 DNS** , and choose **Confirm**. - - 13. It can take a few minutes for the instance to be ready for you to connect to it. Check that your instance has passed its status checks; you can view this information in the **Status check** column. - - + 8. You can keep the default selections for the other configuration settings for your instance. To determine the storage types that are supported, see the _Compute and storage_ section in [AWS Local Zones features](https://aws.amazon.com/about-aws/global-infrastructure/localzones/features/). @@ -177,0 +152 @@ Console + 9. Review a summary of your instance configuration in the **Summary** panel, and when you're ready, choose **Launch instance**. @@ -179 +154 @@ Console -AWS CLI + 10. A confirmation page lets you know that your instance is launching. Choose **View all instances** to close the confirmation page and return to the console. @@ -180,0 +156 @@ AWS CLI + 11. On the **Instances** screen, you can view the status of the launch. It takes a short time for an instance to launch. When you launch an instance, its initial state is `pending`. After the instance starts, its state changes to `running` and it receives a public DNS name. If the **Public IPv4 DNS** column is hidden, choose the settings icon (  ) in the top-right corner, turn on **Public IPv4 DNS** , and choose **Confirm**. @@ -182 +158 @@ AWS CLI -###### To get the instance types supported in a Local Zone + 12. It can take a few minutes for the instance to be ready for you to connect to it. Check that your instance has passed its status checks; you can view this information in the **Status check** column. @@ -184 +159,0 @@ AWS CLI -Use the [describe-instance-types](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-types.html) command. @@ -187,4 +161,0 @@ Use the [describe-instance-types](https://docs.aws.amazon.com/cli/latest/referen - aws ec2 describe-instance-type-offerings \ - --filters Name=location,Values=us-west-2-lax-1a \ - --location-type availability-zone \ - --query InstanceTypeOfferrings[*].InstanceType @@ -192 +163 @@ Use the [describe-instance-types](https://docs.aws.amazon.com/cli/latest/referen -###### To launch an EC2 instance in a Local Zone subnet +###### To launch an EC2 instance in a Local Zone subnet using the AWS CLI @@ -194 +165 @@ Use the [describe-instance-types](https://docs.aws.amazon.com/cli/latest/referen -Use the [run-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command. +Use the [run-instances](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/run-instances.html) command as follows to launch an instance in the specified Local Zone subnet. @@ -207 +178 @@ Use the [run-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run -When you are finished with a Local Zone, delete the resources in the Local Zone. To disable a zone group, you must contact AWS Support. Open a case titled "Disable zone group" and provide the name of the zone group. +When you are finished with a Local Zone, delete the resources in the Local Zone. Then contact AWS Support to disable it.