From 14164db00b70f7c205062bd5e437ae1aadfc323d Mon Sep 17 00:00:00 2001 From: AWS SDK for Go v2 automation user Date: Fri, 29 Jul 2022 18:10:52 +0000 Subject: [PATCH] Update API model --- codegen/sdk-codegen/aws-models/ec2.json | 92 +++++---- codegen/sdk-codegen/aws-models/fsx.json | 6 +- codegen/sdk-codegen/aws-models/shield.json | 230 +++++++++++++++++---- 3 files changed, 242 insertions(+), 86 deletions(-) diff --git a/codegen/sdk-codegen/aws-models/ec2.json b/codegen/sdk-codegen/aws-models/ec2.json index 4d42b87c325..ec1b6a88772 100644 --- a/codegen/sdk-codegen/aws-models/ec2.json +++ b/codegen/sdk-codegen/aws-models/ec2.json @@ -1166,7 +1166,7 @@ "target": "com.amazonaws.ec2#AllocateAddressResult" }, "traits": { - "smithy.api#documentation": "

Allocates an Elastic IP address to your Amazon Web Services account. After you allocate the Elastic IP address you can associate \n it with an instance or network interface. After you release an Elastic IP address, it is released to the IP address \n pool and can be allocated to a different Amazon Web Services account.

\n

You can allocate an Elastic IP address from an address pool owned by Amazon Web Services or from an address pool created \n from a public IPv4 address range that you have brought to Amazon Web Services for use with your Amazon Web Services resources using bring your own \n IP addresses (BYOIP). For more information, see Bring Your Own IP Addresses (BYOIP) in the Amazon Elastic Compute Cloud User Guide.

\n

[EC2-VPC] If you release an Elastic IP address, you might be able to recover it. You cannot recover an \n Elastic IP address that you released after it is allocated to another Amazon Web Services account. You cannot recover an Elastic IP\n address for EC2-Classic. To attempt to recover an Elastic IP address that you released, specify it in this operation.

\n

An Elastic IP address is for use either in the EC2-Classic platform or in a VPC. By default, you can allocate\n 5 Elastic IP addresses for EC2-Classic per Region and 5 Elastic IP addresses for EC2-VPC per Region.

\n

For more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.

\n

You can allocate a carrier IP address which is a public IP address from a telecommunication carrier, to a network interface which resides in a subnet in a Wavelength Zone (for example an EC2 instance).

" + "smithy.api#documentation": "

Allocates an Elastic IP address to your Amazon Web Services account. After you allocate the Elastic IP address you can associate \n it with an instance or network interface. After you release an Elastic IP address, it is released to the IP address \n pool and can be allocated to a different Amazon Web Services account.

\n

You can allocate an Elastic IP address from an address pool owned by Amazon Web Services or from an address pool created \n from a public IPv4 address range that you have brought to Amazon Web Services for use with your Amazon Web Services resources using bring your own \n IP addresses (BYOIP). For more information, see Bring Your Own IP Addresses (BYOIP) in the Amazon Elastic Compute Cloud User Guide.

\n

[EC2-VPC] If you release an Elastic IP address, you might be able to recover it. You cannot recover an \n Elastic IP address that you released after it is allocated to another Amazon Web Services account. You cannot recover an Elastic IP\n address for EC2-Classic. To attempt to recover an Elastic IP address that you released, specify it in this operation.

\n

An Elastic IP address is for use either in the EC2-Classic platform or in a VPC. By default, you can allocate\n 5 Elastic IP addresses for EC2-Classic per Region and 5 Elastic IP addresses for EC2-VPC per Region.

\n

For more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.

\n

You can allocate a carrier IP address which is a public IP address from a telecommunication carrier, to a network interface which resides in a subnet in a Wavelength Zone (for example an EC2 instance).

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#AllocateAddressRequest": { @@ -3985,7 +3985,7 @@ "target": "com.amazonaws.ec2#AssociateAddressResult" }, "traits": { - "smithy.api#documentation": "

Associates an Elastic IP address, or carrier IP address (for instances that are in\n subnets in Wavelength Zones) with an instance or a network interface. Before you can use an\n Elastic IP address, you must allocate it to your account.

\n

An Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.

\n

[EC2-Classic, VPC in an EC2-VPC-only account] If the Elastic IP address is already\n associated with a different instance, it is disassociated from that instance and associated\n with the specified instance. If you associate an Elastic IP address with an instance that has\n an existing Elastic IP address, the existing address is disassociated from the instance, but\n remains allocated to your account.

\n

[VPC in an EC2-Classic account] If you don't specify a private IP address, the Elastic\n IP address is associated with the primary IP address. If the Elastic IP address is already\n associated with a different instance or a network interface, you get an error unless you allow\n reassociation. You cannot associate an Elastic IP address with an instance or network\n interface that has an existing Elastic IP address.

\n

[Subnets in Wavelength Zones] You can associate an IP address from the telecommunication\n carrier to the instance or network interface.

\n

You cannot associate an Elastic IP address with an interface in a different network border group.

\n \n

This is an idempotent operation. If you perform the operation more than once, Amazon EC2\n doesn't return an error, and you may be charged for each time the Elastic IP address is\n remapped to the same instance. For more information, see the Elastic IP\n Addresses section of Amazon EC2\n Pricing.

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

Associates an Elastic IP address, or carrier IP address (for instances that are in\n subnets in Wavelength Zones) with an instance or a network interface. Before you can use an\n Elastic IP address, you must allocate it to your account.

\n

An Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.

\n

[EC2-Classic, VPC in an EC2-VPC-only account] If the Elastic IP address is already\n associated with a different instance, it is disassociated from that instance and associated\n with the specified instance. If you associate an Elastic IP address with an instance that has\n an existing Elastic IP address, the existing address is disassociated from the instance, but\n remains allocated to your account.

\n

[VPC in an EC2-Classic account] If you don't specify a private IP address, the Elastic\n IP address is associated with the primary IP address. If the Elastic IP address is already\n associated with a different instance or a network interface, you get an error unless you allow\n reassociation. You cannot associate an Elastic IP address with an instance or network\n interface that has an existing Elastic IP address.

\n

[Subnets in Wavelength Zones] You can associate an IP address from the telecommunication\n carrier to the instance or network interface.

\n

You cannot associate an Elastic IP address with an interface in a different network border group.

\n \n

This is an idempotent operation. If you perform the operation more than once, Amazon EC2\n doesn't return an error, and you may be charged for each time the Elastic IP address is\n remapped to the same instance. For more information, see the Elastic IP\n Addresses section of Amazon EC2\n Pricing.

\n \n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#AssociateAddressRequest": { @@ -4996,7 +4996,7 @@ "target": "com.amazonaws.ec2#AttachClassicLinkVpcResult" }, "traits": { - "smithy.api#documentation": "

Links an EC2-Classic instance to a ClassicLink-enabled VPC through one or more of the VPC's\n\t\t\tsecurity groups. You cannot link an EC2-Classic instance to more than one VPC at a time. You\n\t\t\tcan only link an instance that's in the running state. An instance is\n\t\t\tautomatically unlinked from a VPC when it's stopped - you can link it to the VPC again when\n\t\t\tyou restart it.

\n\t\t

After you've linked an instance, you cannot change the VPC security groups that are associated with it. To change the security groups, you must first unlink the instance, and then link it again.

\n\t\t

Linking your instance to a VPC is sometimes referred to as attaching your instance.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n\t \n\t

Links an EC2-Classic instance to a ClassicLink-enabled VPC through one or more of the VPC's\n\t\t\tsecurity groups. You cannot link an EC2-Classic instance to more than one VPC at a time. You\n\t\t\tcan only link an instance that's in the running state. An instance is\n\t\t\tautomatically unlinked from a VPC when it's stopped - you can link it to the VPC again when\n\t\t\tyou restart it.

\n\t\t

After you've linked an instance, you cannot change the VPC security groups that are associated with it. To change the security groups, you must first unlink the instance, and then link it again.

\n\t\t

Linking your instance to a VPC is sometimes referred to as attaching your instance.

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

Describes a linked EC2-Classic instance.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n\t \n\t\t

Describes a linked EC2-Classic instance.

" } }, "com.amazonaws.ec2#ClassicLinkInstanceList": { @@ -10724,7 +10724,7 @@ "target": "com.amazonaws.ec2#CreateDefaultVpcResult" }, "traits": { - "smithy.api#documentation": "

Creates a default VPC with a size /16 IPv4 CIDR block and a default subnet\n\t\t\tin each Availability Zone. For more information about the components of a default VPC,\n\t\t\tsee Default VPC and\n\t\t\tdefault subnets in the Amazon Virtual Private Cloud User Guide. You cannot\n\t\t\tspecify the components of the default VPC yourself.

\n\t\t

If you deleted your previous default VPC, you can create a default VPC. You cannot have\n\t\t\tmore than one default VPC per Region.

\n\t\t

If your account supports EC2-Classic, you cannot use this action to create a default VPC\n\t\t\tin a Region that supports EC2-Classic. If you want a default VPC in a Region that\n\t\t\tsupports EC2-Classic, see \"I really want a default VPC for my existing EC2 account. Is\n\t\t\tthat possible?\" in the Default VPCs\n\t\t\tFAQ.

" + "smithy.api#documentation": "

Creates a default VPC with a size /16 IPv4 CIDR block and a default subnet\n\t\t\tin each Availability Zone. For more information about the components of a default VPC,\n\t\t\tsee Default VPC and\n\t\t\tdefault subnets in the Amazon Virtual Private Cloud User Guide. You cannot\n\t\t\tspecify the components of the default VPC yourself.

\n\t\t

If you deleted your previous default VPC, you can create a default VPC. You cannot have\n\t\t\tmore than one default VPC per Region.

\n\t\t

If your account supports EC2-Classic, you cannot use this action to create a default VPC\n\t\t\tin a Region that supports EC2-Classic. If you want a default VPC in a Region that\n\t\t\tsupports EC2-Classic, see \"I really want a default VPC for my existing EC2 account. Is\n\t\t\tthat possible?\" in the Default VPCs\n\t\t\tFAQ.

\n\t \n\t

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n\t " } }, "com.amazonaws.ec2#CreateDefaultVpcRequest": { @@ -19505,7 +19505,7 @@ "target": "com.amazonaws.ec2#DescribeAddressesResult" }, "traits": { - "smithy.api#documentation": "

Describes the specified Elastic IP addresses or all of your Elastic IP addresses.

\n

An Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.

" + "smithy.api#documentation": "

Describes the specified Elastic IP addresses or all of your Elastic IP addresses.

\n

An Elastic IP address is for use in either the EC2-Classic platform or in a VPC.\n\t\t\t\tFor more information, see Elastic IP Addresses in the Amazon Elastic Compute Cloud User Guide.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#DescribeAddressesAttribute": { @@ -20145,7 +20145,7 @@ "target": "com.amazonaws.ec2#DescribeClassicLinkInstancesResult" }, "traits": { - "smithy.api#documentation": "

Describes one or more of your linked EC2-Classic instances. This request only returns\n\t\t\tinformation about EC2-Classic instances linked to a VPC through ClassicLink. You cannot\n\t\t\tuse this request to return information about other instances.

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

Describes one or more of your linked EC2-Classic instances. This request only returns\n\t\t\tinformation about EC2-Classic instances linked to a VPC through ClassicLink. You cannot\n\t\t\tuse this request to return information about other instances.

\n\t \n\t

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n\t ", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -23550,7 +23550,7 @@ "target": "com.amazonaws.ec2#DescribeInstancesResult" }, "traits": { - "smithy.api#documentation": "

Describes the specified instances or all instances.

\n

If you specify instance IDs, the output includes information for only the specified\n instances. If you specify filters, the output includes information for only those\n instances that meet the filter criteria. If you do not specify instance IDs or filters,\n the output includes information for all instances, which can affect performance. We\n recommend that you use pagination to ensure that the operation returns quickly and\n successfully.

\n

If you specify an instance ID that is not valid, an error is returned. If you specify\n an instance that you do not own, it is not included in the output.

\n

Recently terminated instances might appear in the returned results. This interval is\n usually less than one hour.

\n

If you describe instances in the rare case where an Availability Zone is experiencing\n a service disruption and you specify instance IDs that are in the affected zone, or do\n not specify any instance IDs at all, the call fails. If you describe instances and\n specify only instance IDs that are in an unaffected zone, the call works\n normally.

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

Describes the specified instances or all instances.

\n

If you specify instance IDs, the output includes information for only the specified\n instances. If you specify filters, the output includes information for only those\n instances that meet the filter criteria. If you do not specify instance IDs or filters,\n the output includes information for all instances, which can affect performance. We\n recommend that you use pagination to ensure that the operation returns quickly and\n successfully.

\n

If you specify an instance ID that is not valid, an error is returned. If you specify\n an instance that you do not own, it is not included in the output.

\n

Recently terminated instances might appear in the returned results. This interval is\n usually less than one hour.

\n

If you describe instances in the rare case where an Availability Zone is experiencing\n a service disruption and you specify instance IDs that are in the affected zone, or do\n not specify any instance IDs at all, the call fails. If you describe instances and\n specify only instance IDs that are in an unaffected zone, the call works\n normally.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide.

\n ", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -26418,7 +26418,7 @@ "target": "com.amazonaws.ec2#DescribeReservedInstancesResult" }, "traits": { - "smithy.api#documentation": "

Describes one or more of the Reserved Instances that you purchased.

\n

For more information about Reserved Instances, see Reserved\n\t\t\t\tInstances in the Amazon EC2 User Guide.

" + "smithy.api#documentation": "

Describes one or more of the Reserved Instances that you purchased.

\n

For more information about Reserved Instances, see Reserved\n\t\t\t\tInstances in the Amazon EC2 User Guide.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#DescribeReservedInstancesListings": { @@ -26489,7 +26489,7 @@ "target": "com.amazonaws.ec2#DescribeReservedInstancesModificationsResult" }, "traits": { - "smithy.api#documentation": "

Describes the modifications made to your Reserved Instances. If no parameter is specified, information about all your Reserved Instances modification requests is returned. If a modification ID is specified, only information about the specific modification is returned.

\n \t

For more information, see Modifying Reserved Instances in the Amazon EC2 User Guide.

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

Describes the modifications made to your Reserved Instances. If no parameter is specified, information about all your Reserved Instances modification requests is returned. If a modification ID is specified, only information about the specific modification is returned.

\n \t

For more information, see Modifying Reserved Instances in the Amazon EC2 User Guide.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n ", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -26560,7 +26560,7 @@ "target": "com.amazonaws.ec2#DescribeReservedInstancesOfferingsResult" }, "traits": { - "smithy.api#documentation": "

Describes Reserved Instance offerings that are available for purchase. With Reserved Instances, you purchase the right to launch instances for a period of time. During that time period, you do not receive insufficient capacity errors, and you pay a lower usage rate than the rate charged for On-Demand instances for the actual time used.

\n

If you have listed your own Reserved Instances for sale in the Reserved Instance Marketplace, they will be excluded from these results. This is to ensure that you do not purchase your own Reserved Instances.

\n

For more information, see Reserved Instance Marketplace\n\t\t\t\tin the Amazon EC2 User Guide.

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

Describes Reserved Instance offerings that are available for purchase. With Reserved Instances, you purchase the right to launch instances for a period of time. During that time period, you do not receive insufficient capacity errors, and you pay a lower usage rate than the rate charged for On-Demand instances for the actual time used.

\n

If you have listed your own Reserved Instances for sale in the Reserved Instance Marketplace, they will be excluded from these results. This is to ensure that you do not purchase your own Reserved Instances.

\n

For more information, see Reserved Instance Marketplace\n\t\t\t\tin the Amazon EC2 User Guide.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n ", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -26862,7 +26862,7 @@ "target": "com.amazonaws.ec2#DescribeScheduledInstanceAvailabilityResult" }, "traits": { - "smithy.api#documentation": "

Finds available schedules that meet the specified criteria.

\n

You can search for an available schedule no more than 3 months in advance. You must meet the minimum required duration of 1,200 hours per year. For example, the minimum daily schedule is 4 hours, the minimum weekly schedule is 24 hours, and the minimum monthly schedule is 100 hours.

\n

After you find a schedule that meets your needs, call PurchaseScheduledInstances\n to purchase Scheduled Instances with that schedule.

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

Finds available schedules that meet the specified criteria.

\n

You can search for an available schedule no more than 3 months in advance. You must meet the minimum required duration of 1,200 hours per year. For example, the minimum daily schedule is 4 hours, the minimum weekly schedule is 24 hours, and the minimum monthly schedule is 100 hours.

\n

After you find a schedule that meets your needs, call PurchaseScheduledInstances\n to purchase Scheduled Instances with that schedule.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n ", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -26972,7 +26972,7 @@ "target": "com.amazonaws.ec2#DescribeScheduledInstancesResult" }, "traits": { - "smithy.api#documentation": "

Describes the specified Scheduled Instances or all your Scheduled Instances.

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

Describes the specified Scheduled Instances or all your Scheduled Instances.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n ", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -30058,7 +30058,7 @@ "target": "com.amazonaws.ec2#DescribeVpcClassicLinkResult" }, "traits": { - "smithy.api#documentation": "

Describes the ClassicLink status of one or more VPCs.

" + "smithy.api#documentation": "

Describes the ClassicLink status of one or more VPCs.

\n\t \n\t

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n\t " } }, "com.amazonaws.ec2#DescribeVpcClassicLinkDnsSupport": { @@ -30070,7 +30070,7 @@ "target": "com.amazonaws.ec2#DescribeVpcClassicLinkDnsSupportResult" }, "traits": { - "smithy.api#documentation": "

Describes the ClassicLink DNS support status of one or more VPCs. If enabled, the DNS\n hostname of a linked EC2-Classic instance resolves to its private IP address when\n addressed from an instance in the VPC to which it's linked. Similarly, the DNS hostname\n of an instance in a VPC resolves to its private IP address when addressed from a linked\n EC2-Classic instance. For more information, see ClassicLink in the Amazon Elastic Compute Cloud User Guide.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

Describes the ClassicLink DNS support status of one or more VPCs. If enabled, the DNS\n hostname of a linked EC2-Classic instance resolves to its private IP address when\n addressed from an instance in the VPC to which it's linked. Similarly, the DNS hostname\n of an instance in a VPC resolves to its private IP address when addressed from a linked\n EC2-Classic instance. For more information, see ClassicLink in the Amazon Elastic Compute Cloud User Guide.

", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -31162,7 +31162,7 @@ "target": "com.amazonaws.ec2#DetachClassicLinkVpcResult" }, "traits": { - "smithy.api#documentation": "

Unlinks (detaches) a linked EC2-Classic instance from a VPC. After the instance has been unlinked, the VPC security groups are no longer associated with it. An instance is automatically unlinked from a VPC when it's stopped.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n\t \n\t\t

Unlinks (detaches) a linked EC2-Classic instance from a VPC. After the instance has been unlinked, the VPC security groups are no longer associated with it. An instance is automatically unlinked from a VPC when it's stopped.

" } }, "com.amazonaws.ec2#DetachClassicLinkVpcRequest": { @@ -32167,7 +32167,7 @@ "target": "com.amazonaws.ec2#DisableVpcClassicLinkResult" }, "traits": { - "smithy.api#documentation": "

Disables ClassicLink for a VPC. You cannot disable ClassicLink for a VPC that has EC2-Classic instances linked to it.

" + "smithy.api#documentation": "

Disables ClassicLink for a VPC. You cannot disable ClassicLink for a VPC that has EC2-Classic instances linked to it.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#DisableVpcClassicLinkDnsSupport": { @@ -32179,7 +32179,7 @@ "target": "com.amazonaws.ec2#DisableVpcClassicLinkDnsSupportResult" }, "traits": { - "smithy.api#documentation": "

Disables ClassicLink DNS support for a VPC. If disabled, DNS hostnames resolve to\n\t\t\tpublic IP addresses when addressed between a linked EC2-Classic instance and instances\n\t\t\tin the VPC to which it's linked. For more information, see ClassicLink in the\n\t\t\t\tAmazon Elastic Compute Cloud User Guide.

\n

You must specify a VPC ID in the request.

" + "smithy.api#documentation": "

Disables ClassicLink DNS support for a VPC. If disabled, DNS hostnames resolve to\n\t\t\tpublic IP addresses when addressed between a linked EC2-Classic instance and instances\n\t\t\tin the VPC to which it's linked. For more information, see ClassicLink in the\n\t\t\t\tAmazon Elastic Compute Cloud User Guide.

\n

You must specify a VPC ID in the request.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#DisableVpcClassicLinkDnsSupportRequest": { @@ -32251,7 +32251,7 @@ "target": "smithy.api#Unit" }, "traits": { - "smithy.api#documentation": "

Disassociates an Elastic IP address from the instance or network interface it's associated with.

\n\t\t\t

An Elastic IP address is for use in either the EC2-Classic platform or in a VPC. For more\n\t\t\tinformation, see Elastic IP\n\t\t\t\tAddresses in the Amazon Elastic Compute Cloud User Guide.

\n

This is an idempotent operation. If you perform the operation more than once, Amazon EC2 doesn't return an error.

" + "smithy.api#documentation": "

Disassociates an Elastic IP address from the instance or network interface it's associated with.

\n\t\t\t

An Elastic IP address is for use in either the EC2-Classic platform or in a VPC. For more\n\t\t\tinformation, see Elastic IP\n\t\t\t\tAddresses in the Amazon Elastic Compute Cloud User Guide.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

This is an idempotent operation. If you perform the operation more than once, Amazon EC2 doesn't return an error.

" } }, "com.amazonaws.ec2#DisassociateAddressRequest": { @@ -34620,7 +34620,7 @@ "target": "com.amazonaws.ec2#EnableVpcClassicLinkResult" }, "traits": { - "smithy.api#documentation": "

Enables a VPC for ClassicLink. You can then link EC2-Classic instances to your\n\t\t\tClassicLink-enabled VPC to allow communication over private IP addresses. You cannot\n\t\t\tenable your VPC for ClassicLink if any of your VPC route tables have existing routes for\n\t\t\taddress ranges within the 10.0.0.0/8 IP address range, excluding local\n\t\t\troutes for VPCs in the 10.0.0.0/16 and 10.1.0.0/16 IP address\n\t\t\tranges. For more information, see ClassicLink in the\n\t\t\t\tAmazon Elastic Compute Cloud User Guide.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

Enables a VPC for ClassicLink. You can then link EC2-Classic instances to your\n\t\t\tClassicLink-enabled VPC to allow communication over private IP addresses. You cannot\n\t\t\tenable your VPC for ClassicLink if any of your VPC route tables have existing routes for\n\t\t\taddress ranges within the 10.0.0.0/8 IP address range, excluding local\n\t\t\troutes for VPCs in the 10.0.0.0/16 and 10.1.0.0/16 IP address\n\t\t\tranges. For more information, see ClassicLink in the\n\t\t\t\tAmazon Elastic Compute Cloud User Guide.

" } }, "com.amazonaws.ec2#EnableVpcClassicLinkDnsSupport": { @@ -34632,7 +34632,7 @@ "target": "com.amazonaws.ec2#EnableVpcClassicLinkDnsSupportResult" }, "traits": { - "smithy.api#documentation": "

Enables a VPC to support DNS hostname resolution for ClassicLink. If enabled, the DNS\n\t\t\thostname of a linked EC2-Classic instance resolves to its private IP address when\n\t\t\taddressed from an instance in the VPC to which it's linked. Similarly, the DNS hostname\n\t\t\tof an instance in a VPC resolves to its private IP address when addressed from a linked\n\t\t\tEC2-Classic instance. For more information, see ClassicLink in the\n\t\t\t\tAmazon Elastic Compute Cloud User Guide.

\n

You must specify a VPC ID in the request.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

Enables a VPC to support DNS hostname resolution for ClassicLink. If enabled, the DNS\n\t\t\thostname of a linked EC2-Classic instance resolves to its private IP address when\n\t\t\taddressed from an instance in the VPC to which it's linked. Similarly, the DNS hostname\n\t\t\tof an instance in a VPC resolves to its private IP address when addressed from a linked\n\t\t\tEC2-Classic instance. For more information, see ClassicLink in the\n\t\t\t\tAmazon Elastic Compute Cloud User Guide.

\n

You must specify a VPC ID in the request.

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

Describes the launch specification for an instance.

" + "smithy.api#documentation": "

Describes the launch specification for an instance.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide for Linux Instances.

\n " } }, "com.amazonaws.ec2#LaunchSpecsList": { @@ -52632,7 +52632,7 @@ "Version": { "target": "com.amazonaws.ec2#String", "traits": { - "smithy.api#documentation": "

The version number of the launch template.

\n

Default: The default version for the launch template.

" + "smithy.api#documentation": "

The launch template version number, $Latest, or $Default.

\n

If the value is $Latest, Amazon EC2 uses the latest version of the launch\n template.

\n

If the value is $Default, Amazon EC2 uses the default version of the launch\n template.

\n

Default: The default version of the launch template.

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

Modifies the Availability Zone, instance count, instance type, or network platform\n (EC2-Classic or EC2-VPC) of your Reserved Instances. The Reserved Instances to be\n modified must be identical, except for Availability Zone, network platform, and instance\n type.

\n\t\t

For more information, see Modifying Reserved\n\t\t\t\tInstances in the Amazon EC2 User Guide.

" + "smithy.api#documentation": "

Modifies the Availability Zone, instance count, instance type, or network platform\n (EC2-Classic or EC2-VPC) of your Reserved Instances. The Reserved Instances to be\n modified must be identical, except for Availability Zone, network platform, and instance\n type.

\n\t\t

For more information, see Modifying Reserved\n\t\t\t\tInstances in the Amazon EC2 User Guide.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#ModifyReservedInstancesRequest": { @@ -57727,7 +57727,7 @@ "target": "com.amazonaws.ec2#ModifyVpcPeeringConnectionOptionsResult" }, "traits": { - "smithy.api#documentation": "

Modifies the VPC peering connection options on one side of a VPC peering connection. You can do the following:

\n \n

If the peered VPCs are in the same Amazon Web Services account, you can enable DNS resolution \n for queries from the local VPC. This ensures that queries from the local VPC resolve to private IP\n addresses in the peer VPC. This option is not available if the peered VPCs are in different\n different Amazon Web Services accounts or different Regions. For peered VPCs in different \n Amazon Web Services accounts, each Amazon Web Services account owner must initiate a separate request \n to modify the peering connection options. For inter-region peering connections, you must use the \n Region for the requester VPC to modify the requester VPC peering options and the Region for the \n accepter VPC to modify the accepter VPC peering options. To verify which VPCs are the accepter and \n the requester for a VPC peering connection, use the DescribeVpcPeeringConnections command.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

Modifies the VPC peering connection options on one side of a VPC peering connection. You can do the following:

\n \n

If the peered VPCs are in the same Amazon Web Services account, you can enable DNS resolution \n for queries from the local VPC. This ensures that queries from the local VPC resolve to private IP\n addresses in the peer VPC. This option is not available if the peered VPCs are in different\n different Amazon Web Services accounts or different Regions. For peered VPCs in different \n Amazon Web Services accounts, each Amazon Web Services account owner must initiate a separate request \n to modify the peering connection options. For inter-region peering connections, you must use the \n Region for the requester VPC to modify the requester VPC peering options and the Region for the \n accepter VPC to modify the accepter VPC peering options. To verify which VPCs are the accepter and \n the requester for a VPC peering connection, use the DescribeVpcPeeringConnections command.

" } }, "com.amazonaws.ec2#ModifyVpcPeeringConnectionOptionsRequest": { @@ -58279,7 +58279,7 @@ "target": "com.amazonaws.ec2#MoveAddressToVpcResult" }, "traits": { - "smithy.api#documentation": "

Moves an Elastic IP address from the EC2-Classic platform to the EC2-VPC platform. The\n Elastic IP address must be allocated to your account for more than 24 hours, and it must not\n be associated with an instance. After the Elastic IP address is moved, it is no longer\n available for use in the EC2-Classic platform, unless you move it back using the\n RestoreAddressToClassic request. You cannot move an Elastic IP address that was\n originally allocated for use in the EC2-VPC platform to the EC2-Classic platform.

" + "smithy.api#documentation": "

Moves an Elastic IP address from the EC2-Classic platform to the EC2-VPC platform. The\n Elastic IP address must be allocated to your account for more than 24 hours, and it must not\n be associated with an instance. After the Elastic IP address is moved, it is no longer\n available for use in the EC2-Classic platform, unless you move it back using the\n RestoreAddressToClassic request. You cannot move an Elastic IP address that was\n originally allocated for use in the EC2-VPC platform to the EC2-Classic platform.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#MoveAddressToVpcRequest": { @@ -58417,7 +58417,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes the status of a moving Elastic IP address.

" + "smithy.api#documentation": "

Describes the status of a moving Elastic IP address.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#MovingAddressStatusSet": { @@ -60983,7 +60983,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes the VPC peering connection options.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

Describes the VPC peering connection options.

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

The VPC peering connection options.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

The VPC peering connection options.

" } }, "com.amazonaws.ec2#PeeringTgwInfo": { @@ -64053,7 +64053,7 @@ "target": "smithy.api#Unit" }, "traits": { - "smithy.api#documentation": "

Releases the specified Elastic IP address.

\n

[EC2-Classic, default VPC] Releasing an Elastic IP address automatically disassociates it\n\t\t\t\tfrom any instance that it's associated with. To disassociate an Elastic IP address without\n\t\t\t\treleasing it, use DisassociateAddress.

\n

[Nondefault VPC] You must use DisassociateAddress to disassociate the Elastic IP address\n\t\t\t before you can release it. Otherwise, Amazon EC2 returns an error (InvalidIPAddress.InUse).

\n

After releasing an Elastic IP address, it is released to the IP address pool. \n Be sure to update your DNS records and any servers or devices that communicate with the address. \n If you attempt to release an Elastic IP address that you already released, you'll get an\n AuthFailure error if the address is already allocated to another Amazon Web Services account.

\n

[EC2-VPC] After you release an Elastic IP address for use in a VPC, you might be able to recover it.\n For more information, see AllocateAddress.

\n

For more\n information, see Elastic IP\n Addresses in the Amazon Elastic Compute Cloud User Guide.

" + "smithy.api#documentation": "

Releases the specified Elastic IP address.

\n

[EC2-Classic, default VPC] Releasing an Elastic IP address automatically disassociates it\n\t\t\t\tfrom any instance that it's associated with. To disassociate an Elastic IP address without\n\t\t\t\treleasing it, use DisassociateAddress.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

[Nondefault VPC] You must use DisassociateAddress to disassociate the Elastic IP address\n\t\t\t before you can release it. Otherwise, Amazon EC2 returns an error (InvalidIPAddress.InUse).

\n

After releasing an Elastic IP address, it is released to the IP address pool. \n Be sure to update your DNS records and any servers or devices that communicate with the address. \n If you attempt to release an Elastic IP address that you already released, you'll get an\n AuthFailure error if the address is already allocated to another Amazon Web Services account.

\n

[EC2-VPC] After you release an Elastic IP address for use in a VPC, you might be able to recover it.\n For more information, see AllocateAddress.

\n

For more\n information, see Elastic IP\n Addresses in the Amazon Elastic Compute Cloud User Guide.

" } }, "com.amazonaws.ec2#ReleaseAddressRequest": { @@ -65291,7 +65291,7 @@ "target": "com.amazonaws.ec2#RequestSpotInstancesResult" }, "traits": { - "smithy.api#documentation": "

Creates a Spot Instance request.

\n

For more information, see Spot Instance requests in\n the Amazon EC2 User Guide for Linux Instances.

\n \n \n

We strongly discourage using the RequestSpotInstances API because it is a legacy\n API with no planned investment. For options for requesting Spot Instances, see\n Which\n is the best Spot request method to use? in the\n Amazon EC2 User Guide for Linux Instances.

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

Creates a Spot Instance request.

\n

For more information, see Spot Instance requests in\n the Amazon EC2 User Guide for Linux Instances.

\n \n \n

We strongly discourage using the RequestSpotInstances API because it is a legacy\n API with no planned investment. For options for requesting Spot Instances, see\n Which\n is the best Spot request method to use? in the\n Amazon EC2 User Guide for Linux Instances.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide for Linux Instances.

\n " } }, "com.amazonaws.ec2#RequestSpotInstancesRequest": { @@ -65613,7 +65613,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes a launch request for one or more instances, and includes owner, requester,\n and security group information that applies to all instances in the launch\n request.

" + "smithy.api#documentation": "

Describes a launch request for one or more instances, and includes owner, requester,\n and security group information that applies to all instances in the launch\n request.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide.

\n " } }, "com.amazonaws.ec2#ReservationFleetInstanceSpecification": { @@ -66033,7 +66033,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes the configuration settings for the modified Reserved Instances.

" + "smithy.api#documentation": "

Describes the configuration settings for the modified Reserved Instances.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#ReservedInstancesConfigurationList": { @@ -67147,6 +67147,18 @@ { "value": "vpc-flow-log", "name": "vpc_flow_log" + }, + { + "value": "capacity-reservation-fleet", + "name": "capacity_reservation_fleet" + }, + { + "value": "traffic-mirror-filter-rule", + "name": "traffic_mirror_filter_rule" + }, + { + "value": "vpc-endpoint-connection-device-type", + "name": "vpc_endpoint_connection_device_type" } ] } @@ -67464,7 +67476,7 @@ "target": "com.amazonaws.ec2#RestoreAddressToClassicResult" }, "traits": { - "smithy.api#documentation": "

Restores an Elastic IP address that was previously moved to the EC2-VPC platform back to the EC2-Classic platform. You cannot move an Elastic IP address that was originally allocated for use in EC2-VPC. The Elastic IP address must not be associated with an instance or network interface.

" + "smithy.api#documentation": "

Restores an Elastic IP address that was previously moved to the EC2-VPC platform back to the EC2-Classic platform. You cannot move an Elastic IP address that was originally allocated for use in EC2-VPC. The Elastic IP address must not be associated with an instance or network interface.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#RestoreAddressToClassicRequest": { @@ -68540,7 +68552,7 @@ "target": "com.amazonaws.ec2#Reservation" }, "traits": { - "smithy.api#documentation": "

Launches the specified number of instances using an AMI for which you have\n permissions.

\n

You can specify a number of options, or leave the default options. The following rules\n apply:

\n \n

You can create a launch template,\n which is a resource that contains the parameters to launch an instance. When you launch\n an instance using RunInstances, you can specify the launch template\n instead of specifying the launch parameters.

\n

To ensure faster instance launches, break up large requests into smaller batches. For\n example, create five separate launch requests for 100 instances each instead of one\n launch request for 500 instances.

\n

An instance is ready for you to use when it's in the running state. You\n can check the state of your instance using DescribeInstances. You can\n tag instances and EBS volumes during launch, after launch, or both. For more\n information, see CreateTags and Tagging your Amazon EC2\n resources.

\n

Linux instances have access to the public key of the key pair at boot. You can use\n this key to provide secure access to the instance. Amazon EC2 public images use this\n feature to provide secure access without passwords. For more information, see Key\n pairs.

\n

For troubleshooting, see What to do if\n an instance immediately terminates, and Troubleshooting connecting to your instance.

" + "smithy.api#documentation": "

Launches the specified number of instances using an AMI for which you have\n permissions.

\n

You can specify a number of options, or leave the default options. The following rules\n apply:

\n \n

You can create a launch template,\n which is a resource that contains the parameters to launch an instance. When you launch\n an instance using RunInstances, you can specify the launch template\n instead of specifying the launch parameters.

\n

To ensure faster instance launches, break up large requests into smaller batches. For\n example, create five separate launch requests for 100 instances each instead of one\n launch request for 500 instances.

\n

An instance is ready for you to use when it's in the running state. You\n can check the state of your instance using DescribeInstances. You can\n tag instances and EBS volumes during launch, after launch, or both. For more\n information, see CreateTags and Tagging your Amazon EC2\n resources.

\n

Linux instances have access to the public key of the key pair at boot. You can use\n this key to provide secure access to the instance. Amazon EC2 public images use this\n feature to provide secure access without passwords. For more information, see Key\n pairs.

\n

For troubleshooting, see What to do if\n an instance immediately terminates, and Troubleshooting connecting to your instance.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide.

\n " } }, "com.amazonaws.ec2#RunInstancesMonitoringEnabled": { @@ -69108,7 +69120,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes a Scheduled Instance.

" + "smithy.api#documentation": "

Describes a Scheduled Instance.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#ScheduledInstanceAvailability": { @@ -69220,7 +69232,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes a schedule that is available for your Scheduled Instances.

" + "smithy.api#documentation": "

Describes a schedule that is available for your Scheduled Instances.

\n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n " } }, "com.amazonaws.ec2#ScheduledInstanceAvailabilitySet": { @@ -71770,7 +71782,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes the launch specification for one or more Spot Instances. If you include\n On-Demand capacity in your fleet request or want to specify an EFA network device, you\n can't use SpotFleetLaunchSpecification; you must use LaunchTemplateConfig.

" + "smithy.api#documentation": "

Describes the launch specification for one or more Spot Instances. If you include\n On-Demand capacity in your fleet request or want to specify an EFA network device, you\n can't use SpotFleetLaunchSpecification; you must use LaunchTemplateConfig.

\n \n \n

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide for Linux Instances.

\n " } }, "com.amazonaws.ec2#SpotFleetMonitoring": { @@ -80367,7 +80379,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes whether a VPC is enabled for ClassicLink.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n\t \n\t\t

Describes whether a VPC is enabled for ClassicLink.

" } }, "com.amazonaws.ec2#VpcClassicLinkIdList": { @@ -80903,7 +80915,7 @@ } }, "traits": { - "smithy.api#documentation": "

Describes the VPC peering connection options.

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

We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see Migrate from EC2-Classic to a VPC in the Amazon Elastic Compute Cloud User Guide.

\n \n

Describes the VPC peering connection options.

" } }, "com.amazonaws.ec2#VpcPeeringConnectionStateReason": { diff --git a/codegen/sdk-codegen/aws-models/fsx.json b/codegen/sdk-codegen/aws-models/fsx.json index a30a82df47d..f477e31a8be 100644 --- a/codegen/sdk-codegen/aws-models/fsx.json +++ b/codegen/sdk-codegen/aws-models/fsx.json @@ -1308,7 +1308,7 @@ "Paths": { "target": "com.amazonaws.fsx#DataRepositoryTaskPaths", "traits": { - "smithy.api#documentation": "

(Optional) The path or paths on the Amazon FSx file system to use when the data repository task is processed. \n The default path is the file system root directory. The paths you provide need to be relative to the mount point of the file system. \n If the mount point is /mnt/fsx and /mnt/fsx/path1 is a directory or \n file on the file system you want to export, then the path to provide is path1.\n If a path that you provide isn't valid, the task fails.

" + "smithy.api#documentation": "

A list of paths for the data repository task to use when the task is processed.\n If a path that you provide isn't valid, the task fails.

\n " } }, "FileSystemId": { @@ -1677,7 +1677,7 @@ "CopyTagsToVolumes": { "target": "com.amazonaws.fsx#Flag", "traits": { - "smithy.api#documentation": "

A Boolean value indicating whether tags for the volume should be copied to snapshots.\n This value defaults to false. If it's set to true, all tags\n for the volume are copied to snapshots where the user doesn't specify tags. If this\n value is true, and you specify one or more tags, only the specified tags\n are copied to snapshots. If you specify one or more tags when creating the snapshot, no\n tags are copied from the volume, regardless of this value.

" + "smithy.api#documentation": "

A Boolean value indicating whether tags for the file system should be copied to volumes.\n This value defaults to false. If it's set to true, all tags\n for the file system are copied to volumes where the user doesn't specify tags. If this\n value is true, and you specify one or more tags, only the specified tags\n are copied to volumes. If you specify one or more tags when creating the volume, no\n tags are copied from the file system, regardless of this value.

" } }, "DailyAutomaticBackupStartTime": { @@ -5113,7 +5113,7 @@ } ], "traits": { - "smithy.api#documentation": "

Lists tags for an Amazon FSx file systems and backups in the case of Amazon FSx for\n Windows File Server.

\n\n

When retrieving all tags, you can optionally specify the MaxResults\n parameter to limit the number of tags in a response. If more tags remain, Amazon FSx\n returns a NextToken value in the response. In this case, send a later\n request with the NextToken request parameter set to the value of\n NextToken from the last response.

\n\n

This action is used in an iterative process to retrieve a list of your tags.\n ListTagsForResource is called first without a\n NextTokenvalue. Then the action continues to be called with the\n NextToken parameter set to the value of the last NextToken\n value until a response has no NextToken.

\n\n

When using this action, keep the following in mind:

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

Lists tags for Amazon FSx resources.

\n\n

When retrieving all tags, you can optionally specify the MaxResults\n parameter to limit the number of tags in a response. If more tags remain, Amazon FSx\n returns a NextToken value in the response. In this case, send a later\n request with the NextToken request parameter set to the value of\n NextToken from the last response.

\n\n

This action is used in an iterative process to retrieve a list of your tags.\n ListTagsForResource is called first without a\n NextTokenvalue. Then the action continues to be called with the\n NextToken parameter set to the value of the last NextToken\n value until a response has no NextToken.

\n\n

When using this action, keep the following in mind:

\n ", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", diff --git a/codegen/sdk-codegen/aws-models/shield.json b/codegen/sdk-codegen/aws-models/shield.json index 7dab9f0c7df..38d2908adb5 100644 --- a/codegen/sdk-codegen/aws-models/shield.json +++ b/codegen/sdk-codegen/aws-models/shield.json @@ -43,7 +43,7 @@ "name": "shield" }, "aws.protocols#awsJson1_1": {}, - "smithy.api#documentation": "Shield Advanced\n

