From 67509d43371d9854fb3e55586d493bc16446e8c4 Mon Sep 17 00:00:00 2001 From: awstools Date: Mon, 21 Oct 2024 18:17:32 +0000 Subject: [PATCH] feat(client-ec2): Amazon EC2 now allows you to create network interfaces with just the EFA driver and no ENA driver by specifying the network interface type as efa-only. --- .../AssignPrivateNatGatewayAddressCommand.ts | 2 +- .../AssociateNatGatewayAddressCommand.ts | 8 ++- .../commands/CreateDefaultSubnetCommand.ts | 2 +- .../src/commands/CreateFlowLogsCommand.ts | 2 +- .../src/commands/CreateNatGatewayCommand.ts | 8 ++- .../commands/CreateNetworkInterfaceCommand.ts | 4 +- .../CreateSubnetCidrReservationCommand.ts | 4 +- .../src/commands/CreateVpcCommand.ts | 2 +- .../src/commands/DeleteVpcCommand.ts | 8 ++- .../DescribeNetworkInterfacesCommand.ts | 2 +- .../src/commands/DisableImageCommand.ts | 2 +- .../DisassociateNatGatewayAddressCommand.ts | 2 +- ...nceTypesFromInstanceRequirementsCommand.ts | 6 +- ...UnassignPrivateNatGatewayAddressCommand.ts | 4 +- clients/client-ec2/src/models/models_0.ts | 2 +- clients/client-ec2/src/models/models_1.ts | 24 ++++---- clients/client-ec2/src/models/models_2.ts | 2 + clients/client-ec2/src/models/models_6.ts | 7 ++- codegen/sdk-codegen/aws-models/ec2.json | 56 +++++++++++-------- 19 files changed, 90 insertions(+), 57 deletions(-) diff --git a/clients/client-ec2/src/commands/AssignPrivateNatGatewayAddressCommand.ts b/clients/client-ec2/src/commands/AssignPrivateNatGatewayAddressCommand.ts index df6f0575e839..897137ee6e16 100644 --- a/clients/client-ec2/src/commands/AssignPrivateNatGatewayAddressCommand.ts +++ b/clients/client-ec2/src/commands/AssignPrivateNatGatewayAddressCommand.ts @@ -34,7 +34,7 @@ export interface AssignPrivateNatGatewayAddressCommandOutput /** *

Assigns private IPv4 addresses to a private NAT gateway. For more information, see - * Work with NAT gateways in the Amazon VPC User Guide.

+ * Work with NAT gateways in the Amazon VPC 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/AssociateNatGatewayAddressCommand.ts b/clients/client-ec2/src/commands/AssociateNatGatewayAddressCommand.ts index 1c7304887784..fd15cb4caf79 100644 --- a/clients/client-ec2/src/commands/AssociateNatGatewayAddressCommand.ts +++ b/clients/client-ec2/src/commands/AssociateNatGatewayAddressCommand.ts @@ -29,11 +29,15 @@ export interface AssociateNatGatewayAddressCommandOutput extends AssociateNatGat /** *

Associates Elastic IP addresses (EIPs) and private IPv4 addresses with a public NAT gateway. For more information, - * see Work with NAT gateways in the Amazon VPC User Guide.

+ * see Work with NAT gateways in the Amazon VPC User Guide.

*

By default, you can associate up to 2 Elastic IP addresses per public NAT gateway. You can increase the limit by requesting a quota adjustment. * For more information, see Elastic IP address quotas in the Amazon VPC User Guide.

* - *

When you associate an EIP or secondary EIPs with a public NAT gateway, the network border group of the EIPs must match the network border group of the Availability Zone (AZ) that the public NAT gateway is in. If it's not the same, the EIP will fail to associate. You can see the network border group for the subnet's AZ by viewing the details of the subnet. Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. For more information about network border groups and EIPs, see Allocate an Elastic IP address in the Amazon VPC User Guide. + *

When you associate an EIP or secondary EIPs with a public NAT gateway, the network border group of the EIPs + * must match the network border group of the Availability Zone (AZ) that the public NAT gateway is in. If it's not the same, + * the EIP will fail to associate. You can see the network border group for the subnet's AZ by viewing the details of the subnet. + * Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. For more information + * about network border groups and EIPs, see Allocate an Elastic IP address in the Amazon VPC User Guide. *

* * @example diff --git a/clients/client-ec2/src/commands/CreateDefaultSubnetCommand.ts b/clients/client-ec2/src/commands/CreateDefaultSubnetCommand.ts index ff41ae009a70..f56ffd604427 100644 --- a/clients/client-ec2/src/commands/CreateDefaultSubnetCommand.ts +++ b/clients/client-ec2/src/commands/CreateDefaultSubnetCommand.ts @@ -30,7 +30,7 @@ export interface CreateDefaultSubnetCommandOutput extends CreateDefaultSubnetRes /** *

Creates a default subnet with a size /20 IPv4 CIDR block in the * specified Availability Zone in your default VPC. You can have only one default subnet - * per Availability Zone. For more information, see Create a default + * per Availability Zone. For more information, see Create a default * subnet in the Amazon VPC User Guide.

* @example * Use a bare-bones client and the command you need to make an API call. diff --git a/clients/client-ec2/src/commands/CreateFlowLogsCommand.ts b/clients/client-ec2/src/commands/CreateFlowLogsCommand.ts index dea86735d296..ca566056103a 100644 --- a/clients/client-ec2/src/commands/CreateFlowLogsCommand.ts +++ b/clients/client-ec2/src/commands/CreateFlowLogsCommand.ts @@ -32,7 +32,7 @@ export interface CreateFlowLogsCommandOutput extends CreateFlowLogsResult, __Met * subnet, or VPC.

*

Flow log data for a monitored network interface is recorded as flow log records, which are log events * consisting of fields that describe the traffic flow. For more information, see - * Flow log records + * Flow log records * in the Amazon VPC User Guide.

*

When publishing to CloudWatch Logs, flow log records are published to a log group, and each network * interface has a unique log stream in the log group. When publishing to Amazon S3, flow log records for all diff --git a/clients/client-ec2/src/commands/CreateNatGatewayCommand.ts b/clients/client-ec2/src/commands/CreateNatGatewayCommand.ts index 7df35501274c..5e396b9245d3 100644 --- a/clients/client-ec2/src/commands/CreateNatGatewayCommand.ts +++ b/clients/client-ec2/src/commands/CreateNatGatewayCommand.ts @@ -39,7 +39,13 @@ export interface CreateNatGatewayCommandOutput extends CreateNatGatewayResult, _ * private IPv4 addresses, and communicating between overlapping networks.

*

For more information, see NAT gateways in the Amazon VPC User Guide.

* - *

When you create a public NAT gateway and assign it an EIP or secondary EIPs, the network border group of the EIPs must match the network border group of the Availability Zone (AZ) that the public NAT gateway is in. If it's not the same, the NAT gateway will fail to launch. You can see the network border group for the subnet's AZ by viewing the details of the subnet. Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. For more information about network border groups and EIPs, see Allocate an Elastic IP address in the Amazon VPC User Guide. + *

When you create a public NAT gateway and assign it an EIP or secondary EIPs, + * the network border group of the EIPs must match the network border group of the Availability Zone (AZ) + * that the public NAT gateway is in. If it's not the same, the NAT gateway will fail to launch. + * You can see the network border group for the subnet's AZ by viewing the details of the subnet. + * Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. + * For more information about network border groups and EIPs, see Allocate an Elastic IP address + * in the Amazon VPC User Guide. *

* * @example diff --git a/clients/client-ec2/src/commands/CreateNetworkInterfaceCommand.ts b/clients/client-ec2/src/commands/CreateNetworkInterfaceCommand.ts index d414ce5069d4..8d5d49968a98 100644 --- a/clients/client-ec2/src/commands/CreateNetworkInterfaceCommand.ts +++ b/clients/client-ec2/src/commands/CreateNetworkInterfaceCommand.ts @@ -52,7 +52,7 @@ export interface CreateNetworkInterfaceCommandOutput extends CreateNetworkInterf * }, * ], * Ipv6PrefixCount: Number("int"), - * InterfaceType: "efa" || "branch" || "trunk", + * InterfaceType: "efa" || "efa-only" || "branch" || "trunk", * TagSpecifications: [ // TagSpecificationList * { // TagSpecification * ResourceType: "capacity-reservation" || "client-vpn-endpoint" || "customer-gateway" || "carrier-gateway" || "coip-pool" || "dedicated-host" || "dhcp-options" || "egress-only-internet-gateway" || "elastic-ip" || "elastic-gpu" || "export-image-task" || "export-instance-task" || "fleet" || "fpga-image" || "host-reservation" || "image" || "import-image-task" || "import-snapshot-task" || "instance" || "instance-event-window" || "internet-gateway" || "ipam" || "ipam-pool" || "ipam-scope" || "ipv4pool-ec2" || "ipv6pool-ec2" || "key-pair" || "launch-template" || "local-gateway" || "local-gateway-route-table" || "local-gateway-virtual-interface" || "local-gateway-virtual-interface-group" || "local-gateway-route-table-vpc-association" || "local-gateway-route-table-virtual-interface-group-association" || "natgateway" || "network-acl" || "network-interface" || "network-insights-analysis" || "network-insights-path" || "network-insights-access-scope" || "network-insights-access-scope-analysis" || "placement-group" || "prefix-list" || "replace-root-volume-task" || "reserved-instances" || "route-table" || "security-group" || "security-group-rule" || "snapshot" || "spot-fleet-request" || "spot-instances-request" || "subnet" || "subnet-cidr-reservation" || "traffic-mirror-filter" || "traffic-mirror-session" || "traffic-mirror-target" || "transit-gateway" || "transit-gateway-attachment" || "transit-gateway-connect-peer" || "transit-gateway-multicast-domain" || "transit-gateway-policy-table" || "transit-gateway-route-table" || "transit-gateway-route-table-announcement" || "volume" || "vpc" || "vpc-endpoint" || "vpc-endpoint-connection" || "vpc-endpoint-service" || "vpc-endpoint-service-permission" || "vpc-peering-connection" || "vpn-connection" || "vpn-gateway" || "vpc-flow-log" || "capacity-reservation-fleet" || "traffic-mirror-filter-rule" || "vpc-endpoint-connection-device-type" || "verified-access-instance" || "verified-access-group" || "verified-access-endpoint" || "verified-access-policy" || "verified-access-trust-provider" || "vpn-connection-device-type" || "vpc-block-public-access-exclusion" || "ipam-resource-discovery" || "ipam-resource-discovery-association" || "instance-connect-endpoint" || "ipam-external-resource-verification-token", @@ -135,7 +135,7 @@ export interface CreateNetworkInterfaceCommandOutput extends CreateNetworkInterf * // GroupName: "STRING_VALUE", * // }, * // ], - * // InterfaceType: "interface" || "natGateway" || "efa" || "trunk" || "load_balancer" || "network_load_balancer" || "vpc_endpoint" || "branch" || "transit_gateway" || "lambda" || "quicksight" || "global_accelerator_managed" || "api_gateway_managed" || "gateway_load_balancer" || "gateway_load_balancer_endpoint" || "iot_rules_managed" || "aws_codestar_connections_managed", + * // InterfaceType: "interface" || "natGateway" || "efa" || "efa-only" || "trunk" || "load_balancer" || "network_load_balancer" || "vpc_endpoint" || "branch" || "transit_gateway" || "lambda" || "quicksight" || "global_accelerator_managed" || "api_gateway_managed" || "gateway_load_balancer" || "gateway_load_balancer_endpoint" || "iot_rules_managed" || "aws_codestar_connections_managed", * // Ipv6Addresses: [ // NetworkInterfaceIpv6AddressesList * // { // NetworkInterfaceIpv6Address * // Ipv6Address: "STRING_VALUE", diff --git a/clients/client-ec2/src/commands/CreateSubnetCidrReservationCommand.ts b/clients/client-ec2/src/commands/CreateSubnetCidrReservationCommand.ts index ecf5ab78750e..6ebc490e5643 100644 --- a/clients/client-ec2/src/commands/CreateSubnetCidrReservationCommand.ts +++ b/clients/client-ec2/src/commands/CreateSubnetCidrReservationCommand.ts @@ -29,8 +29,8 @@ export interface CreateSubnetCidrReservationCommandOutput extends CreateSubnetCi /** *

Creates a subnet CIDR reservation. For more information, see Subnet CIDR reservations - * in the Amazon VPC User Guide and Assign prefixes - * to network interfaces in the Amazon EC2 User Guide.

+ * in the Amazon VPC User Guide and Manage prefixes + * for your network interfaces in the Amazon EC2 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/CreateVpcCommand.ts b/clients/client-ec2/src/commands/CreateVpcCommand.ts index c204621d0afe..3d12021e5855 100644 --- a/clients/client-ec2/src/commands/CreateVpcCommand.ts +++ b/clients/client-ec2/src/commands/CreateVpcCommand.ts @@ -33,7 +33,7 @@ export interface CreateVpcCommandOutput extends CreateVpcResult, __MetadataBeare *

You can optionally request an IPv6 CIDR block for the VPC. You can request an * Amazon-provided IPv6 CIDR block from Amazon's pool of IPv6 addresses or an IPv6 CIDR * block from an IPv6 address pool that you provisioned through bring your own IP addresses - * (BYOIP).

+ * (BYOIP).

*

By default, each instance that you launch in the VPC has the default DHCP options, which * include only a default DNS server that we provide (AmazonProvidedDNS). For more * information, see DHCP option sets in the Amazon VPC User Guide.

diff --git a/clients/client-ec2/src/commands/DeleteVpcCommand.ts b/clients/client-ec2/src/commands/DeleteVpcCommand.ts index e0fd2dae6d78..2c244a307113 100644 --- a/clients/client-ec2/src/commands/DeleteVpcCommand.ts +++ b/clients/client-ec2/src/commands/DeleteVpcCommand.ts @@ -28,7 +28,13 @@ export interface DeleteVpcCommandInput extends DeleteVpcRequest {} export interface DeleteVpcCommandOutput extends __MetadataBearer {} /** - *

Deletes the specified VPC. You must detach or delete all gateways and resources that are associated with the VPC before you can delete it. For example, you must terminate all instances running in the VPC, delete all security groups associated with the VPC (except the default one), delete all route tables associated with the VPC (except the default one), and so on. When you delete the VPC, it deletes the VPC's default security group, network ACL, and route table.

+ *

Deletes the specified VPC. You must detach or delete all gateways and resources that are associated + * with the VPC before you can delete it. For example, you must terminate all instances running in the VPC, + * delete all security groups associated with the VPC (except the default one), delete all route tables + * associated with the VPC (except the default one), and so on. When you delete the VPC, it deletes the + * default security group, network ACL, and route table for the VPC.

+ *

If you created a flow log for the VPC that you are deleting, note that flow logs for deleted + * VPCs are eventually automatically removed.

* @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/DescribeNetworkInterfacesCommand.ts b/clients/client-ec2/src/commands/DescribeNetworkInterfacesCommand.ts index cc8b8708339b..98aa4ebb2c2f 100644 --- a/clients/client-ec2/src/commands/DescribeNetworkInterfacesCommand.ts +++ b/clients/client-ec2/src/commands/DescribeNetworkInterfacesCommand.ts @@ -102,7 +102,7 @@ export interface DescribeNetworkInterfacesCommandOutput extends DescribeNetworkI * // GroupName: "STRING_VALUE", * // }, * // ], - * // InterfaceType: "interface" || "natGateway" || "efa" || "trunk" || "load_balancer" || "network_load_balancer" || "vpc_endpoint" || "branch" || "transit_gateway" || "lambda" || "quicksight" || "global_accelerator_managed" || "api_gateway_managed" || "gateway_load_balancer" || "gateway_load_balancer_endpoint" || "iot_rules_managed" || "aws_codestar_connections_managed", + * // InterfaceType: "interface" || "natGateway" || "efa" || "efa-only" || "trunk" || "load_balancer" || "network_load_balancer" || "vpc_endpoint" || "branch" || "transit_gateway" || "lambda" || "quicksight" || "global_accelerator_managed" || "api_gateway_managed" || "gateway_load_balancer" || "gateway_load_balancer_endpoint" || "iot_rules_managed" || "aws_codestar_connections_managed", * // Ipv6Addresses: [ // NetworkInterfaceIpv6AddressesList * // { // NetworkInterfaceIpv6Address * // Ipv6Address: "STRING_VALUE", diff --git a/clients/client-ec2/src/commands/DisableImageCommand.ts b/clients/client-ec2/src/commands/DisableImageCommand.ts index 2464b2c7ee5c..36a910c4b041 100644 --- a/clients/client-ec2/src/commands/DisableImageCommand.ts +++ b/clients/client-ec2/src/commands/DisableImageCommand.ts @@ -36,7 +36,7 @@ export interface DisableImageCommandOutput extends DisableImageResult, __Metadat *

A disabled AMI does not appear in DescribeImages API calls by * default.

*

Only the AMI owner can disable an AMI.

- *

You can re-enable a disabled AMI using EnableImage.

+ *

You can re-enable a disabled AMI using EnableImage.

*

For more information, see Disable an AMI in the * Amazon EC2 User Guide.

* @example diff --git a/clients/client-ec2/src/commands/DisassociateNatGatewayAddressCommand.ts b/clients/client-ec2/src/commands/DisassociateNatGatewayAddressCommand.ts index 61cda1ff992d..b8295d36a71c 100644 --- a/clients/client-ec2/src/commands/DisassociateNatGatewayAddressCommand.ts +++ b/clients/client-ec2/src/commands/DisassociateNatGatewayAddressCommand.ts @@ -31,7 +31,7 @@ export interface DisassociateNatGatewayAddressCommandOutput /** *

Disassociates secondary Elastic IP addresses (EIPs) from a public NAT gateway. - * You cannot disassociate your primary EIP. For more information, see Edit secondary IP address associations in the Amazon VPC User Guide.

+ * You cannot disassociate your primary EIP. For more information, see Edit secondary IP address associations in the Amazon VPC User Guide.

*

While disassociating is in progress, you cannot associate/disassociate additional EIPs while the connections are being drained. You are, however, allowed to delete the NAT gateway.

*

An EIP is released only at the end of MaxDrainDurationSeconds. It stays * associated and supports the existing connections but does not support any new connections diff --git a/clients/client-ec2/src/commands/GetInstanceTypesFromInstanceRequirementsCommand.ts b/clients/client-ec2/src/commands/GetInstanceTypesFromInstanceRequirementsCommand.ts index 136ee821e260..6e2638b04744 100644 --- a/clients/client-ec2/src/commands/GetInstanceTypesFromInstanceRequirementsCommand.ts +++ b/clients/client-ec2/src/commands/GetInstanceTypesFromInstanceRequirementsCommand.ts @@ -43,9 +43,9 @@ export interface GetInstanceTypesFromInstanceRequirementsCommandOutput *

When you specify multiple parameters, you get instance types that satisfy all of the * specified parameters. If you specify multiple values for a parameter, you get instance * types that satisfy any of the specified values.

- *

For more information, see Preview instance types with specified attributes, Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot - * placement score in the Amazon EC2 User Guide, and Creating an - * Auto Scaling group using attribute-based instance type selection in the + *

For more information, see Preview instance types with specified attributes, Specify attributes for instance type selection for EC2 Fleet or Spot Fleet, and Spot + * placement score in the Amazon EC2 User Guide, and Creating + * mixed instance groups using attribute-based instance type selection in the * Amazon EC2 Auto Scaling User Guide.

* @example * Use a bare-bones client and the command you need to make an API call. diff --git a/clients/client-ec2/src/commands/UnassignPrivateNatGatewayAddressCommand.ts b/clients/client-ec2/src/commands/UnassignPrivateNatGatewayAddressCommand.ts index f04c070ad34e..aaacca4c2565 100644 --- a/clients/client-ec2/src/commands/UnassignPrivateNatGatewayAddressCommand.ts +++ b/clients/client-ec2/src/commands/UnassignPrivateNatGatewayAddressCommand.ts @@ -33,7 +33,9 @@ export interface UnassignPrivateNatGatewayAddressCommandOutput __MetadataBearer {} /** - *

Unassigns secondary private IPv4 addresses from a private NAT gateway. You cannot unassign your primary private IP. For more information, see Edit secondary IP address associations in the Amazon VPC User Guide.

+ *

Unassigns secondary private IPv4 addresses from a private NAT gateway. You cannot unassign your primary private IP. For more information, + * see Edit secondary IP address associations + * in the Amazon VPC User Guide.

*

While unassigning is in progress, you cannot assign/unassign additional IP addresses while the connections are being drained. You are, however, allowed to delete the NAT gateway.

*

A private IP address will only be released at the end of MaxDrainDurationSeconds. The * private IP addresses stay associated and support the existing connections, but do not diff --git a/clients/client-ec2/src/models/models_0.ts b/clients/client-ec2/src/models/models_0.ts index 4940f49d3154..785c92020c92 100644 --- a/clients/client-ec2/src/models/models_0.ts +++ b/clients/client-ec2/src/models/models_0.ts @@ -4172,7 +4172,7 @@ export interface AssociateCapacityReservationBillingOwnerRequest { CapacityReservationId: string | undefined; /** - *

The ID of the consumer account to which assign billing.

+ *

The ID of the consumer account to which to assign billing.

* @public */ UnusedReservationBillingOwnerId: string | undefined; diff --git a/clients/client-ec2/src/models/models_1.ts b/clients/client-ec2/src/models/models_1.ts index 0f770905330c..cf8778f0b175 100644 --- a/clients/client-ec2/src/models/models_1.ts +++ b/clients/client-ec2/src/models/models_1.ts @@ -3049,8 +3049,8 @@ export interface VCpuCountRangeRequest { * AWS::EC2::Instance Amazon Web Services CloudFormation resource, you can't specify * InstanceRequirements.

* - *

For more information, see Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot - * placement score in the Amazon EC2 User Guide.

+ *

For more information, see Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot + * placement score in the Amazon EC2 User Guide.

* @public */ export interface InstanceRequirementsRequest { @@ -4502,8 +4502,8 @@ export interface VCpuCountRange { * wizard or with the RunInstances API, you * can't specify InstanceRequirements.

* - *

For more information, see Create a mixed instances group using attribute-based instance type selection in - * the Amazon EC2 Auto Scaling User Guide, and also Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot + *

For more information, see Create mixed instances group using attribute-based instance type selection in + * the Amazon EC2 Auto Scaling User Guide, and also Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot * placement score in the Amazon EC2 User Guide.

* @public */ @@ -5397,8 +5397,8 @@ export interface CreateFlowLogsRequest { *

The fields to include in the flow log record. List the fields in the order in which * they should appear. If you omit this parameter, the flow log is created using the * default format. If you specify this parameter, you must include at least one - * field. For more information about the available fields, see Flow log - * records in the Amazon VPC User Guide or Transit Gateway Flow Log + * field. For more information about the available fields, see Flow log records + * in the Amazon VPC User Guide or Transit Gateway Flow Log * records in the Amazon Web Services Transit Gateway Guide.

*

Specify the fields using the $\{field-id\} format, separated by spaces.

* @public @@ -5645,8 +5645,8 @@ export interface EbsBlockDevice { VolumeType?: VolumeType; /** - *

Identifier (key ID, key alias, ID ARN, or alias ARN) for a customer managed CMK under - * which the EBS volume is encrypted.

+ *

Identifier (key ID, key alias, key ARN, or alias ARN) of the customer managed KMS key + * to use for EBS encryption.

*

This parameter is only supported on BlockDeviceMapping objects called by * RunInstances, RequestSpotFleet, * and RequestSpotInstances.

@@ -9184,7 +9184,7 @@ export interface RequestLaunchTemplateData { * wizard, or with the RunInstances API or * AWS::EC2::Instance Amazon Web Services CloudFormation resource, you can't specify InstanceRequirements.

* - *

For more information, see Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot + *

For more information, see Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot * placement score in the Amazon EC2 User Guide.

* @public */ @@ -11362,7 +11362,7 @@ export interface CreateNatGatewayRequest { PrivateIpAddress?: string; /** - *

Secondary EIP allocation IDs. For more information, see Create a NAT gateway + *

Secondary EIP allocation IDs. For more information, see Create a NAT gateway * in the Amazon VPC User Guide.

* @public */ @@ -11370,14 +11370,14 @@ export interface CreateNatGatewayRequest { /** *

Secondary private IPv4 addresses. For more information about secondary addresses, see - * Create a NAT gateway in the Amazon VPC User Guide.

+ * Create a NAT gateway in the Amazon VPC User Guide.

* @public */ SecondaryPrivateIpAddresses?: string[]; /** *

[Private NAT gateway only] The number of secondary private IPv4 addresses you want to assign to the NAT gateway. - * For more information about secondary addresses, see Create a NAT gateway + * For more information about secondary addresses, see Create a NAT gateway * in the Amazon VPC User Guide.

* @public */ diff --git a/clients/client-ec2/src/models/models_2.ts b/clients/client-ec2/src/models/models_2.ts index 08ad528b7280..57996f1b9077 100644 --- a/clients/client-ec2/src/models/models_2.ts +++ b/clients/client-ec2/src/models/models_2.ts @@ -215,6 +215,7 @@ export interface CreateNetworkInsightsPathResult { export const NetworkInterfaceCreationType = { branch: "branch", efa: "efa", + efa_only: "efa-only", trunk: "trunk", } as const; @@ -590,6 +591,7 @@ export const NetworkInterfaceType = { aws_codestar_connections_managed: "aws_codestar_connections_managed", branch: "branch", efa: "efa", + efa_only: "efa-only", gateway_load_balancer: "gateway_load_balancer", gateway_load_balancer_endpoint: "gateway_load_balancer_endpoint", global_accelerator_managed: "global_accelerator_managed", diff --git a/clients/client-ec2/src/models/models_6.ts b/clients/client-ec2/src/models/models_6.ts index 4b9b71d02c06..bdd634bbb22f 100644 --- a/clients/client-ec2/src/models/models_6.ts +++ b/clients/client-ec2/src/models/models_6.ts @@ -7928,9 +7928,10 @@ export interface ModifySubnetAttributeRequest { /** *

Indicates whether DNS queries made to the Amazon-provided DNS Resolver in this subnet * should return synthetic IPv6 addresses for IPv4-only destinations.

- * - *

You must first configure a NAT gateway in a public subnet (separate from the subnet containing the IPv6-only workloads). For example, the subnet containing the NAT gateway should have a 0.0.0.0/0 route pointing to the internet gateway. For more information, see Configure DNS64 and NAT64 in the Amazon VPC User Guide.

- * + *

You must first configure a NAT gateway in a public subnet (separate from the subnet + * containing the IPv6-only workloads). For example, the subnet containing the NAT gateway + * should have a 0.0.0.0/0 route pointing to the internet gateway. For more + * information, see Configure DNS64 and NAT64 in the Amazon VPC User Guide.

* @public */ EnableDns64?: AttributeBooleanValue; diff --git a/codegen/sdk-codegen/aws-models/ec2.json b/codegen/sdk-codegen/aws-models/ec2.json index 39007e91f3d7..7043b88fa939 100644 --- a/codegen/sdk-codegen/aws-models/ec2.json +++ b/codegen/sdk-codegen/aws-models/ec2.json @@ -6196,7 +6196,7 @@ "target": "com.amazonaws.ec2#AssignPrivateNatGatewayAddressResult" }, "traits": { - "smithy.api#documentation": "

Assigns private IPv4 addresses to a private NAT gateway. For more information, see \n Work with NAT gateways in the Amazon VPC User Guide.

" + "smithy.api#documentation": "

Assigns private IPv4 addresses to a private NAT gateway. For more information, see \n Work with NAT gateways in the Amazon VPC User Guide.

" } }, "com.amazonaws.ec2#AssignPrivateNatGatewayAddressRequest": { @@ -6426,7 +6426,7 @@ "target": "com.amazonaws.ec2#AccountID", "traits": { "smithy.api#clientOptional": {}, - "smithy.api#documentation": "

The ID of the consumer account to which assign billing.

", + "smithy.api#documentation": "

The ID of the consumer account to which to assign billing.

", "smithy.api#required": {} } } @@ -6932,7 +6932,7 @@ "target": "com.amazonaws.ec2#AssociateNatGatewayAddressResult" }, "traits": { - "smithy.api#documentation": "

Associates Elastic IP addresses (EIPs) and private IPv4 addresses with a public NAT gateway. For more information, \n see Work with NAT gateways in the Amazon VPC User Guide.

\n

By default, you can associate up to 2 Elastic IP addresses per public NAT gateway. You can increase the limit by requesting a quota adjustment. \n For more information, see Elastic IP address quotas in the Amazon VPC User Guide.

\n \n

When you associate an EIP or secondary EIPs with a public NAT gateway, the network border group of the EIPs must match the network border group of the Availability Zone (AZ) that the public NAT gateway is in. If it's not the same, the EIP will fail to associate. You can see the network border group for the subnet's AZ by viewing the details of the subnet. Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. For more information about network border groups and EIPs, see Allocate an Elastic IP address in the Amazon VPC User Guide. \n

\n " + "smithy.api#documentation": "

Associates Elastic IP addresses (EIPs) and private IPv4 addresses with a public NAT gateway. For more information, \n see Work with NAT gateways in the Amazon VPC User Guide.

\n

By default, you can associate up to 2 Elastic IP addresses per public NAT gateway. You can increase the limit by requesting a quota adjustment. \n For more information, see Elastic IP address quotas in the Amazon VPC User Guide.

\n \n

When you associate an EIP or secondary EIPs with a public NAT gateway, the network border group of the EIPs \n must match the network border group of the Availability Zone (AZ) that the public NAT gateway is in. If it's not the same, \n the EIP will fail to associate. You can see the network border group for the subnet's AZ by viewing the details of the subnet.\n Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. For more information \n about network border groups and EIPs, see Allocate an Elastic IP address in the Amazon VPC User Guide. \n

\n " } }, "com.amazonaws.ec2#AssociateNatGatewayAddressRequest": { @@ -15166,7 +15166,7 @@ "target": "com.amazonaws.ec2#CreateDefaultSubnetResult" }, "traits": { - "smithy.api#documentation": "

Creates a default subnet with a size /20 IPv4 CIDR block in the\n specified Availability Zone in your default VPC. You can have only one default subnet\n per Availability Zone. For more information, see Create a default\n subnet in the Amazon VPC User Guide.

" + "smithy.api#documentation": "

Creates a default subnet with a size /20 IPv4 CIDR block in the\n specified Availability Zone in your default VPC. You can have only one default subnet\n per Availability Zone. For more information, see Create a default\n subnet in the Amazon VPC User Guide.

" } }, "com.amazonaws.ec2#CreateDefaultSubnetRequest": { @@ -15675,7 +15675,7 @@ "target": "com.amazonaws.ec2#CreateFlowLogsResult" }, "traits": { - "smithy.api#documentation": "

Creates one or more flow logs to capture information about IP traffic for a specific network interface,\n subnet, or VPC.

\n

Flow log data for a monitored network interface is recorded as flow log records, which are log events \n consisting of fields that describe the traffic flow. For more information, see \n Flow log records \n in the Amazon VPC User Guide.

\n

When publishing to CloudWatch Logs, flow log records are published to a log group, and each network \n interface has a unique log stream in the log group. When publishing to Amazon S3, flow log records for all \n of the monitored network interfaces are published to a single log file object that is stored in the specified \n bucket.

\n

For more information, see VPC Flow Logs \n in the Amazon VPC User Guide.

" + "smithy.api#documentation": "

Creates one or more flow logs to capture information about IP traffic for a specific network interface,\n subnet, or VPC.

\n

Flow log data for a monitored network interface is recorded as flow log records, which are log events \n consisting of fields that describe the traffic flow. For more information, see \n Flow log records \n in the Amazon VPC User Guide.

\n

When publishing to CloudWatch Logs, flow log records are published to a log group, and each network \n interface has a unique log stream in the log group. When publishing to Amazon S3, flow log records for all \n of the monitored network interfaces are published to a single log file object that is stored in the specified \n bucket.

\n

For more information, see VPC Flow Logs \n in the Amazon VPC User Guide.

" } }, "com.amazonaws.ec2#CreateFlowLogsRequest": { @@ -15749,7 +15749,7 @@ "LogFormat": { "target": "com.amazonaws.ec2#String", "traits": { - "smithy.api#documentation": "

The fields to include in the flow log record. List the fields in the order in which\n they should appear. If you omit this parameter, the flow log is created using the\n default format. If you specify this parameter, you must include at least one\n field. For more information about the available fields, see Flow log\n records in the Amazon VPC User Guide or Transit Gateway Flow Log\n records in the Amazon Web Services Transit Gateway Guide.

\n

Specify the fields using the ${field-id} format, separated by spaces.

" + "smithy.api#documentation": "

The fields to include in the flow log record. List the fields in the order in which\n they should appear. If you omit this parameter, the flow log is created using the\n default format. If you specify this parameter, you must include at least one\n field. For more information about the available fields, see Flow log records \n in the Amazon VPC User Guide or Transit Gateway Flow Log\n records in the Amazon Web Services Transit Gateway Guide.

\n

Specify the fields using the ${field-id} format, separated by spaces.

" } }, "TagSpecifications": { @@ -17409,7 +17409,7 @@ "target": "com.amazonaws.ec2#CreateNatGatewayResult" }, "traits": { - "smithy.api#documentation": "

Creates a NAT gateway in the specified subnet. This action creates a network interface\n in the specified subnet with a private IP address from the IP address range of the\n subnet. You can create either a public NAT gateway or a private NAT gateway.

\n

With a public NAT gateway, internet-bound traffic from a private subnet can be routed\n to the NAT gateway, so that instances in a private subnet can connect to the internet.

\n

With a private NAT gateway, private communication is routed across VPCs and on-premises\n networks through a transit gateway or virtual private gateway. Common use cases include\n running large workloads behind a small pool of allowlisted IPv4 addresses, preserving\n private IPv4 addresses, and communicating between overlapping networks.

\n

For more information, see NAT gateways in the Amazon VPC User Guide.

\n \n

When you create a public NAT gateway and assign it an EIP or secondary EIPs, the network border group of the EIPs must match the network border group of the Availability Zone (AZ) that the public NAT gateway is in. If it's not the same, the NAT gateway will fail to launch. You can see the network border group for the subnet's AZ by viewing the details of the subnet. Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. For more information about network border groups and EIPs, see Allocate an Elastic IP address in the Amazon VPC User Guide. \n

\n ", + "smithy.api#documentation": "

Creates a NAT gateway in the specified subnet. This action creates a network interface\n in the specified subnet with a private IP address from the IP address range of the\n subnet. You can create either a public NAT gateway or a private NAT gateway.

\n

With a public NAT gateway, internet-bound traffic from a private subnet can be routed\n to the NAT gateway, so that instances in a private subnet can connect to the internet.

\n

With a private NAT gateway, private communication is routed across VPCs and on-premises\n networks through a transit gateway or virtual private gateway. Common use cases include\n running large workloads behind a small pool of allowlisted IPv4 addresses, preserving\n private IPv4 addresses, and communicating between overlapping networks.

\n

For more information, see NAT gateways in the Amazon VPC User Guide.

\n \n

When you create a public NAT gateway and assign it an EIP or secondary EIPs, \n the network border group of the EIPs must match the network border group of the Availability Zone (AZ) \n that the public NAT gateway is in. If it's not the same, the NAT gateway will fail to launch. \n You can see the network border group for the subnet's AZ by viewing the details of the subnet. \n Similarly, you can view the network border group of an EIP by viewing the details of the EIP address. \n For more information about network border groups and EIPs, see Allocate an Elastic IP address \n in the Amazon VPC User Guide. \n

\n ", "smithy.api#examples": [ { "title": "To create a NAT gateway", @@ -17488,21 +17488,21 @@ "SecondaryAllocationIds": { "target": "com.amazonaws.ec2#AllocationIdList", "traits": { - "smithy.api#documentation": "

Secondary EIP allocation IDs. For more information, see Create a NAT gateway \n in the Amazon VPC User Guide.

", + "smithy.api#documentation": "

Secondary EIP allocation IDs. For more information, see Create a NAT gateway \n in the Amazon VPC User Guide.

", "smithy.api#xmlName": "SecondaryAllocationId" } }, "SecondaryPrivateIpAddresses": { "target": "com.amazonaws.ec2#IpList", "traits": { - "smithy.api#documentation": "

Secondary private IPv4 addresses. For more information about secondary addresses, see \n Create a NAT gateway in the Amazon VPC User Guide.

", + "smithy.api#documentation": "

Secondary private IPv4 addresses. For more information about secondary addresses, see \n Create a NAT gateway in the Amazon VPC User Guide.

", "smithy.api#xmlName": "SecondaryPrivateIpAddress" } }, "SecondaryPrivateIpAddressCount": { "target": "com.amazonaws.ec2#PrivateIpAddressCount", "traits": { - "smithy.api#documentation": "

[Private NAT gateway only] The number of secondary private IPv4 addresses you want to assign to the NAT gateway. \n For more information about secondary addresses, see Create a NAT gateway \n in the Amazon VPC User Guide.

" + "smithy.api#documentation": "

[Private NAT gateway only] The number of secondary private IPv4 addresses you want to assign to the NAT gateway. \n For more information about secondary addresses, see Create a NAT gateway \n in the Amazon VPC User Guide.

" } } }, @@ -19284,7 +19284,7 @@ "target": "com.amazonaws.ec2#CreateSubnetCidrReservationResult" }, "traits": { - "smithy.api#documentation": "

Creates a subnet CIDR reservation. For more information, see Subnet CIDR reservations \n in the Amazon VPC User Guide and Assign prefixes \n to network interfaces in the Amazon EC2 User Guide.

" + "smithy.api#documentation": "

Creates a subnet CIDR reservation. For more information, see Subnet CIDR reservations \n in the Amazon VPC User Guide and Manage prefixes \n for your network interfaces in the Amazon EC2 User Guide.

" } }, "com.amazonaws.ec2#CreateSubnetCidrReservationRequest": { @@ -21523,7 +21523,7 @@ "target": "com.amazonaws.ec2#CreateVpcResult" }, "traits": { - "smithy.api#documentation": "

Creates a VPC with the specified CIDR blocks. For more information, see IP addressing for your VPCs and subnets in the \n Amazon VPC User Guide.

\n

You can optionally request an IPv6 CIDR block for the VPC. You can request an\n Amazon-provided IPv6 CIDR block from Amazon's pool of IPv6 addresses or an IPv6 CIDR\n block from an IPv6 address pool that you provisioned through bring your own IP addresses\n (BYOIP).

\n

By default, each instance that you launch in the VPC has the default DHCP options, which\n\t\t\tinclude only a default DNS server that we provide (AmazonProvidedDNS). For more\n\t\t\tinformation, see DHCP option sets in the Amazon VPC User Guide.

\n

You can specify the instance tenancy value for the VPC when you create it. You can't change\n this value for the VPC after you create it. For more information, see Dedicated Instances in the\n Amazon EC2 User Guide.

", + "smithy.api#documentation": "

Creates a VPC with the specified CIDR blocks. For more information, see IP addressing for your VPCs and subnets in the \n Amazon VPC User Guide.

\n

You can optionally request an IPv6 CIDR block for the VPC. You can request an\n Amazon-provided IPv6 CIDR block from Amazon's pool of IPv6 addresses or an IPv6 CIDR\n block from an IPv6 address pool that you provisioned through bring your own IP addresses\n (BYOIP).

\n

By default, each instance that you launch in the VPC has the default DHCP options, which\n\t\t\tinclude only a default DNS server that we provide (AmazonProvidedDNS). For more\n\t\t\tinformation, see DHCP option sets in the Amazon VPC User Guide.

\n

You can specify the instance tenancy value for the VPC when you create it. You can't change\n this value for the VPC after you create it. For more information, see Dedicated Instances in the\n Amazon EC2 User Guide.

", "smithy.api#examples": [ { "title": "To create a VPC", @@ -26554,7 +26554,7 @@ "target": "smithy.api#Unit" }, "traits": { - "smithy.api#documentation": "

Deletes the specified VPC. You must detach or delete all gateways and resources that are associated with the VPC before you can delete it. For example, you must terminate all instances running in the VPC, delete all security groups associated with the VPC (except the default one), delete all route tables associated with the VPC (except the default one), and so on. When you delete the VPC, it deletes the VPC's default security group, network ACL, and route table.

", + "smithy.api#documentation": "

Deletes the specified VPC. You must detach or delete all gateways and resources that are associated \n\t\t with the VPC before you can delete it. For example, you must terminate all instances running in the VPC, \n\t\t delete all security groups associated with the VPC (except the default one), delete all route tables \n\t\t associated with the VPC (except the default one), and so on. When you delete the VPC, it deletes the \n\t\t default security group, network ACL, and route table for the VPC.

\n

If you created a flow log for the VPC that you are deleting, note that flow logs for deleted \n VPCs are eventually automatically removed.

", "smithy.api#examples": [ { "title": "To delete a VPC", @@ -44034,7 +44034,7 @@ "target": "com.amazonaws.ec2#DisableImageResult" }, "traits": { - "smithy.api#documentation": "

Sets the AMI state to disabled and removes all launch permissions from the\n AMI. A disabled AMI can't be used for instance launches.

\n

A disabled AMI can't be shared. If an AMI was public or previously shared, it is made\n private. If an AMI was shared with an Amazon Web Services account, organization, or Organizational Unit,\n they lose access to the disabled AMI.

\n

A disabled AMI does not appear in DescribeImages API calls by\n default.

\n

Only the AMI owner can disable an AMI.

\n

You can re-enable a disabled AMI using EnableImage.

\n

For more information, see Disable an AMI in the\n Amazon EC2 User Guide.

" + "smithy.api#documentation": "

Sets the AMI state to disabled and removes all launch permissions from the\n AMI. A disabled AMI can't be used for instance launches.

\n

A disabled AMI can't be shared. If an AMI was public or previously shared, it is made\n private. If an AMI was shared with an Amazon Web Services account, organization, or Organizational Unit,\n they lose access to the disabled AMI.

\n

A disabled AMI does not appear in DescribeImages API calls by\n default.

\n

Only the AMI owner can disable an AMI.

\n

You can re-enable a disabled AMI using EnableImage.

\n

For more information, see Disable an AMI in the\n Amazon EC2 User Guide.

" } }, "com.amazonaws.ec2#DisableImageBlockPublicAccess": { @@ -45033,7 +45033,7 @@ "target": "com.amazonaws.ec2#DisassociateNatGatewayAddressResult" }, "traits": { - "smithy.api#documentation": "

Disassociates secondary Elastic IP addresses (EIPs) from a public NAT gateway. \n You cannot disassociate your primary EIP. For more information, see Edit secondary IP address associations in the Amazon VPC User Guide.

\n

While disassociating is in progress, you cannot associate/disassociate additional EIPs while the connections are being drained. You are, however, allowed to delete the NAT gateway.

\n

An EIP is released only at the end of MaxDrainDurationSeconds. It stays\n associated and supports the existing connections but does not support any new connections\n (new connections are distributed across the remaining associated EIPs). As the existing\n connections drain out, the EIPs (and the corresponding private IP addresses mapped to them) \n are released.

" + "smithy.api#documentation": "

Disassociates secondary Elastic IP addresses (EIPs) from a public NAT gateway. \n You cannot disassociate your primary EIP. For more information, see Edit secondary IP address associations in the Amazon VPC User Guide.

\n

While disassociating is in progress, you cannot associate/disassociate additional EIPs while the connections are being drained. You are, however, allowed to delete the NAT gateway.

\n

An EIP is released only at the end of MaxDrainDurationSeconds. It stays\n associated and supports the existing connections but does not support any new connections\n (new connections are distributed across the remaining associated EIPs). As the existing\n connections drain out, the EIPs (and the corresponding private IP addresses mapped to them) \n are released.

" } }, "com.amazonaws.ec2#DisassociateNatGatewayAddressRequest": { @@ -45996,7 +45996,7 @@ "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.

\n

This parameter is only supported on BlockDeviceMapping objects called by\n RunInstances, RequestSpotFleet,\n and RequestSpotInstances.

", + "smithy.api#documentation": "

Identifier (key ID, key alias, key ARN, or alias ARN) of the customer managed KMS key \n to use for EBS encryption.

\n

This parameter is only supported on BlockDeviceMapping objects called by\n RunInstances, RequestSpotFleet,\n and RequestSpotInstances.

", "smithy.api#xmlName": "kmsKeyId" } }, @@ -52816,7 +52816,7 @@ "target": "com.amazonaws.ec2#GetInstanceTypesFromInstanceRequirementsResult" }, "traits": { - "smithy.api#documentation": "

Returns a list of instance types with the specified instance attributes. You can\n use the response to preview the instance types without launching instances. Note\n that the response does not consider capacity.

\n

When you specify multiple parameters, you get instance types that satisfy all of the\n specified parameters. If you specify multiple values for a parameter, you get instance\n types that satisfy any of the specified values.

\n

For more information, see Preview instance types with specified attributes, Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot\n placement score in the Amazon EC2 User Guide, and Creating an\n Auto Scaling group using attribute-based instance type selection in the\n Amazon EC2 Auto Scaling User Guide.

", + "smithy.api#documentation": "

Returns a list of instance types with the specified instance attributes. You can\n use the response to preview the instance types without launching instances. Note\n that the response does not consider capacity.

\n

When you specify multiple parameters, you get instance types that satisfy all of the\n specified parameters. If you specify multiple values for a parameter, you get instance\n types that satisfy any of the specified values.

\n

For more information, see Preview instance types with specified attributes, Specify attributes for instance type selection for EC2 Fleet or Spot Fleet, and Spot\n placement score in the Amazon EC2 User Guide, and Creating\n mixed instance groups using attribute-based instance type selection in the\n Amazon EC2 Auto Scaling User Guide.

", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -61409,7 +61409,7 @@ } }, "traits": { - "smithy.api#documentation": "

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will\n identify instance types with these attributes.

\n

You must specify VCpuCount and MemoryMiB. All other attributes\n are optional. Any unspecified optional attribute is set to its default.

\n

When you specify multiple attributes, you get instance types that satisfy all of the\n specified attributes. If you specify multiple values for an attribute, you get instance\n types that satisfy any of the specified values.

\n

To limit the list of instance types from which Amazon EC2 can identify matching instance types, \n you can use one of the following parameters, but not both in the same request:

\n \n \n

If you specify InstanceRequirements, you can't specify\n InstanceType.

\n

Attribute-based instance type selection is only supported when using Auto Scaling\n groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in\n the launch instance\n wizard or with the RunInstances API, you\n can't specify InstanceRequirements.

\n \n

For more information, see Create a mixed instances group using attribute-based instance type selection in\n the Amazon EC2 Auto Scaling User Guide, and also Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot\n placement score in the Amazon EC2 User Guide.

" + "smithy.api#documentation": "

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will\n identify instance types with these attributes.

\n

You must specify VCpuCount and MemoryMiB. All other attributes\n are optional. Any unspecified optional attribute is set to its default.

\n

When you specify multiple attributes, you get instance types that satisfy all of the\n specified attributes. If you specify multiple values for an attribute, you get instance\n types that satisfy any of the specified values.

\n

To limit the list of instance types from which Amazon EC2 can identify matching instance types, \n you can use one of the following parameters, but not both in the same request:

\n \n \n

If you specify InstanceRequirements, you can't specify\n InstanceType.

\n

Attribute-based instance type selection is only supported when using Auto Scaling\n groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in\n the launch instance\n wizard or with the RunInstances API, you\n can't specify InstanceRequirements.

\n \n

For more information, see Create mixed instances group using attribute-based instance type selection in\n the Amazon EC2 Auto Scaling User Guide, and also Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot\n placement score in the Amazon EC2 User Guide.

" } }, "com.amazonaws.ec2#InstanceRequirementsRequest": { @@ -61573,7 +61573,7 @@ } }, "traits": { - "smithy.api#documentation": "

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will\n identify instance types with these attributes.

\n

You must specify VCpuCount and MemoryMiB. All other attributes\n are optional. Any unspecified optional attribute is set to its default.

\n

When you specify multiple attributes, you get instance types that satisfy all of the\n specified attributes. If you specify multiple values for an attribute, you get instance\n types that satisfy any of the specified values.

\n

To limit the list of instance types from which Amazon EC2 can identify matching instance types, \n you can use one of the following parameters, but not both in the same request:

\n \n \n

If you specify InstanceRequirements, you can't specify\n InstanceType.

\n

Attribute-based instance type selection is only supported when using Auto Scaling\n groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in\n the launch instance\n wizard, or with the RunInstances API or\n AWS::EC2::Instance Amazon Web Services CloudFormation resource, you can't specify\n InstanceRequirements.

\n \n

For more information, see Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot\n placement score in the Amazon EC2 User Guide.

" + "smithy.api#documentation": "

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will\n identify instance types with these attributes.

\n

You must specify VCpuCount and MemoryMiB. All other attributes\n are optional. Any unspecified optional attribute is set to its default.

\n

When you specify multiple attributes, you get instance types that satisfy all of the\n specified attributes. If you specify multiple values for an attribute, you get instance\n types that satisfy any of the specified values.

\n

To limit the list of instance types from which Amazon EC2 can identify matching instance types, \n you can use one of the following parameters, but not both in the same request:

\n \n \n

If you specify InstanceRequirements, you can't specify\n InstanceType.

\n

Attribute-based instance type selection is only supported when using Auto Scaling\n groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in\n the launch instance\n wizard, or with the RunInstances API or\n AWS::EC2::Instance Amazon Web Services CloudFormation resource, you can't specify\n InstanceRequirements.

\n \n

For more information, see Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot\n placement score in the Amazon EC2 User Guide.

" } }, "com.amazonaws.ec2#InstanceRequirementsWithMetadataRequest": { @@ -78481,7 +78481,7 @@ "EnableDns64": { "target": "com.amazonaws.ec2#AttributeBooleanValue", "traits": { - "smithy.api#documentation": "

Indicates whether DNS queries made to the Amazon-provided DNS Resolver in this subnet \n should return synthetic IPv6 addresses for IPv4-only destinations.

\n \n

You must first configure a NAT gateway in a public subnet (separate from the subnet containing the IPv6-only workloads). For example, the subnet containing the NAT gateway should have a 0.0.0.0/0 route pointing to the internet gateway. For more information, see Configure DNS64 and NAT64 in the Amazon VPC User Guide.

\n " + "smithy.api#documentation": "

Indicates whether DNS queries made to the Amazon-provided DNS Resolver in this subnet \n should return synthetic IPv6 addresses for IPv4-only destinations.

\n

You must first configure a NAT gateway in a public subnet (separate from the subnet \n containing the IPv6-only workloads). For example, the subnet containing the NAT gateway \n should have a 0.0.0.0/0 route pointing to the internet gateway. For more \n information, see Configure DNS64 and NAT64 in the Amazon VPC User Guide.

" } }, "PrivateDnsHostnameTypeOnLaunch": { @@ -83041,6 +83041,12 @@ "smithy.api#enumValue": "efa" } }, + "efa_only": { + "target": "smithy.api#Unit", + "traits": { + "smithy.api#enumValue": "efa-only" + } + }, "branch": { "target": "smithy.api#Unit", "traits": { @@ -83350,6 +83356,12 @@ "smithy.api#enumValue": "efa" } }, + "efa_only": { + "target": "smithy.api#Unit", + "traits": { + "smithy.api#enumValue": "efa-only" + } + }, "trunk": { "target": "smithy.api#Unit", "traits": { @@ -89583,7 +89595,7 @@ "InstanceRequirements": { "target": "com.amazonaws.ec2#InstanceRequirementsRequest", "traits": { - "smithy.api#documentation": "

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will\n identify instance types with these attributes.

\n

You must specify VCpuCount and MemoryMiB. All other attributes\n are optional. Any unspecified optional attribute is set to its default.

\n

When you specify multiple attributes, you get instance types that satisfy all of the\n specified attributes. If you specify multiple values for an attribute, you get instance\n types that satisfy any of the specified values.

\n

To limit the list of instance types from which Amazon EC2 can identify matching instance types, \n you can use one of the following parameters, but not both in the same request:

\n \n \n

If you specify InstanceRequirements, you can't specify\n InstanceType.

\n

Attribute-based instance type selection is only supported when using Auto Scaling\n groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in\n the launch instance\n wizard, or with the RunInstances API or\n AWS::EC2::Instance Amazon Web Services CloudFormation resource, you can't specify InstanceRequirements.

\n \n

For more information, see Attribute-based instance type selection for EC2 Fleet, Attribute-based instance type selection for Spot Fleet, and Spot\n placement score in the Amazon EC2 User Guide.

" + "smithy.api#documentation": "

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will\n identify instance types with these attributes.

\n

You must specify VCpuCount and MemoryMiB. All other attributes\n are optional. Any unspecified optional attribute is set to its default.

\n

When you specify multiple attributes, you get instance types that satisfy all of the\n specified attributes. If you specify multiple values for an attribute, you get instance\n types that satisfy any of the specified values.

\n

To limit the list of instance types from which Amazon EC2 can identify matching instance types, \n you can use one of the following parameters, but not both in the same request:

\n \n \n

If you specify InstanceRequirements, you can't specify\n InstanceType.

\n

Attribute-based instance type selection is only supported when using Auto Scaling\n groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in\n the launch instance\n wizard, or with the RunInstances API or\n AWS::EC2::Instance Amazon Web Services CloudFormation resource, you can't specify InstanceRequirements.

\n \n

For more information, see Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot\n placement score in the Amazon EC2 User Guide.

" } }, "PrivateDnsNameOptions": { @@ -104530,7 +104542,7 @@ "target": "com.amazonaws.ec2#UnassignPrivateNatGatewayAddressResult" }, "traits": { - "smithy.api#documentation": "

Unassigns secondary private IPv4 addresses from a private NAT gateway. You cannot unassign your primary private IP. For more information, see Edit secondary IP address associations in the Amazon VPC User Guide.

\n

While unassigning is in progress, you cannot assign/unassign additional IP addresses while the connections are being drained. You are, however, allowed to delete the NAT gateway.

\n

A private IP address will only be released at the end of MaxDrainDurationSeconds. The\n private IP addresses stay associated and support the existing connections, but do not\n support any new connections (new connections are distributed across the remaining\n assigned private IP address). After the existing connections drain out, the private IP\n addresses are released.

\n

\n

" + "smithy.api#documentation": "

Unassigns secondary private IPv4 addresses from a private NAT gateway. You cannot unassign your primary private IP. For more information, \n see Edit secondary IP address associations \n in the Amazon VPC User Guide.

\n

While unassigning is in progress, you cannot assign/unassign additional IP addresses while the connections are being drained. You are, however, allowed to delete the NAT gateway.

\n

A private IP address will only be released at the end of MaxDrainDurationSeconds. The\n private IP addresses stay associated and support the existing connections, but do not\n support any new connections (new connections are distributed across the remaining\n assigned private IP address). After the existing connections drain out, the private IP\n addresses are released.

\n

\n

" } }, "com.amazonaws.ec2#UnassignPrivateNatGatewayAddressRequest": {