AWS local-zones documentation change
Summary
Updated terminology from 'Enable' to 'Opt-in' for Local Zones. Changed console navigation from Amazon EC2 to AWS Global View. Added detailed steps for opting in via console/CLI, launching EC2 instances in Local Zones, and disabling zone groups. Enhanced instance type discovery and subnet creation instructions.
Security assessment
Changes are procedural updates for feature access and resource management. No security vulnerabilities, patches, or security-specific features are mentioned. The key pair mention is standard operational guidance, not new security documentation.
Diff
diff --git a/local-zones/latest/ug/getting-started.md b/local-zones/latest/ug/getting-started.md index 03b69c2e2..037efff1f 100644 --- a//local-zones/latest/ug/getting-started.md +++ b//local-zones/latest/ug/getting-started.md @@ -5 +5 @@ -Step 1: Enable a Local ZoneStep 2: Create a Local Zone subnetStep 3: Create a resource in your Local Zone subnetStep 4: Clean up +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 @@ -9 +9 @@ Step 1: Enable a Local ZoneStep 2: Create a Local Zone subnetStep 3: Create a re -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. +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. @@ -13 +13 @@ To get started with AWS Local Zones, you must first enable a Local Zone through - * Step 1: Enable a Local Zone + * Step 1: Opt-in to a Local Zone @@ -24 +24 @@ To get started with AWS Local Zones, you must first enable a Local Zone through -## Step 1: Enable a Local Zone +## Step 1: Opt-in to a Local Zone @@ -26 +26 @@ To get started with AWS Local Zones, you must first enable a Local Zone through -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. +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. @@ -28 +28 @@ You can use the Amazon EC2 console or a command line interface to determine whic -###### To enable a Local Zone using the console +AWS Global View console @@ -30 +29,0 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). @@ -32 +31,5 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 2. From the navigation bar, choose the **Regions** selector and then choose the parent Region. +###### 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**. @@ -34 +37 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 3. From the Amazon EC2 console dashboard, in the **Account attributes** box, choose **Zones**. + 3. Choose the **Local Zones** tab. @@ -36 +39 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 4. (Optional) To filter the list of zones, choose the **All Zones** filter and then **Local Zones**. + 4. Find the Local Zone that you want to enable. You can scroll down the list or enter a term in the Search field. @@ -38 +41 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 5. Select the row of the Local Zone that you want to use. + 5. Select the row for the Local Zone. @@ -40 +43 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 6. Choose **Actions** , **Manage Zone group**. + 6. Choose **Opt-in**. @@ -42 +45 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 7. On the **Manage zone group** pop-up, select **Enable**. + 7. You will be asked to enable the parent Region of the Local Zone. Choose **Enable Region**. @@ -44 +47 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 8. Choose **Update**. + 8. On the **Enable Region** pop-up, choose **Enable Region**. @@ -46 +49 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 9. To confirm that you want to enable the Local Zone, enter **Enable**. + 9. From the **Local Zones** tab on the **Regions and Zones** page, select the Local Zone and choose **Opt-in**. @@ -48 +51 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 10. Choose **Enable zone group**. + 10. On the **Opt-in Zone group** pop-up, choose **Opt-in Zone group**. @@ -49,0 +53 @@ You can use the Amazon EC2 console or a command line interface to determine whic +You can now use the Local Zone. @@ -53 +56,0 @@ You can use the Amazon EC2 console or a command line interface to determine whic -###### To enable a Local Zone using the AWS CLI @@ -55 +58 @@ You can use the Amazon EC2 console or a command line interface to determine whic -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. +AWS CLI @@ -57,0 +61,4 @@ Use the [describe-availability-zones](https://awscli.amazonaws.com/v2/documentat +###### To opt in to a Local Zone + + 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. + @@ -63,2 +70 @@ Use the [describe-availability-zones](https://awscli.amazonaws.com/v2/documentat -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. - + 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. @@ -75 +84,4 @@ When you add a subnet, you must specify an IPv4 CIDR block for the subnet from t -###### To add a Local Zone subnet to a VPC using the console +Console + + +###### To add a Local Zone subnet to a VPC @@ -102 +114,4 @@ When you add a subnet, you must specify an IPv4 CIDR block for the subnet from t -###### To add a Local Zone subnet to a VPC using the AWS CLI +AWS CLI + + +###### To add a Local Zone subnet to a VPC @@ -104 +119 @@ When you add a subnet, you must specify an IPv4 CIDR block for the subnet from t -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. +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. @@ -116 +131,4 @@ After you create a subnet in a Local Zone, you can deploy AWS resources in the L -###### To launch an Amazon EC2 instance in a Local Zone subnet using the console +Console + + +###### To launch an Amazon EC2 instance in a Local Zone subnet @@ -120 +138,5 @@ After you create a subnet in a Local Zone, you can deploy AWS resources in the L - 2. From the Amazon EC2 console dashboard, in the **Launch instance** box, choose **Launch instance**. + 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**. @@ -122 +144 @@ After you create a subnet in a Local Zone, you can deploy AWS resources in the L - 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. + 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. @@ -124 +146 @@ After you create a subnet in a Local Zone, you can deploy AWS resources in the L - 4. Under **Application and OS Images (Amazon Machine Image)** , do the following: + 6. Under **Application and OS Images (Amazon Machine Image)** , do the following: @@ -132,7 +154 @@ After you create a subnet in a Local Zone, you can deploy AWS resources in the L - 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. + 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. @@ -140 +156 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo - 7. Next to **Network settings** , choose **Edit** , and then: + 8. Next to **Network settings** , choose **Edit** , and then: @@ -150 +166,11 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo - 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/). + 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. + + @@ -152 +177,0 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo - 9. Review a summary of your instance configuration in the **Summary** panel, and when you're ready, choose **Launch instance**. @@ -154 +179 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo - 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. +AWS CLI @@ -156 +180,0 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo - 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**. @@ -158 +182 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo - 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. +###### To get the instance types supported in a Local Zone @@ -159,0 +184 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo +Use the [describe-instance-types](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-types.html) command. @@ -161,0 +187,4 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo + aws ec2 describe-instance-type-offerings \ + --filters Name=location,Values=us-west-2-lax-1a \ + --location-type availability-zone \ + --query InstanceTypeOfferrings[*].InstanceType @@ -163 +192 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo -###### To launch an EC2 instance in a Local Zone subnet using the AWS CLI +###### To launch an EC2 instance in a Local Zone subnet @@ -165 +194 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo -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. +Use the [run-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command. @@ -178 +207 @@ Use the [run-instances](https://awscli.amazonaws.com/v2/documentation/api/latest -When you are finished with a Local Zone, delete the resources in the Local Zone. Then contact AWS Support to disable it. +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.