This is the Shield Advanced API Reference. This guide is for developers who need detailed information about the Shield Advanced API actions, \n data types, and errors. For detailed information about WAF and Shield Advanced features and an overview of how to use the WAF and Shield Advanced APIs, see the \n WAF and Shield Developer Guide.

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

This is the Shield Advanced API Reference. This guide is for developers who need detailed information about the Shield Advanced API actions,\n data types, and errors. For detailed information about WAF and Shield Advanced features and an overview of how to use the WAF and Shield Advanced APIs, see the\n WAF and Shield Developer Guide.

", "smithy.api#title": "AWS Shield", "smithy.api#xmlNamespace": { "uri": "http://ddp.amazonaws.com/doc/2016-06-02/" @@ -198,12 +198,13 @@ "Action": { "target": "com.amazonaws.shield#ResponseAction", "traits": { + "smithy.api#documentation": "

Specifies the action setting that Shield Advanced should use in the WAF rules that it creates on behalf of the\n protected resource in response to DDoS attacks. You specify this as part of the configuration for the automatic application layer DDoS mitigation feature,\n when you enable or update automatic mitigation. Shield Advanced creates the WAF rules in a Shield Advanced-managed rule group, inside the web ACL that you have associated with the resource.

", "smithy.api#required": {} } } }, "traits": { - "smithy.api#documentation": "

