Assigns the specified IPv6 addresses to the specified network interface. You can\n specify specific IPv6 addresses, or you can specify the number of IPv6\n addresses to be automatically assigned from the subnet's IPv6 CIDR block range.\n You can assign as many IPv6 addresses to a network interface as you can assign private\n IPv4 addresses, and the limit varies by instance type.
\nYou must specify either the IPv6 addresses or the IPv6 address count in the request.
\nYou can optionally use Prefix Delegation on the network interface. You must specify\n either the IPV6 Prefix Delegation prefixes, or the IPv6 Prefix Delegation count. For\n information, see \n Assigning prefixes to network interfaces in the Amazon EC2 User Guide.
" + "smithy.api#documentation": "Assigns one or more IPv6 addresses to the specified network interface. You can\n specify one or more specific IPv6 addresses, or you can specify the number of IPv6\n addresses to be automatically assigned from within the subnet's IPv6 CIDR block range.\n You can assign as many IPv6 addresses to a network interface as you can assign private\n IPv4 addresses, and the limit varies per instance type.
\nYou must specify either the IPv6 addresses or the IPv6 address count in the request.
\nYou can optionally use Prefix Delegation on the network interface. You must specify\n either the IPV6 Prefix Delegation prefixes, or the IPv6 Prefix Delegation count. For\n information, see \n Assigning prefixes to network interfaces in the Amazon EC2 User Guide.
" } }, "com.amazonaws.ec2#AssignIpv6AddressesRequest": { @@ -6131,7 +6137,7 @@ "Ipv6Prefixes": { "target": "com.amazonaws.ec2#IpPrefixList", "traits": { - "smithy.api#documentation": "One or more IPv6 prefixes assigned to the network interface. You can't use this option if you use the Ipv6PrefixCount option.
One or more IPv6 prefixes assigned to the network interface. You cannot use this option if you use the Ipv6PrefixCount option.
Assigns the specified secondary private IP addresses to the specified network interface.
\nYou can specify specific secondary IP addresses, or you can specify the number \n of secondary IP addresses to be automatically assigned from the subnet's CIDR block range. \n The number of secondary IP addresses that you can assign to an instance varies by instance type.\n For more information about Elastic IP addresses, see Elastic IP Addresses in the Amazon EC2 User Guide.
\nWhen you move a secondary private IP address to another network interface, any Elastic IP address \n that is associated with the IP address is also moved.
\nRemapping an IP address is an asynchronous operation. When you move an IP address from one network\n interface to another, check network/interfaces/macs/mac/local-ipv4s in the instance\n metadata to confirm that the remapping is complete.
You must specify either the IP addresses or the IP address count in the request.
\nYou can optionally use Prefix Delegation on the network interface. You must specify\n either the IPv4 Prefix Delegation prefixes, or the IPv4 Prefix Delegation count. For\n information, see \n Assigning prefixes to network interfaces in the Amazon EC2 User Guide.
", + "smithy.api#documentation": "Assigns one or more secondary private IP addresses to the specified network interface.
\nYou can specify one or more specific secondary IP addresses, or you can specify the number \n of secondary IP addresses to be automatically assigned within the subnet's CIDR block range. \n The number of secondary IP addresses that you can assign to an instance varies by instance type.\n For more information about Elastic IP addresses, see Elastic IP Addresses in the Amazon EC2 User Guide.
\nWhen you move a secondary private IP address to another network interface, any Elastic IP address \n that is associated with the IP address is also moved.
\nRemapping an IP address is an asynchronous operation. When you move an IP address from one network\n interface to another, check network/interfaces/macs/mac/local-ipv4s in the instance\n metadata to confirm that the remapping is complete.
You must specify either the IP addresses or the IP address count in the request.
\nYou can optionally use Prefix Delegation on the network interface. You must specify\n either the IPv4 Prefix Delegation prefixes, or the IPv4 Prefix Delegation count. For\n information, see \n Assigning prefixes to network interfaces in the Amazon EC2 User Guide.
", "smithy.api#examples": [ { "title": "To assign a specific secondary private IP address to an interface", @@ -6236,14 +6242,14 @@ "Ipv4Prefixes": { "target": "com.amazonaws.ec2#IpPrefixList", "traits": { - "smithy.api#documentation": "One or more IPv4 prefixes assigned to the network interface. You can't use this option if you use the Ipv4PrefixCount option.
One or more IPv4 prefixes assigned to the network interface. You cannot use this option if you use the Ipv4PrefixCount option.
The number of IPv4 prefixes that Amazon Web Services automatically assigns to the network interface. You can't 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 cannot use this option if you use the Ipv4 Prefixes option.
Cancels the specified Capacity Reservation, releases the reserved capacity, and changes \n\t\t\tthe Capacity Reservation's state to cancelled.
You can cancel a Capacity Reservation that is in the following states:
\n\n assessing\n
\n active and there is no commitment duration or the commitment \n\t\t\t\t\tduration has elapsed. You can't cancel a future-dated Capacity Reservation during the commitment duration.
You can't modify or cancel a Capacity Block. For more information, see Capacity Blocks for ML.
\nIf a future-dated Capacity Reservation enters the delayed state, the commitment \n\t\t\tduration is waived, and you can cancel it as soon as it enters the active state.
Instances running in the reserved capacity continue running until you stop them. Stopped\n\t\t\tinstances that target the Capacity Reservation can no longer launch. Modify these instances to either\n\t\t\ttarget a different Capacity Reservation, launch On-Demand Instance capacity, or run in any open Capacity Reservation\n\t\t\tthat has matching attributes and sufficient capacity.
" + "smithy.api#documentation": "Cancels the specified Capacity Reservation, releases the reserved capacity, and changes \n\t\t\tthe Capacity Reservation's state to cancelled.
You can cancel a Capacity Reservation that is in the following states:
\n\n assessing\n
\n active and there is no commitment duration or the commitment \n\t\t\t\t\tduration has elapsed. You can't cancel a future-dated Capacity Reservation during the commitment duration.
If a future-dated Capacity Reservation enters the delayed state, the commitment \n\t\t\tduration is waived, and you can cancel it as soon as it enters the active state.
Instances running in the reserved capacity continue running until you stop them. Stopped\n\t\t\tinstances that target the Capacity Reservation can no longer launch. Modify these instances to either\n\t\t\ttarget a different Capacity Reservation, launch On-Demand Instance capacity, or run in any open Capacity Reservation\n\t\t\tthat has matching attributes and sufficient capacity.
" } }, "com.amazonaws.ec2#CancelCapacityReservationFleetError": { @@ -14731,7 +14737,7 @@ "target": "com.amazonaws.ec2#CopySnapshotResult" }, "traits": { - "smithy.api#documentation": "Copies a point-in-time snapshot of an EBS volume and stores it in Amazon S3. You can copy a\n snapshot within the same Region, from one Region to another, or from a Region to an Outpost. \n You can't copy a snapshot from an Outpost to a Region, from one Outpost to another, or within \n the same Outpost.
\nYou can use the snapshot to create EBS volumes or Amazon Machine Images (AMIs).
\nWhen copying snapshots to a Region, copies of encrypted EBS snapshots remain encrypted. \n \tCopies of unencrypted snapshots remain unencrypted, unless you enable encryption for the \n \tsnapshot copy operation. By default, encrypted snapshot copies use the default KMS key; \n \thowever, you can specify a different KMS key. To copy an encrypted \n \tsnapshot that has been shared from another account, you must have permissions for the KMS key \n \tused to encrypt the snapshot.
\nSnapshots copied to an Outpost are encrypted by default using the default encryption key\n for the Region, or a different key that you specify in the request using KmsKeyId. Outposts do not support unencrypted snapshots. For more information,\n see Amazon EBS\n local snapshots on Outposts in the Amazon EBS User Guide.
\nSnapshots created by copying another snapshot have an arbitrary volume ID that should not\n be used for any purpose.
\nFor more information, see Copy an Amazon EBS snapshot in the\n Amazon EBS User Guide.
", + "smithy.api#documentation": "Copies a point-in-time snapshot of an EBS volume and stores it in Amazon S3. You can copy a\n snapshot within the same Region, from one Region to another, or from a Region to an Outpost. \n You can't copy a snapshot from an Outpost to a Region, from one Outpost to another, or within \n the same Outpost.
\nYou can use the snapshot to create EBS volumes or Amazon Machine Images (AMIs).
\nWhen copying snapshots to a Region, copies of encrypted EBS snapshots remain encrypted. \n \tCopies of unencrypted snapshots remain unencrypted, unless you enable encryption for the \n \tsnapshot copy operation. By default, encrypted snapshot copies use the default KMS key; \n \thowever, you can specify a different KMS key. To copy an encrypted \n \tsnapshot that has been shared from another account, you must have permissions for the KMS key \n \tused to encrypt the snapshot.
\nSnapshots copied to an Outpost are encrypted by default using the default\n \t\tencryption key for the Region, or a different key that you specify in the request using \n \t\tKmsKeyId. Outposts do not support unencrypted \n \t snapshots. For more information, \n \t\t\tAmazon EBS local snapshots on Outposts in the Amazon EBS User Guide.
\nSnapshots created by copying another snapshot have an arbitrary volume ID that should not\n be used for any purpose.
\nFor more information, see Copy an Amazon EBS snapshot in the\n Amazon EBS User Guide.
", "smithy.api#examples": [ { "title": "To copy a snapshot", @@ -18172,7 +18178,7 @@ "target": "com.amazonaws.ec2#CreateManagedPrefixListResult" }, "traits": { - "smithy.api#documentation": "Creates a managed prefix list. You can specify entries for the prefix list. \n Each entry consists of a CIDR block and an optional description.
" + "smithy.api#documentation": "Creates a managed prefix list. You can specify one or more entries for the prefix list. \n Each entry consists of a CIDR block and an optional description.
" } }, "com.amazonaws.ec2#CreateManagedPrefixListRequest": { @@ -18991,7 +18997,7 @@ "Groups": { "target": "com.amazonaws.ec2#SecurityGroupIdStringList", "traits": { - "smithy.api#documentation": "The IDs of the security groups.
", + "smithy.api#documentation": "The IDs of one or more security groups.
", "smithy.api#xmlName": "SecurityGroupId" } }, @@ -19819,7 +19825,7 @@ "target": "com.amazonaws.ec2#Snapshot" }, "traits": { - "smithy.api#documentation": "Creates a snapshot of an EBS volume and stores it in Amazon S3. You can use snapshots for\n \tbackups, to make copies of EBS volumes, and to save data before shutting down an\n \tinstance.
\nThe location of the source EBS volume determines where you can create the snapshot.
\nIf the source volume is in a Region, you must create the snapshot in the same \n Region as the volume.
\nIf the source volume is in a Local Zone, you can create the snapshot in the same Local\n Zone or in its parent Amazon Web Services Region.
\nIf the source volume is on an Outpost, you can create the snapshot on the same \n Outpost or in its parent Amazon Web Services Region.
\nWhen a snapshot is created, any Amazon Web Services Marketplace product codes that are associated with the\n source volume are propagated to the snapshot.
\nYou can take a snapshot of an attached volume that is in use. However, snapshots only\n capture data that has been written to your Amazon EBS volume at the time the snapshot command is\n issued; this might exclude any data that has been cached by any applications or the operating\n system. If you can pause any file systems on the volume long enough to take a snapshot, your\n snapshot should be complete. However, if you cannot pause all file writes to the volume, you\n should unmount the volume from within the instance, issue the snapshot command, and then\n remount the volume to ensure a consistent and complete snapshot. You may remount and use your\n volume while the snapshot status is pending.
When you create a snapshot for an EBS volume that serves as a root device, we recommend \n that you stop the instance before taking the snapshot.
\nSnapshots that are taken from encrypted volumes are automatically encrypted. Volumes that\n are created from encrypted snapshots are also automatically encrypted. Your encrypted volumes\n and any associated snapshots always remain protected. For more information, see Amazon EBS encryption\n in the Amazon EBS User Guide.
", + "smithy.api#documentation": "Creates a snapshot of an EBS volume and stores it in Amazon S3. You can use snapshots for\n \tbackups, to make copies of EBS volumes, and to save data before shutting down an\n \tinstance.
\nThe location of the source EBS volume determines where you can create the snapshot.
\nIf the source volume is in a Region, you must create the snapshot in the same \n Region as the volume.
\nIf the source volume is in a Local Zone, you can create the snapshot in the same \n Local Zone or in parent Amazon Web Services Region.
\nIf the source volume is on an Outpost, you can create the snapshot on the same \n Outpost or in its parent Amazon Web Services Region.
\nWhen a snapshot is created, any Amazon Web Services Marketplace product codes that are associated with the\n source volume are propagated to the snapshot.
\nYou can take a snapshot of an attached volume that is in use. However, snapshots only\n capture data that has been written to your Amazon EBS volume at the time the snapshot command is\n issued; this might exclude any data that has been cached by any applications or the operating\n system. If you can pause any file systems on the volume long enough to take a snapshot, your\n snapshot should be complete. However, if you cannot pause all file writes to the volume, you\n should unmount the volume from within the instance, issue the snapshot command, and then\n remount the volume to ensure a consistent and complete snapshot. You may remount and use your\n volume while the snapshot status is pending.
When you create a snapshot for an EBS volume that serves as a root device, we recommend \n that you stop the instance before taking the snapshot.
\nSnapshots that are taken from encrypted volumes are automatically encrypted. Volumes that\n are created from encrypted snapshots are also automatically encrypted. Your encrypted volumes\n and any associated snapshots always remain protected. For more information, \n Amazon EBS encryption \n in the Amazon EBS User Guide.
", "smithy.api#examples": [ { "title": "To create a snapshot", @@ -19900,7 +19906,7 @@ "target": "com.amazonaws.ec2#CreateSnapshotsResult" }, "traits": { - "smithy.api#documentation": "Creates crash-consistent snapshots of multiple EBS volumes attached to an Amazon EC2 instance.\n Volumes are chosen by specifying an instance. Each volume attached to the specified instance \n will produce one snapshot that is crash-consistent across the instance. You can include all of \n the volumes currently attached to the instance, or you can exclude the root volume or specific \n data (non-root) volumes from the multi-volume snapshot set.
\nThe location of the source instance determines where you can create the snapshots.
\nIf the source instance is in a Region, you must create the snapshots in the same \n Region as the instance.
\nIf the source instance is in a Local Zone, you can create the snapshots in the same\n Local Zone or in its parent Amazon Web Services Region.
\nIf the source instance is on an Outpost, you can create the snapshots on the same \n Outpost or in its parent Amazon Web Services Region.
\nCreates crash-consistent snapshots of multiple EBS volumes attached to an Amazon EC2 instance.\n Volumes are chosen by specifying an instance. Each volume attached to the specified instance \n will produce one snapshot that is crash-consistent across the instance. You can include all of \n the volumes currently attached to the instance, or you can exclude the root volume or specific \n data (non-root) volumes from the multi-volume snapshot set.
\nThe location of the source instance determines where you can create the snapshots.
\nIf the source instance is in a Region, you must create the snapshots in the same \n Region as the instance.
\nIf the source instance is in a Local Zone, you can create the snapshots in the same \n Local Zone or in parent Amazon Web Services Region.
\nIf the source instance is on an Outpost, you can create the snapshots on the same \n Outpost or in its parent Amazon Web Services Region.
\nDeletes the specified snapshot.
\nWhen you make periodic snapshots of a volume, the snapshots are incremental, and only the\n blocks on the device that have changed since your last snapshot are saved in the new snapshot.\n When you delete a snapshot, only the data not needed for any other snapshot is removed. So\n regardless of which prior snapshots have been deleted, all active snapshots will have access\n to all the information needed to restore the volume.
\nYou cannot delete a snapshot of the root device of an EBS volume used by a registered AMI.\n You must first deregister the AMI before you can delete the snapshot.
\nFor more information, see Delete an Amazon EBS snapshot in the\n Amazon EBS User Guide.
", + "smithy.api#documentation": "Deletes the specified snapshot.
\nWhen you make periodic snapshots of a volume, the snapshots are incremental, and only the\n blocks on the device that have changed since your last snapshot are saved in the new snapshot.\n When you delete a snapshot, only the data not needed for any other snapshot is removed. So\n regardless of which prior snapshots have been deleted, all active snapshots will have access\n to all the information needed to restore the volume.
\nYou cannot delete a snapshot of the root device of an EBS volume used by a registered AMI.\n You must first de-register the AMI before you can delete the snapshot.
\nFor more information, see Delete an Amazon EBS snapshot in the\n Amazon EBS User Guide.
", "smithy.api#examples": [ { "title": "To delete a snapshot", @@ -29694,7 +29700,7 @@ "target": "com.amazonaws.ec2#DescribeCapacityBlockOfferingsResult" }, "traits": { - "smithy.api#documentation": "Describes Capacity Block offerings available for purchase in the Amazon Web Services Region that you're currently using. With Capacity Blocks, you purchase a\n\t\t\tspecific instance type for a period of time.
\nTo search for an available Capacity Block offering, you specify a reservation duration\n and instance count. You must select one of the following options.
\nFor reservation durations 1-day increments\n up 14 days and 7-day increments up to 182 days total\n
\nFor instance count 1, 2, 4, 8, 16, 32, or\n 64 instances\n
\nDescribes Capacity Block offerings available for purchase in the Amazon Web Services Region that you're currently using. With Capacity Blocks, you purchase a\n\t\t\tspecific instance type for a period of time.
", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -34175,7 +34181,7 @@ "target": "com.amazonaws.ec2#DescribeInstanceTopologyResult" }, "traits": { - "smithy.api#documentation": "Describes a tree-based hierarchy that represents the physical host placement of your\n EC2 instances within an Availability Zone or Local Zone. You can use this information to\n determine the relative proximity of your EC2 instances within the Amazon Web Services network to\n support your tightly coupled workloads.
\n\n Limitations\n
\nSupported zones
\nAvailability Zone
\nLocal Zone
\nSupported instance types
\n\n hpc6a.48xlarge | hpc6id.32xlarge |\n hpc7a.12xlarge | hpc7a.24xlarge |\n hpc7a.48xlarge | hpc7a.96xlarge |\n hpc7g.4xlarge | hpc7g.8xlarge |\n hpc7g.16xlarge\n
\n p3dn.24xlarge | p4d.24xlarge |\n p4de.24xlarge | p5.48xlarge |\n p5e.48xlarge | p5en.48xlarge\n
\n trn1.2xlarge | trn1.32xlarge |\n trn1n.32xlarge | trn2.48xlarge |\n trn2u.48xlarge\n
For more information, see Amazon EC2 instance\n topology in the Amazon EC2 User Guide.
", + "smithy.api#documentation": "Describes a tree-based hierarchy that represents the physical host placement of your\n EC2 instances within an Availability Zone or Local Zone. You can use this information to\n determine the relative proximity of your EC2 instances within the Amazon Web Services network to\n support your tightly coupled workloads.
\n\n Limitations\n
\nSupported zones
\nAvailability Zone
\nLocal Zone
\nSupported instance types
\n\n hpc6a.48xlarge | hpc6id.32xlarge |\n hpc7a.12xlarge | hpc7a.24xlarge |\n hpc7a.48xlarge | hpc7a.96xlarge |\n hpc7g.4xlarge | hpc7g.8xlarge |\n hpc7g.16xlarge\n
\n p3dn.24xlarge | p4d.24xlarge |\n p4de.24xlarge | p5.48xlarge |\n p5e.48xlarge | p5en.48xlarge\n
\n trn1.2xlarge | trn1.32xlarge |\n trn1n.32xlarge\n
For more information, see Amazon EC2 instance\n topology in the Amazon EC2 User Guide.
", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -37758,7 +37764,7 @@ "target": "com.amazonaws.ec2#DescribeNetworkInterfacesResult" }, "traits": { - "smithy.api#documentation": "Describes the specified network interfaces or all your network interfaces.
\nIf you have a large number of network interfaces, the operation fails unless \n you use pagination or one of the following filters: group-id, \n mac-address, private-dns-name, private-ip-address, \n private-dns-name, subnet-id, or vpc-id.
We strongly recommend using only paginated requests. Unpaginated requests are\n susceptible to throttling and timeouts.
\nDescribes one or more of your network interfaces.
\nIf you have a large number of network interfaces, the operation fails unless \n you use pagination or one of the following filters: group-id, \n mac-address, private-dns-name, private-ip-address, \n private-dns-name, subnet-id, or vpc-id.
We strongly recommend using only paginated requests. Unpaginated requests are\n susceptible to throttling and timeouts.
\nOne or more filters.
\n\n association.allocation-id - The allocation ID returned when you\n\t\t allocated the Elastic IP address (IPv4) for your network interface.
\n association.association-id - The association ID returned when the\n\t\t network interface was associated with an IPv4 address.
\n addresses.association.owner-id - The owner ID of the addresses associated with the network interface.
\n addresses.association.public-ip - The association ID returned when\n\t\t the network interface was associated with the Elastic IP address\n\t\t (IPv4).
\n addresses.primary - Whether the private IPv4 address is the primary\n IP address associated with the network interface.
\n addresses.private-ip-address - The private IPv4 addresses\n\t\t associated with the network interface.
\n association.ip-owner-id - The owner of the Elastic IP address\n (IPv4) associated with the network interface.
\n association.public-ip - The address of the Elastic IP address\n (IPv4) bound to the network interface.
\n association.public-dns-name - The public DNS name for the network\n interface (IPv4).
\n attachment.attach-time - The time that the network interface was attached to an instance.
\n attachment.attachment-id - The ID of the interface attachment.
\n attachment.delete-on-termination - Indicates whether the attachment is deleted when an instance is terminated.
\n attachment.device-index - The device index to which the network interface is attached.
\n attachment.instance-id - The ID of the instance to which the network interface is attached.
\n attachment.instance-owner-id - The owner ID of the instance to which the network interface is attached.
\n attachment.status - The status of the attachment (attaching | attached | detaching | detached).
\n availability-zone - The Availability Zone of the network interface.
\n description - The description of the network interface.
\n group-id - The ID of a security group associated with the network interface.
\n ipv6-addresses.ipv6-address - An IPv6 address associated with\n the network interface.
\n interface-type - The type of network interface (api_gateway_managed | \n\t\t aws_codestar_connections_managed | branch | ec2_instance_connect_endpoint | \n\t\t efa | efa-only | efs | gateway_load_balancer | \n\t\t gateway_load_balancer_endpoint | global_accelerator_managed | interface | \n\t\t iot_rules_managed | lambda | load_balancer | nat_gateway | \n\t\t network_load_balancer | quicksight | transit_gateway | trunk | \n\t\t vpc_endpoint).
\n mac-address - The MAC address of the network interface.
\n network-interface-id - The ID of the network interface.
\n operator.managed - A Boolean that indicates whether this is a\n managed network interface.
\n operator.principal - The principal that manages the network\n interface. Only valid for managed network interfaces, where managed\n is true.
\n owner-id - The Amazon Web Services account ID of the network interface owner.
\n private-dns-name - The private DNS name of the network interface (IPv4).
\n private-ip-address - The private IPv4 address or addresses of the\n network interface.
\n requester-id - The alias or Amazon Web Services account ID of the principal or service that created the network interface.
\n requester-managed - Indicates whether the network interface is being managed by an Amazon Web Services \n\t\t service (for example, Amazon Web Services Management Console, Auto Scaling, and so on).
\n source-dest-check - Indicates whether the network interface performs source/destination checking. \n\t\t A value of true means checking is enabled, and false means checking is disabled. \n\t\t The value must be false for the network interface to perform network address translation (NAT) in your VPC.
\n status - The status of the network interface. If the network interface is not attached to an instance, the status is available; \n\t\t if a network interface is attached to an instance the status is in-use.
\n subnet-id - The ID of the subnet for the network interface.
\n tag:Owner and the value TeamA, specify tag:Owner for the filter name and TeamA for the filter value.
\n tag-key - The key of a tag assigned to the resource. Use this filter to find all resources assigned a tag with a specific key, regardless of the tag value.
\n vpc-id - The ID of the VPC for the network interface.
One or more filters.
\n\n association.allocation-id - The allocation ID returned when you\n\t\t allocated the Elastic IP address (IPv4) for your network interface.
\n association.association-id - The association ID returned when the\n\t\t network interface was associated with an IPv4 address.
\n addresses.association.owner-id - The owner ID of the addresses associated with the network interface.
\n addresses.association.public-ip - The association ID returned when\n\t\t the network interface was associated with the Elastic IP address\n\t\t (IPv4).
\n addresses.primary - Whether the private IPv4 address is the primary\n IP address associated with the network interface.
\n addresses.private-ip-address - The private IPv4 addresses\n\t\t associated with the network interface.
\n association.ip-owner-id - The owner of the Elastic IP address\n (IPv4) associated with the network interface.
\n association.public-ip - The address of the Elastic IP address\n (IPv4) bound to the network interface.
\n association.public-dns-name - The public DNS name for the network\n interface (IPv4).
\n attachment.attach-time - The time that the network interface was attached to an instance.
\n attachment.attachment-id - The ID of the interface attachment.
\n attachment.delete-on-termination - Indicates whether the attachment is deleted when an instance is terminated.
\n attachment.device-index - The device index to which the network interface is attached.
\n attachment.instance-id - The ID of the instance to which the network interface is attached.
\n attachment.instance-owner-id - The owner ID of the instance to which the network interface is attached.
\n attachment.status - The status of the attachment (attaching | attached | detaching | detached).
\n availability-zone - The Availability Zone of the network interface.
\n description - The description of the network interface.
\n group-id - The ID of a security group associated with the network interface.
\n ipv6-addresses.ipv6-address - An IPv6 address associated with\n the network interface.
\n interface-type - The type of network interface (api_gateway_managed | \n\t\t aws_codestar_connections_managed | branch | ec2_instance_connect_endpoint | \n\t\t efa | efa-only | efs | gateway_load_balancer | \n\t\t gateway_load_balancer_endpoint | global_accelerator_managed | interface | \n\t\t iot_rules_managed | lambda | load_balancer | nat_gateway | \n\t\t network_load_balancer | quicksight | transit_gateway | trunk | \n\t\t vpc_endpoint).
\n mac-address - The MAC address of the network interface.
\n network-interface-id - The ID of the network interface.
\n owner-id - The Amazon Web Services account ID of the network interface owner.
\n private-dns-name - The private DNS name of the network interface (IPv4).
\n private-ip-address - The private IPv4 address or addresses of the\n network interface.
\n requester-id - The alias or Amazon Web Services account ID of the principal or service that created the network interface.
\n requester-managed - Indicates whether the network interface is being managed by an Amazon Web Services \n\t\t service (for example, Amazon Web Services Management Console, Auto Scaling, and so on).
\n source-dest-check - Indicates whether the network interface performs source/destination checking. \n\t\t A value of true means checking is enabled, and false means checking is disabled. \n\t\t The value must be false for the network interface to perform network address translation (NAT) in your VPC.
\n status - The status of the network interface. If the network interface is not attached to an instance, the status is available; \n\t\t if a network interface is attached to an instance the status is in-use.
\n subnet-id - The ID of the subnet for the network interface.
\n tag:Owner and the value TeamA, specify tag:Owner for the filter name and TeamA for the filter value.
\n tag-key - The key of a tag assigned to the resource. Use this filter to find all resources assigned a tag with a specific key, regardless of the tag value.
\n vpc-id - The ID of the VPC for the network interface.
Suppresses the specified device included in the block device mapping.
", + "smithy.api#documentation": "suppress the specified device included in the block device mapping.
", "smithy.api#xmlName": "noDevice" } } @@ -64021,7 +64027,7 @@ "target": "com.amazonaws.ec2#Integer", "traits": { "aws.protocols#ec2QueryName": "SecondaryPrivateIpAddressCount", - "smithy.api#documentation": "The number of secondary private IPv4 addresses. You can’t specify this parameter and\n also specify a secondary private IP address using the PrivateIpAddress\n parameter.
The number of secondary private IPv4 addresses. You can't specify this option and specify more than one private IP address using the private IP addresses option. You cannot specify this option if you're\n \tlaunching more than one instance in a RunInstances request.
", "smithy.api#xmlName": "secondaryPrivateIpAddressCount" } }, @@ -64323,7 +64329,7 @@ "target": "com.amazonaws.ec2#AcceleratorTypeSet", "traits": { "aws.protocols#ec2QueryName": "AcceleratorTypeSet", - "smithy.api#documentation": "The accelerator types that must be on the instance type.
\nFor instance types with FPGA accelerators, specify fpga.
For instance types with GPU accelerators, specify gpu.
For instance types with Inference accelerators, specify inference.
Default: Any accelerator type
", + "smithy.api#documentation": "The accelerator types that must be on the instance type.
\nFor instance types with GPU accelerators, specify gpu.
For instance types with FPGA accelerators, specify fpga.
Default: Any accelerator type
", "smithy.api#xmlName": "acceleratorTypeSet" } }, @@ -64506,7 +64512,7 @@ "AcceleratorTypes": { "target": "com.amazonaws.ec2#AcceleratorTypeSet", "traits": { - "smithy.api#documentation": "The accelerator types that must be on the instance type.
\nFor instance types with FPGA accelerators, specify fpga.
For instance types with GPU accelerators, specify gpu.
For instance types with Inference accelerators, specify inference.
Default: Any accelerator type
", + "smithy.api#documentation": "The accelerator types that must be on the instance type.
\nTo include instance types with GPU hardware, specify gpu.
To include instance types with FPGA hardware, specify fpga.
Default: Any accelerator type
", "smithy.api#xmlName": "AcceleratorType" } }, @@ -74358,7 +74364,7 @@ } }, "traits": { - "smithy.api#documentation": "Describes the IPv6 prefix option for a network interface.
" + "smithy.api#documentation": "Describes the IPv4 prefix option for a network interface.
" } }, "com.amazonaws.ec2#Ipv6PrefixSpecificationResponse": { @@ -109260,7 +109266,7 @@ "target": "com.amazonaws.ec2#UnassignIpv6AddressesResult" }, "traits": { - "smithy.api#documentation": "Unassigns the specified IPv6 addresses or Prefix Delegation prefixes from a network interface.
" + "smithy.api#documentation": "Unassigns one or more IPv6 addresses IPv4 Prefix Delegation prefixes from a network interface.
" } }, "com.amazonaws.ec2#UnassignIpv6AddressesRequest": { @@ -109319,7 +109325,7 @@ "target": "com.amazonaws.ec2#IpPrefixList", "traits": { "aws.protocols#ec2QueryName": "UnassignedIpv6PrefixSet", - "smithy.api#documentation": "The IPv6 prefixes that have been unassigned from the network interface.
", + "smithy.api#documentation": "The IPv4 prefixes that have been unassigned from the network interface.
", "smithy.api#xmlName": "unassignedIpv6PrefixSet" } } @@ -109337,7 +109343,7 @@ "target": "smithy.api#Unit" }, "traits": { - "smithy.api#documentation": "Unassigns the specified secondary private IP addresses or IPv4 Prefix Delegation prefixes from a \n \tnetwork interface.
", + "smithy.api#documentation": "Unassigns one or more secondary private IP addresses, or IPv4 Prefix Delegation prefixes from a \n \tnetwork interface.
", "smithy.api#examples": [ { "title": "To unassign a secondary private IP address from a network interface",