AWS AWSEC2 documentation change
Summary
Updated terminology from 'Amazon EBS-backed instances' to 'Instances with an Amazon EBS root volume' and 'instance store-backed instances' to 'Instances with an instance store root volume'. Changed references from 'instance store-backed AMI' to 'Amazon S3-backed AMI' for Linux instances.
Security assessment
The changes are primarily terminology updates and clarifications about root volume types. There is no mention of vulnerabilities, security incidents, or new security controls. The existing security implications (data persistence differences between EBS/instance store) remain unchanged from previous documentation.
Diff
diff --git a/AWSEC2/latest/UserGuide/RootDeviceStorage.md b/AWSEC2/latest/UserGuide/RootDeviceStorage.md index 59cafc560..01abb2077 100644 --- a//AWSEC2/latest/UserGuide/RootDeviceStorage.md +++ b//AWSEC2/latest/UserGuide/RootDeviceStorage.md @@ -5 +5 @@ -Amazon EBS-backed instancesInstance store-backed instances (Linux instances only) +Instances with an Amazon EBS root volumeInstances with an instance store root volume (Linux instances only) @@ -11 +11 @@ When you launch an instance, we create a _root volume_ for the instance. The roo -The AMI that you use to launch an instance determines the type of root volume. You can launch an instance from either an _Amazon EBS-backed AMI_ (Linux and Windows instances) or an _instance store-backed AMI_ (Linux instances only). There are significant differences between what you can do with each type of AMI. For more information about these differences, see [Root device type](./ComponentsAMIs.html#storage-for-the-root-device). +The AMI that you use to launch an instance determines the type of root volume. You can launch an instance from either an _Amazon EBS-backed AMI_ (Linux and Windows instances) or an _Amazon S3-backed AMI_ (Linux instances only). There are significant differences between what you can do with each type of AMI. For more information about these differences, see [Root volume type](./ComponentsAMIs.html#storage-for-the-root-device). @@ -19 +19 @@ We reserve specific device names for root volumes. For more information, see [De - * Amazon EBS-backed instances + * Instances with an Amazon EBS root volume @@ -21 +21 @@ We reserve specific device names for root volumes. For more information, see [De - * Instance store-backed instances (Linux instances only) + * Instances with an instance store root volume (Linux instances only) @@ -30 +30 @@ We reserve specific device names for root volumes. For more information, see [De -## Amazon EBS-backed instances +## Instances with an Amazon EBS root volume @@ -32 +32 @@ We reserve specific device names for root volumes. For more information, see [De -Instances that use Amazon EBS for the root volume automatically have an Amazon EBS volume attached. When you launch an Amazon EBS-backed instance, we create an Amazon EBS volume for each Amazon EBS snapshot referenced by the AMI you use. You can optionally use other Amazon EBS volumes or instance store volumes, depending on the instance type. +Instances that use Amazon EBS for the root volume automatically have an Amazon EBS volume attached. When you launch an instance with an Amazon EBS-AMI, we create an Amazon EBS volume for each Amazon EBS snapshot referenced by the AMI. You can optionally use other Amazon EBS volumes or instance store volumes, depending on the instance type. @@ -34 +34 @@ Instances that use Amazon EBS for the root volume automatically have an Amazon E -An Amazon EBS-backed instance can be stopped and later restarted without affecting data stored in the attached volumes. There are various instance– and volume-related tasks you can do when an Amazon EBS-backed instance is in a stopped state. For example, you can modify the properties of the instance, change its size, or update the kernel it is using, or you can attach your root volume to a different running instance for debugging or any other purpose. For more information, see [Amazon EBS volumes](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes.html). +An instance with an EBS root volume can be stopped and later restarted without affecting data stored in the attached volumes. There are various instance– and volume-related tasks you can do when an instance with an EBS root volume is in a stopped state. For example, you can modify the properties of the instance, change its size, or update the kernel it is using, or you can attach its root volume to a different running instance for debugging or any other purpose. For more information, see [Amazon EBS volumes](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes.html). @@ -36 +36 @@ An Amazon EBS-backed instance can be stopped and later restarted without affecti - + @@ -44 +44 @@ You can't use `st1` or `sc1` EBS volumes as root volumes. -If an Amazon EBS-backed instance fails, you can restore your session by following one of these methods: +If an instance with an EBS root volume fails, you can restore your session by following one of these methods: @@ -65 +65 @@ If an Amazon EBS-backed instance fails, you can restore your session by followin -## Instance store-backed instances (Linux instances only) +## Instances with an instance store root volume (Linux instances only) @@ -69 +69 @@ If an Amazon EBS-backed instance fails, you can restore your session by followin -Windows instances do not support instance-store backed root volumes. +Windows instances do not support instance store root volumes. @@ -71 +71 @@ Windows instances do not support instance-store backed root volumes. -Instances that use instance stores for the root volume automatically have one or more instance store volumes available, with one volume serving as the root volume. When an instance is launched, the image that is used to boot the instance is copied to the root volume. Note that you can optionally use additional instance store volumes, depending on the instance type. +Instances that use instance store for the root volume automatically have one or more instance store volumes available, with one volume serving as the root volume. When an instance is launched from an Amazon S3-backed AMI, the AMI is copied to the root volume. Note that you can optionally use additional instance store volumes, depending on the instance type. @@ -73 +73 @@ Instances that use instance stores for the root volume automatically have one or -Any data on the instance store volumes persists as long as the instance is running, but this data is deleted when the instance is terminated (instance store-backed instances do not support the **Stop** action) or if it fails (such as if an underlying drive has issues). For more information, see [Instance store temporary block storage for EC2 instances](./InstanceStorage.html). +Any data on the instance store volumes persists as long as the instance is running, but this data is deleted when the instance is terminated (instances with an instance store root volume do not support the **Stop** action) or if it fails (such as if an underlying drive has issues). For more information, see [Instance store temporary block storage for EC2 instances](./InstanceStorage.html). @@ -75 +75 @@ Any data on the instance store volumes persists as long as the instance is runni - + @@ -83 +83 @@ Only the following instance types support an instance store volume as the root v -After an instance store-backed instance fails or terminates, it cannot be restored. If you plan to use Amazon EC2 instance store-backed instances, we highly recommend that you distribute the data on your instance stores across multiple Availability Zones. You should also back up critical data from your instance store volumes to persistent storage on a regular basis. +After an instance with an instance store root volume fails or terminates, it can't be restored. If you plan to use an instances with an instance store root volume, we highly recommend that you distribute the data on your instance store volumes across multiple Availability Zones. You should also back up critical data from your instance store volumes to persistent storage on a regular basis.