AWS ebs: NVMe reservations now supported on Multi-Attach io1 volumes
Summary
Extends NVMe reservation (storage fencing) support documentation from Multi-Attach io2 volumes to also include Multi-Attach io1 volumes, including default enablement dates and reattach procedure for existing volumes.
Security assessment
The change documents that NVMe reservations (storage fencing protocols that control and coordinate multi-instance access to shared volumes) are now available for io1 volumes. This is access-coordination/data-consistency guidance rather than a fix for a specific vulnerability, so it is security-adjacent documentation only.
Evidence
+Multi-Attach enabled `io1` and `io2` volumes support NVMe reservations, which is a set of industry-standard storage fencing protocols. These protocols enable you to create and manage reservations that control and coordinate access from multiple instances to a shared volume. Shared storage applications use reservations to make sure that data remains consistent.
Diff
diff --git a/ebs/latest/userguide/nvme-reservations.md b/ebs/latest/userguide/nvme-reservations.md index 5e66236..3c88094 100644 --- a//ebs/latest/userguide/nvme-reservations.md +++ b//ebs/latest/userguide/nvme-reservations.md @@ -11 +11 @@ RequirementsEnabling support for NVMe reservationsSupported NVMe Reservation com -Multi-Attach enabled `io2` volumes support NVMe reservations, which is a set of industry-standard storage fencing protocols. These protocols enable you to create and manage reservations that control and coordinate access from multiple instances to a shared volume. Shared storage applications use reservations to make sure that data remains consistent. +Multi-Attach enabled `io1` and `io2` volumes support NVMe reservations, which is a set of industry-standard storage fencing protocols. These protocols enable you to create and manage reservations that control and coordinate access from multiple instances to a shared volume. Shared storage applications use reservations to make sure that data remains consistent. @@ -28 +28 @@ Multi-Attach enabled `io2` volumes support NVMe reservations, which is a set of -NVMe reservations is supported with Multi-Attach enabled `io2` volumes only. Multi-Attach enabled volumes can be attached only to instances built on the Nitro system. +NVMe reservations is supported with Multi-Attach enabled `io1` and `io2` volumes. Multi-Attach enabled volumes can be attached only to instances built on the Nitro system. @@ -51 +51 @@ If you're using EC2Launch v2 to initialize your disks, you must upgrade to versi -Support for NVMe reservations is enabled by default for all Multi-Attach enabled `io2` volumes created after **September 18, 2023**. +Support for NVMe reservations is enabled by default for all Multi-Attach enabled `io2` volumes created after **September 18, 2023** , and for all Multi-Attach enabled `io1` volumes created after **October 1, 2026**. @@ -53 +53 @@ Support for NVMe reservations is enabled by default for all Multi-Attach enabled -To enable support for NVMe reservations for existing `io2` volumes created before September 18, 2023, you must detach all instances from the volume and then reattach the required instances. All attachments made after detaching all of the instances will have NVMe reservations enabled. +To enable support for NVMe reservations for existing `io2` volumes created before September 18, 2023, or existing `io1` volumes created before October 1, 2026, you must detach all instances from the volume and then reattach the required instances. All attachments made after detaching all of the instances will have NVMe reservations enabled.