The automatic application layer DDoS mitigation settings for a Protection. \n This configuration determines whether Shield Advanced automatically \n manages rules in the web ACL in order to respond to application layer events that Shield Advanced determines to be DDoS attacks.

" + "smithy.api#documentation": "

The automatic application layer DDoS mitigation settings for a Protection.\n This configuration determines whether Shield Advanced automatically\n manages rules in the web ACL in order to respond to application layer events that Shield Advanced determines to be DDoS attacks.

" } }, "com.amazonaws.shield#ApplicationLayerAutomaticResponseStatus": { @@ -256,7 +257,7 @@ } ], "traits": { - "smithy.api#documentation": "

Authorizes the Shield Response Team (SRT) to access the specified Amazon S3 bucket containing log data such as Application Load Balancer access logs, CloudFront logs, or logs from third party sources. You can associate up to 10 Amazon S3 buckets with your subscription.

\n

To use the services of the SRT and make an AssociateDRTLogBucket request, you must be subscribed to the Business Support plan or the Enterprise Support plan.

" + "smithy.api#documentation": "

Authorizes the Shield Response Team (SRT) to access the specified Amazon S3 bucket containing log data such as Application Load Balancer access logs, CloudFront logs, or logs from third party sources. You can associate up to 10 Amazon S3 buckets with your subscription.

