$DiskNumber = (Get-Disk -Path $Path).Number $Device = ((Get-EC2Volume -VolumeId $EbsVolumeId ).Attachment).Device $EbsVolumeId = $SerialNumber.Substring(0,20).Replace('AWS','AWS-') $EbsVolumeId = $SerialNumber.Substring(0,20).Replace('vol','vol-') $SerialNumber = (Get-Disk -Path $Path).SerialNumber For more information, see Upgrade PV drivers on Windows instances. Your Windows AMI uses Red Hat PV drivers, you can update your instance to use the Citrixĭrivers. If you launch an instanceįrom a Windows AMI that uses AWS PV or Citrix PV drivers, you can use the relationshipsĭescribed on this page to map your Windows disks to your instance store and EBS volumes. Instance store and EBS volumes to Windows disks and drive letters. Windows Amazon Machine Images (AMIs) contain a set of drivers that are used by Amazon EC2 to map More information, see Device names on Windows instances. When you add a volume to your instance, you specify the device name that Amazon EC2 uses. For more information, see Make an Amazon EBS volume available for use on Instance, or attach them while your instance is running.

You can also add EBS volumes when you create your AMI or launch your That are available to your instance, you must specify them when you create your AMI or Instance store volumes available to the instance. For more information, see Instance volume limits.ĭepending on the instance type of your instance, you'll have from 0 to 24 possible

Windows instance uses AWS PV or Citrix PV drivers, you can optionally add up to 25 Your Windows instance comes with an EBS volume that serves as the root volume.

Amazon windows 3.1 setup disk