CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2
StackOverflowFan
StackOverflowFan

Reputation: 149

After attaching a volume to Windows 2016 instance thru AWS mangement console, I can't find it when I remote into the windows server?

I was able to create a new volume (attached pic). It says successfully attached to the windows 2016 instance. But when I RDP into that windows server, I only see "C" drive but not the newly attached volume. How do I see that ?

Attached volume from AWS console

Upvotes: 1

Views: 586

Answers (2)

Mallik Mallesh
Mallik Mallesh

Reputation: 1

Step1: Open the C:\ProgramData\Amazon\EC2- Windows\Launch\Config\DriveLetterMappingConfig.json file in a text editor.

Step2: update values: "volumeName": "Volume Name", "driveLetter": "D"

Step3: RUN Below Command PS C:> C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\InitializeDisks.ps1

Upvotes: 0

Ryan
Ryan

Reputation: 6517

Windows Server 2016 instances inside EC2 don't initialize secondary volumes at launch.

According to the link above, running the following command will cause it to do so every time the instance reboots:

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

See also: Configuring a Windows Instance Using EC2Launch

Upvotes: 2

Related Questions