\n

To use the services of the SRT and make an AssociateDRTLogBucket request, you must be subscribed to the Business Support plan or the Enterprise Support plan.

" } }, "com.amazonaws.shield#AssociateDRTLogBucketRequest": { @@ -304,7 +305,7 @@ } ], "traits": { - "smithy.api#documentation": "

Authorizes the Shield Response Team (SRT) using the specified role, to access your Amazon Web Services account to assist with DDoS attack mitigation during potential attacks. This enables the SRT to inspect your WAF configuration and create or update WAF rules and web ACLs.

\n

You can associate only one RoleArn with your subscription. If you submit an AssociateDRTRole request for an account that already has an associated role, the new RoleArn will replace the existing RoleArn.

\n

Prior to making the AssociateDRTRole request, you must attach the AWSShieldDRTAccessPolicy managed policy to the role that you'll specify in the request. You can access this policy in the IAM console at AWSShieldDRTAccessPolicy. For more information see Adding and removing IAM identity permissions. The role must also trust the service principal \ndrt.shield.amazonaws.com. For more information, see IAM JSON policy elements: Principal.

\n\n

The SRT will have access only to your WAF and Shield resources. By submitting this request, you authorize the SRT to inspect your WAF and Shield configuration and create and update WAF rules and web ACLs on your behalf. The SRT takes these actions only if explicitly authorized by you.

