From 0d9d3e82ea19aa0cf6930ba02282277b92bc2d29 Mon Sep 17 00:00:00 2001
From: awstools UnauthorizedOperation
.
If you have Local Zones enabled, you can choose a network border group for Local Zones when you provision and advertise a BYOIPv4 CIDR. Choose the network border group carefully as the EIP and the Amazon Web Services resource it is associated with must reside in the same network border group.
+ *You can provision BYOIP address ranges to and advertise them in the following Local Zone network border groups:
+ *us-east-1-dfw-2
+ *us-west-2-lax-1
+ *us-west-2-phx-2
+ *You cannot provision or advertise BYOIPv6 address ranges in Local Zones at this time.
+ *The state of the address pool.
*/ State?: ByoipCidrState; + + /** + * @public + *If you have Local Zones enabled, you can choose a network border group for Local Zones when you provision and advertise a BYOIPv4 CIDR. Choose the network border group carefully as the EIP and the Amazon Web Services resource it is associated with must reside in the same network border group.
+ *You can provision BYOIP address ranges to and advertise them in the following Local Zone network border groups:
+ *us-east-1-dfw-2
+ *us-west-2-lax-1
+ *us-west-2-phx-2
+ *You cannot provision or advertise BYOIPv6 address ranges in Local Zones at this time.
+ *IMDSv2 uses token-backed sessions. Set the use of HTTP tokens to optional
- * (in other words, set the use of IMDSv2 to optional
) or
- * required
(in other words, set the use of IMDSv2 to
- * required
).
Indicates whether IMDSv2 is required.
*
- * optional
- When IMDSv2 is optional, you can choose to retrieve instance metadata with or without
- * a session token in your request. If you retrieve the IAM role credentials
- * without a token, the IMDSv1 role credentials are returned. If you retrieve the IAM role credentials
- * using a valid session token, the IMDSv2 role credentials are returned.
optional
- IMDSv2 is optional. You can choose whether to send a
+ * session token in your instance metadata retrieval requests. If you retrieve
+ * IAM role credentials without a session token, you receive the IMDSv1 role
+ * credentials. If you retrieve IAM role credentials using a valid session token,
+ * you receive the IMDSv2 role credentials.
*
- * required
- When IMDSv2 is required, you must send a session token
- * with any instance metadata retrieval requests. In this state, retrieving the IAM role
- * credentials always returns IMDSv2 credentials; IMDSv1 credentials are not available.
required
- IMDSv2 is required. You must send a session token
+ * in your instance metadata retrieval requests. With this option, retrieving the
+ * IAM role credentials always returns IMDSv2 credentials; IMDSv1 credentials are
+ * not available.
* Default: optional
- *
Default: If the value of ImdsSupport
for the Amazon Machine Image (AMI)
+ * for your instance is v2.0
, the default is required
.
Associates a public IPv4 address with eth0 for a new network interface.
+ *Starting on February 1, 2024, Amazon Web Services will charge for all public IPv4 addresses, including public IPv4 addresses + * associated with running instances and Elastic IP addresses. For more information, see the Public IPv4 Address tab on the Amazon VPC pricing page.
*/ AssociatePublicIpAddress?: boolean; @@ -7380,29 +7381,8 @@ export interface RequestLaunchTemplateData { /** * @public - *The tags to apply to the resources that are created during instance launch.
- *You can specify tags for the following resources only:
- *Instances
- *Volumes
- *Elastic graphics
- *Spot Instance requests
- *Network interfaces
- *To tag a resource after it has been created, see CreateTags.
- *To tag the launch template itself, you must use the TagSpecification parameter.
- *The tags to apply to the resources that are created during instance launch. These + * tags are not applied to the launch template.
*/ TagSpecifications?: LaunchTemplateTagSpecificationRequest[]; @@ -8162,18 +8142,24 @@ export interface LaunchTemplateInstanceMetadataOptions { /** * @public - *Indicates whether IMDSv2 is optional
or required
.
- * optional
- When IMDSv2 is optional, you can choose to retrieve instance metadata with or without
- * a session token in your request. If you retrieve the IAM role credentials
- * without a token, the IMDSv1 role credentials are returned. If you retrieve the IAM role credentials
- * using a valid session token, the IMDSv2 role credentials are returned.
- * required
- When IMDSv2 is required, you must send a session token
- * with any instance metadata retrieval requests. In this state, retrieving the IAM role
- * credentials always returns IMDSv2 credentials; IMDSv1 credentials are not available.
Default: optional
- *
Indicates whether IMDSv2 is required.
+ *
+ * optional
- IMDSv2 is optional. You can choose whether to send a
+ * session token in your instance metadata retrieval requests. If you retrieve
+ * IAM role credentials without a session token, you receive the IMDSv1 role
+ * credentials. If you retrieve IAM role credentials using a valid session token,
+ * you receive the IMDSv2 role credentials.
+ * required
- IMDSv2 is required. You must send a session token
+ * in your instance metadata retrieval requests. With this option, retrieving the
+ * IAM role credentials always returns IMDSv2 credentials; IMDSv1 credentials are
+ * not available.
Indicates whether to associate a public IPv4 address with eth0 for a new network * interface.
+ *Starting on February 1, 2024, Amazon Web Services will charge for all public IPv4 addresses, including public IPv4 addresses + * associated with running instances and Elastic IP addresses. For more information, see the Public IPv4 Address tab on the Amazon VPC pricing page.
*/ AssociatePublicIpAddress?: boolean; diff --git a/clients/client-ec2/src/models/models_4.ts b/clients/client-ec2/src/models/models_4.ts index 9b10ea0000ce..d20c6e7128e7 100644 --- a/clients/client-ec2/src/models/models_4.ts +++ b/clients/client-ec2/src/models/models_4.ts @@ -10815,6 +10815,8 @@ export interface InstanceNetworkInterfaceSpecification { * assigned to a new network interface, not an existing one. You cannot specify more than one * network interface in the request. If launching into a default subnet, the default value is *true
.
+ * Starting on February 1, 2024, Amazon Web Services will charge for all public IPv4 addresses, including public IPv4 addresses + * associated with running instances and Elastic IP addresses. For more information, see the Public IPv4 Address tab on the Amazon VPC pricing page.
*/ AssociatePublicIpAddress?: boolean; diff --git a/clients/client-ec2/src/models/models_6.ts b/clients/client-ec2/src/models/models_6.ts index 7eb67efea15f..2cc615e942c8 100644 --- a/clients/client-ec2/src/models/models_6.ts +++ b/clients/client-ec2/src/models/models_6.ts @@ -8645,6 +8645,27 @@ export interface ProvisionByoipCidrRequest { *Reserved.
*/ MultiRegion?: boolean; + + /** + * @public + *If you have Local Zones enabled, you can choose a network border group for Local Zones when you provision and advertise a BYOIPv4 CIDR. Choose the network border group carefully as the EIP and the Amazon Web Services resource it is associated with must reside in the same network border group.
+ *You can provision BYOIP address ranges to and advertise them in the following Local Zone network border groups:
+ *us-east-1-dfw-2
+ *us-west-2-lax-1
+ *us-west-2-phx-2
+ *You cannot provision or advertise BYOIPv6 address ranges in Local Zones at this time.
+ *Checks whether you have the required permissions for the action, without actually making the request, \n and provides an error response. If you have the required permissions, the error response is DryRunOperation
. \n Otherwise, it is UnauthorizedOperation
.
If you have Local Zones enabled, you can choose a network border group for Local Zones when you provision and advertise a BYOIPv4 CIDR. Choose the network border group carefully as the EIP and the Amazon Web Services resource it is associated with must reside in the same network border group.
\nYou can provision BYOIP address ranges to and advertise them in the following Local Zone network border groups:
\nus-east-1-dfw-2
\nus-west-2-lax-1
\nus-west-2-phx-2
\nYou cannot provision or advertise BYOIPv6 address ranges in Local Zones at this time.
\nENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the\n\t\t\tmaximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances.\n\t\t\tWith ENA Express, you can communicate between two EC2 instances in the same subnet within the same\n\t\t\taccount, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
\nTo improve the reliability of network packet delivery, ENA Express reorders network packets on the\n\t\t\treceiving end by default. However, some UDP-based applications are designed to handle network packets\n\t\t\tthat are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express\n\t\t\tis enabled, you can specify whether UDP network traffic uses it.
" + "smithy.api#documentation": "ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the \n\t\t\tmaximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. \n\t\t\tWith ENA Express, you can communicate between two EC2 instances in the same subnet within the same \n\t\t\taccount, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
\nTo improve the reliability of network packet delivery, ENA Express reorders network packets on the \n\t\t\treceiving end by default. However, some UDP-based applications are designed to handle network packets \n\t\t\tthat are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express \n\t\t\tis enabled, you can specify whether UDP network traffic uses it.
" } }, "com.amazonaws.ec2#AttachmentEnaSrdUdpSpecification": { @@ -8023,13 +8029,13 @@ "target": "com.amazonaws.ec2#Boolean", "traits": { "aws.protocols#ec2QueryName": "EnaSrdUdpEnabled", - "smithy.api#documentation": "Indicates whether UDP traffic to and from the instance uses ENA Express. To specify this setting,\n\t\t\tyou must first enable ENA Express.
", + "smithy.api#documentation": "Indicates whether UDP traffic to and from the instance uses ENA Express. To specify this setting, \n\t\t\tyou must first enable ENA Express.
", "smithy.api#xmlName": "enaSrdUdpEnabled" } } }, "traits": { - "smithy.api#documentation": "ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic\n\t\t\tautomatically uses it. However, some UDP-based applications are designed to handle network packets that are\n\t\t\tout of order, without a need for retransmission, such as live video broadcasting or other near-real-time\n\t\t\tapplications. For UDP traffic, you can specify whether to use ENA Express, based on your application\n\t\t\tenvironment needs.
" + "smithy.api#documentation": "ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic \n\t\t\tautomatically uses it. However, some UDP-based applications are designed to handle network packets that are \n\t\t\tout of order, without a need for retransmission, such as live video broadcasting or other near-real-time \n\t\t\tapplications. For UDP traffic, you can specify whether to use ENA Express, based on your application \n\t\t\tenvironment needs.
" } }, "com.amazonaws.ec2#AttachmentStatus": { @@ -9434,6 +9440,14 @@ "smithy.api#documentation": "The state of the address pool.
", "smithy.api#xmlName": "state" } + }, + "NetworkBorderGroup": { + "target": "com.amazonaws.ec2#String", + "traits": { + "aws.protocols#ec2QueryName": "NetworkBorderGroup", + "smithy.api#documentation": "If you have Local Zones enabled, you can choose a network border group for Local Zones when you provision and advertise a BYOIPv4 CIDR. Choose the network border group carefully as the EIP and the Amazon Web Services resource it is associated with must reside in the same network border group.
\nYou can provision BYOIP address ranges to and advertise them in the following Local Zone network border groups:
\nus-east-1-dfw-2
\nus-west-2-lax-1
\nus-west-2-phx-2
\nYou cannot provision or advertise BYOIPv6 address ranges in Local Zones at this time.
\nENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the\n\t\t\tmaximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances.\n\t\t\tWith ENA Express, you can communicate between two EC2 instances in the same subnet within the same\n\t\t\taccount, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
\nTo improve the reliability of network packet delivery, ENA Express reorders network packets on the\n\t\t\treceiving end by default. However, some UDP-based applications are designed to handle network packets\n\t\t\tthat are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express\n\t\t\tis enabled, you can specify whether UDP network traffic uses it.
" + "smithy.api#documentation": "ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the \n\t\t\tmaximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. \n\t\t\tWith ENA Express, you can communicate between two EC2 instances in the same subnet within the same \n\t\t\taccount, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
\nTo improve the reliability of network packet delivery, ENA Express reorders network packets on the \n\t\t\treceiving end by default. However, some UDP-based applications are designed to handle network packets \n\t\t\tthat are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express \n\t\t\tis enabled, you can specify whether UDP network traffic uses it.
" } }, "com.amazonaws.ec2#EnaSrdSpecificationRequest": { @@ -45306,12 +45320,12 @@ "EnaSrdUdpEnabled": { "target": "com.amazonaws.ec2#Boolean", "traits": { - "smithy.api#documentation": "Indicates whether UDP traffic to and from the instance uses ENA Express. To specify this setting,\n\t\t\tyou must first enable ENA Express.
" + "smithy.api#documentation": "Indicates whether UDP traffic to and from the instance uses ENA Express. To specify this setting, \n\t\t\tyou must first enable ENA Express.
" } } }, "traits": { - "smithy.api#documentation": "ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic\n\t\t\tautomatically uses it. However, some UDP-based applications are designed to handle network packets that are\n\t\t\tout of order, without a need for retransmission, such as live video broadcasting or other near-real-time\n\t\t\tapplications. For UDP traffic, you can specify whether to use ENA Express, based on your application\n\t\t\tenvironment needs.
" + "smithy.api#documentation": "ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic \n\t\t\tautomatically uses it. However, some UDP-based applications are designed to handle network packets that are \n\t\t\tout of order, without a need for retransmission, such as live video broadcasting or other near-real-time \n\t\t\tapplications. For UDP traffic, you can specify whether to use ENA Express, based on your application \n\t\t\tenvironment needs.
" } }, "com.amazonaws.ec2#EnaSrdUdpSpecificationRequest": { @@ -57298,7 +57312,7 @@ } }, "traits": { - "smithy.api#documentation": "ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the\n\t\t\tmaximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances.\n\t\t\tWith ENA Express, you can communicate between two EC2 instances in the same subnet within the same\n\t\t\taccount, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
\nTo improve the reliability of network packet delivery, ENA Express reorders network packets on the\n\t\t\treceiving end by default. However, some UDP-based applications are designed to handle network packets\n\t\t\tthat are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express\n\t\t\tis enabled, you can specify whether UDP network traffic uses it.
" + "smithy.api#documentation": "ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the \n\t\t\tmaximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. \n\t\t\tWith ENA Express, you can communicate between two EC2 instances in the same subnet within the same \n\t\t\taccount, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
\nTo improve the reliability of network packet delivery, ENA Express reorders network packets on the \n\t\t\treceiving end by default. However, some UDP-based applications are designed to handle network packets \n\t\t\tthat are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express \n\t\t\tis enabled, you can specify whether UDP network traffic uses it.
" } }, "com.amazonaws.ec2#InstanceAttachmentEnaSrdUdpSpecification": { @@ -57308,13 +57322,13 @@ "target": "com.amazonaws.ec2#Boolean", "traits": { "aws.protocols#ec2QueryName": "EnaSrdUdpEnabled", - "smithy.api#documentation": "Indicates whether UDP traffic to and from the instance uses ENA Express. To specify this setting,\n\t\t\tyou must first enable ENA Express.
", + "smithy.api#documentation": "Indicates whether UDP traffic to and from the instance uses ENA Express. To specify this setting, \n\t\t\tyou must first enable ENA Express.
", "smithy.api#xmlName": "enaSrdUdpEnabled" } } }, "traits": { - "smithy.api#documentation": "ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic\n\t\t\tautomatically uses it. However, some UDP-based applications are designed to handle network packets that are\n\t\t\tout of order, without a need for retransmission, such as live video broadcasting or other near-real-time\n\t\t\tapplications. For UDP traffic, you can specify whether to use ENA Express, based on your application\n\t\t\tenvironment needs.
" + "smithy.api#documentation": "ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic \n\t\t\tautomatically uses it. However, some UDP-based applications are designed to handle network packets that are \n\t\t\tout of order, without a need for retransmission, such as live video broadcasting or other near-real-time \n\t\t\tapplications. For UDP traffic, you can specify whether to use ENA Express, based on your application \n\t\t\tenvironment needs.
" } }, "com.amazonaws.ec2#InstanceAttribute": { @@ -58988,7 +59002,7 @@ "target": "com.amazonaws.ec2#InstanceAttachmentEnaSrdSpecification", "traits": { "aws.protocols#ec2QueryName": "EnaSrdSpecification", - "smithy.api#documentation": "Contains the ENA Express settings for the network interface that's attached\n\t\t\tto the instance.
", + "smithy.api#documentation": "Contains the ENA Express settings for the network interface that's attached \n\t\t\tto the instance.
", "smithy.api#xmlName": "enaSrdSpecification" } } @@ -59013,7 +59027,7 @@ "target": "com.amazonaws.ec2#Boolean", "traits": { "aws.protocols#ec2QueryName": "AssociatePublicIpAddress", - "smithy.api#documentation": "Indicates whether to assign a public IPv4 address to an instance you launch in a VPC. The\n public IP address can only be assigned to a network interface for eth0, and can only be\n assigned to a new network interface, not an existing one. You cannot specify more than one\n network interface in the request. If launching into a default subnet, the default value is\n true
.
Indicates whether to assign a public IPv4 address to an instance you launch in a VPC. The\n public IP address can only be assigned to a network interface for eth0, and can only be\n assigned to a new network interface, not an existing one. You cannot specify more than one\n network interface in the request. If launching into a default subnet, the default value is\n true
.
Starting on February 1, 2024, Amazon Web Services will charge for all public IPv4 addresses, including public IPv4 addresses \nassociated with running instances and Elastic IP addresses. For more information, see the Public IPv4 Address tab on the Amazon VPC pricing page.
", "smithy.api#xmlName": "associatePublicIpAddress" } }, @@ -59157,7 +59171,7 @@ "EnaSrdSpecification": { "target": "com.amazonaws.ec2#EnaSrdSpecificationRequest", "traits": { - "smithy.api#documentation": "Specifies the ENA Express settings for the network interface that's attached to\n\t\t\tthe instance.
" + "smithy.api#documentation": "Specifies the ENA Express settings for the network interface that's attached to \n\t\t\tthe instance.
" } }, "ConnectionTrackingSpecification": { @@ -66503,6 +66517,7 @@ "target": "com.amazonaws.ec2#IpamPoolSourceResource", "traits": { "aws.protocols#ec2QueryName": "SourceResource", + "smithy.api#documentation": "The resource used to provision CIDRs to a resource planning pool.
", "smithy.api#xmlName": "sourceResource" } } @@ -69651,7 +69666,7 @@ "target": "com.amazonaws.ec2#LaunchTemplateHttpTokensState", "traits": { "aws.protocols#ec2QueryName": "HttpTokens", - "smithy.api#documentation": "Indicates whether IMDSv2 is optional
or required
.
\n optional
- When IMDSv2 is optional, you can choose to retrieve instance metadata with or without \n a session token in your request. If you retrieve the IAM role credentials \n without a token, the IMDSv1 role credentials are returned. If you retrieve the IAM role credentials \n using a valid session token, the IMDSv2 role credentials are returned.
\n required
- When IMDSv2 is required, you must send a session token \n with any instance metadata retrieval requests. In this state, retrieving the IAM role \n credentials always returns IMDSv2 credentials; IMDSv1 credentials are not available.
Default: optional
\n
Indicates whether IMDSv2 is required.
\n\n optional
- IMDSv2 is optional. You can choose whether to send a \n session token in your instance metadata retrieval requests. If you retrieve \n IAM role credentials without a session token, you receive the IMDSv1 role \n credentials. If you retrieve IAM role credentials using a valid session token, \n you receive the IMDSv2 role credentials.
\n required
- IMDSv2 is required. You must send a session token \n in your instance metadata retrieval requests. With this option, retrieving the \n IAM role credentials always returns IMDSv2 credentials; IMDSv1 credentials are \n not available.
IMDSv2 uses token-backed sessions. Set the use of HTTP tokens to optional
\n (in other words, set the use of IMDSv2 to optional
) or\n required
(in other words, set the use of IMDSv2 to\n required
).
\n optional
- When IMDSv2 is optional, you can choose to retrieve instance metadata with or without \n a session token in your request. If you retrieve the IAM role credentials \n without a token, the IMDSv1 role credentials are returned. If you retrieve the IAM role credentials \n using a valid session token, the IMDSv2 role credentials are returned.
\n required
- When IMDSv2 is required, you must send a session token \n with any instance metadata retrieval requests. In this state, retrieving the IAM role \n credentials always returns IMDSv2 credentials; IMDSv1 credentials are not available.
Default: optional
\n
Indicates whether IMDSv2 is required.
\n\n optional
- IMDSv2 is optional. You can choose whether to send a \n session token in your instance metadata retrieval requests. If you retrieve \n IAM role credentials without a session token, you receive the IMDSv1 role \n credentials. If you retrieve IAM role credentials using a valid session token, \n you receive the IMDSv2 role credentials.
\n required
- IMDSv2 is required. You must send a session token \n in your instance metadata retrieval requests. With this option, retrieving the \n IAM role credentials always returns IMDSv2 credentials; IMDSv1 credentials are \n not available.
Default: If the value of ImdsSupport
for the Amazon Machine Image (AMI) \n for your instance is v2.0
, the default is required
.
Indicates whether to associate a public IPv4 address with eth0 for a new network\n interface.
", + "smithy.api#documentation": "Indicates whether to associate a public IPv4 address with eth0 for a new network\n interface.
\nStarting on February 1, 2024, Amazon Web Services will charge for all public IPv4 addresses, including public IPv4 addresses \nassociated with running instances and Elastic IP addresses. For more information, see the Public IPv4 Address tab on the Amazon VPC pricing page.
", "smithy.api#xmlName": "associatePublicIpAddress" } }, @@ -69986,7 +70001,7 @@ "AssociatePublicIpAddress": { "target": "com.amazonaws.ec2#Boolean", "traits": { - "smithy.api#documentation": "Associates a public IPv4 address with eth0 for a new network interface.
" + "smithy.api#documentation": "Associates a public IPv4 address with eth0 for a new network interface.
\nStarting on February 1, 2024, Amazon Web Services will charge for all public IPv4 addresses, including public IPv4 addresses \nassociated with running instances and Elastic IP addresses. For more information, see the Public IPv4 Address tab on the Amazon VPC pricing page.
" } }, "DeleteOnTermination": { @@ -83035,6 +83050,12 @@ "traits": { "smithy.api#documentation": "Reserved.
" } + }, + "NetworkBorderGroup": { + "target": "com.amazonaws.ec2#String", + "traits": { + "smithy.api#documentation": "If you have Local Zones enabled, you can choose a network border group for Local Zones when you provision and advertise a BYOIPv4 CIDR. Choose the network border group carefully as the EIP and the Amazon Web Services resource it is associated with must reside in the same network border group.
\nYou can provision BYOIP address ranges to and advertise them in the following Local Zone network border groups:
\nus-east-1-dfw-2
\nus-west-2-lax-1
\nus-west-2-phx-2
\nYou cannot provision or advertise BYOIPv6 address ranges in Local Zones at this time.
\nThe tags to apply to the resources that are created during instance launch.
\nYou can specify tags for the following resources only:
\nInstances
\nVolumes
\nElastic graphics
\nSpot Instance requests
\nNetwork interfaces
\nTo tag a resource after it has been created, see CreateTags.
\nTo tag the launch template itself, you must use the TagSpecification parameter.
\nThe tags to apply to the resources that are created during instance launch. These\n tags are not applied to the launch template.
", "smithy.api#xmlName": "TagSpecification" } },