class Aws::EC2::Types::CreateVolumeRequest

@see docs.aws.amazon.com/goto/WebAPI/ec2-2016-11-15/CreateVolumeRequest AWS API Documentation
@return [String] : docs.aws.amazon.com/AWSEC2/latest/APIReference/Run_Instance_Idempotency.html not need to pass this option.
**A suitable default value is auto-generated.** You should normally Idempotency].
idempotency of the request. For more information, see [Ensure
Unique, case-sensitive identifier that you provide to ensure the
@!attribute [rw] client_token
@return [Integer]
Valid Range: Minimum value of 125. Maximum value of 1000.
This parameter is valid only for ‘gp3` volumes.
MiB/s.
The throughput to provision for a volume, with a maximum of 1,000
@!attribute [rw] throughput
@return [Boolean] : docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volumes-multi.html [1]: docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances Elastic Compute Cloud User Guide*.
information, see [ Amazon EBS Multi-Attach] in the *Amazon
parameter is supported with `io1` and `io2` volumes only. For more
on the Nitro System] in the same Availability Zone. This
Multi-Attach, you can attach the volume to up to 16 [Instances built
Indicates whether to enable Amazon EBS Multi-Attach. If you enable
@!attribute [rw] multi_attach_enabled
@return [Array<Types::TagSpecification>]
The tags to apply to the volume during creation.
@!attribute [rw] tag_specifications
@return [Boolean]
`DryRunOperation`. Otherwise, it is `UnauthorizedOperation`.
If you have the required permissions, the error response is
without actually making the request, and provides an error response.
Checks whether you have the required permissions for the action,
@!attribute [rw] dry_run
@return [String] : docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html Default: `gp2`
*Amazon Elastic Compute Cloud User Guide*.
For more information, see [Amazon EBS volume types] in the
be used as boot volumes.
Throughput Optimized HDD (`st1`) and Cold HDD (`sc1`) volumes can’t
* Magnetic: ‘standard`
* Cold HDD: `sc1`
* Throughput Optimized HDD: `st1`
* Provisioned IOPS SSD: `io1` | `io2`
* General Purpose SSD: `gp2` | `gp3`
The volume type. This parameter can be one of the following values:
@!attribute [rw] volume_type
@return [String]
either a snapshot ID or a volume size.
The snapshot from which to create the volume. You must specify
@!attribute [rw] snapshot_id
@return [Integer]
* `standard`: 1-1,024
* `st1` and `sc1`: 125-16,384
* `io1` and `io2`: 4-16,384
* `gp2` and `gp3`: 1-16,384
The following are the supported volumes sizes for each volume type:
larger than the snapshot size.
snapshot size. You can specify a volume size that is equal to or
ID or a volume size. If you specify a snapshot, the default is the
The size of the volume, in GiBs. You must specify either a snapshot
@!attribute [rw] size
@return [String]
The Amazon Resource Name (ARN) of the Outpost.
@!attribute [rw] outpost_arn
@return [String]
the action can appear to complete, but eventually fails.
Therefore, if you specify an ID, alias, or ARN that is not valid,
Amazon Web Services authenticates the KMS key asynchronously.
arn:aws:kms:us-east-1:012345678910:alias/ExampleAlias.
* Alias ARN. For example,
arn:aws:kms:us-east-1:012345678910:key/1234abcd-12ab-34cd-56ef-1234567890ab.
* Key ARN. For example,
* Key alias. For example, alias/ExampleAlias.
* Key ID. For example, 1234abcd-12ab-34cd-56ef-1234567890ab.
You can specify the KMS key using any of the following:
encrypted state must be `true`.
KMS key for Amazon EBS is used. If `KmsKeyId` is specified, the
for Amazon EBS encryption. If this parameter is not specified, your
The identifier of the Key Management Service (KMS) KMS key to use
@!attribute [rw] kms_key_id
@return [Integer] : docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances `gp2`, `st1`, `sc1`, or `standard` volumes.
for `gp3` volumes is 3,000 IOPS. This parameter is not supported for
This parameter is required for `io1` and `io2` volumes. The default
performance up to 32,000 IOPS.
built on the Nitro System]. Other instance families support
`io1` and `io2` volumes support up to 64,000 IOPS only on [Instances
* `io2`: 100-64,000 IOPS
* `io1`: 100-64,000 IOPS
* `gp3`: 3,000-16,000 IOPS
The following are the supported values for each volume type:
accumulates I/O credits for bursting.
baseline performance of the volume and the rate at which the volume
provisioned for the volume. For `gp2` volumes, this represents the
and `io2` volumes, this represents the number of IOPS that are
The number of I/O operations per second (IOPS). For `gp3`, `io1`,
@!attribute [rw] iops
@return [Boolean] : docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html#EBSEncryption_supported_instances [1]: docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html#encryption-by-default instance types].
support Amazon EBS encryption. For more information, see [Supported
Encrypted Amazon EBS volumes must be attached to instances that
Guide*.
[Encryption by default] in the *Amazon Elastic Compute Cloud User
whether encryption by default is enabled. For more information, see
(new or from a snapshot), starting encryption state, ownership, and
setting the encryption state to `true` depends on the volume origin
Indicates whether the volume should be encrypted. The effect of
@!attribute [rw] encrypted
@return [String]
example, `us-east-1a`.
The ID of the Availability Zone in which to create the volume. For
@!attribute [rw] availability_zone

class Aws::EC2::Types::CreateVolumeRequest

Namespace

Included Modules

Defined in