\n

You must have the iam:PassRole permission to make an AssociateDRTRole request. For more information, see Granting a user permissions to pass a role to an Amazon Web Services service.

\n

To use the services of the SRT and make an AssociateDRTRole request, you must be subscribed to the Business Support plan or the Enterprise Support plan.

" + "smithy.api#documentation": "

Authorizes the Shield Response Team (SRT) using the specified role, to access your Amazon Web Services account to assist with DDoS attack mitigation during potential attacks. This enables the SRT to inspect your WAF configuration and create or update WAF rules and web ACLs.

\n

You can associate only one RoleArn with your subscription. If you submit an AssociateDRTRole request for an account that already has an associated role, the new RoleArn will replace the existing RoleArn.

\n

Prior to making the AssociateDRTRole request, you must attach the AWSShieldDRTAccessPolicy managed policy to the role that you'll specify in the request. You can access this policy in the IAM console at AWSShieldDRTAccessPolicy. For more information see Adding and removing IAM identity permissions. The role must also trust the service principal\ndrt.shield.amazonaws.com. For more information, see IAM JSON policy elements: Principal.

\n\n

The SRT will have access only to your WAF and Shield resources. By submitting this request, you authorize the SRT to inspect your WAF and Shield configuration and create and update WAF rules and web ACLs on your behalf. The SRT takes these actions only if explicitly authorized by you.

