AWS Documentation » Amazon EC2 » User Guide for Linux Instances » Storage » Amazon Elastic Block Store (Amazon EBS) » Amazon EBS Volumes » Modifying the Size, IOPS, or Type of an EBS Volume on Linux » Limitations When Modifying EBS Volumes

Limitations When Modifying EBS Volumes

Be aware of the following limits and requirements when you modify an EBS volume:

• In some cases, you must detach the volume or stop the instance for modification to proceed. If you encounter an error message while attempting to modify an EBS volume, or if you are modifying an EBS volume attached to a previous-generation instance type, take one of the following steps:

  • For a non-root volume, detach the volume from the instance, apply the modifications, and then re-attach the volume. For more information, see Detaching an Amazon EBS Volume from an Instance and Attaching an Amazon EBS Volume to an Instance.

  • For a root (boot) volume, stop the instance, apply the modifications, and then restart the instance. For more information, see Appendix: Starting and Stopping an Instance to Modify an EBS Volume.

• A gp2 volume that is attached to an instance as a root volume cannot be modified to an st1 or sc1 volume. If detached and modified to st1 or sc1, it cannot be attached to an instance as the root volume.

• A gp2 volume cannot be modified to an st1 or sc1 volume if the requested volume size is below the minimum size for st1 and sc1 volumes.

• When provisioning over 32,000 IOPS on an existing io1 volume, you may need to do one of the following in order to see full performance:

  • Detach and attach the volume.

  • Restart the instance.

• Decreasing the size of an EBS volume is not supported. However, you can create a smaller volume and then migrate your data to it using an application-level tool such as rsync.

• After modifying a volume, wait at least six hours and ensure that the volume is in the in-use or available state before applying further modifications to the same volume.

• While m3.medium instances fully support volume modification, some m3.large, m3.xlarge, and m3.2xlarge instances might not support all volume modification features. If you encounter an error, see Appendix: Starting and Stopping an Instance to Modify an EBS Volume.

Volume Modification Support on Older Volumes

Before you can modify a volume that was attached to an instance before November 1, 2016, you must initialize volume modification support using one of the following actions:

• Detach and attach the volume.

• Restart the instance.

To determine whether you must initialize volume modification support using the console

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. On the navigation pane, choose Instances.

3. Choose the Show/Hide Columns icon (the gear). Select the Launch Time and Block Devices attributes and then choose Close.

4. Sort the list of instances by the Launch Time column. For instances that were started before the cutoff date, check when the devices were attached. In the following example, you must initialize volume modification for the first instance because it was started before the cutoff date and its root volume was attached before the cutoff date. The other instances are ready because they were started after the cutoff, regardless of when the volumes were attached.

   

To determine whether you must initialize volume modification support using the CLI

To find an instance that was last started before the cutoff date with a volume that was attached before the cutoff date, use the following describe-instances command.

aws ec2 describe-instances --query "Reservations[*].Instances[*].[InstanceId,LaunchTime<='2016-11-01',BlockDeviceMappings[*][Ebs.AttachTime<='2016-11-01']]" --output text

The output for each instance shows its ID, whether it was started before the cutoff date (True or False), and whether its volumes were attached before the cutoff date (True or False). In the following example output, you must initialize volume modification for the first instance because it was started before the cutoff date and its root volume was attached before the cutoff date. The other instances are ready because they were started after the cutoff, regardless of when the volumes were attached.

i-e905622e              True
True
i-719f99a8              False
True
i-006b02c1b78381e57     False
False
False
i-e3d172ed              False
True