AWS local-zones documentation change
Summary
Restructured documentation for enabling Local Zones and launching EC2 instances, updated console navigation steps, added CLI command examples, and clarified instance type selection requirements.
Security assessment
Changes focus on procedural improvements and documentation structure rather than addressing security vulnerabilities. The key pair requirement warning remains similar to previous guidance about secure access practices, but does not introduce new security features or address specific vulnerabilities.
Diff
diff --git a/local-zones/latest/ug/getting-started.md b/local-zones/latest/ug/getting-started.md index 03b69c2e2..86d5acda7 100644 --- a//local-zones/latest/ug/getting-started.md +++ b//local-zones/latest/ug/getting-started.md @@ -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. +First, enable the Local Zone that you want to use. @@ -28 +28,4 @@ You can use the Amazon EC2 console or a command line interface to determine whic -###### To enable a Local Zone using the console +Console + + +###### To enable a Local Zone @@ -34,3 +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**. - - 4. (Optional) To filter the list of zones, choose the **All Zones** filter and then **Local Zones**. + 3. From the Amazon EC2 console dashboard, in the **Account attributes** pane, under **Settings** , choose **Zones**. @@ -38 +39 @@ 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. + 4. (Optional) To filter the list of zones, choose the **All Zones** filter and then choose **Local Zones**. @@ -40 +41 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 6. Choose **Actions** , **Manage Zone group**. + 5. Select the Local Zone. @@ -42 +43 @@ 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**. + 6. Choose **Actions** , **Opt in**. @@ -44 +45 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 8. Choose **Update**. + 7. When prompted for confirmation, enter `Enable` and then choose **Enable zone group**. @@ -46 +46,0 @@ 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**. @@ -48 +47,0 @@ You can use the Amazon EC2 console or a command line interface to determine whic - 10. Choose **Enable zone group**. @@ -50,0 +50 @@ You can use the Amazon EC2 console or a command line interface to determine whic +AWS CLI @@ -53 +53 @@ You can use the Amazon EC2 console or a command line interface to determine whic -###### To enable a Local Zone using the AWS CLI +###### To enable a Local Zone @@ -75 +75,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 +105,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 @@ -114 +120,5 @@ Use the [create-subnet](https://awscli.amazonaws.com/v2/documentation/api/latest -After you create a subnet in a Local Zone, you can deploy AWS resources in the Local Zone. For example, the following procedure shows how to launch an Amazon EC2 instance in a Local Zone. +After you create a subnet in a Local Zone, you can deploy AWS resources in the Local Zone. + +The following example shows how to select a supported instance type and then launch an Amazon EC2 instance in a Local Zone using that instance type. + +Console @@ -116 +126,2 @@ 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 + +###### To launch an Amazon EC2 instance in a Local Zone subnet @@ -120 +131,3 @@ 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. @@ -122 +135 @@ 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. + 4. Select one of the instance types, and then choose **Actions** , **Launch instance**. @@ -124 +137,3 @@ 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: + 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. + + 6. Under **Application and OS Images (Amazon Machine Image)** , do the following: @@ -132,5 +147 @@ 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 + 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. @@ -138,3 +149 @@ After you create a subnet in a Local Zone, you can deploy AWS resources in the L -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. Next to **Network settings** , choose **Edit** , and then: + 8. Next to **Network settings** , choose **Edit** , and then: @@ -150 +159,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 +170,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 +172 @@ 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 +173,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 +175 @@ 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 +177 @@ Do not choose **Proceed without a key pair (Not recommended)**. If you launch yo +Use the [describe-instance-types](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-instance-types.html) command. @@ -161,0 +180,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 +185 @@ 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 +187 @@ 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://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/run-instances.html) command. @@ -178 +200 @@ 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.