Amazon EBS and NVMe
EBS volumes are exposed as NVMe block devices on Nitro-based instances.
Note
The EBS performance guarantees stated in Amazon EBS Product Details are valid regardless of the block-device interface.
Some of these instance types also support NVMe instance store volumes. For more information, see NVMe SSD Volumes.
Identifying the EBS Device
EBS uses single-root I/O virtualization (SR-IOV) to provide volume attachments on Nitro-based instances using the NVMe specification. These devices rely on standard NVMe drivers on the operating system. These drivers typically discover attached devices by scanning the PCI bus during instance boot, and create device nodes based on the order in which the devices respond, not on how the devices are specified in the block device mapping.
Windows Server 2008 R2 and Later
You can also run the ebsnvme-id command to map the NVMe device disk number to an EBS volume ID and device name.
By default, all EBS NVMe devices are enumerated. You can pass a disk number to enumerate
information for a specific device.
You can download ebsnvme-id.zip and extract the contents to your Amazon EC2 instance to get access to ebsnvme-id.exe.
PS C:\Users\Administrator\Desktop> ebsnvme-id.exe Disk Number: 0 Volume ID: vol-0d6d7ee9f6e471a7f Device Name: sda1 Disk Number: 1 Volume ID: vol-03a26248ff39b57cf Device Name: xvdd Disk Number: 2 Volume ID: vol-038bd1c629aa125e6 Device Name: xvde Disk Number: 3 Volume ID: vol-034f9d29ec0b64c89 Device Name: xvdb Disk Number: 4 Volume ID: vol-03e2dbe464b66f0a1 Device Name: xvdc PS C:\Users\Administrator\Desktop> ebsnvme-id.exe 4 Disk Number: 4 Volume ID: vol-03e2dbe464b66f0a1 Device Name: xvdc
Working with NVMe EBS Volumes
The latest AWS Windows AMIs contain the AWS NVMe driver that is required by instance types that expose EBS volumes as NVMe block devices. However, if you resize your root volume on a Windows system, you must rescan the volume in order for this change to be reflected in the instance. If you launched your instance from a different AMI, it might not contain the required AWS NVMe driver. If your instance does not have the latest AWS NVMe driver, you must install it. For more information, see AWS NVMe Drivers for Windows Instances.
I/O Operation Timeout
Most operating systems specify a timeout for I/O operations submitted to
NVMe devices. On Windows systems, the default timeout is 60 seconds and the maximum
is
255 seconds. You can modify the TimeoutValue disk class registry setting
using the procedure described in Registry Entries for SCSI Miniport Drivers.
