Request Parameters Response Elements Errors Examples See Also

ModifyVolume

You can modify several parameters of an existing EBS volume, including volume size, volume type, and IOPS capacity. If your EBS volume is attached to a current-generation EC2 instance type, you might be able to apply these changes without stopping the instance or detaching the volume from it. For more information about modifying EBS volumes, see Amazon EBS Elastic Volumes in the Amazon EBS User Guide.

When you complete a resize operation on your volume, you need to extend the volume's file-system size to take advantage of the new storage capacity. For more information, see Extend the file system.

For more information, see Monitor the progress of volume modifications in the Amazon EBS User Guide.

With previous-generation instance types, resizing an EBS volume might require detaching and reattaching the volume or stopping and restarting the instance.

After modifying a volume, you must wait at least six hours and ensure that the volume is in the in-use or available state before you can modify the same volume. This is sometimes referred to as a cooldown period.

Request Parameters

The following parameters are for this specific action. For more information about required and optional parameters that are common to all actions, see Common Query Parameters.

DryRun

Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.

Type: Boolean

Required: No

Iops

The target IOPS rate of the volume. This parameter is valid only for gp3, io1, and io2 volumes.

The following are the supported values for each volume type:

gp3: 3,000 - 16,000 IOPS
io1: 100 - 64,000 IOPS
io2: 100 - 256,000 IOPS

For io2 volumes, you can achieve up to 256,000 IOPS on instances built on the Nitro System. On other instances, you can achieve performance up to 32,000 IOPS.

Default: The existing value is retained if you keep the same volume type. If you change the volume type to io1, io2, or gp3, the default is 3,000.

Type: Integer

Required: No

MultiAttachEnabled

Specifies whether to enable Amazon EBS Multi-Attach. If you enable Multi-Attach, you can attach the volume to up to 16 Nitro-based instances in the same Availability Zone. This parameter is supported with io1 and io2 volumes only. For more information, see Amazon EBS Multi-Attach in the Amazon EBS User Guide.

Type: Boolean

Required: No

Size

The target size of the volume, in GiB. The target volume size must be greater than or equal to the existing size of the volume.

The following are the supported volumes sizes for each volume type:

gp2 and gp3: 1 - 16,384 GiB
io1: 4 - 16,384 GiB
io2: 4 - 65,536 GiB
st1 and sc1: 125 - 16,384 GiB
standard: 1 - 1024 GiB

Default: The existing size is retained.

Type: Integer

Required: No

Throughput

The target throughput of the volume, in MiB/s. This parameter is valid only for gp3 volumes. The maximum value is 1,000.

Default: The existing value is retained if the source and target volume type is gp3. Otherwise, the default value is 125.

Valid Range: Minimum value of 125. Maximum value of 1000.

Type: Integer

Required: No

VolumeId

The ID of the volume.

Type: String

Required: Yes

VolumeType

The target EBS volume type of the volume. For more information, see Amazon EBS volume types in the Amazon EBS User Guide.

Default: The existing type is retained.

Type: String

Valid Values: standard | io1 | io2 | gp2 | sc1 | st1 | gp3

Required: No

Response Elements

The following elements are returned by the service.

requestId

The ID of the request.

Type: String

volumeModification

Information about the volume modification.

Type: VolumeModification object

Errors

For information about the errors that are common to all actions, see Common client error codes.

Examples

Modify size, type, and IOPS provisioning of a volume

This example illustrates one usage of ModifyVolume.

Sample Request


https://ec2.amazonaws.com/?Action=ModifyVolume
&VolumeId=vol-1234567890EXAMPLE
&VolumeType=io1
&Iops=10000
&Size=200
&Version=2016-11-15

Sample Response


<ModifyVolumeResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
    <requestId>5jkdf074-37ed-4004-8671-a78ee82bf1cbEXAMPLE</requestId>
    <volumeModification>
        <targetIops>10000</targetIops>
        <originalIops>300</originalIops>
        <modificationState>modifying</modificationState>
        <targetSize>200</targetSize>
        <targetVolumeType>io1</targetVolumeType>
        <targetMultiAttachEnabled>false</targetMultiAttachEnabled>
        <volumeId>vol-1234567890EXAMPLE</volumeId>
        <progress>0</progress>
        <startTime>2017-01-19T23:58:04.922Z</startTime>
        <originalSize>100</originalSize>
        <originalVolumeType>gp2</originalVolumeType>
        <originalMultiAttachEnabled>false</originalMultiAttachEnabled>
    </volumeModification>
</ModifyVolumeResponse>

Modify Multi-Attach support

This example illustrates one usage of ModifyVolume.

Sample Request


https://ec2.amazonaws.com/?Action=ModifyVolume
&VolumeId=vol-1234567890EXAMPLE
&MultiAttachEnabled=true
&Version=2016-11-15

Sample Response


<ModifyVolumeResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
    <requestId>5jkdf074-37ed-4004-8671-a78ee82bf1cbEXAMPLE</requestId>
    <volumeModification>
        <originalMultiAttachEnabled>false</originalMultiAttachEnabled>
        <targetMultiAttachEnabled>true</targetMultiAttachEnabled>
    </volumeModification>
</ModifyVolumeResponse>