I can't see secondary volumes when using an EC2 Windows Server 2016 instance. How do I resolve this?

New Windows Server 2016 instances launched from EC2 Windows Server 2016 AMIs do not initialize secondary volumes on launch. This is the default behavior of EC2Launch. EC2Launch is a bundle of Windows PowerShell scripts that perform instance startup tasks. You can schedule the script to run on every boot with the following AWS PowerShell command:

C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\InitializeDisks.ps1 –Schedule

Note: The disk initialization script will execute each time the instance boots.

You can also initialize attached disks at the instance launch by adding the following path to the PowerShell script in Amazon EC2 UserData:

<powershell>

C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\InitializeDisks.ps1

</powershell>

 

For more information on initializing disks on Windows Server 2016, see Initialize Drives and Drive Letter Mappings.

EC2, Windows, EBS


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-11-11