AWS AWSEC2 documentation change
Summary
Updated terminology from 'root device volume' to 'root volume' and clarified instance store root volume requirements in recovery procedures
Security assessment
The changes appear to be terminology standardization (device -> volume) and clarification of existing recovery procedures. No specific security vulnerabilities are addressed, though the documentation emphasizes the security requirement of needing private keys for instance store root volumes. This is a routine documentation improvement rather than a direct security fix.
Diff
diff --git a/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.md b/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.md index 843564acd..618c959ef 100644 --- a//AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.md +++ b//AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.md @@ -620 +620 @@ If you lose the private key for an EBS-backed instance, you can regain access to -This procedure is only supported for instances with EBS root volumes. If the root device is an instance store volume, you cannot use this procedure to regain access to your instance; you must have the private key to connect to the instance. To determine the root device type of your instance, open the Amazon EC2 console, choose **Instances** , select the instance, choose the **Storage** tab, and in the **Root device details** section, check the value of **Root device type**. +This procedure is only supported for instances with EBS root volumes. If the instance has an instance store root volume, you cannot use this procedure to regain access to your instance; you must have the private key to connect to the instance. To determine the root volume type of your instance, open the Amazon EC2 console, choose **Instances** , select the instance, choose the **Storage** tab, and in the **Root device details** section, check the value of **Root device type**. @@ -674 +674 @@ Make note of the following information because you'll need it to complete this p -Choose **Instance state** , **Stop instance**. If this option is disabled, either the instance is already stopped or its root device is an instance store volume. +Choose **Instance state** , **Stop instance**. If this option is disabled, either the instance is already stopped or its root volume is an instance store volume. @@ -703 +703 @@ When you stop an instance, the data on any instance store volumes is erased. To - 1. In the navigation pane, choose **Volumes** and select the root device volume for the original instance (you made note of its volume ID in a previous step). Choose **Actions** , **Detach volume** , and then choose **Detach**. Wait for the state of the volume to become `available`. (You might need to choose the Refresh icon.) + 1. In the navigation pane, choose **Volumes** and select the root volume for the original instance (you made note of its volume ID in a previous step). Choose **Actions** , **Detach volume** , and then choose **Detach**. Wait for the state of the volume to become `available`. (You might need to choose the Refresh icon.) @@ -793 +793 @@ If the user ID and group ID have changed, use the following command to restore t - 2. Detach the volume from the temporary instance (you unmounted it in the previous step): From the Amazon EC2 console, choose **Volumes** in the navigation pane, select the root device volume for the original instance (you made note of the volume ID in a previous step), choose **Actions** , **Detach volume** , and then choose **Detach**. Wait for the state of the volume to become `available`. (You might need to choose the Refresh icon.) + 2. Detach the volume from the temporary instance (you unmounted it in the previous step): From the Amazon EC2 console, choose **Volumes** in the navigation pane, select the root volume for the original instance (you made note of the volume ID in a previous step), choose **Actions** , **Detach volume** , and then choose **Detach**. Wait for the state of the volume to become `available`. (You might need to choose the Refresh icon.) @@ -795 +795 @@ If the user ID and group ID have changed, use the following command to restore t - 3. Reattach the volume to the original instance: With the volume still selected, choose **Actions** , **Attach volume**. Select the instance ID of the original instance, specify the device name that you noted earlier in Step 2 for the original root device attachment (`/dev/sda1` or `/dev/xvda`), and then choose **Attach volume**. + 3. Reattach the volume to the original instance: With the volume still selected, choose **Actions** , **Attach volume**. Select the instance ID of the original instance, specify the device name that you noted earlier in Step 2 for the original root volume attachment (`/dev/sda1` or `/dev/xvda`), and then choose **Attach volume**. @@ -799 +799 @@ If the user ID and group ID have changed, use the following command to restore t -If you don't specify the same device name as the original attachment, you cannot start the original instance. Amazon EC2 expects the root device volume at `sda1` or `/dev/xvda`. +If you don't specify the same device name as the original attachment, you cannot start the original instance. Amazon EC2 expects the root volume at `sda1` or `/dev/xvda`.