\n

You must have the iam:PassRole permission to make an AssociateDRTRole request. For more information, see Granting a user permissions to pass a role to an Amazon Web Services service.

\n

To use the services of the SRT and make an AssociateDRTRole request, you must be subscribed to the Business Support plan or the Enterprise Support plan.

" } }, "com.amazonaws.shield#AssociateDRTRoleRequest": { @@ -465,7 +466,7 @@ "AttackProperties": { "target": "com.amazonaws.shield#AttackProperties", "traits": { - "smithy.api#documentation": "

The array of objects that provide details of the Shield event.

\n

For infrastructure \n layer events (L3 and L4 events), you can view metrics for top contributors in Amazon CloudWatch metrics. \n For more information, see Shield metrics and alarms \n in the WAF Developer Guide.

" + "smithy.api#documentation": "

The array of objects that provide details of the Shield event.

\n

For infrastructure\n layer events (L3 and L4 events), you can view metrics for top contributors in Amazon CloudWatch metrics.\n For more information, see Shield metrics and alarms\n in the WAF Developer Guide.

" } }, "Mitigations": { @@ -516,7 +517,7 @@ "AttackLayer": { "target": "com.amazonaws.shield#AttackLayer", "traits": { - "smithy.api#documentation": "

The type of Shield event that was observed. NETWORK indicates layer 3 and layer 4 events and APPLICATION\n indicates layer 7 events.

\n

For infrastructure \n layer events (L3 and L4 events), you can view metrics for top contributors in Amazon CloudWatch metrics. \n For more information, see Shield metrics and alarms \n in the WAF Developer Guide.

" + "smithy.api#documentation": "

The type of Shield event that was observed. NETWORK indicates layer 3 and layer 4 events and APPLICATION\n indicates layer 7 events.

\n

For infrastructure\n layer events (L3 and L4 events), you can view metrics for top contributors in Amazon CloudWatch metrics.\n For more information, see Shield metrics and alarms\n in the WAF Developer Guide.

" } }, "AttackPropertyIdentifier": { @@ -817,7 +818,7 @@ } ], "traits": { - "smithy.api#documentation": "

Enables Shield Advanced for a specific Amazon Web Services resource. The resource can be an Amazon CloudFront distribution, Elastic Load Balancing load balancer, Global Accelerator accelerator, Elastic IP Address, or an Amazon Route 53 hosted zone.

\n

You can add protection to only a single resource with each CreateProtection request. You can add protection to multiple resources \n at once through the Shield Advanced console at https://console.aws.amazon.com/wafv2/shieldv2#/.\n For more information see \n Getting Started with Shield Advanced \n and Adding Shield Advanced protection to Amazon Web Services resources.

" + "smithy.api#documentation": "

Enables Shield Advanced for a specific Amazon Web Services resource. The resource can be an Amazon CloudFront distribution, Amazon Route 53 hosted zone, Global Accelerator standard accelerator, Elastic IP Address, Application Load Balancer, or a Classic Load Balancer. You can protect Amazon EC2 instances and Network Load Balancers by association with protected Amazon EC2 Elastic IP addresses.

\n

You can add protection to only a single resource with each CreateProtection request. You can add protection to multiple resources\n at once through the Shield Advanced console at https://console.aws.amazon.com/wafv2/shieldv2#/.\n For more information see\n Getting Started with Shield Advanced\n and Adding Shield Advanced protection to Amazon Web Services resources.

" } }, "com.amazonaws.shield#CreateProtectionGroup": { @@ -879,7 +880,7 @@ "ResourceType": { "target": "com.amazonaws.shield#ProtectedResourceType", "traits": { - "smithy.api#documentation": "

The resource type to include in the protection group. All protected resources of this type are included in the protection group. Newly protected resources of this type are automatically added to the group. \n You must set this when you set Pattern to BY_RESOURCE_TYPE and you must not set it for any other Pattern setting.

" + "smithy.api#documentation": "

The resource type to include in the protection group. All protected resources of this type are included in the protection group. Newly protected resources of this type are automatically added to the group.\n You must set this when you set Pattern to BY_RESOURCE_TYPE and you must not set it for any other Pattern setting.

" } }, "Members": { @@ -913,7 +914,7 @@ "ResourceArn": { "target": "com.amazonaws.shield#ResourceArn", "traits": { - "smithy.api#documentation": "

The ARN (Amazon Resource Name) of the resource to be protected.

\n

The ARN should be in one of the following formats:

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

The ARN (Amazon Resource Name) of the resource to be protected.

\n

The ARN should be in one of the following formats:

\n ", "smithy.api#required": {} } }, @@ -953,7 +954,7 @@ } ], "traits": { - "smithy.api#documentation": "

Activates Shield Advanced for an account.

\n \n

When you initally create a subscription, your subscription is set to be automatically renewed at the end of the existing subscription period. You can change this by submitting an UpdateSubscription request.

" + "smithy.api#documentation": "

Activates Shield Advanced for an account.

\n \n

For accounts that are members of an Organizations organization, Shield Advanced subscriptions are billed against the organization's payer account,\n regardless of whether the payer account itself is subscribed.

\n \n

When you initially create a subscription, your subscription is set to be automatically renewed at the end of the existing subscription period. You can change this by submitting an UpdateSubscription request.

" } }, "com.amazonaws.shield#CreateSubscriptionRequest": { @@ -1118,7 +1119,7 @@ "Attack": { "target": "com.amazonaws.shield#AttackDetail", "traits": { - "smithy.api#documentation": "

The attack that is described.

" + "smithy.api#documentation": "

The attack that you requested.

" } } } @@ -1150,6 +1151,7 @@ "TimeRange": { "target": "com.amazonaws.shield#TimeRange", "traits": { + "smithy.api#documentation": "

The time range of the attack.

", "smithy.api#required": {} } }, @@ -1311,13 +1313,13 @@ "ProtectionId": { "target": "com.amazonaws.shield#ProtectionId", "traits": { - "smithy.api#documentation": "

The unique identifier (ID) for the Protection object that is\n described. When submitting the DescribeProtection request you must provide either the ResourceArn or the ProtectionID, but not both.

" + "smithy.api#documentation": "

The unique identifier (ID) for the Protection object to describe. \n You must provide either the ResourceArn of the protected resource or the ProtectionID of the protection, but not both.

" } }, "ResourceArn": { "target": "com.amazonaws.shield#ResourceArn", "traits": { - "smithy.api#documentation": "

The ARN (Amazon Resource Name) of the Amazon Web Services resource for the Protection object that is\n described. When submitting the DescribeProtection request you must provide either the ResourceArn or the ProtectionID, but not both.

" + "smithy.api#documentation": "

The ARN (Amazon Resource Name) of the protected Amazon Web Services resource. \n You must provide either the ResourceArn of the protected resource or the ProtectionID of the protection, but not both.

" } } } @@ -1328,7 +1330,7 @@ "Protection": { "target": "com.amazonaws.shield#Protection", "traits": { - "smithy.api#documentation": "

The Protection object that is described.

" + "smithy.api#documentation": "

The Protection that you requested.

" } } } @@ -1394,7 +1396,7 @@ } ], "traits": { - "smithy.api#documentation": "

Disable the Shield Advanced automatic application layer DDoS mitigation feature for the resource. This \n stops Shield Advanced from creating, verifying, and applying WAF rules for attacks that it detects for the resource.

" + "smithy.api#documentation": "

Disable the Shield Advanced automatic application layer DDoS mitigation feature for the protected resource. This\n stops Shield Advanced from creating, verifying, and applying WAF rules for attacks that it detects for the resource.

" } }, "com.amazonaws.shield#DisableApplicationLayerAutomaticResponseRequest": { @@ -1403,7 +1405,7 @@ "ResourceArn": { "target": "com.amazonaws.shield#ResourceArn", "traits": { - "smithy.api#documentation": "

The ARN (Amazon Resource Name) of the resource.

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

The ARN (Amazon Resource Name) of the protected resource.

", "smithy.api#required": {} } } @@ -1673,7 +1675,7 @@ } ], "traits": { - "smithy.api#documentation": "

