Skip to content

modify_volume async

modify_volume(
    *,
    config_overrides: Optional[AsyncEC2ClientConfig] = None,
    dry_run: Optional[Boolean] = None,
    volume_id: Optional[VolumeId] = None,
    size: Optional[Integer] = None,
    volume_type: Optional[VolumeType] = None,
    iops: Optional[Integer] = None,
    throughput: Optional[Integer] = None,
    multi_attach_enabled: Optional[Boolean] = None,
) -> ModifyVolumeResult

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 you initiate a volume modification, you must wait for that modification to reach the completed state before you can initiate another modification for the same volume. You can modify a volume up to four times within a rolling 24-hour period, as long as the volume is in the in-use or available state, and all previous modifications for that volume are completed. If you exceed this limit, you get an error message that indicates when you can perform your next modification.

Parameters:

  • dry_run (Optional[Boolean], default: None ) –

    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.

  • volume_id (Optional[VolumeId], default: None ) –

    The ID of the volume.

  • size (Optional[Integer], default: None ) –

    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: 1 - 16,384 GiB

    • gp3: 1 - 65,536 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.

  • volume_type (Optional[VolumeType], default: None ) –

    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.

  • iops (Optional[Integer], default: None ) –

    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 - 80,000 IOPS

    • io1: 100 - 64,000 IOPS

    • io2: 100 - 256,000 IOPS

    Instances built on the Nitro System can support up to 256,000 IOPS. Other instances can support 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.

  • throughput (Optional[Integer], default: None ) –

    The target throughput of the volume, in MiB/s. This parameter is valid only for gp3 volumes. The maximum value is 2,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 2,000.

  • multi_attach_enabled (Optional[Boolean], default: None ) –

    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.

Raises:

Source code in docs_src/capo_ec2/_services/async_ec2.py
async def modify_volume(
    self,
    *,
    config_overrides: Optional[AsyncEC2ClientConfig] = None,
    dry_run: Optional["capo_ec2.types.boolean.Boolean"] = None,
    volume_id: Optional["capo_ec2.types.volume_id.VolumeId"] = None,
    size: Optional["capo_ec2.types.integer.Integer"] = None,
    volume_type: Optional["capo_ec2.types.volume_type.VolumeType"] = None,
    iops: Optional["capo_ec2.types.integer.Integer"] = None,
    throughput: Optional["capo_ec2.types.integer.Integer"] = None,
    multi_attach_enabled: Optional["capo_ec2.types.boolean.Boolean"] = None,
) -> "capo_ec2.types.modify_volume_result.ModifyVolumeResult":
    """<p>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 <a href="https://docs.aws.amazon.com/ebs/latest/userguide/ebs-modify-volume.html">Amazon EBS Elastic Volumes</a> in the <i>Amazon EBS User Guide</i>.</p> <p>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 <a href="https://docs.aws.amazon.com/ebs/latest/userguide/recognize-expanded-volume-linux.html">Extend the file system</a>.</p> <p>For more information, see <a href="https://docs.aws.amazon.com/ebs/latest/userguide/monitoring-volume-modifications.html">Monitor the progress of volume modifications</a> in the <i>Amazon EBS User Guide</i>.</p> <p>With previous-generation instance types, resizing an EBS volume might require detaching and reattaching the volume or stopping and restarting the instance.</p> <p>After you initiate a volume modification, you must wait for that modification to reach the <code>completed</code> state before you can initiate another modification for the same volume. You can modify a volume up to four times within a rolling 24-hour period, as long as the volume is in the <code>in-use</code> or <code>available</code> state, and all previous modifications for that volume are <code>completed</code>. If you exceed this limit, you get an error message that indicates when you can perform your next modification.</p>

    Args:
        dry_run: <p>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 <code>DryRunOperation</code>. Otherwise, it is <code>UnauthorizedOperation</code>.</p>
        volume_id: <p>The ID of the volume.</p>
        size: <p>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.</p> <p>The following are the supported volumes sizes for each volume type:</p> <ul> <li> <p> <code>gp2</code>: 1 - 16,384 GiB</p> </li> <li> <p> <code>gp3</code>: 1 - 65,536 GiB</p> </li> <li> <p> <code>io1</code>: 4 - 16,384 GiB</p> </li> <li> <p> <code>io2</code>: 4 - 65,536 GiB</p> </li> <li> <p> <code>st1</code> and <code>sc1</code>: 125 - 16,384 GiB</p> </li> <li> <p> <code>standard</code>: 1 - 1024 GiB</p> </li> </ul> <p>Default: The existing size is retained.</p>
        volume_type: <p>The target EBS volume type of the volume. For more information, see <a href="https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volume-types.html">Amazon EBS volume types</a> in the <i>Amazon EBS User Guide</i>.</p> <p>Default: The existing type is retained.</p>
        iops: <p>The target IOPS rate of the volume. This parameter is valid only for <code>gp3</code>, <code>io1</code>, and <code>io2</code> volumes.</p> <p>The following are the supported values for each volume type:</p> <ul> <li> <p> <code>gp3</code>: 3,000 - 80,000 IOPS</p> </li> <li> <p> <code>io1</code>: 100 - 64,000 IOPS</p> </li> <li> <p> <code>io2</code>: 100 - 256,000 IOPS</p> </li> </ul> <note> <p> <a href="https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html"> Instances built on the Nitro System</a> can support up to 256,000 IOPS. Other instances can support up to 32,000 IOPS.</p> </note> <p>Default: The existing value is retained if you keep the same volume type. If you change the volume type to <code>io1</code>, <code>io2</code>, or <code>gp3</code>, the default is 3,000.</p>
        throughput: <p>The target throughput of the volume, in MiB/s. This parameter is valid only for <code>gp3</code> volumes. The maximum value is 2,000.</p> <p>Default: The existing value is retained if the source and target volume type is <code>gp3</code>. Otherwise, the default value is 125.</p> <p>Valid Range: Minimum value of 125. Maximum value of 2,000.</p>
        multi_attach_enabled: <p>Specifies whether to enable Amazon EBS Multi-Attach. If you enable Multi-Attach, you can attach the volume to up to 16 <a href="https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html"> Nitro-based instances</a> in the same Availability Zone. This parameter is supported with <code>io1</code> and <code>io2</code> volumes only. For more information, see <a href="https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes-multi.html"> Amazon EBS Multi-Attach</a> in the <i>Amazon EBS User Guide</i>.</p>

    Raises:
        capo_ec2.errors.UnknownServiceError: The service returned an error code this client does not model.
    """

    async def _handler(
        req: "AsyncOperationRequest[capo_ec2.types.modify_volume_request.ModifyVolumeRequest]",
    ) -> AsyncOperationResponse[
        "capo_ec2.types.modify_volume_result.ModifyVolumeResult"
    ]:
        import capo_ec2._operations.amazon_ec2.modify_volume

        (
            output,
            http_response,
        ) = await capo_ec2._operations.amazon_ec2.modify_volume.async_modify_volume(
            req.options, req.input
        )
        return AsyncOperationResponse(output=output, response=http_response)

    interceptors_, options_ = self.operation_options(
        config_overrides, OperationLogging("ModifyVolume")
    )
    input_: capo_ec2.types.modify_volume_request.ModifyVolumeRequest = {}
    if dry_run is not None:
        input_["dry_run"] = dry_run
    if volume_id is not None:
        input_["volume_id"] = volume_id
    if size is not None:
        input_["size"] = size
    if volume_type is not None:
        input_["volume_type"] = volume_type
    if iops is not None:
        input_["iops"] = iops
    if throughput is not None:
        input_["throughput"] = throughput
    if multi_attach_enabled is not None:
        input_["multi_attach_enabled"] = multi_attach_enabled

    response = await aexecute_pipeline(
        AsyncOperationRequest(input=input_, options=options_),
        handler=_handler,
        interceptors=list(interceptors_),
    )
    await response.response.aclose()
    return response.output