How do I troubleshoot issues that occur when I change my Amazon EBS volume type?

Resolution

The following are common issues that occur when you change your Amazon EBS volume type: 

The size or performance isn't within the limits of the target volume type that you want to change to

When you modify a volume type, the size and performance must be within the limits of the target volume type. For example, if you modify a gp3 volume that's bigger than 1024 GiB to Magnetic, then you get an error message. This error occurs because standard volumes have a maximum size of 1024 GiB. Magnetic is a previous generation volume type. It's a best practice to use a current volume type for higher performance. For more information see, Amazon EBS volume types.

After you increase the size of your volume, the new size is immediately available to use. However, if the volume is in the Optimizing state, then volume performance is between the source and target configuration specifications.

The option to change the volume type on your Multi-Attach activated io1 or io2 volume is grayed out

You can't change the volume type on your Multi-Attach activated io1 or io2 volume. You can modify only the size and Provisioned IOPS for Multi-Attach activated io2 volumes. For more information on Multi-Attach volumes, see Considerations and limitations.

You don't see the sc1 and st1 HDD-backed volume types in the dropdown list for certain volume types

An sc1 or st1 volume isn't supported as a boot volume for all volume types. You can't change the following volume types to an sc1 or st1 volume:

• io1
• io2
• gp2
• gp3
• standard

For more information on Amazon EBS volume modifications, see Requirements for Amazon EBS volume modifications.

You don't see the expected performance after you change your volume type

Make sure that your workload doesn't exceed the IOPS or throughput limits of your new volume type or instance limits. If Amazon CloudWatch doesn't show that you reached your limits, then your workload might still be micro-bursting. If your workload isn't micro-bursting and you still can't determine whether you reached your limits, then contact AWS Support.

Related information

Why is my Amazon EBS volume stuck in the Optimizing state when I modify the volume?