AWS ebs medium security documentation change
Summary
Updated EBS volume attachment requirements and limitations, including instance type limits, Multi-Attach capabilities, AWS Marketplace product code handling, and device naming behavior
Security assessment
Removed explicit requirement that encrypted volumes must be attached to instances supporting EBS encryption. This omission could lead users to inadvertently attach encrypted volumes to unsupported instances, potentially compromising encryption security.
Diff
diff --git a/ebs/latest/userguide/ebs-attaching-volume.md b/ebs/latest/userguide/ebs-attaching-volume.md index 348f8bc82..27b83286c 100644 --- a//ebs/latest/userguide/ebs-attaching-volume.md +++ b//ebs/latest/userguide/ebs-attaching-volume.md @@ -13 +13 @@ For information about adding EBS volumes to your instance at launch, see [instan - * You must attach a volume to an instance in the same Availability Zone as the volume. + * The maximum number of Amazon EBS volumes that you can attach to an instance depends on the instance type. If you exceed the volume attachment limit for an instance type, the attachment request fails with the `AttachmentLimitExceeded` error. For more information, see [Instance volume limits](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/volume_limits.html). @@ -15 +15 @@ For information about adding EBS volumes to your instance at launch, see [instan - * The volume must be in the `Available` state. + * You can attach volumes to instances that are in the same Availability Zone only. @@ -17 +17 @@ For information about adding EBS volumes to your instance at launch, see [instan - * If the volume is encrypted, it can only be attached to instance types that support Amazon EBS encryption. For more information, see [Amazon EBS encryption](./ebs-encryption.html). + * Multi-Attach enabled volumes can be attached to up to 16 instances. For more information, see [Attach an EBS volume to multiple EC2 instances using Multi-Attach](./ebs-volumes-multi.html). @@ -19 +19 @@ For information about adding EBS volumes to your instance at launch, see [instan - * Determine how many volumes you can attach to your instance. The maximum number of Amazon EBS volumes that you can attach to an instance depends on the instance type and instance size. If you attempt to attach a number of volumes that exceeds the instance type's volume limit, the request fails. For more information, see [Instance volume limits](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/volume_limits.html). + * If the volume has an AWS Marketplace product code: @@ -21,7 +21 @@ For information about adding EBS volumes to your instance at launch, see [instan - * Determine whether you can attach your volume to multiple instances and enable Multi-Attach. For more information, see [Attach an EBS volume to multiple EC2 instances using Multi-Attach](./ebs-volumes-multi.html). - - * If a volume is encrypted, you can attach it only to an instance that supports Amazon EBS encryption. For more information, see [Supported instance types](./ebs-encryption-requirements.html#ebs-encryption_supported_instances). - - * If a volume has an AWS Marketplace product code: - - * You can attach a volume only to a stopped instance. + * You can attach it to a stopped instance only. @@ -33 +27 @@ For information about adding EBS volumes to your instance at launch, see [instan - * AWS Marketplace product codes are copied from the volume to the instance. + * AWS Marketplace codes are copied from the volume to the instance. @@ -35 +29,3 @@ For information about adding EBS volumes to your instance at launch, see [instan - * In some situations, you might find that a volume other than the volume attached to `/dev/xvda` or `/dev/sda` has become the root volume of your instance. This can happen when you have attached the root volume of another instance, or a volume created from the snapshot of a root volume, to an instance with an existing root volume. For more information, see [Boot from the wrong volume](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-booting-from-wrong-volume.html). + * This device name you specify is used by Amazon EC2. The block device driver can mount the device with a device name that is different from the one you specify. For more information, see [Device names for volumes on Amazon EC2 instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html). + + * In some cases, a volume other than the volume attached to `/dev/xvda` or `/dev/sda` can become the root volume for the instance. This can happen if you attach the root volume of another instance, or a volume created from the snapshot of a root volume, to an instance with an existing root volume. For more information, see [ Boot from the wrong volume](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-booting-from-wrong-volume.html). @@ -61,2 +56,0 @@ Console -This device name is used by Amazon EC2. The block device driver for the instance might assign a different device name when mounting the volume. For more information, see [device names on Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html) or [device names for volumes on EC2 instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html). -