A user increased the size of an EBS volume attached to a Windows EC2 instance from the EC2 console, but the instance's file system still shows the old capacity. What must a SysOps administrator do to make the extra space usable by the OS?

When an EBS volume's size is increased from the EC2 console, the underlying block device is expanded, but the operating system's file system does not automatically recognize this change. The SysOps administrator must manually extend the file system within the Windows operating system. This is typically done using Disk Management or the diskpart command-line utility to expand the partition to fill the newly available space. Detaching and reattaching the volume, or rebooting the instance, will not extend the file system; these actions only re-establish the connection or restart the OS, not reconfigure the partition layout. Snapshotting and replacing the volume is an overly complex and unnecessary step, as the existing volume can be extended in place.