Which solution will provide the LEAST disruption with MINIMAL effort?
Create a snapshot and restore it to a larger gp2 volume.
Create a RAID 0 with another new gp2 volume to increase capacity.
Leverage the Elastic Volumes feature of EBS to increase gp2 volume size.
Write a script to migrate data to a larger gp2 volume.
Explanations:
Creating a snapshot and restoring to a larger volume involves downtime, which increases disruption. The process also requires manual effort and time.
Creating a RAID 0 array adds complexity and does not directly address the underlying issue of volume space. RAID configurations are not ideal for simplicity.
Elastic Volumes allow for seamless resizing of EBS volumes with minimal disruption and no downtime, making it the most efficient solution with minimal effort.
Writing a script to migrate data requires more manual effort and increases complexity compared to using Elastic Volumes, making it a more disruptive solution.
I infer that the answer is:
Leverage the Elastic Volumes feature of EBS to increase gp2 volume size.