Enable the Shield Advanced automatic application layer DDoS mitigation for the resource.

\n \n

This feature is available for Amazon CloudFront distributions only.

\n \n

This causes Shield Advanced to create, verify, and apply WAF rules for DDoS attacks that it detects for the \n resource. Shield Advanced applies the rules in a Shield rule group inside the web ACL that you've associated \n with the resource. For information about how automatic mitigation works and the requirements for using it, see \n Shield Advanced automatic application layer DDoS mitigation.

\n

Don't use this action to make changes to automatic mitigation settings when it's already enabled for a resource. Instead, use UpdateApplicationLayerAutomaticResponse.

\n

To use this feature, you must associate a web ACL with the protected resource. The web ACL must be created using the latest version of WAF (v2). You can associate the web ACL through the Shield Advanced console \n at https://console.aws.amazon.com/wafv2/shieldv2#/. For more information, \n see Getting Started with Shield Advanced.

\n

You can also do this through the WAF console or the WAF API, but you must manage Shield Advanced automatic mitigation through Shield Advanced. For information about WAF, see \n WAF Developer Guide.

" + "smithy.api#documentation": "

Enable the Shield Advanced automatic application layer DDoS mitigation for the protected resource.

\n \n

This feature is available for Amazon CloudFront distributions and Application Load Balancers only.

\n \n

This causes Shield Advanced to create, verify, and apply WAF rules for DDoS attacks that it detects for the\n resource. Shield Advanced applies the rules in a Shield rule group inside the web ACL that you've associated\n with the resource. For information about how automatic mitigation works and the requirements for using it, see\n Shield Advanced automatic application layer DDoS mitigation.

\n \n

Don't use this action to make changes to automatic mitigation settings when it's already enabled for a resource. Instead, use UpdateApplicationLayerAutomaticResponse.

\n \n

To use this feature, you must associate a web ACL with the protected resource. The web ACL must be created using the latest version of WAF (v2). You can associate the web ACL through the Shield Advanced console\n at https://console.aws.amazon.com/wafv2/shieldv2#/. For more information,\n see Getting Started with Shield Advanced. You can also associate the web ACL to the resource through the WAF console or the WAF API, but you must manage Shield Advanced automatic mitigation through Shield Advanced. For information about WAF, see\n WAF Developer Guide.

" } }, "com.amazonaws.shield#EnableApplicationLayerAutomaticResponseRequest": { @@ -1682,14 +1684,14 @@ "ResourceArn": { "target": "com.amazonaws.shield#ResourceArn", "traits": { - "smithy.api#documentation": "

The ARN (Amazon Resource Name) of the resource.

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

The ARN (Amazon Resource Name) of the protected resource.

", "smithy.api#required": {} } }, "Action": { "target": "com.amazonaws.shield#ResponseAction", "traits": { - "smithy.api#documentation": "

Specifies the action setting that Shield Advanced should use in the WAF rules that it creates on behalf of the \n protected resource in response to DDoS attacks. You specify this as part of the configuration for the automatic application layer DDoS mitigation feature, \n when you enable or update automatic mitigation. Shield Advanced creates the WAF rules in a Shield Advanced-managed rule group, inside the web ACL that you have associated with the resource.

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

Specifies the action setting that Shield Advanced should use in the WAF rules that it creates on behalf of the\n protected resource in response to DDoS attacks. You specify this as part of the configuration for the automatic application layer DDoS mitigation feature,\n when you enable or update automatic mitigation. Shield Advanced creates the WAF rules in a Shield Advanced-managed rule group, inside the web ACL that you have associated with the resource.

", "smithy.api#required": {} } } @@ -1788,6 +1790,64 @@ "target": "com.amazonaws.shield#HealthCheckId" } }, + "com.amazonaws.shield#InclusionProtectionFilters": { + "type": "structure", + "members": { + "ResourceArns": { + "target": "com.amazonaws.shield#ResourceArnFilters", + "traits": { + "smithy.api#documentation": "

The ARN (Amazon Resource Name) of the resource whose protection you want to retrieve.

" + } + }, + "ProtectionNames": { + "target": "com.amazonaws.shield#ProtectionNameFilters", + "traits": { + "smithy.api#documentation": "

The name of the protection that you want to retrieve.

" + } + }, + "ResourceTypes": { + "target": "com.amazonaws.shield#ProtectedResourceTypeFilters", + "traits": { + "smithy.api#documentation": "

The type of protected resource whose protections you want to retrieve.

" + } + } + }, + "traits": { + "smithy.api#documentation": "

Narrows the set of protections that the call retrieves. You can retrieve a single protection by providing its name or the ARN (Amazon Resource Name) of its protected resource. You can also retrieve all protections for a specific resource type. You can provide up to one criteria per filter type. Shield Advanced returns protections that exactly match all of the filter criteria that you provide.

" + } + }, + "com.amazonaws.shield#InclusionProtectionGroupFilters": { + "type": "structure", + "members": { + "ProtectionGroupIds": { + "target": "com.amazonaws.shield#ProtectionGroupIdFilters", + "traits": { + "smithy.api#documentation": "

The ID of the protection group that you want to retrieve.

" + } + }, + "Patterns": { + "target": "com.amazonaws.shield#ProtectionGroupPatternFilters", + "traits": { + "smithy.api#documentation": "

The pattern specification of the protection groups that you want to retrieve.

" + } + }, + "ResourceTypes": { + "target": "com.amazonaws.shield#ProtectedResourceTypeFilters", + "traits": { + "smithy.api#documentation": "

The resource type configuration of the protection groups that you want to retrieve. In the protection group configuration, you specify the resource type when you set the group's Pattern to BY_RESOURCE_TYPE.

" + } + }, + "Aggregations": { + "target": "com.amazonaws.shield#ProtectionGroupAggregationFilters", + "traits": { + "smithy.api#documentation": "

The aggregation setting of the protection groups that you want to retrieve.

" + } + } + }, + "traits": { + "smithy.api#documentation": "

Narrows the set of protection groups that the call retrieves. You can retrieve a single protection group by its name and you can retrieve all protection groups that are configured with a specific pattern, aggregation, or resource type. You can provide up to one criteria per filter type. Shield Advanced returns the protection groups that exactly match all of the search criteria that you provide.

" + } + }, "com.amazonaws.shield#Integer": { "type": "integer" }, @@ -1954,7 +2014,7 @@ "ResourceArns": { "target": "com.amazonaws.shield#ResourceArnFilterList", "traits": { - "smithy.api#documentation": "

The ARNs (Amazon Resource Names) of the resources that were attacked. If you leave this \n blank, all applicable resources for this account will be included.

" + "smithy.api#documentation": "

The ARNs (Amazon Resource Names) of the resources that were attacked. If you leave this\n blank, all applicable resources for this account will be included.

" } }, "StartTime": { @@ -1972,13 +2032,13 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" } }, "MaxResults": { "target": "com.amazonaws.shield#MaxResults", "traits": { - "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value \n in the response.

\n

The default setting is 20.

" + "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value\n in the response.

\n

The default setting is 20.

" } } } @@ -1995,7 +2055,7 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" } } } @@ -2020,7 +2080,7 @@ } ], "traits": { - "smithy.api#documentation": "

Retrieves the ProtectionGroup objects for the account.

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

Retrieves ProtectionGroup objects for the account. You can retrieve all protection groups or you can provide \n filtering criteria and retrieve just the subset of protection groups that match the criteria.

", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -2034,13 +2094,19 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" } }, "MaxResults": { "target": "com.amazonaws.shield#MaxResults", "traits": { - "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value \n in the response.

\n

The default setting is 20.

" + "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value\n in the response.

\n

The default setting is 20.

" + } + }, + "InclusionFilters": { + "target": "com.amazonaws.shield#InclusionProtectionGroupFilters", + "traits": { + "smithy.api#documentation": "

Narrows the set of protection groups that the call retrieves. You can retrieve a single protection group by its name and you can retrieve all protection groups that are configured with specific pattern or aggregation settings. You can provide up to one criteria per filter type. Shield Advanced returns the protection groups that exactly match all of the search criteria that you provide.

" } } } @@ -2058,7 +2124,7 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" } } } @@ -2083,7 +2149,7 @@ } ], "traits": { - "smithy.api#documentation": "

Lists all Protection objects for the account.

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

Retrieves Protection objects for the account. You can retrieve all protections or you can provide \n filtering criteria and retrieve just the subset of protections that match the criteria.

", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -2098,13 +2164,19 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" } }, "MaxResults": { "target": "com.amazonaws.shield#MaxResults", "traits": { - "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value \n in the response.

\n

The default setting is 20.

" + "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value\n in the response.

\n

The default setting is 20.

" + } + }, + "InclusionFilters": { + "target": "com.amazonaws.shield#InclusionProtectionFilters", + "traits": { + "smithy.api#documentation": "

Narrows the set of protections that the call retrieves. You can retrieve a single protection by providing its name or the ARN (Amazon Resource Name) of its protected resource. You can also retrieve all protections for a specific resource type. You can provide up to one criteria per filter type. Shield Advanced returns protections that exactly match all of the filter criteria that you provide.

" } } } @@ -2121,7 +2193,7 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" } } } @@ -2167,13 +2239,13 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

\n

On your first call to a list operation, leave this setting empty.

" } }, "MaxResults": { "target": "com.amazonaws.shield#MaxResults", "traits": { - "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value \n in the response.

