This should work. We have had to do the same process to increase the size of some of our AWS EBS disk sets.

Also, for AWS we have decided it is easiest to manage our EBS volumes if we do not stripe a Windows volume over multiple EBS disks, but instead have a 1 to 1 mapping between Windows volumes and EBS disks. Where we need more IO than EBS provides by default, we use Provisioned IOPS.

This approach has the advantage that if we need to increase volume size we can use an EBS Snapshot to copy the data and folder structure to a new EBS volume, which is a lot easier than rebuilding a Windows stripe set. Also, if we over-provision or under-provision the IOPS it is a lot easier to change when doing things this way.

The only downside so far is this gives a 1TB limit on volume size, which has meant in a few cases we had to relocate the data files of a large database to a new drive letter. However, the simplification of management from using a 1 to 1 mapping made the effort of relocating the database worth while.