For more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
*You can allocate a carrier IP address which is a public IP address from a telecommunication carrier, to a network interface which resides in a subnet in a Wavelength Zone (for example an EC2 instance).
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*When the IAM role is associated with the ACM certificate, the certificate, certificate chain, and encrypted - * private key are placed in an Amazon S3 bucket that only the associated IAM role can access. The private key of the certificate + * private key are placed in an Amazon S3 location that only the associated IAM role can access. The private key of the certificate * is encrypted with an Amazon Web Services managed key that has an attached attestation-based key policy.
* *To enable the IAM role to access the Amazon S3 object, you must grant it permission to call s3:GetObject
@@ -3941,7 +3941,7 @@ export class EC2 extends EC2Client {
*
For more information about VPC security group quotas, see Amazon VPC quotas.
* *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*Creates a network interface in the specified subnet.
- *For more information about network interfaces, see Elastic Network Interfaces - * in the Amazon Virtual Private Cloud User Guide.
+ *The number of IP addresses you can assign to a network interface varies by instance + * type. For more information, see IP Addresses Per ENI Per + * Instance Type in the Amazon Virtual Private Cloud User Guide.
+ *For more information about network interfaces, see Elastic network interfaces + * in the Amazon Elastic Compute Cloud User Guide.
*/ public createNetworkInterface( args: CreateNetworkInterfaceCommandInput, @@ -6217,7 +6220,7 @@ export class EC2 extends EC2Client { *For more information about VPC security group limits, see Amazon VPC Limits.
* *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*Creates crash-consistent snapshots of multiple EBS volumes and stores the data in S3. * Volumes are chosen by specifying an instance. Any attached volumes will produce one snapshot - * each that is crash-consistent across the instance. Boot volumes can be excluded by changing the - * parameters.
+ * each that is crash-consistent across the instance. + * + *You can include all of the volumes currently attached to the instance, or you can exclude + * the root volume or specific data (non-root) volumes from the multi-volume snapshot set.
* *You can create multi-volume snapshots of instances in a Region and instances on an
* Outpost. If you create snapshots from an instance in a Region, the snapshots must be stored
@@ -8705,7 +8710,7 @@ export class EC2 extends EC2Client {
* DependencyViolation in EC2-VPC.
We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*An Elastic IP address is for use in either the EC2-Classic platform or in a VPC. * For more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*This is an idempotent operation. If you perform the operation more than once, Amazon EC2 doesn't return an error.
*/ @@ -17624,6 +17629,12 @@ export class EC2 extends EC2Client { /** *Import single or multi-volume disk images or EBS snapshots into an Amazon Machine Image (AMI).
+ *Amazon Web Services VM Import/Export strongly recommends specifying a value for either the
+ * --license-type or --usage-operation parameter when you create a new
+ * VM Import task. This ensures your operating system is licensed appropriately and your billing is
+ * optimized.
For more information, see Importing a * VM as an image using VM Import/Export in the VM Import/Export User Guide.
*/ @@ -20051,7 +20062,7 @@ export class EC2 extends EC2Client { * RestoreAddressToClassic request. You cannot move an Elastic IP address that was * originally allocated for use in the EC2-VPC platform to the EC2-Classic platform. *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*[Nondefault VPC] You must use DisassociateAddress to disassociate the Elastic IP address
* before you can release it. Otherwise, Amazon EC2 returns an error (InvalidIPAddress.InUse).
Restores an Elastic IP address that was previously moved to the EC2-VPC platform back to the EC2-Classic platform. You cannot move an Elastic IP address that was originally allocated for use in EC2-VPC. The Elastic IP address must not be associated with an instance or network interface.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*Rule changes are propagated to instances within the security group as quickly as possible. However, a small delay might occur.
* *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*For more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
*You can allocate a carrier IP address which is a public IP address from a telecommunication carrier, to a network interface which resides in a subnet in a Wavelength Zone (for example an EC2 instance).
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*When the IAM role is associated with the ACM certificate, the certificate, certificate chain, and encrypted - * private key are placed in an Amazon S3 bucket that only the associated IAM role can access. The private key of the certificate + * private key are placed in an Amazon S3 location that only the associated IAM role can access. The private key of the certificate * is encrypted with an Amazon Web Services managed key that has an attached attestation-based key policy.
* *To enable the IAM role to access the Amazon S3 object, you must grant it permission to call s3:GetObject
diff --git a/clients/client-ec2/src/commands/AuthorizeSecurityGroupIngressCommand.ts b/clients/client-ec2/src/commands/AuthorizeSecurityGroupIngressCommand.ts
index eb5ca332c50cc..3da159cb03e68 100644
--- a/clients/client-ec2/src/commands/AuthorizeSecurityGroupIngressCommand.ts
+++ b/clients/client-ec2/src/commands/AuthorizeSecurityGroupIngressCommand.ts
@@ -44,7 +44,7 @@ export interface AuthorizeSecurityGroupIngressCommandOutput
*
For more information about VPC security group quotas, see Amazon VPC quotas.
* *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*Creates a network interface in the specified subnet.
- *For more information about network interfaces, see Elastic Network Interfaces - * in the Amazon Virtual Private Cloud User Guide.
+ *The number of IP addresses you can assign to a network interface varies by instance + * type. For more information, see IP Addresses Per ENI Per + * Instance Type in the Amazon Virtual Private Cloud User Guide.
+ *For more information about network interfaces, see Elastic network interfaces + * in the Amazon Elastic Compute Cloud User Guide.
* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-ec2/src/commands/CreateSecurityGroupCommand.ts b/clients/client-ec2/src/commands/CreateSecurityGroupCommand.ts index f8e94ed4b73c9..b79033ba3d36b 100644 --- a/clients/client-ec2/src/commands/CreateSecurityGroupCommand.ts +++ b/clients/client-ec2/src/commands/CreateSecurityGroupCommand.ts @@ -45,7 +45,7 @@ export interface CreateSecurityGroupCommandOutput extends CreateSecurityGroupRes *For more information about VPC security group limits, see Amazon VPC Limits.
* *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*Creates crash-consistent snapshots of multiple EBS volumes and stores the data in S3. * Volumes are chosen by specifying an instance. Any attached volumes will produce one snapshot - * each that is crash-consistent across the instance. Boot volumes can be excluded by changing the - * parameters.
+ * each that is crash-consistent across the instance. + * + *You can include all of the volumes currently attached to the instance, or you can exclude + * the root volume or specific data (non-root) volumes from the multi-volume snapshot set.
* *You can create multi-volume snapshots of instances in a Region and instances on an
* Outpost. If you create snapshots from an instance in a Region, the snapshots must be stored
diff --git a/clients/client-ec2/src/commands/DeleteSecurityGroupCommand.ts b/clients/client-ec2/src/commands/DeleteSecurityGroupCommand.ts
index 4edbceaba00eb..0596980f73875 100644
--- a/clients/client-ec2/src/commands/DeleteSecurityGroupCommand.ts
+++ b/clients/client-ec2/src/commands/DeleteSecurityGroupCommand.ts
@@ -30,7 +30,7 @@ export interface DeleteSecurityGroupCommandOutput extends __MetadataBearer {}
* DependencyViolation in EC2-VPC.
We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*An Elastic IP address is for use in either the EC2-Classic platform or in a VPC. * For more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*This is an idempotent operation. If you perform the operation more than once, Amazon EC2 doesn't return an error.
* @example diff --git a/clients/client-ec2/src/commands/ImportImageCommand.ts b/clients/client-ec2/src/commands/ImportImageCommand.ts index 7f3cf55f50c6a..9993054f7defa 100644 --- a/clients/client-ec2/src/commands/ImportImageCommand.ts +++ b/clients/client-ec2/src/commands/ImportImageCommand.ts @@ -26,6 +26,12 @@ export interface ImportImageCommandOutput extends ImportImageResult, __MetadataB /** *Import single or multi-volume disk images or EBS snapshots into an Amazon Machine Image (AMI).
+ *Amazon Web Services VM Import/Export strongly recommends specifying a value for either the
+ * --license-type or --usage-operation parameter when you create a new
+ * VM Import task. This ensures your operating system is licensed appropriately and your billing is
+ * optimized.
For more information, see Importing a * VM as an image using VM Import/Export in the VM Import/Export User Guide.
* @example diff --git a/clients/client-ec2/src/commands/MoveAddressToVpcCommand.ts b/clients/client-ec2/src/commands/MoveAddressToVpcCommand.ts index 1a46761e2a602..404020b5f0208 100644 --- a/clients/client-ec2/src/commands/MoveAddressToVpcCommand.ts +++ b/clients/client-ec2/src/commands/MoveAddressToVpcCommand.ts @@ -35,7 +35,7 @@ export interface MoveAddressToVpcCommandOutput extends MoveAddressToVpcResult, _ * RestoreAddressToClassic request. You cannot move an Elastic IP address that was * originally allocated for use in the EC2-VPC platform to the EC2-Classic platform. *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*[Nondefault VPC] You must use DisassociateAddress to disassociate the Elastic IP address
* before you can release it. Otherwise, Amazon EC2 returns an error (InvalidIPAddress.InUse).
Restores an Elastic IP address that was previously moved to the EC2-VPC platform back to the EC2-Classic platform. You cannot move an Elastic IP address that was originally allocated for use in EC2-VPC. The Elastic IP address must not be associated with an instance or network interface.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*Rule changes are propagated to instances within the security group as quickly as possible. However, a small delay might occur.
* *We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*Exclude a particular CIDR range from being returned by the pool.
+ *Exclude a particular CIDR range from being returned by the pool. Disallowed CIDRs are only allowed if using netmask length for allocation.
*/ DisallowedCidrs?: string[]; } @@ -2501,7 +2501,7 @@ export interface AssignIpv6AddressesRequest { Ipv6AddressCount?: number; /** - *One or more specific IPv6 addresses to be assigned to the network interface. You can't use this option if you're specifying a number of IPv6 addresses.
+ *The IPv6 addresses to be assigned to the network interface. You can't use this option if you're specifying a number of IPv6 addresses.
*/ Ipv6Addresses?: string[]; @@ -2556,7 +2556,7 @@ export interface AssignPrivateIpAddressesRequest { NetworkInterfaceId: string | undefined; /** - *One or more IP addresses to be assigned as a secondary private IP address to the network interface. You can't specify this parameter when also specifying a number of secondary IP addresses.
+ *The IP addresses to be assigned as a secondary private IP address to the network interface. You can't specify this parameter when also specifying a number of secondary IP addresses.
*If you don't specify an IP address, Amazon EC2 automatically selects an IP address within the subnet range.
*/ PrivateIpAddresses?: string[]; @@ -3893,7 +3893,7 @@ export interface PrefixListId { /** *Describes a security group and Amazon Web Services account ID pair.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*[EC2-Classic, default VPC] The name of the security group. You must specify either the - * security group ID or the security group name in the request.
+ * security group ID or the security group name in the request. For security groups in a + * nondefault VPC, you must specify the security group ID. */ GroupName?: string; diff --git a/clients/client-ec2/src/models/models_1.ts b/clients/client-ec2/src/models/models_1.ts index f82206e4000e9..b44abc09a2d9c 100644 --- a/clients/client-ec2/src/models/models_1.ts +++ b/clients/client-ec2/src/models/models_1.ts @@ -666,7 +666,7 @@ export interface InstanceRequirementsRequest { *For instance types with Xilinx VU9P FPGAs, specify vu9p.
For instance types with Amazon Web Services Inferentia GPUs, specify inferentia.
For instance types with Amazon Web Services Inferentia chips, specify inferentia.
For instance types with NVIDIA GRID K520 GPUs, specify k520.
For instance types with Xilinx VU9P FPGAs, specify vu9p.
For instance types with Amazon Web Services Inferentia GPUs, specify inferentia.
For instance types with Amazon Web Services Inferentia chips, specify inferentia.
For instance types with NVIDIA GRID K520 GPUs, specify k520.
The private IPv4 addresses.
+ *The private IPv4 address.
*/ PrivateIpAddress?: string; } @@ -4066,7 +4066,7 @@ export interface RequestLaunchTemplateData { /** *The instance type. For more information, see Instance types in the * Amazon Elastic Compute Cloud User Guide.
- *If you specify InstanceTypes, you can't specify
+ *
If you specify InstanceType, you can't specify
* InstanceRequirements.
One or more IPv4 delegated prefixes assigned to the network interface.
+ *The IPv4 delegated prefixes assigned to the network interface.
*/ Ipv4Prefix?: string; } @@ -4825,7 +4825,7 @@ export interface InstanceIpv6Address { */ export interface Ipv6PrefixSpecificationResponse { /** - *One or more IPv6 delegated prefixes assigned to the network interface.
+ *The IPv6 delegated prefixes assigned to the network interface.
*/ Ipv6Prefix?: string; } @@ -6472,9 +6472,6 @@ export enum NetworkInterfaceCreationType { trunk = "trunk", } -/** - *Contains the parameters for CreateNetworkInterface.
- */ export interface CreateNetworkInterfaceRequest { /** *A description for the network interface.
@@ -6495,15 +6492,18 @@ export interface CreateNetworkInterfaceRequest { /** *The number of IPv6 addresses to assign to a network interface. Amazon EC2
- * automatically selects the IPv6 addresses from the subnet range. You can't use this
- * option if specifying specific IPv6 addresses. If your subnet has the AssignIpv6AddressOnCreation attribute set
- * to true, you can specify 0 to override this setting.
You can't specify a count of IPv6 addresses using this parameter if you've specified + * one of the following: specific IPv6 addresses, specific IPv6 prefixes, or a count of IPv6 prefixes.
+ *If your subnet has the AssignIpv6AddressOnCreation attribute set, you can
+ * override that setting by specifying 0 as the IPv6 address count.
One or more specific IPv6 addresses from the IPv6 CIDR block range of your subnet. - * You can't use this option if you're specifying a number of IPv6 addresses.
+ *The IPv6 addresses from the IPv6 CIDR block range of your subnet.
+ *You can't specify IPv6 addresses using this parameter if you've specified one of the + * following: a count of IPv6 addresses, specific IPv6 prefixes, or a count of IPv6 prefixes.
*/ Ipv6Addresses?: InstanceIpv6Address[]; @@ -6517,7 +6517,9 @@ export interface CreateNetworkInterfaceRequest { PrivateIpAddress?: string; /** - *One or more private IPv4 addresses.
+ *The private IPv4 addresses.
+ *You can't specify private IPv4 addresses if you've specified one of the following: + * a count of private IPv4 addresses, specific IPv4 prefixes, or a count of IPv4 prefixes.
*/ PrivateIpAddresses?: PrivateIpAddressSpecification[]; @@ -6526,35 +6528,43 @@ export interface CreateNetworkInterfaceRequest { * you specify a number of secondary IPv4 addresses, Amazon EC2 selects these IP addresses * within the subnet's IPv4 CIDR range. You can't specify this option and specify more than * one private IP address usingprivateIpAddresses.
- * The number of IP addresses you can assign to a network interface varies by instance - * type. For more information, see IP Addresses Per ENI Per - * Instance Type in the Amazon Virtual Private Cloud User Guide.
+ *You can't specify a count of private IPv4 addresses if you've specified one of the following: + * specific private IPv4 addresses, specific IPv4 prefixes, or a count of IPv4 prefixes.
*/ SecondaryPrivateIpAddressCount?: number; /** - *One or more IPv4 prefixes assigned to the network interface. You cannot use this option if you use the Ipv4PrefixCount option.
The IPv4 prefixes assigned to the network interface.
+ *You can't specify IPv4 prefixes if you've specified one of the following: + * a count of IPv4 prefixes, specific private IPv4 addresses, or a count of private IPv4 addresses.
*/ Ipv4Prefixes?: Ipv4PrefixSpecificationRequest[]; /** - *The number of IPv4 prefixes that Amazon Web Services automatically assigns to the network interface. You cannot use this option if you use the Ipv4 Prefixes option.
The number of IPv4 prefixes that Amazon Web Services automatically assigns to the network interface.
+ *You can't specify a count of IPv4 prefixes if you've specified one of the following: + * specific IPv4 prefixes, specific private IPv4 addresses, or a count of private IPv4 + * addresses.
*/ Ipv4PrefixCount?: number; /** - *One or more IPv6 prefixes assigned to the network interface. You cannot use this option if you use the Ipv6PrefixCount option.
The IPv6 prefixes assigned to the network interface.
+ *You can't specify IPv6 prefixes if you've specified one of the following: + * a count of IPv6 prefixes, specific IPv6 addresses, or a count of IPv6 addresses.
*/ Ipv6Prefixes?: Ipv6PrefixSpecificationRequest[]; /** - *The number of IPv6 prefixes that Amazon Web Services automatically assigns to the network interface. You cannot use this option if you use the Ipv6Prefixes option.
The number of IPv6 prefixes that Amazon Web Services automatically assigns to the network interface.
+ *You can't specify a count of IPv6 prefixes if you've specified one of the following: + * specific IPv6 prefixes, specific IPv6 addresses, or a count of IPv6 addresses.
*/ Ipv6PrefixCount?: number; /** *The type of network interface. The default is interface.
The only supported values are efa and trunk.
The only supported values are efa and trunk.
Contains the output of CreateNetworkInterface.
- */ export interface CreateNetworkInterfaceResult { /** *Information about the network interface.
@@ -7921,6 +7928,12 @@ export interface InstanceSpecification { */ ExcludeBootVolume?: boolean; + /** + *The IDs of the data (non-root) volumes to exclude from the multi-volume snapshot set. + * If you specify the ID of the root volume, the request fails. To exclude the root volume, + * use ExcludeBootVolume.
+ *You can specify up to 40 volume IDs per request.
+ */ ExcludeDataVolumeIds?: string[]; } diff --git a/clients/client-ec2/src/models/models_2.ts b/clients/client-ec2/src/models/models_2.ts index 61eddceacb915..842c79dda824e 100644 --- a/clients/client-ec2/src/models/models_2.ts +++ b/clients/client-ec2/src/models/models_2.ts @@ -4701,7 +4701,9 @@ export interface DeleteSecurityGroupRequest { GroupId?: string; /** - *[EC2-Classic, default VPC] The name of the security group. You can specify either the security group name or the security group ID.
+ *[EC2-Classic, default VPC] The name of the security group. You can specify either the + * security group name or the security group ID. For security groups in a nondefault VPC, + * you must specify the security group ID.
*/ GroupName?: string; diff --git a/clients/client-ec2/src/models/models_3.ts b/clients/client-ec2/src/models/models_3.ts index 498c0315e9a25..694c9e674718b 100644 --- a/clients/client-ec2/src/models/models_3.ts +++ b/clients/client-ec2/src/models/models_3.ts @@ -5233,11 +5233,11 @@ export interface DescribeImagesRequest { Owners?: string[]; /** - *If true, all deprecated AMIs are included in the response. If
- * false, no deprecated AMIs are included in the response. If no value is
- * specified, the default value is false.
Specifies whether to include deprecated AMIs.
+ *Default: No deprecated AMIs are included in the response.
*If you are the AMI owner, all deprecated AMIs appear in the response regardless of the value (true or false) that you set for this parameter.
If you are the AMI owner, all deprecated AMIs appear in the response regardless of what + * you specify for this parameter.
*One or more security groups.
+ *The security groups.
*/ Groups?: GroupIdentifier[]; /** - *One or more IPv6 addresses associated with the network interface.
+ *The IPv6 addresses associated with the network interface.
*/ Ipv6Addresses?: InstanceIpv6Address[]; @@ -7129,7 +7129,7 @@ export interface InstanceNetworkInterface { PrivateIpAddress?: string; /** - *One or more private IPv4 addresses associated with the network interface.
+ *The private IPv4 addresses associated with the network interface.
*/ PrivateIpAddresses?: InstancePrivateIpAddress[]; diff --git a/clients/client-ec2/src/models/models_4.ts b/clients/client-ec2/src/models/models_4.ts index e77b5968f734f..2e35ebaff0890 100644 --- a/clients/client-ec2/src/models/models_4.ts +++ b/clients/client-ec2/src/models/models_4.ts @@ -472,7 +472,7 @@ export enum MoveStatus { /** *Describes the status of a moving Elastic IP address.
*We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
+ *We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
*One or more network interface permission IDs.
+ *The network interface permission IDs.
*/ NetworkInterfacePermissionIds?: string[]; @@ -1366,7 +1366,7 @@ export interface DescribeNetworkInterfacesRequest { DryRun?: boolean; /** - *One or more network interface IDs.
+ *The network interface IDs.
*Default: Describes all your network interfaces.
*/ NetworkInterfaceIds?: string[]; @@ -4098,7 +4098,7 @@ export interface InstanceNetworkInterfaceSpecification { Ipv6AddressCount?: number; /** - *One or more IPv6 addresses to assign to the network interface. You cannot specify + *
The IPv6 addresses to assign to the network interface. You cannot specify * this option and the option to assign a number of IPv6 addresses in the same request. You * cannot specify this option if you've specified a minimum number of instances to * launch.
@@ -4118,7 +4118,7 @@ export interface InstanceNetworkInterfaceSpecification { PrivateIpAddress?: string; /** - *One or more private IPv4 addresses to assign to the network interface. Only one private IPv4 address can be designated as primary. You cannot specify this option if you're + *
The private IPv4 addresses to assign to the network interface. Only one private IPv4 address can be designated as primary. You cannot specify this option if you're * launching more than one instance in a RunInstances request.
*/ PrivateIpAddresses?: PrivateIpAddressSpecification[]; @@ -4160,7 +4160,7 @@ export interface InstanceNetworkInterfaceSpecification { NetworkCardIndex?: number; /** - *One or more IPv4 delegated prefixes to be assigned to the network interface. You cannot + *
The IPv4 delegated prefixes to be assigned to the network interface. You cannot
* use this option if you use the Ipv4PrefixCount option.
One or more IPv6 delegated prefixes to be assigned to the network interface. You cannot + *
The IPv6 delegated prefixes to be assigned to the network interface. You cannot
* use this option if you use the Ipv6PrefixCount option.
The license type to be used for the Amazon Machine Image (AMI) after importing.
- *By default, we detect the source-system operating system (OS) and apply the appropriate license. Specify
- * AWS to replace the source-system license with an Amazon Web Services license, if appropriate. Specify BYOL
- * to retain the source-system license, if appropriate.
Specify AWS to replace the source-system license with an Amazon Web Services
+ * license or BYOL to retain the source-system license. Leaving this parameter
+ * undefined is the same as choosing AWS when importing a Windows Server operating
+ * system, and the same as choosing BYOL when importing a Windows client operating
+ * system (such as Windows 10) or a Linux operating system.
To use BYOL, you must have existing licenses with rights to use these licenses in a third party
* cloud, such as Amazon Web Services. For more information, see Prerequisites in the
* VM Import/Export User Guide.
The name of the attribute.
+ *The name of the attribute to modify.
+ *You can modify the following attributes only: disableApiTermination | instanceType |
+ * kernel | ramdisk | instanceInitiatedShutdownBehavior | blockDeviceMapping |
+ * userData | sourceDestCheck | groupSet | ebsOptimized | sriovNetSupport |
+ * enaSupport | nvmeSupport | disableApiStop | enclaveOptions
+ *
A private Autonomous System Number (ASN) for the Amazon side of a BGP session. * The range is 64512 to 65534 for 16-bit ASNs and 4200000000 to 4294967294 for 32-bit ASNs.
+ *The modify ASN operation is not allowed on a transit gateway with active BGP sessions. You must first delete all transit gateway attachments that have BGP configured prior to modifying the ASN on the transit gateway.
*/ AmazonSideAsn?: number; } diff --git a/clients/client-ec2/src/models/models_6.ts b/clients/client-ec2/src/models/models_6.ts index b6860bced3880..4b009243fcf6e 100644 --- a/clients/client-ec2/src/models/models_6.ts +++ b/clients/client-ec2/src/models/models_6.ts @@ -2071,7 +2071,8 @@ export interface RevokeSecurityGroupIngressRequest { /** *[EC2-Classic, default VPC] The name of the security group. You must specify either the - * security group ID or the security group name in the request.
+ * security group ID or the security group name in the request. For security groups in a + * nondefault VPC, you must specify the security group ID. */ GroupName?: string; @@ -3652,7 +3653,7 @@ export interface UnassignIpv6AddressesRequest { Ipv6Addresses?: string[]; /** - *One or more IPv6 prefixes to unassign from the network interface.
+ *The IPv6 prefixes to unassign from the network interface.
*/ Ipv6Prefixes?: string[]; @@ -3794,7 +3795,8 @@ export interface UpdateSecurityGroupRuleDescriptionsIngressRequest { /** *[EC2-Classic, default VPC] The name of the security group. You must specify either the - * security group ID or the security group name in the request.
+ * security group ID or the security group name in the request. For security groups in a + * nondefault VPC, you must specify the security group ID. */ GroupName?: string; diff --git a/clients/client-ec2/src/protocols/Aws_ec2.ts b/clients/client-ec2/src/protocols/Aws_ec2.ts index cf9346b630d9e..04c7d22ef532a 100644 --- a/clients/client-ec2/src/protocols/Aws_ec2.ts +++ b/clients/client-ec2/src/protocols/Aws_ec2.ts @@ -61750,8 +61750,8 @@ const deserializeAws_ec2EbsBlockDevice = (output: any, context: __SerdeContext): if (output["volumeType"] !== undefined) { contents.VolumeType = __expectString(output["volumeType"]); } - if (output["KmsKeyId"] !== undefined) { - contents.KmsKeyId = __expectString(output["KmsKeyId"]); + if (output["kmsKeyId"] !== undefined) { + contents.KmsKeyId = __expectString(output["kmsKeyId"]); } if (output["throughput"] !== undefined) { contents.Throughput = __strictParseInt32(output["throughput"]) as number; diff --git a/codegen/sdk-codegen/aws-models/ec2.json b/codegen/sdk-codegen/aws-models/ec2.json index 3f9589b67a5e0..d6c893d6d8398 100644 --- a/codegen/sdk-codegen/aws-models/ec2.json +++ b/codegen/sdk-codegen/aws-models/ec2.json @@ -1299,7 +1299,7 @@ "target": "com.amazonaws.ec2#AllocateAddressResult" }, "traits": { - "smithy.api#documentation": "Allocates an Elastic IP address to your Amazon Web Services account. After you allocate the Elastic IP address you can associate \n it with an instance or network interface. After you release an Elastic IP address, it is released to the IP address \n pool and can be allocated to a different Amazon Web Services account.
\nYou can allocate an Elastic IP address from an address pool owned by Amazon Web Services or from an address pool created \n from a public IPv4 address range that you have brought to Amazon Web Services for use with your Amazon Web Services resources using bring your own \n IP addresses (BYOIP). For more information, see Bring Your Own IP Addresses (BYOIP) in the Amazon Elastic Compute Cloud User Guide.
\n[EC2-VPC] If you release an Elastic IP address, you might be able to recover it. You cannot recover an \n Elastic IP address that you released after it is allocated to another Amazon Web Services account. You cannot recover an Elastic IP\n address for EC2-Classic. To attempt to recover an Elastic IP address that you released, specify it in this operation.
\nAn Elastic IP address is for use either in the EC2-Classic platform or in a VPC. By default, you can allocate\n 5 Elastic IP addresses for EC2-Classic per Region and 5 Elastic IP addresses for EC2-VPC per Region.
\nFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
\nYou can allocate a carrier IP address which is a public IP address from a telecommunication carrier, to a network interface which resides in a subnet in a Wavelength Zone (for example an EC2 instance).
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nAllocates an Elastic IP address to your Amazon Web Services account. After you allocate the Elastic IP address you can associate \n it with an instance or network interface. After you release an Elastic IP address, it is released to the IP address \n pool and can be allocated to a different Amazon Web Services account.
\nYou can allocate an Elastic IP address from an address pool owned by Amazon Web Services or from an address pool created \n from a public IPv4 address range that you have brought to Amazon Web Services for use with your Amazon Web Services resources using bring your own \n IP addresses (BYOIP). For more information, see Bring Your Own IP Addresses (BYOIP) in the Amazon Elastic Compute Cloud User Guide.
\n[EC2-VPC] If you release an Elastic IP address, you might be able to recover it. You cannot recover an \n Elastic IP address that you released after it is allocated to another Amazon Web Services account. You cannot recover an Elastic IP\n address for EC2-Classic. To attempt to recover an Elastic IP address that you released, specify it in this operation.
\nAn Elastic IP address is for use either in the EC2-Classic platform or in a VPC. By default, you can allocate\n 5 Elastic IP addresses for EC2-Classic per Region and 5 Elastic IP addresses for EC2-VPC per Region.
\nFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
\nYou can allocate a carrier IP address which is a public IP address from a telecommunication carrier, to a network interface which resides in a subnet in a Wavelength Zone (for example an EC2 instance).
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nExclude a particular CIDR range from being returned by the pool.
", + "smithy.api#documentation": "Exclude a particular CIDR range from being returned by the pool. Disallowed CIDRs are only allowed if using netmask length for allocation.
", "smithy.api#xmlName": "DisallowedCidr" } } @@ -4067,7 +4067,7 @@ "target": "com.amazonaws.ec2#Ipv6AddressList", "traits": { "aws.protocols#ec2QueryName": "Ipv6Addresses", - "smithy.api#documentation": "One or more specific IPv6 addresses to be assigned to the network interface. You can't use this option if you're specifying a number of IPv6 addresses.
", + "smithy.api#documentation": "The IPv6 addresses to be assigned to the network interface. You can't use this option if you're specifying a number of IPv6 addresses.
", "smithy.api#xmlName": "ipv6Addresses" } }, @@ -4166,7 +4166,7 @@ "target": "com.amazonaws.ec2#PrivateIpAddressStringList", "traits": { "aws.protocols#ec2QueryName": "PrivateIpAddress", - "smithy.api#documentation": "One or more IP addresses to be assigned as a secondary private IP address to the network interface. You can't specify this parameter when also specifying a number of secondary IP addresses.
\nIf you don't specify an IP address, Amazon EC2 automatically selects an IP address within the subnet range.
", + "smithy.api#documentation": "The IP addresses to be assigned as a secondary private IP address to the network interface. You can't specify this parameter when also specifying a number of secondary IP addresses.
\nIf you don't specify an IP address, Amazon EC2 automatically selects an IP address within the subnet range.
", "smithy.api#xmlName": "privateIpAddress" } }, @@ -4263,7 +4263,7 @@ "target": "com.amazonaws.ec2#AssociateAddressResult" }, "traits": { - "smithy.api#documentation": "Associates an Elastic IP address, or carrier IP address (for instances that are in\n subnets in Wavelength Zones) with an instance or a network interface. Before you can use an\n Elastic IP address, you must allocate it to your account.
\nAn Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
\n[EC2-Classic, VPC in an EC2-VPC-only account] If the Elastic IP address is already\n associated with a different instance, it is disassociated from that instance and associated\n with the specified instance. If you associate an Elastic IP address with an instance that has\n an existing Elastic IP address, the existing address is disassociated from the instance, but\n remains allocated to your account.
\n[VPC in an EC2-Classic account] If you don't specify a private IP address, the Elastic\n IP address is associated with the primary IP address. If the Elastic IP address is already\n associated with a different instance or a network interface, you get an error unless you allow\n reassociation. You cannot associate an Elastic IP address with an instance or network\n interface that has an existing Elastic IP address.
\n[Subnets in Wavelength Zones] You can associate an IP address from the telecommunication\n carrier to the instance or network interface.
\nYou cannot associate an Elastic IP address with an interface in a different network border group.
\nThis is an idempotent operation. If you perform the operation more than once, Amazon EC2\n doesn't return an error, and you may be charged for each time the Elastic IP address is\n remapped to the same instance. For more information, see the Elastic IP\n Addresses section of Amazon EC2\n Pricing.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nAssociates an Elastic IP address, or carrier IP address (for instances that are in\n subnets in Wavelength Zones) with an instance or a network interface. Before you can use an\n Elastic IP address, you must allocate it to your account.
\nAn Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
\n[EC2-Classic, VPC in an EC2-VPC-only account] If the Elastic IP address is already\n associated with a different instance, it is disassociated from that instance and associated\n with the specified instance. If you associate an Elastic IP address with an instance that has\n an existing Elastic IP address, the existing address is disassociated from the instance, but\n remains allocated to your account.
\n[VPC in an EC2-Classic account] If you don't specify a private IP address, the Elastic\n IP address is associated with the primary IP address. If the Elastic IP address is already\n associated with a different instance or a network interface, you get an error unless you allow\n reassociation. You cannot associate an Elastic IP address with an instance or network\n interface that has an existing Elastic IP address.
\n[Subnets in Wavelength Zones] You can associate an IP address from the telecommunication\n carrier to the instance or network interface.
\nYou cannot associate an Elastic IP address with an interface in a different network border group.
\nThis is an idempotent operation. If you perform the operation more than once, Amazon EC2\n doesn't return an error, and you may be charged for each time the Elastic IP address is\n remapped to the same instance. For more information, see the Elastic IP\n Addresses section of Amazon EC2\n Pricing.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nAssociates an Identity and Access Management (IAM) role with an Certificate Manager (ACM) certificate. \n\t\t\tThis enables the certificate to be used by the ACM for Nitro Enclaves application inside an enclave. For more \n\t\t\tinformation, see Certificate Manager for Nitro Enclaves in the Amazon Web Services Nitro Enclaves \n\t\t\t\t\tUser Guide.
\n\t\t\n\t\tWhen the IAM role is associated with the ACM certificate, the certificate, certificate chain, and encrypted \n\t\t\tprivate key are placed in an Amazon S3 bucket that only the associated IAM role can access. The private key of the certificate \n\t\t\tis encrypted with an Amazon Web Services managed key that has an attached attestation-based key policy.
\n\t\t\n\t\tTo enable the IAM role to access the Amazon S3 object, you must grant it permission to call s3:GetObject \n\t\t\ton the Amazon S3 bucket returned by the command. To enable the IAM role to access the KMS key,\n\t\t\tyou must grant it permission to call kms:Decrypt on the KMS key returned by the command. \n\t\t\tFor more information, see \n\t\t\t\tGrant the role permission to access the certificate and encryption key in the \n\t\t\tAmazon Web Services Nitro Enclaves User Guide.
Associates an Identity and Access Management (IAM) role with an Certificate Manager (ACM) certificate. \n\t\t\tThis enables the certificate to be used by the ACM for Nitro Enclaves application inside an enclave. For more \n\t\t\tinformation, see Certificate Manager for Nitro Enclaves in the Amazon Web Services Nitro Enclaves \n\t\t\t\t\tUser Guide.
\n\t\t\n\t\tWhen the IAM role is associated with the ACM certificate, the certificate, certificate chain, and encrypted \n\t\t\tprivate key are placed in an Amazon S3 location that only the associated IAM role can access. The private key of the certificate \n\t\t\tis encrypted with an Amazon Web Services managed key that has an attached attestation-based key policy.
\n\t\t\n\t\tTo enable the IAM role to access the Amazon S3 object, you must grant it permission to call s3:GetObject \n\t\t\ton the Amazon S3 bucket returned by the command. To enable the IAM role to access the KMS key,\n\t\t\tyou must grant it permission to call kms:Decrypt on the KMS key returned by the command. \n\t\t\tFor more information, see \n\t\t\t\tGrant the role permission to access the certificate and encryption key in the \n\t\t\tAmazon Web Services Nitro Enclaves User Guide.
Adds the specified inbound (ingress) rules to a security group.
\nAn inbound rule permits instances to receive traffic from the specified IPv4 or IPv6 CIDR\n address range, or from the instances that are associated with the specified destination security \n groups. When specifying an inbound rule for your security group in a VPC, the\n IpPermissions must include a source for the traffic.
You specify a protocol for each rule (for example, TCP). \n For TCP and UDP, you must also specify the destination port or port range. \n For ICMP/ICMPv6, you must also specify the ICMP/ICMPv6 type and code. \n You can use -1 to mean all types or all codes.
\nRule changes are propagated to instances within the security group as quickly as possible. \n However, a small delay might occur.
\nFor more information about VPC security group quotas, see Amazon VPC quotas.
\n \nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nAdds the specified inbound (ingress) rules to a security group.
\nAn inbound rule permits instances to receive traffic from the specified IPv4 or IPv6 CIDR\n address range, or from the instances that are associated with the specified destination security \n groups. When specifying an inbound rule for your security group in a VPC, the\n IpPermissions must include a source for the traffic.
You specify a protocol for each rule (for example, TCP). \n For TCP and UDP, you must also specify the destination port or port range. \n For ICMP/ICMPv6, you must also specify the ICMP/ICMPv6 type and code. \n You can use -1 to mean all types or all codes.
\nRule changes are propagated to instances within the security group as quickly as possible. \n However, a small delay might occur.
\nFor more information about VPC security group quotas, see Amazon VPC quotas.
\n \nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\n[EC2-Classic, default VPC] The name of the security group. You must specify either the\n\t\t\tsecurity group ID or the security group name in the request.
" + "smithy.api#documentation": "[EC2-Classic, default VPC] The name of the security group. You must specify either the\n security group ID or the security group name in the request. For security groups in a\n nondefault VPC, you must specify the security group ID.
" } }, "IpPermissions": { @@ -13862,7 +13862,7 @@ "target": "com.amazonaws.ec2#CreateNetworkInterfaceResult" }, "traits": { - "smithy.api#documentation": "Creates a network interface in the specified subnet.
\nFor more information about network interfaces, see Elastic Network Interfaces \n in the Amazon Virtual Private Cloud User Guide.
" + "smithy.api#documentation": "Creates a network interface in the specified subnet.
\nThe number of IP addresses you can assign to a network interface varies by instance\n type. For more information, see IP Addresses Per ENI Per\n Instance Type in the Amazon Virtual Private Cloud User Guide.
\nFor more information about network interfaces, see Elastic network interfaces \n in the Amazon Elastic Compute Cloud User Guide.
" } }, "com.amazonaws.ec2#CreateNetworkInterfacePermission": { @@ -13971,7 +13971,7 @@ "aws.protocols#ec2QueryName": "Ipv6AddressCount", "smithy.api#clientOptional": {}, "smithy.api#default": 0, - "smithy.api#documentation": "The number of IPv6 addresses to assign to a network interface. Amazon EC2\n automatically selects the IPv6 addresses from the subnet range. You can't use this\n option if specifying specific IPv6 addresses. If your subnet has the AssignIpv6AddressOnCreation attribute set\n to true, you can specify 0 to override this setting.
The number of IPv6 addresses to assign to a network interface. Amazon EC2\n automatically selects the IPv6 addresses from the subnet range.
\nYou can't specify a count of IPv6 addresses using this parameter if you've specified \n one of the following: specific IPv6 addresses, specific IPv6 prefixes, or a count of IPv6 prefixes.
\nIf your subnet has the AssignIpv6AddressOnCreation attribute set, you can\n override that setting by specifying 0 as the IPv6 address count.
One or more specific IPv6 addresses from the IPv6 CIDR block range of your subnet.\n You can't use this option if you're specifying a number of IPv6 addresses.
", + "smithy.api#documentation": "The IPv6 addresses from the IPv6 CIDR block range of your subnet.
\nYou can't specify IPv6 addresses using this parameter if you've specified one of the \n following: a count of IPv6 addresses, specific IPv6 prefixes, or a count of IPv6 prefixes.
", "smithy.api#xmlName": "ipv6Addresses" } }, @@ -13995,7 +13995,7 @@ "target": "com.amazonaws.ec2#PrivateIpAddressSpecificationList", "traits": { "aws.protocols#ec2QueryName": "PrivateIpAddresses", - "smithy.api#documentation": "One or more private IPv4 addresses.
", + "smithy.api#documentation": "The private IPv4 addresses.
\nYou can't specify private IPv4 addresses if you've specified one of the following:\n a count of private IPv4 addresses, specific IPv4 prefixes, or a count of IPv4 prefixes.
", "smithy.api#xmlName": "privateIpAddresses" } }, @@ -14005,14 +14005,14 @@ "aws.protocols#ec2QueryName": "SecondaryPrivateIpAddressCount", "smithy.api#clientOptional": {}, "smithy.api#default": 0, - "smithy.api#documentation": "The number of secondary private IPv4 addresses to assign to a network interface. When\n you specify a number of secondary IPv4 addresses, Amazon EC2 selects these IP addresses\n within the subnet's IPv4 CIDR range. You can't specify this option and specify more than\n one private IP address using privateIpAddresses.
The number of IP addresses you can assign to a network interface varies by instance\n type. For more information, see IP Addresses Per ENI Per\n Instance Type in the Amazon Virtual Private Cloud User Guide.
", + "smithy.api#documentation": "The number of secondary private IPv4 addresses to assign to a network interface. When\n you specify a number of secondary IPv4 addresses, Amazon EC2 selects these IP addresses\n within the subnet's IPv4 CIDR range. You can't specify this option and specify more than\n one private IP address using privateIpAddresses.
You can't specify a count of private IPv4 addresses if you've specified one of the following:\n specific private IPv4 addresses, specific IPv4 prefixes, or a count of IPv4 prefixes.
", "smithy.api#xmlName": "secondaryPrivateIpAddressCount" } }, "Ipv4Prefixes": { "target": "com.amazonaws.ec2#Ipv4PrefixList", "traits": { - "smithy.api#documentation": "One or more IPv4 prefixes assigned to the network interface. You cannot use this option if you use the Ipv4PrefixCount option.
The IPv4 prefixes assigned to the network interface.
\nYou can't specify IPv4 prefixes if you've specified one of the following:\n a count of IPv4 prefixes, specific private IPv4 addresses, or a count of private IPv4 addresses.
", "smithy.api#xmlName": "Ipv4Prefix" } }, @@ -14021,13 +14021,13 @@ "traits": { "smithy.api#clientOptional": {}, "smithy.api#default": 0, - "smithy.api#documentation": "The number of IPv4 prefixes that Amazon Web Services automatically assigns to the network interface. You cannot use this option if you use the Ipv4 Prefixes option.
The number of IPv4 prefixes that Amazon Web Services automatically assigns to the network interface.
\nYou can't specify a count of IPv4 prefixes if you've specified one of the following:\n specific IPv4 prefixes, specific private IPv4 addresses, or a count of private IPv4\n addresses.
" } }, "Ipv6Prefixes": { "target": "com.amazonaws.ec2#Ipv6PrefixList", "traits": { - "smithy.api#documentation": "One or more IPv6 prefixes assigned to the network interface. You cannot use this option if you use the Ipv6PrefixCount option.
The IPv6 prefixes assigned to the network interface.
\nYou can't specify IPv6 prefixes if you've specified one of the following:\n a count of IPv6 prefixes, specific IPv6 addresses, or a count of IPv6 addresses.
", "smithy.api#xmlName": "Ipv6Prefix" } }, @@ -14036,13 +14036,13 @@ "traits": { "smithy.api#clientOptional": {}, "smithy.api#default": 0, - "smithy.api#documentation": "The number of IPv6 prefixes that Amazon Web Services automatically assigns to the network interface. You cannot use this option if you use the Ipv6Prefixes option.
The number of IPv6 prefixes that Amazon Web Services automatically assigns to the network interface.
\nYou can't specify a count of IPv6 prefixes if you've specified one of the following:\n specific IPv6 prefixes, specific IPv6 addresses, or a count of IPv6 addresses.
" } }, "InterfaceType": { "target": "com.amazonaws.ec2#NetworkInterfaceCreationType", "traits": { - "smithy.api#documentation": "The type of network interface. The default is interface.
The only supported values are efa and trunk.
The type of network interface. The default is interface.
The only supported values are efa and trunk.
Contains the parameters for CreateNetworkInterface.
" } }, "com.amazonaws.ec2#CreateNetworkInterfaceResult": { @@ -14093,9 +14090,6 @@ "smithy.api#xmlName": "clientToken" } } - }, - "traits": { - "smithy.api#documentation": "Contains the output of CreateNetworkInterface.
" } }, "com.amazonaws.ec2#CreatePlacementGroup": { @@ -14647,7 +14641,7 @@ "target": "com.amazonaws.ec2#CreateSecurityGroupResult" }, "traits": { - "smithy.api#documentation": "Creates a security group.
\nA security group acts as a virtual firewall for your instance to control inbound and outbound traffic.\n For more information, see\n\t\t\t\tAmazon EC2 security groups in \n\t\t\t\tthe Amazon Elastic Compute Cloud User Guide and \n\t\t\t\tSecurity groups for your VPC in the\n\t\t\t\tAmazon Virtual Private Cloud User Guide.
\nWhen you create a security group, you specify a friendly name of your choice. You can have a security group for use in EC2-Classic with the same name as a security group for use in a VPC. However, you can't have two security groups for use in EC2-Classic with the same name or two security groups for use in a VPC with the same name.
\nYou have a default security group for use in EC2-Classic and a default security group for use in your VPC. If you don't specify a security group when you launch an instance, the instance is launched into the appropriate default security group. A default security group includes a default rule that grants instances unrestricted network access to each other.
\nYou can add or remove rules from your security groups using \n\t\t\t\t\tAuthorizeSecurityGroupIngress,\n\t\t\t\t\tAuthorizeSecurityGroupEgress,\n\t\t\t\t\tRevokeSecurityGroupIngress, and\n\t\t\t\t\tRevokeSecurityGroupEgress.
\nFor more information about VPC security group limits, see Amazon VPC Limits.
\n \nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nCreates a security group.
\nA security group acts as a virtual firewall for your instance to control inbound and outbound traffic.\n For more information, see\n\t\t\t\tAmazon EC2 security groups in \n\t\t\t\tthe Amazon Elastic Compute Cloud User Guide and \n\t\t\t\tSecurity groups for your VPC in the\n\t\t\t\tAmazon Virtual Private Cloud User Guide.
\nWhen you create a security group, you specify a friendly name of your choice. You can have a security group for use in EC2-Classic with the same name as a security group for use in a VPC. However, you can't have two security groups for use in EC2-Classic with the same name or two security groups for use in a VPC with the same name.
\nYou have a default security group for use in EC2-Classic and a default security group for use in your VPC. If you don't specify a security group when you launch an instance, the instance is launched into the appropriate default security group. A default security group includes a default rule that grants instances unrestricted network access to each other.
\nYou can add or remove rules from your security groups using \n\t\t\t\t\tAuthorizeSecurityGroupIngress,\n\t\t\t\t\tAuthorizeSecurityGroupEgress,\n\t\t\t\t\tRevokeSecurityGroupIngress, and\n\t\t\t\t\tRevokeSecurityGroupEgress.
\nFor more information about VPC security group limits, see Amazon VPC Limits.
\n \nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nCreates crash-consistent snapshots of multiple EBS volumes and stores the data in S3.\n Volumes are chosen by specifying an instance. Any attached volumes will produce one snapshot\n each that is crash-consistent across the instance. Boot volumes can be excluded by changing the \n parameters.
\n \t\nYou can create multi-volume snapshots of instances in a Region and instances on an \n \tOutpost. If you create snapshots from an instance in a Region, the snapshots must be stored \n \tin the same Region as the instance. If you create snapshots from an instance on an Outpost, \n \tthe snapshots can be stored on the same Outpost as the instance, or in the Region for that \n \tOutpost.
" + "smithy.api#documentation": "Creates crash-consistent snapshots of multiple EBS volumes and stores the data in S3.\n Volumes are chosen by specifying an instance. Any attached volumes will produce one snapshot\n each that is crash-consistent across the instance.
\n \nYou can include all of the volumes currently attached to the instance, or you can exclude \n the root volume or specific data (non-root) volumes from the multi-volume snapshot set.
\n \t\nYou can create multi-volume snapshots of instances in a Region and instances on an \n \tOutpost. If you create snapshots from an instance in a Region, the snapshots must be stored \n \tin the same Region as the instance. If you create snapshots from an instance on an Outpost, \n \tthe snapshots can be stored on the same Outpost as the instance, or in the Region for that \n \tOutpost.
" } }, "com.amazonaws.ec2#CreateSnapshotsRequest": { @@ -19603,7 +19597,7 @@ "target": "smithy.api#Unit" }, "traits": { - "smithy.api#documentation": "Deletes a security group.
\nIf you attempt to delete a security group that is associated with an instance, or is\n\t\t\t referenced by another security group, the operation fails with\n\t\t\t\tInvalidGroup.InUse in EC2-Classic or\n\t\t\t\tDependencyViolation in EC2-VPC.
We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nDeletes a security group.
\nIf you attempt to delete a security group that is associated with an instance, or is\n\t\t\t referenced by another security group, the operation fails with\n\t\t\t\tInvalidGroup.InUse in EC2-Classic or\n\t\t\t\tDependencyViolation in EC2-VPC.
We are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\n[EC2-Classic, default VPC] The name of the security group. You can specify either the security group name or the security group ID.
" + "smithy.api#documentation": "[EC2-Classic, default VPC] The name of the security group. You can specify either the\n security group name or the security group ID. For security groups in a nondefault VPC,\n you must specify the security group ID.
" } }, "DryRun": { @@ -21354,7 +21348,7 @@ "target": "com.amazonaws.ec2#DescribeAddressesResult" }, "traits": { - "smithy.api#documentation": "Describes the specified Elastic IP addresses or all of your Elastic IP addresses.
\nAn Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nDescribes the specified Elastic IP addresses or all of your Elastic IP addresses.
\nAn Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nIf true, all deprecated AMIs are included in the response. If\n false, no deprecated AMIs are included in the response. If no value is\n specified, the default value is false.
If you are the AMI owner, all deprecated AMIs appear in the response regardless of the value (true or false) that you set for this parameter.
Specifies whether to include deprecated AMIs.
\nDefault: No deprecated AMIs are included in the response.
\nIf you are the AMI owner, all deprecated AMIs appear in the response regardless of what\n you specify for this parameter.
\nOne or more network interface permission IDs.
", + "smithy.api#documentation": "The network interface permission IDs.
", "smithy.api#xmlName": "NetworkInterfacePermissionId" } }, @@ -28065,7 +28059,7 @@ "NetworkInterfaceIds": { "target": "com.amazonaws.ec2#NetworkInterfaceIdList", "traits": { - "smithy.api#documentation": "One or more network interface IDs.
\n\t\tDefault: Describes all your network interfaces.
", + "smithy.api#documentation": "The network interface IDs.
\n\t\tDefault: Describes all your network interfaces.
", "smithy.api#xmlName": "NetworkInterfaceId" } }, @@ -29382,7 +29376,7 @@ "target": "com.amazonaws.ec2#DescribeSecurityGroupsResult" }, "traits": { - "smithy.api#documentation": "Describes the specified security groups or all of your security groups.
\nA security group is for use with instances either in the EC2-Classic platform \n\t\t\t\tor in a specific VPC. For more information, see\n\t\t\t\tAmazon EC2 security groups in \n\t\t\t\tthe Amazon Elastic Compute Cloud User Guide and \n\t\t\t\tSecurity groups for your VPC in the\n\t\t\t\tAmazon Virtual Private Cloud User Guide.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nDescribes the specified security groups or all of your security groups.
\nA security group is for use with instances either in the EC2-Classic platform \n\t\t\t\tor in a specific VPC. For more information, see\n\t\t\t\tAmazon EC2 security groups in \n\t\t\t\tthe Amazon Elastic Compute Cloud User Guide and \n\t\t\t\tSecurity groups for your VPC in the\n\t\t\t\tAmazon Virtual Private Cloud User Guide.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nDisassociates an Elastic IP address from the instance or network interface it's associated with.
\n\t\t\tAn Elastic IP address is for use in either the EC2-Classic platform or in a VPC. For more\n\t\t\tinformation, see Elastic IP\n\t\t\t\tAddresses in the Amazon Elastic Compute Cloud User Guide.
\n \nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nThis is an idempotent operation. If you perform the operation more than once, Amazon EC2 doesn't return an error.
" + "smithy.api#documentation": "Disassociates an Elastic IP address from the instance or network interface it's associated with.
\n\t\t\tAn Elastic IP address is for use in either the EC2-Classic platform or in a VPC. For more\n\t\t\tinformation, see Elastic IP\n\t\t\t\tAddresses in the Amazon Elastic Compute Cloud User Guide.
\n \nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nThis is an idempotent operation. If you perform the operation more than once, Amazon EC2 doesn't return an error.
" } }, "com.amazonaws.ec2#DisassociateAddressRequest": { @@ -35779,8 +35773,9 @@ "KmsKeyId": { "target": "com.amazonaws.ec2#String", "traits": { + "aws.protocols#ec2QueryName": "KmsKeyId", "smithy.api#documentation": "Identifier (key ID, key alias, ID ARN, or alias ARN) for a customer managed CMK under\n which the EBS volume is encrypted.
\nThis parameter is only supported on BlockDeviceMapping objects called by\n RunInstances, RequestSpotFleet,\n and RequestSpotInstances.
Import single or multi-volume disk images or EBS snapshots into an Amazon Machine Image (AMI).
\nFor more information, see Importing a \n VM as an image using VM Import/Export in the VM Import/Export User Guide.
" + "smithy.api#documentation": "Import single or multi-volume disk images or EBS snapshots into an Amazon Machine Image (AMI).
\nAmazon Web Services VM Import/Export strongly recommends specifying a value for either the\n --license-type or --usage-operation parameter when you create a new\n VM Import task. This ensures your operating system is licensed appropriately and your billing is\n optimized.
For more information, see Importing a \n VM as an image using VM Import/Export in the VM Import/Export User Guide.
" } }, "com.amazonaws.ec2#ImportImageLicenseConfigurationRequest": { @@ -45250,7 +45245,7 @@ "LicenseType": { "target": "com.amazonaws.ec2#String", "traits": { - "smithy.api#documentation": "The license type to be used for the Amazon Machine Image (AMI) after importing.
\nBy default, we detect the source-system operating system (OS) and apply the appropriate license. Specify\n AWS to replace the source-system license with an Amazon Web Services license, if appropriate. Specify BYOL\n to retain the source-system license, if appropriate.
To use BYOL, you must have existing licenses with rights to use these licenses in a third party\n cloud, such as Amazon Web Services. For more information, see Prerequisites in the\n VM Import/Export User Guide.
The license type to be used for the Amazon Machine Image (AMI) after importing.
\nSpecify AWS to replace the source-system license with an Amazon Web Services\n license or BYOL to retain the source-system license. Leaving this parameter\n undefined is the same as choosing AWS when importing a Windows Server operating\n system, and the same as choosing BYOL when importing a Windows client operating\n system (such as Windows 10) or a Linux operating system.
To use BYOL, you must have existing licenses with rights to use these licenses in a third party\n cloud, such as Amazon Web Services. For more information, see Prerequisites in the\n VM Import/Export User Guide.
One or more security groups.
", + "smithy.api#documentation": "The security groups.
", "smithy.api#xmlName": "groupSet" } }, @@ -48216,7 +48211,7 @@ "target": "com.amazonaws.ec2#InstanceIpv6AddressList", "traits": { "aws.protocols#ec2QueryName": "Ipv6AddressesSet", - "smithy.api#documentation": "One or more IPv6 addresses associated with the network interface.
", + "smithy.api#documentation": "The IPv6 addresses associated with the network interface.
", "smithy.api#xmlName": "ipv6AddressesSet" } }, @@ -48264,7 +48259,7 @@ "target": "com.amazonaws.ec2#InstancePrivateIpAddressList", "traits": { "aws.protocols#ec2QueryName": "PrivateIpAddressesSet", - "smithy.api#documentation": "One or more private IPv4 addresses associated with the network interface.
", + "smithy.api#documentation": "The private IPv4 addresses associated with the network interface.
", "smithy.api#xmlName": "privateIpAddressesSet" } }, @@ -48512,7 +48507,7 @@ "target": "com.amazonaws.ec2#InstanceIpv6AddressList", "traits": { "aws.protocols#ec2QueryName": "Ipv6Addresses", - "smithy.api#documentation": "One or more IPv6 addresses to assign to the network interface. You cannot specify\n this option and the option to assign a number of IPv6 addresses in the same request. You\n cannot specify this option if you've specified a minimum number of instances to\n launch.
", + "smithy.api#documentation": "The IPv6 addresses to assign to the network interface. You cannot specify\n this option and the option to assign a number of IPv6 addresses in the same request. You\n cannot specify this option if you've specified a minimum number of instances to\n launch.
", "smithy.api#xmlName": "ipv6AddressesSet" } }, @@ -48536,7 +48531,7 @@ "target": "com.amazonaws.ec2#PrivateIpAddressSpecificationList", "traits": { "aws.protocols#ec2QueryName": "PrivateIpAddresses", - "smithy.api#documentation": "One or more private IPv4 addresses to assign to the network interface. Only one private IPv4 address can be designated as primary. You cannot specify this option if you're\n \tlaunching more than one instance in a RunInstances request.
", + "smithy.api#documentation": "The private IPv4 addresses to assign to the network interface. Only one private IPv4 address can be designated as primary. You cannot specify this option if you're\n \tlaunching more than one instance in a RunInstances request.
", "smithy.api#xmlName": "privateIpAddressesSet" } }, @@ -48583,7 +48578,7 @@ "Ipv4Prefixes": { "target": "com.amazonaws.ec2#Ipv4PrefixList", "traits": { - "smithy.api#documentation": "One or more IPv4 delegated prefixes to be assigned to the network interface. You cannot \n use this option if you use the Ipv4PrefixCount option.
The IPv4 delegated prefixes to be assigned to the network interface. You cannot \n use this option if you use the Ipv4PrefixCount option.
One or more IPv6 delegated prefixes to be assigned to the network interface. You cannot \n use this option if you use the Ipv6PrefixCount option.
The IPv6 delegated prefixes to be assigned to the network interface. You cannot \n use this option if you use the Ipv6PrefixCount option.
The accelerators that must be on the instance type.
\nFor instance types with NVIDIA A100 GPUs, specify a100.
For instance types with NVIDIA V100 GPUs, specify v100.
For instance types with NVIDIA K80 GPUs, specify k80.
For instance types with NVIDIA T4 GPUs, specify t4.
For instance types with NVIDIA M60 GPUs, specify m60.
For instance types with AMD Radeon Pro V520 GPUs, specify radeon-pro-v520.
For instance types with Xilinx VU9P FPGAs, specify vu9p.
For instance types with Amazon Web Services Inferentia GPUs, specify inferentia.
For instance types with NVIDIA GRID K520 GPUs, specify k520.
Default: Any accelerator
", + "smithy.api#documentation": "The accelerators that must be on the instance type.
\nFor instance types with NVIDIA A100 GPUs, specify a100.
For instance types with NVIDIA V100 GPUs, specify v100.
For instance types with NVIDIA K80 GPUs, specify k80.
For instance types with NVIDIA T4 GPUs, specify t4.
For instance types with NVIDIA M60 GPUs, specify m60.
For instance types with AMD Radeon Pro V520 GPUs, specify radeon-pro-v520.
For instance types with Xilinx VU9P FPGAs, specify vu9p.
For instance types with Amazon Web Services Inferentia chips, specify inferentia.
For instance types with NVIDIA GRID K520 GPUs, specify k520.
Default: Any accelerator
", "smithy.api#xmlName": "acceleratorNameSet" } }, @@ -48993,7 +48988,7 @@ "AcceleratorNames": { "target": "com.amazonaws.ec2#AcceleratorNameSet", "traits": { - "smithy.api#documentation": "The accelerators that must be on the instance type.
\nFor instance types with NVIDIA A100 GPUs, specify a100.
For instance types with NVIDIA V100 GPUs, specify v100.
For instance types with NVIDIA K80 GPUs, specify k80.
For instance types with NVIDIA T4 GPUs, specify t4.
For instance types with NVIDIA M60 GPUs, specify m60.
For instance types with AMD Radeon Pro V520 GPUs, specify radeon-pro-v520.
For instance types with Xilinx VU9P FPGAs, specify vu9p.
For instance types with Amazon Web Services Inferentia GPUs, specify inferentia.
For instance types with NVIDIA GRID K520 GPUs, specify k520.
Default: Any accelerator
", + "smithy.api#documentation": "The accelerators that must be on the instance type.
\nFor instance types with NVIDIA A100 GPUs, specify a100.
For instance types with NVIDIA V100 GPUs, specify v100.
For instance types with NVIDIA K80 GPUs, specify k80.
For instance types with NVIDIA T4 GPUs, specify t4.
For instance types with NVIDIA M60 GPUs, specify m60.
For instance types with AMD Radeon Pro V520 GPUs, specify radeon-pro-v520.
For instance types with Xilinx VU9P FPGAs, specify vu9p.
For instance types with Amazon Web Services Inferentia chips, specify inferentia.
For instance types with NVIDIA GRID K520 GPUs, specify k520.
Default: Any accelerator
", "smithy.api#xmlName": "AcceleratorName" } }, @@ -49056,6 +49051,7 @@ "ExcludeDataVolumeIds": { "target": "com.amazonaws.ec2#VolumeIdStringList", "traits": { + "smithy.api#documentation": "The IDs of the data (non-root) volumes to exclude from the multi-volume snapshot set. \n If you specify the ID of the root volume, the request fails. To exclude the root volume, \n use ExcludeBootVolume.
\nYou can specify up to 40 volume IDs per request.
", "smithy.api#xmlName": "ExcludeDataVolumeId" } } @@ -55043,7 +55039,7 @@ "target": "com.amazonaws.ec2#String", "traits": { "aws.protocols#ec2QueryName": "Ipv4Prefix", - "smithy.api#documentation": "One or more IPv4 delegated prefixes assigned to the network interface.
", + "smithy.api#documentation": "The IPv4 delegated prefixes assigned to the network interface.
", "smithy.api#xmlName": "ipv4Prefix" } } @@ -55260,7 +55256,7 @@ "target": "com.amazonaws.ec2#String", "traits": { "aws.protocols#ec2QueryName": "Ipv6Prefix", - "smithy.api#documentation": "One or more IPv6 delegated prefixes assigned to the network interface.
", + "smithy.api#documentation": "The IPv6 delegated prefixes assigned to the network interface.
", "smithy.api#xmlName": "ipv6Prefix" } } @@ -60131,7 +60127,7 @@ "target": "com.amazonaws.ec2#InstanceAttributeName", "traits": { "aws.protocols#ec2QueryName": "Attribute", - "smithy.api#documentation": "The name of the attribute.
", + "smithy.api#documentation": "The name of the attribute to modify.
\nYou can modify the following attributes only: disableApiTermination | instanceType | \n kernel | ramdisk | instanceInitiatedShutdownBehavior | blockDeviceMapping | \n userData | sourceDestCheck | groupSet | ebsOptimized | sriovNetSupport | \n enaSupport | nvmeSupport | disableApiStop | enclaveOptions\n
A private Autonomous System Number (ASN) for the Amazon side of a BGP session. \n The range is 64512 to 65534 for 16-bit ASNs and 4200000000 to 4294967294 for 32-bit ASNs.
" + "smithy.api#documentation": "A private Autonomous System Number (ASN) for the Amazon side of a BGP session. \n The range is 64512 to 65534 for 16-bit ASNs and 4200000000 to 4294967294 for 32-bit ASNs.
\nThe modify ASN operation is not allowed on a transit gateway with active BGP sessions. You must first delete all transit gateway attachments that have BGP configured prior to modifying the ASN on the transit gateway.
" } } }, @@ -63562,7 +63558,7 @@ "target": "com.amazonaws.ec2#MoveAddressToVpcResult" }, "traits": { - "smithy.api#documentation": "Moves an Elastic IP address from the EC2-Classic platform to the EC2-VPC platform. The\n Elastic IP address must be allocated to your account for more than 24 hours, and it must not\n be associated with an instance. After the Elastic IP address is moved, it is no longer\n available for use in the EC2-Classic platform, unless you move it back using the\n RestoreAddressToClassic request. You cannot move an Elastic IP address that was\n originally allocated for use in the EC2-VPC platform to the EC2-Classic platform.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nMoves an Elastic IP address from the EC2-Classic platform to the EC2-VPC platform. The\n Elastic IP address must be allocated to your account for more than 24 hours, and it must not\n be associated with an instance. After the Elastic IP address is moved, it is no longer\n available for use in the EC2-Classic platform, unless you move it back using the\n RestoreAddressToClassic request. You cannot move an Elastic IP address that was\n originally allocated for use in the EC2-VPC platform to the EC2-Classic platform.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nDescribes the status of a moving Elastic IP address.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nDescribes the status of a moving Elastic IP address.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nThe private IPv4 addresses.
", + "smithy.api#documentation": "The private IPv4 address.
", "smithy.api#xmlName": "privateIpAddress" } } @@ -69681,7 +69677,7 @@ "target": "smithy.api#Unit" }, "traits": { - "smithy.api#documentation": "Releases the specified Elastic IP address.
\n[EC2-Classic, default VPC] Releasing an Elastic IP address automatically disassociates it\n\t\t\t\tfrom any instance that it's associated with. To disassociate an Elastic IP address without\n\t\t\t\treleasing it, use DisassociateAddress.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\n[Nondefault VPC] You must use DisassociateAddress to disassociate the Elastic IP address\n\t\t\t before you can release it. Otherwise, Amazon EC2 returns an error (InvalidIPAddress.InUse).
After releasing an Elastic IP address, it is released to the IP address pool. \n Be sure to update your DNS records and any servers or devices that communicate with the address. \n If you attempt to release an Elastic IP address that you already released, you'll get an\n AuthFailure error if the address is already allocated to another Amazon Web Services account.
[EC2-VPC] After you release an Elastic IP address for use in a VPC, you might be able to recover it.\n For more information, see AllocateAddress.
\nFor more\n information, see Elastic IP\n Addresses in the Amazon Elastic Compute Cloud User Guide.
" + "smithy.api#documentation": "Releases the specified Elastic IP address.
\n[EC2-Classic, default VPC] Releasing an Elastic IP address automatically disassociates it\n\t\t\t\tfrom any instance that it's associated with. To disassociate an Elastic IP address without\n\t\t\t\treleasing it, use DisassociateAddress.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\n[Nondefault VPC] You must use DisassociateAddress to disassociate the Elastic IP address\n\t\t\t before you can release it. Otherwise, Amazon EC2 returns an error (InvalidIPAddress.InUse).
After releasing an Elastic IP address, it is released to the IP address pool. \n Be sure to update your DNS records and any servers or devices that communicate with the address. \n If you attempt to release an Elastic IP address that you already released, you'll get an\n AuthFailure error if the address is already allocated to another Amazon Web Services account.
[EC2-VPC] After you release an Elastic IP address for use in a VPC, you might be able to recover it.\n For more information, see AllocateAddress.
\nFor more\n information, see Elastic IP\n Addresses in the Amazon Elastic Compute Cloud User Guide.
" } }, "com.amazonaws.ec2#ReleaseAddressRequest": { @@ -70777,7 +70773,7 @@ "InstanceType": { "target": "com.amazonaws.ec2#InstanceType", "traits": { - "smithy.api#documentation": "The instance type. For more information, see Instance types in the\n Amazon Elastic Compute Cloud User Guide.
\nIf you specify InstanceTypes, you can't specify\n InstanceRequirements.
The instance type. For more information, see Instance types in the\n Amazon Elastic Compute Cloud User Guide.
\nIf you specify InstanceType, you can't specify\n InstanceRequirements.
Restores an Elastic IP address that was previously moved to the EC2-VPC platform back to the EC2-Classic platform. You cannot move an Elastic IP address that was originally allocated for use in EC2-VPC. The Elastic IP address must not be associated with an instance or network interface.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nRestores an Elastic IP address that was previously moved to the EC2-VPC platform back to the EC2-Classic platform. You cannot move an Elastic IP address that was originally allocated for use in EC2-VPC. The Elastic IP address must not be associated with an instance or network interface.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nRemoves the specified inbound (ingress) rules from a security group.
\n\nYou can specify rules using either rule IDs or security group rule properties. If you use\n rule properties, the values that you specify (for example, ports) must match the existing rule's \n values exactly. Each rule has a protocol, from and to ports, and source (CIDR range, \n security group, or prefix list). For the TCP and UDP protocols, you must also specify the \n destination port or range of ports. For the ICMP protocol, you must also specify the ICMP type \n and code. If the security group rule has a description, you do not need to specify the description \n to revoke the rule.
\n[EC2-Classic, default VPC] If the values you specify do not match the existing rule's values, no error is\n returned, and the output describes the security group rules that were not revoked.
\nAmazon Web Services recommends that you describe the security group to verify that the rules were removed.
\n\nRule changes are propagated to instances within the security group as quickly as possible. However, a small delay might occur.
\n \nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nRemoves the specified inbound (ingress) rules from a security group.
\n\nYou can specify rules using either rule IDs or security group rule properties. If you use\n rule properties, the values that you specify (for example, ports) must match the existing rule's \n values exactly. Each rule has a protocol, from and to ports, and source (CIDR range, \n security group, or prefix list). For the TCP and UDP protocols, you must also specify the \n destination port or range of ports. For the ICMP protocol, you must also specify the ICMP type \n and code. If the security group rule has a description, you do not need to specify the description \n to revoke the rule.
\n[EC2-Classic, default VPC] If the values you specify do not match the existing rule's values, no error is\n returned, and the output describes the security group rules that were not revoked.
\nAmazon Web Services recommends that you describe the security group to verify that the rules were removed.
\n\nRule changes are propagated to instances within the security group as quickly as possible. However, a small delay might occur.
\n \nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\n[EC2-Classic, default VPC] The name of the security group. You must specify either the\n security group ID or the security group name in the request.
" + "smithy.api#documentation": "[EC2-Classic, default VPC] The name of the security group. You must specify either the\n security group ID or the security group name in the request. For security groups in a\n nondefault VPC, you must specify the security group ID.
" } }, "IpPermissions": { @@ -85022,7 +85018,7 @@ "Ipv6Prefixes": { "target": "com.amazonaws.ec2#IpPrefixList", "traits": { - "smithy.api#documentation": "One or more IPv6 prefixes to unassign from the network interface.
", + "smithy.api#documentation": "The IPv6 prefixes to unassign from the network interface.
", "smithy.api#xmlName": "Ipv6Prefix" } }, @@ -85439,7 +85435,7 @@ "GroupName": { "target": "com.amazonaws.ec2#SecurityGroupName", "traits": { - "smithy.api#documentation": "[EC2-Classic, default VPC] The name of the security group. You must specify either the\n\t\t\tsecurity group ID or the security group name in the request.
" + "smithy.api#documentation": "[EC2-Classic, default VPC] The name of the security group. You must specify either the\n security group ID or the security group name in the request. For security groups in a\n nondefault VPC, you must specify the security group ID.
" } }, "IpPermissions": { @@ -85629,7 +85625,7 @@ } }, "traits": { - "smithy.api#documentation": "Describes a security group and Amazon Web Services account ID pair.
\nWe are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\nDescribes a security group and Amazon Web Services account ID pair.
\nWe are retiring EC2-Classic. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.
\n