\n

The default setting is 20.

" + "smithy.api#documentation": "

The greatest number of objects that you want Shield Advanced to return to the list request. Shield Advanced might return fewer objects\n than you indicate in this setting, even if more objects are available. If there are more objects remaining, Shield Advanced will always also return a NextToken value\n in the response.

\n

The default setting is 20.

" } } } @@ -2191,7 +2263,7 @@ "NextToken": { "target": "com.amazonaws.shield#Token", "traits": { - "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects, \n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and \n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" + "smithy.api#documentation": "

When you request a list of objects from Shield Advanced, if the response does not include all of the remaining available objects,\n Shield Advanced includes a NextToken value in the response. You can retrieve the next batch of objects by requesting the list again and\n providing the token that was returned by the prior call in your request.

\n

You can indicate the maximum number of objects that you want Shield Advanced to return for a single call with the MaxResults\n setting. Shield Advanced will not return more than MaxResults objects, but may return fewer, even if more objects are still available.

\n

Whenever more objects remain that Shield Advanced has not yet returned to you, the response will include a NextToken value.

" } } } @@ -2317,7 +2389,7 @@ } }, "traits": { - "smithy.api#documentation": "

The ARN of the role that you specifed does not exist.

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

The ARN of the role that you specified does not exist.

", "smithy.api#error": "client" } }, @@ -2393,6 +2465,18 @@ ] } }, + "com.amazonaws.shield#ProtectedResourceTypeFilters": { + "type": "list", + "member": { + "target": "com.amazonaws.shield#ProtectedResourceType" + }, + "traits": { + "smithy.api#length": { + "min": 1, + "max": 1 + } + } + }, "com.amazonaws.shield#Protection": { "type": "structure", "members": { @@ -2429,7 +2513,7 @@ "ApplicationLayerAutomaticResponseConfiguration": { "target": "com.amazonaws.shield#ApplicationLayerAutomaticResponseConfiguration", "traits": { - "smithy.api#documentation": "

The automatic application layer DDoS mitigation settings for the protection. \n This configuration determines whether Shield Advanced automatically \n manages rules in the web ACL in order to respond to application layer events that Shield Advanced determines to be DDoS attacks.

" + "smithy.api#documentation": "

The automatic application layer DDoS mitigation settings for the protection.\n This configuration determines whether Shield Advanced automatically\n manages rules in the web ACL in order to respond to application layer events that Shield Advanced determines to be DDoS attacks.

" } } }, @@ -2457,20 +2541,20 @@ "Pattern": { "target": "com.amazonaws.shield#ProtectionGroupPattern", "traits": { - "smithy.api#documentation": "

The criteria to use to choose the protected resources for inclusion in the group. You can include all resources that have protections, provide a list of resource Amazon Resource Names (ARNs), or include all resources of a specified resource type.

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

The criteria to use to choose the protected resources for inclusion in the group. You can include all resources that have protections, provide a list of resource ARNs (Amazon Resource Names), or include all resources of a specified resource type.

", "smithy.api#required": {} } }, "ResourceType": { "target": "com.amazonaws.shield#ProtectedResourceType", "traits": { - "smithy.api#documentation": "

The resource type to include in the protection group. All protected resources of this type are included in the protection group. \n You must set this when you set Pattern to BY_RESOURCE_TYPE and you must not set it for any other Pattern setting.

" + "smithy.api#documentation": "

The resource type to include in the protection group. All protected resources of this type are included in the protection group.\n You must set this when you set Pattern to BY_RESOURCE_TYPE and you must not set it for any other Pattern setting.

" } }, "Members": { "target": "com.amazonaws.shield#ProtectionGroupMembers", "traits": { - "smithy.api#documentation": "

The Amazon Resource Names (ARNs) of the resources to include in the protection group. You must set this when you set Pattern to ARBITRARY and you must not set it for any other Pattern setting.

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

The ARNs (Amazon Resource Names) of the resources to include in the protection group. You must set this when you set Pattern to ARBITRARY and you must not set it for any other Pattern setting.

", "smithy.api#required": {} } }, @@ -2504,6 +2588,18 @@ ] } }, + "com.amazonaws.shield#ProtectionGroupAggregationFilters": { + "type": "list", + "member": { + "target": "com.amazonaws.shield#ProtectionGroupAggregation" + }, + "traits": { + "smithy.api#length": { + "min": 1, + "max": 1 + } + } + }, "com.amazonaws.shield#ProtectionGroupArbitraryPatternLimits": { "type": "structure", "members": { @@ -2529,6 +2625,18 @@ "smithy.api#pattern": "^[a-zA-Z0-9\\\\-]*$" } }, + "com.amazonaws.shield#ProtectionGroupIdFilters": { + "type": "list", + "member": { + "target": "com.amazonaws.shield#ProtectionGroupId" + }, + "traits": { + "smithy.api#length": { + "min": 1, + "max": 1 + } + } + }, "com.amazonaws.shield#ProtectionGroupLimits": { "type": "structure", "members": { @@ -2582,6 +2690,18 @@ ] } }, + "com.amazonaws.shield#ProtectionGroupPatternFilters": { + "type": "list", + "member": { + "target": "com.amazonaws.shield#ProtectionGroupPattern" + }, + "traits": { + "smithy.api#length": { + "min": 1, + "max": 1 + } + } + }, "com.amazonaws.shield#ProtectionGroupPatternTypeLimits": { "type": "structure", "members": { @@ -2638,6 +2758,18 @@ "smithy.api#pattern": "^[ a-zA-Z0-9_\\\\.\\\\-]*$" } }, + "com.amazonaws.shield#ProtectionNameFilters": { + "type": "list", + "member": { + "target": "com.amazonaws.shield#ProtectionName" + }, + "traits": { + "smithy.api#length": { + "min": 1, + "max": 1 + } + } + }, "com.amazonaws.shield#Protections": { "type": "list", "member": { @@ -2678,6 +2810,18 @@ "target": "com.amazonaws.shield#ResourceArn" } }, + "com.amazonaws.shield#ResourceArnFilters": { + "type": "list", + "member": { + "target": "com.amazonaws.shield#ResourceArn" + }, + "traits": { + "smithy.api#length": { + "min": 1, + "max": 1 + } + } + }, "com.amazonaws.shield#ResourceArnList": { "type": "list", "member": { @@ -2719,7 +2863,7 @@ } }, "traits": { - "smithy.api#documentation": "

Specifies the action setting that Shield Advanced should use in the WAF rules that it creates on behalf of the \n protected resource in response to DDoS attacks. You specify this as part of the configuration for the automatic application layer DDoS mitigation feature, \n when you enable or update automatic mitigation. Shield Advanced creates the WAF rules in a Shield Advanced-managed rule group, inside the web ACL that you have associated with the resource.

" + "smithy.api#documentation": "

Specifies the action setting that Shield Advanced should use in the WAF rules that it creates on behalf of the\n protected resource in response to DDoS attacks. You specify this as part of the configuration for the automatic application layer DDoS mitigation feature,\n when you enable or update automatic mitigation. Shield Advanced creates the WAF rules in a Shield Advanced-managed rule group, inside the web ACL that you have associated with the resource.

" } }, "com.amazonaws.shield#RoleArn": { @@ -3223,7 +3367,7 @@ "Action": { "target": "com.amazonaws.shield#ResponseAction", "traits": { - "smithy.api#documentation": "

Specifies the action setting that Shield Advanced should use in the WAF rules that it creates on behalf of the \n protected resource in response to DDoS attacks. You specify this as part of the configuration for the automatic application layer DDoS mitigation feature, \n when you enable or update automatic mitigation. Shield Advanced creates the WAF rules in a Shield Advanced-managed rule group, inside the web ACL that you have associated with the resource.

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

Specifies the action setting that Shield Advanced should use in the WAF rules that it creates on behalf of the\n protected resource in response to DDoS attacks. You specify this as part of the configuration for the automatic application layer DDoS mitigation feature,\n when you enable or update automatic mitigation. Shield Advanced creates the WAF rules in a Shield Advanced-managed rule group, inside the web ACL that you have associated with the resource.

", "smithy.api#required": {} } } @@ -3327,7 +3471,7 @@ "ResourceType": { "target": "com.amazonaws.shield#ProtectedResourceType", "traits": { - "smithy.api#documentation": "

The resource type to include in the protection group. All protected resources of this type are included in the protection group. \n You must set this when you set Pattern to BY_RESOURCE_TYPE and you must not set it for any other Pattern setting.

" + "smithy.api#documentation": "

The resource type to include in the protection group. All protected resources of this type are included in the protection group.\n You must set this when you set Pattern to BY_RESOURCE_TYPE and you must not set it for any other Pattern setting.

" } }, "Members": { @@ -3368,7 +3512,7 @@ } ], "traits": { - "smithy.api#documentation": "

Updates the details of an existing subscription. Only enter values for parameters you want to change. Empty parameters are not updated.

" + "smithy.api#documentation": "

Updates the details of an existing subscription. Only enter values for parameters you want to change. Empty parameters are not updated.

\n \n

For accounts that are members of an Organizations organization, Shield Advanced subscriptions are billed against the organization's payer account,\n regardless of whether the payer account itself is subscribed.

\n " } }, "com.amazonaws.shield#UpdateSubscriptionRequest": {