From 06813a8c7c3f770b5d801e2a17354d37071bb343 Mon Sep 17 00:00:00 2001 From: AWS SDK for Go v2 automation user Date: Thu, 14 Apr 2022 18:03:40 +0000 Subject: [PATCH] Update API model --- codegen/sdk-codegen/aws-models/appflow.json | 100 ++++++- codegen/sdk-codegen/aws-models/appstream.json | 22 ++ codegen/sdk-codegen/aws-models/batch.json | 255 ++++++++++++++---- .../sdk-codegen/aws-models/cloudwatch.json | 39 ++- codegen/sdk-codegen/aws-models/ec2.json | 212 +++++++++++++-- codegen/sdk-codegen/aws-models/glue.json | 6 + 6 files changed, 550 insertions(+), 84 deletions(-) diff --git a/codegen/sdk-codegen/aws-models/appflow.json b/codegen/sdk-codegen/aws-models/appflow.json index 1ea5b90c8d4..f21f240a81f 100644 --- a/codegen/sdk-codegen/aws-models/appflow.json +++ b/codegen/sdk-codegen/aws-models/appflow.json @@ -283,7 +283,7 @@ "traits": { "smithy.api#length": { "min": 0, - "max": 512 + "max": 2048 }, "smithy.api#pattern": "^\\S+$" } @@ -4871,6 +4871,77 @@ "smithy.api#documentation": "

The OAuth 2.0 credentials required for OAuth 2.0 authentication.

" } }, + "com.amazonaws.appflow#OAuth2CustomParameter": { + "type": "structure", + "members": { + "key": { + "target": "com.amazonaws.appflow#Key", + "traits": { + "smithy.api#documentation": "

The key of the custom parameter required for OAuth 2.0 authentication.

" + } + }, + "isRequired": { + "target": "com.amazonaws.appflow#Boolean", + "traits": { + "smithy.api#documentation": "

Indicates whether the custom parameter for OAuth 2.0 authentication is required.

" + } + }, + "label": { + "target": "com.amazonaws.appflow#Label", + "traits": { + "smithy.api#documentation": "

The label of the custom parameter used for OAuth 2.0 authentication.

" + } + }, + "description": { + "target": "com.amazonaws.appflow#Description", + "traits": { + "smithy.api#documentation": "

A description about the custom parameter used for OAuth 2.0 authentication.

" + } + }, + "isSensitiveField": { + "target": "com.amazonaws.appflow#Boolean", + "traits": { + "smithy.api#documentation": "

Indicates whether this authentication custom parameter is a sensitive field.

" + } + }, + "connectorSuppliedValues": { + "target": "com.amazonaws.appflow#ConnectorSuppliedValueList", + "traits": { + "smithy.api#documentation": "

Contains default values for this authentication parameter that are supplied by the\n connector.

" + } + }, + "type": { + "target": "com.amazonaws.appflow#OAuth2CustomPropType", + "traits": { + "smithy.api#documentation": "

Indicates whether custom parameter is used with TokenUrl or AuthUrl.

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

Custom parameter required for OAuth 2.0 authentication.

" + } + }, + "com.amazonaws.appflow#OAuth2CustomPropType": { + "type": "string", + "traits": { + "smithy.api#enum": [ + { + "value": "TOKEN_URL", + "name": "TOKEN_URL" + }, + { + "value": "AUTH_URL", + "name": "AUTH_URL" + } + ] + } + }, + "com.amazonaws.appflow#OAuth2CustomPropertiesList": { + "type": "list", + "member": { + "target": "com.amazonaws.appflow#OAuth2CustomParameter" + } + }, "com.amazonaws.appflow#OAuth2Defaults": { "type": "structure", "members": { @@ -4897,6 +4968,12 @@ "traits": { "smithy.api#documentation": "

OAuth 2.0 grant types supported by the connector.

" } + }, + "oauth2CustomProperties": { + "target": "com.amazonaws.appflow#OAuth2CustomPropertiesList", + "traits": { + "smithy.api#documentation": "

List of custom parameters required for OAuth 2.0 authentication.

" + } } }, "traits": { @@ -4940,6 +5017,12 @@ "smithy.api#documentation": "

The OAuth 2.0 grant type used by connector for OAuth 2.0 authentication.

", "smithy.api#required": {} } + }, + "tokenUrlCustomProperties": { + "target": "com.amazonaws.appflow#TokenUrlCustomProperties", + "traits": { + "smithy.api#documentation": "

Associates your token URL with a map of properties that you define. Use this parameter\n to provide any additional details that the connector requires to authenticate your\n request.

" + } } }, "traits": { @@ -7799,6 +7882,21 @@ "smithy.api#pattern": "^(https?)://[-a-zA-Z0-9+&@#/%?=~_|!:,.;]*[-a-zA-Z0-9+&@#/%=~_|]$" } }, + "com.amazonaws.appflow#TokenUrlCustomProperties": { + "type": "map", + "key": { + "target": "com.amazonaws.appflow#CustomPropertyKey" + }, + "value": { + "target": "com.amazonaws.appflow#CustomPropertyValue" + }, + "traits": { + "smithy.api#length": { + "min": 0, + "max": 50 + } + } + }, "com.amazonaws.appflow#TokenUrlList": { "type": "list", "member": { diff --git a/codegen/sdk-codegen/aws-models/appstream.json b/codegen/sdk-codegen/aws-models/appstream.json index 667c0ca134b..a3bdb0f1389 100644 --- a/codegen/sdk-codegen/aws-models/appstream.json +++ b/codegen/sdk-codegen/aws-models/appstream.json @@ -1382,6 +1382,12 @@ "traits": { "smithy.api#documentation": "

The USB device filter strings that specify which USB devices a user can redirect to the fleet streaming session, when using the Windows native client. This is allowed but not required for Elastic fleets.

" } + }, + "SessionScriptS3Location": { + "target": "com.amazonaws.appstream#S3Location", + "traits": { + "smithy.api#documentation": "

The S3 location of the session scripts configuration zip file. This only applies to Elastic fleets.

" + } } } }, @@ -4121,6 +4127,12 @@ "traits": { "smithy.api#documentation": "

The USB device filter strings associated with the fleet.

" } + }, + "SessionScriptS3Location": { + "target": "com.amazonaws.appstream#S3Location", + "traits": { + "smithy.api#documentation": "

The S3 location of the session scripts configuration zip file. This only applies to Elastic fleets.

" + } } }, "traits": { @@ -4151,6 +4163,10 @@ { "value": "USB_DEVICE_FILTER_STRINGS", "name": "USB_DEVICE_FILTER_STRINGS" + }, + { + "value": "SESSION_SCRIPT_S3_LOCATION", + "name": "SESSION_SCRIPT_S3_LOCATION" } ] } @@ -6867,6 +6883,12 @@ "traits": { "smithy.api#documentation": "

The USB device filter strings that specify which USB devices a user can redirect to the fleet streaming session, when using the Windows native client. This is allowed but not required for Elastic fleets.

" } + }, + "SessionScriptS3Location": { + "target": "com.amazonaws.appstream#S3Location", + "traits": { + "smithy.api#documentation": "

The S3 location of the session scripts configuration zip file. This only applies to Elastic fleets.

" + } } } }, diff --git a/codegen/sdk-codegen/aws-models/batch.json b/codegen/sdk-codegen/aws-models/batch.json index 4e5af544be5..50f9f9c1e7f 100644 --- a/codegen/sdk-codegen/aws-models/batch.json +++ b/codegen/sdk-codegen/aws-models/batch.json @@ -415,6 +415,21 @@ ] } }, + "com.amazonaws.batch#CRUpdateAllocationStrategy": { + "type": "string", + "traits": { + "smithy.api#enum": [ + { + "value": "BEST_FIT_PROGRESSIVE", + "name": "BEST_FIT_PROGRESSIVE" + }, + { + "value": "SPOT_CAPACITY_OPTIMIZED", + "name": "SPOT_CAPACITY_OPTIMIZED" + } + ] + } + }, "com.amazonaws.batch#CancelJob": { "type": "operation", "input": { @@ -505,8 +520,7 @@ "ecsClusterArn": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon Resource Name (ARN) of the underlying Amazon ECS cluster used by the compute environment.

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

The Amazon Resource Name (ARN) of the underlying Amazon ECS cluster used by the compute environment.

" } }, "tags": { @@ -518,7 +532,7 @@ "type": { "target": "com.amazonaws.batch#CEType", "traits": { - "smithy.api#documentation": "

The type of the compute environment: MANAGED or UNMANAGED. For more information, see\n Compute Environments in the\n Batch User Guide.

" + "smithy.api#documentation": "

The type of the compute environment: MANAGED or UNMANAGED. For more information, see\n Compute environments in the\n Batch User Guide.

" } }, "state": { @@ -542,7 +556,7 @@ "computeResources": { "target": "com.amazonaws.batch#ComputeResource", "traits": { - "smithy.api#documentation": "

The compute resources defined for the compute environment. For more information, see Compute Environments in the\n Batch User Guide.

" + "smithy.api#documentation": "

The compute resources defined for the compute environment. For more information, see Compute environments in the\n Batch User Guide.

" } }, "serviceRole": { @@ -550,6 +564,12 @@ "traits": { "smithy.api#documentation": "

The service role associated with the compute environment that allows Batch to make calls to Amazon Web Services API\n operations on your behalf. For more information, see Batch service IAM role in the\n Batch User Guide.

" } + }, + "updatePolicy": { + "target": "com.amazonaws.batch#UpdatePolicy", + "traits": { + "smithy.api#documentation": "

Specifies the infrastructure update policy for the compute environment. For more information about\n infrastructure updates, see Updating compute\n environments in the Batch User Guide.

" + } } }, "traits": { @@ -596,20 +616,20 @@ "type": { "target": "com.amazonaws.batch#CRType", "traits": { - "smithy.api#documentation": "

The type of compute environment: EC2, SPOT, FARGATE, or\n FARGATE_SPOT. For more information, see Compute Environments in the\n Batch User Guide.

\n

If you choose SPOT, you must also specify an Amazon EC2 Spot Fleet role with the\n spotIamFleetRole parameter. For more information, see Amazon EC2 Spot Fleet role in the\n Batch User Guide.

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

The type of compute environment: EC2, SPOT, FARGATE, or\n FARGATE_SPOT. For more information, see Compute environments in the\n Batch User Guide.

\n

If you choose SPOT, you must also specify an Amazon EC2 Spot Fleet role with the\n spotIamFleetRole parameter. For more information, see Amazon EC2 spot fleet role in the\n Batch User Guide.

", "smithy.api#required": {} } }, "allocationStrategy": { "target": "com.amazonaws.batch#CRAllocationStrategy", "traits": { - "smithy.api#documentation": "

The allocation strategy to use for the compute resource if not enough instances of the best fitting instance\n type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more\n information, see Allocation Strategies\n in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n
\n
BEST_FIT (default)
\n
\n

Batch selects an instance type that best fits the needs of the jobs with a preference for the lowest-cost\n instance type. If additional instances of the selected instance type aren't available, Batch waits for the\n additional instances to be available. If there aren't enough instances available, or if the user is reaching\n Amazon EC2 service limits\n then additional jobs aren't run until the currently running jobs have completed. This allocation strategy keeps\n costs lower but can limit scaling. If you are using Spot Fleets with BEST_FIT then the Spot Fleet IAM\n Role must be specified.

\n
\n
BEST_FIT_PROGRESSIVE
\n
\n

Batch will select additional instance types that are large enough to meet the requirements of the jobs in\n the queue, with a preference for instance types with a lower cost per unit vCPU. If additional instances of the\n previously selected instance types aren't available, Batch will select new instance types.

\n
\n
SPOT_CAPACITY_OPTIMIZED
\n
\n

Batch will select one or more instance types that are large enough to meet the requirements of the jobs in\n the queue, with a preference for instance types that are less likely to be interrupted. This allocation strategy\n is only available for Spot Instance compute resources.

\n
\n
\n

With both BEST_FIT_PROGRESSIVE and SPOT_CAPACITY_OPTIMIZED strategies, Batch might\n need to go above maxvCpus to meet your capacity requirements. In this event, Batch never exceeds\n maxvCpus by more than a single instance.

" + "smithy.api#documentation": "

The allocation strategy to use for the compute resource if not enough instances of the best fitting instance\n type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more\n information, see Allocation strategies\n in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n
\n
BEST_FIT (default)
\n
\n

Batch selects an instance type that best fits the needs of the jobs with a preference for the lowest-cost\n instance type. If additional instances of the selected instance type aren't available, Batch waits for the\n additional instances to be available. If there aren't enough instances available, or if the user is reaching\n Amazon EC2 service limits\n then additional jobs aren't run until the currently running jobs have completed. This allocation strategy keeps\n costs lower but can limit scaling. If you are using Spot Fleets with BEST_FIT then the Spot Fleet IAM\n Role must be specified. Compute resources that use a BEST_FIT allocation strategy don't support\n infrastructure updates and can't update some parameters. For more information, see Updating compute environments in the\n Batch User Guide.

\n
\n
BEST_FIT_PROGRESSIVE
\n
\n

Batch will select additional instance types that are large enough to meet the requirements of the jobs in\n the queue, with a preference for instance types with a lower cost per unit vCPU. If additional instances of the\n previously selected instance types aren't available, Batch will select new instance types.

\n
\n
SPOT_CAPACITY_OPTIMIZED
\n
\n

Batch will select one or more instance types that are large enough to meet the requirements of the jobs in\n the queue, with a preference for instance types that are less likely to be interrupted. This allocation strategy\n is only available for Spot Instance compute resources.

\n
\n
\n

With both BEST_FIT_PROGRESSIVE and SPOT_CAPACITY_OPTIMIZED strategies, Batch might\n need to go above maxvCpus to meet your capacity requirements. In this event, Batch never exceeds\n maxvCpus by more than a single instance.

" } }, "minvCpus": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The minimum number of Amazon EC2 vCPUs that an environment should maintain (even if the compute environment is\n DISABLED).

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The minimum number of Amazon EC2 vCPUs that an environment should maintain (even if the compute environment is\n DISABLED).

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "maxvCpus": { @@ -622,13 +642,13 @@ "desiredvCpus": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The desired number of Amazon EC2 vCPUS in the compute environment. Batch modifies this value between the minimum\n and maximum values, based on job queue demand.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The desired number of Amazon EC2 vCPUS in the compute environment. Batch modifies this value between the minimum\n and maximum values, based on job queue demand.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "instanceTypes": { "target": "com.amazonaws.batch#StringList", "traits": { - "smithy.api#documentation": "

The instances types that can be launched. You can specify instance families to launch any instance type within\n those families (for example, c5 or p3), or you can specify specific sizes within a family\n (such as c5.8xlarge). You can also choose optimal to select instance types (from the C4,\n M4, and R4 instance families) that match the demand of your job queues.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

When you create a compute environment, the instance types that you select for the compute environment must\n share the same architecture. For example, you can't mix x86 and ARM instances in the same compute\n environment.

\n \n \n

Currently, optimal uses instance types from the C4, M4, and R4 instance families. In Regions that\n don't have instance types from those instance families, instance types from the C5, M5. and R5 instance families are\n used.

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

The instances types that can be launched. You can specify instance families to launch any instance type within\n those families (for example, c5 or p3), or you can specify specific sizes within a family\n (such as c5.8xlarge). You can also choose optimal to select instance types (from the C4,\n M4, and R4 instance families) that match the demand of your job queues.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

When you create a compute environment, the instance types that you select for the compute environment must\n share the same architecture. For example, you can't mix x86 and ARM instances in the same compute\n environment.

\n \n \n

Currently, optimal uses instance types from the C4, M4, and R4 instance families. In Regions that\n don't have instance types from those instance families, instance types from the C5, M5. and R5 instance families are\n used.

\n " } }, "imageId": { @@ -637,13 +657,13 @@ "smithy.api#deprecated": { "message": "This field is deprecated, use ec2Configuration[].imageIdOverride instead." }, - "smithy.api#documentation": "

The Amazon Machine Image (AMI) ID used for instances launched in the compute environment. This parameter is\n overridden by the imageIdOverride member of the Ec2Configuration structure.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

The AMI that you choose for a compute environment must match the architecture of the instance types that\n you intend to use for that compute environment. For example, if your compute environment uses A1 instance types,\n the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the\n Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized\n Amazon Linux 2 AMI\n in the Amazon Elastic Container Service Developer Guide.

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

The Amazon Machine Image (AMI) ID used for instances launched in the compute environment. This parameter is\n overridden by the imageIdOverride member of the Ec2Configuration structure.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

The AMI that you choose for a compute environment must match the architecture of the instance types that\n you intend to use for that compute environment. For example, if your compute environment uses A1 instance types,\n the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the\n Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized\n Amazon Linux 2 AMI\n in the Amazon Elastic Container Service Developer Guide.

\n " } }, "subnets": { "target": "com.amazonaws.batch#StringList", "traits": { - "smithy.api#documentation": "

The VPC subnets where the compute resources are launched. These subnets must be within the same VPC. Fargate\n compute resources can contain up to 16 subnets. For more information, see VPCs and Subnets in the Amazon VPC User\n Guide.

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

The VPC subnets where the compute resources are launched. These subnets must be within the same VPC. Fargate\n compute resources can contain up to 16 subnets. For more information, see VPCs and subnets in the Amazon VPC User\n Guide.

", "smithy.api#required": {} } }, @@ -656,54 +676,54 @@ "ec2KeyPair": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon EC2 key pair that's used for instances launched in the compute environment. You can use this key pair to\n log in to your instances with SSH.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The Amazon EC2 key pair that's used for instances launched in the compute environment. You can use this key pair to\n log in to your instances with SSH.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "instanceRole": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment. You can specify the short name\n or full Amazon Resource Name (ARN) of an instance profile. For example,\n \n ecsInstanceRole\n or\n arn:aws:iam:::instance-profile/ecsInstanceRole\n .\n For more information, see Amazon ECS Instance\n Role in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment. You can specify the short name\n or full Amazon Resource Name (ARN) of an instance profile. For example,\n \n ecsInstanceRole\n or\n arn:aws:iam:::instance-profile/ecsInstanceRole\n .\n For more information, see Amazon ECS instance\n role in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "tags": { "target": "com.amazonaws.batch#TagsMap", "traits": { - "smithy.api#documentation": "

Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch,\n these take the form of \"String1\": \"String2\", where String1 is the tag key and String2 is the tag value−for\n example, { \"Name\": \"Batch Instance - C4OnDemand\" }. This is helpful for recognizing your Batch\n instances in the Amazon EC2 console. These tags can't be updated or removed after the compute environment is created. Any\n changes to these tags require that you create a new compute environment and remove the old compute environment. These\n tags aren't seen when using the Batch ListTagsForResource API operation.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch,\n these take the form of \"String1\": \"String2\", where String1 is the tag key and String2 is the tag value−for\n example, { \"Name\": \"Batch Instance - C4OnDemand\" }. This is helpful for recognizing your Batch\n instances in the Amazon EC2 console. These tags can't be updated or removed after the compute environment is created. Any\n changes to these tags require that you create a new compute environment and remove the old compute environment. These\n tags aren't seen when using the Batch ListTagsForResource API operation.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "placementGroup": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon EC2 placement group to associate with your compute resources. If you intend to submit multi-node parallel\n jobs to your compute environment, you should consider creating a cluster placement group and associate it with your\n compute resources. This keeps your multi-node parallel job on a logical grouping of instances within a single\n Availability Zone with high network flow potential. For more information, see Placement Groups in the Amazon EC2 User Guide for\n Linux Instances.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The Amazon EC2 placement group to associate with your compute resources. If you intend to submit multi-node parallel\n jobs to your compute environment, you should consider creating a cluster placement group and associate it with your\n compute resources. This keeps your multi-node parallel job on a logical grouping of instances within a single\n Availability Zone with high network flow potential. For more information, see Placement groups in the Amazon EC2 User Guide for\n Linux Instances.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "bidPercentage": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The maximum percentage that a Spot Instance price can be when compared with the On-Demand price for that\n instance type before instances are launched. For example, if your maximum percentage is 20%, then the Spot price must\n be less than 20% of the current On-Demand price for that Amazon EC2 instance. You always pay the lowest (market) price and\n never more than your maximum percentage. If you leave this field empty, the default value is 100% of the On-Demand\n price.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The maximum percentage that a Spot Instance price can be when compared with the On-Demand price for that\n instance type before instances are launched. For example, if your maximum percentage is 20%, then the Spot price must\n be less than 20% of the current On-Demand price for that Amazon EC2 instance. You always pay the lowest (market) price and\n never more than your maximum percentage. If you leave this field empty, the default value is 100% of the On-Demand\n price.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "spotIamFleetRole": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon Resource Name (ARN) of the Amazon EC2 Spot Fleet IAM role applied to a SPOT compute environment. This role is\n required if the allocation strategy set to BEST_FIT or if the allocation strategy isn't specified. For\n more information, see Amazon EC2 Spot Fleet\n Role in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

To tag your Spot Instances on creation, the Spot Fleet IAM role specified here must use the newer AmazonEC2SpotFleetTaggingRole managed policy. The previously recommended AmazonEC2SpotFleetRole managed policy doesn't have the required permissions to tag Spot\n Instances. For more information, see Spot Instances not tagged on creation in the\n Batch User Guide.

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

The Amazon Resource Name (ARN) of the Amazon EC2 Spot Fleet IAM role applied to a SPOT compute environment. This role is\n required if the allocation strategy set to BEST_FIT or if the allocation strategy isn't specified. For\n more information, see Amazon EC2 spot fleet\n role in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

To tag your Spot Instances on creation, the Spot Fleet IAM role specified here must use the newer AmazonEC2SpotFleetTaggingRole managed policy. The previously recommended AmazonEC2SpotFleetRole managed policy doesn't have the required permissions to tag Spot\n Instances. For more information, see Spot instances not tagged on creation in the\n Batch User Guide.

\n " } }, "launchTemplate": { "target": "com.amazonaws.batch#LaunchTemplateSpecification", "traits": { - "smithy.api#documentation": "

The launch template to use for your compute resources. Any other compute resource parameters that you specify in\n a CreateComputeEnvironment API operation override the same parameters in the launch template. You\n must specify either the launch template ID or launch template name in the request, but not both. For more\n information, see Launch Template Support in\n the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The launch template to use for your compute resources. Any other compute resource parameters that you specify in\n a CreateComputeEnvironment API operation override the same parameters in the launch template. You\n must specify either the launch template ID or launch template name in the request, but not both. For more\n information, see Launch template support in\n the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "ec2Configuration": { "target": "com.amazonaws.batch#Ec2ConfigurationList", "traits": { - "smithy.api#documentation": "

Provides information used to select Amazon Machine Images (AMIs) for EC2 instances in the compute environment.\n If Ec2Configuration isn't specified, the default is ECS_AL2.

\n

One or two values can be provided.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

Provides information used to select Amazon Machine Images (AMIs) for EC2 instances in the compute environment.\n If Ec2Configuration isn't specified, the default is ECS_AL2.

\n

One or two values can be provided.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

An object representing an Batch compute resource. For more information, see Compute Environments in the\n Batch User Guide.

" + "smithy.api#documentation": "

An object representing an Batch compute resource. For more information, see Compute environments in the\n Batch User Guide.

" } }, "com.amazonaws.batch#ComputeResourceUpdate": { @@ -712,7 +732,7 @@ "minvCpus": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The minimum number of Amazon EC2 vCPUs that an environment should maintain.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The minimum number of Amazon EC2 vCPUs that an environment should maintain (even if the compute environment is\n DISABLED).

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "maxvCpus": { @@ -724,24 +744,96 @@ "desiredvCpus": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The desired number of Amazon EC2 vCPUS in the compute environment.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

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

The desired number of Amazon EC2 vCPUS in the compute environment. Batch modifies this value between the minimum\n and maximum values based on job queue demand.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " } }, "subnets": { "target": "com.amazonaws.batch#StringList", "traits": { - "smithy.api#documentation": "

The VPC subnets where the compute resources are launched. Fargate compute resources can contain up to 16\n subnets. Providing an empty list will be handled as if this parameter wasn't specified and no change is made. This\n can't be specified for EC2 compute resources. For more information, see VPCs and Subnets in the Amazon VPC User\n Guide.

" + "smithy.api#documentation": "

The VPC subnets where the compute resources are launched. Fargate compute resources can contain up to 16\n subnets. For Fargate compute resources, providing an empty list will be handled as if this parameter wasn't\n specified and no change is made. For EC2 compute resources, providing an empty list removes the VPC subnets from the\n compute resource. For more information, see VPCs and subnets in the Amazon VPC User Guide.

\n

When updating a compute environment, changing the VPC subnets requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide.

" } }, "securityGroupIds": { "target": "com.amazonaws.batch#StringList", "traits": { - "smithy.api#documentation": "

The Amazon EC2 security groups associated with instances launched in the compute environment. This parameter is\n required for Fargate compute resources, where it can contain up to 5 security groups. This can't be specified for\n EC2 compute resources. Providing an empty list is handled as if this parameter wasn't specified and no change is\n made.

" + "smithy.api#documentation": "

The Amazon EC2 security groups associated with instances launched in the compute environment. This parameter is\n required for Fargate compute resources, where it can contain up to 5 security groups. For Fargate compute\n resources, providing an empty list is handled as if this parameter wasn't specified and no change is made. For EC2\n compute resources, providing an empty list removes the security groups from the compute resource.

\n

When updating a compute environment, changing the EC2 security groups requires an infrastructure update of the\n compute environment. For more information, see Updating compute environments in the\n Batch User Guide.

" + } + }, + "allocationStrategy": { + "target": "com.amazonaws.batch#CRUpdateAllocationStrategy", + "traits": { + "smithy.api#documentation": "

The allocation strategy to use for the compute resource if not enough instances of the best fitting instance\n type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more\n information, see Allocation strategies\n in the Batch User Guide.

\n

When updating a compute environment, changing the allocation strategy requires an infrastructure update of the\n compute environment. For more information, see Updating compute environments in the\n Batch User Guide. BEST_FIT isn't supported when updating a compute\n environment.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n
\n
BEST_FIT_PROGRESSIVE
\n
\n

Batch will select additional instance types that are large enough to meet the requirements of the jobs in\n the queue, with a preference for instance types with a lower cost per unit vCPU. If additional instances of the\n previously selected instance types aren't available, Batch will select new instance types.

\n
\n
SPOT_CAPACITY_OPTIMIZED
\n
\n

Batch will select one or more instance types that are large enough to meet the requirements of the jobs in\n the queue, with a preference for instance types that are less likely to be interrupted. This allocation strategy\n is only available for Spot Instance compute resources.

\n
\n
\n

With both BEST_FIT_PROGRESSIVE and SPOT_CAPACITY_OPTIMIZED strategies, Batch might\n need to go above maxvCpus to meet your capacity requirements. In this event, Batch never exceeds\n maxvCpus by more than a single instance.

" + } + }, + "instanceTypes": { + "target": "com.amazonaws.batch#StringList", + "traits": { + "smithy.api#documentation": "

The instances types that can be launched. You can specify instance families to launch any instance type within\n those families (for example, c5 or p3), or you can specify specific sizes within a family\n (such as c5.8xlarge). You can also choose optimal to select instance types (from the C4,\n M4, and R4 instance families) that match the demand of your job queues.

\n

When updating a compute environment, changing this setting requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

When you create a compute environment, the instance types that you select for the compute environment must\n share the same architecture. For example, you can't mix x86 and ARM instances in the same compute\n environment.

\n \n \n

Currently, optimal uses instance types from the C4, M4, and R4 instance families. In Regions that\n don't have instance types from those instance families, instance types from the C5, M5. and R5 instance families are\n used.

\n " + } + }, + "ec2KeyPair": { + "target": "com.amazonaws.batch#String", + "traits": { + "smithy.api#documentation": "

The Amazon EC2 key pair that's used for instances launched in the compute environment. You can use this key pair to\n log in to your instances with SSH. To remove the Amazon EC2 key pair, set this value to an empty string.

\n

When updating a compute environment, changing the EC2 key pair requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " + } + }, + "instanceRole": { + "target": "com.amazonaws.batch#String", + "traits": { + "smithy.api#documentation": "

The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment. You can specify the short name\n or full Amazon Resource Name (ARN) of an instance profile. For example,\n \n ecsInstanceRole\n or\n arn:aws:iam:::instance-profile/ecsInstanceRole\n .\n For more information, see Amazon ECS instance\n role in the Batch User Guide.

\n

When updating a compute environment, changing this setting requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " + } + }, + "tags": { + "target": "com.amazonaws.batch#TagsMap", + "traits": { + "smithy.api#documentation": "

Key-value pair tags to be applied to EC2 resources that are launched in the compute environment. For Batch,\n these take the form of \"String1\": \"String2\", where String1 is the tag key and String2 is the tag value−for\n example, { \"Name\": \"Batch Instance - C4OnDemand\" }. This is helpful for recognizing your Batch\n instances in the Amazon EC2 console. These tags aren't seen when using the Batch ListTagsForResource API\n operation.

\n

When updating a compute environment, changing this setting requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " + } + }, + "placementGroup": { + "target": "com.amazonaws.batch#String", + "traits": { + "smithy.api#documentation": "

The Amazon EC2 placement group to associate with your compute resources. If you intend to submit multi-node parallel\n jobs to your compute environment, you should consider creating a cluster placement group and associate it with your\n compute resources. This keeps your multi-node parallel job on a logical grouping of instances within a single\n Availability Zone with high network flow potential. For more information, see Placement groups in the Amazon EC2 User Guide for\n Linux Instances.

\n

When updating a compute environment, changing the placement group requires an infrastructure update of the\n compute environment. For more information, see Updating compute environments in the\n Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " + } + }, + "bidPercentage": { + "target": "com.amazonaws.batch#Integer", + "traits": { + "smithy.api#documentation": "

The maximum percentage that a Spot Instance price can be when compared with the On-Demand price for that\n instance type before instances are launched. For example, if your maximum percentage is 20%, then the Spot price must\n be less than 20% of the current On-Demand price for that Amazon EC2 instance. You always pay the lowest (market) price and\n never more than your maximum percentage.

\n

When updating a compute environment, changing the bid percentage requires an infrastructure update of the\n compute environment. For more information, see Updating compute environments in the\n Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " + } + }, + "launchTemplate": { + "target": "com.amazonaws.batch#LaunchTemplateSpecification", + "traits": { + "smithy.api#documentation": "

The updated launch template to use for your compute resources. You must specify either the launch template ID or\n launch template name in the request, but not both. For more information, see Launch template support in the Batch User Guide.\n To remove the custom launch template and use the default launch template, set launchTemplateId or\n launchTemplateName member of the launch template specification to an empty string. Removing the launch\n template from a compute environment will not remove the AMI specified in the launch template. In order to update the\n AMI specified in a launch template, the updateToLatestImageVersion parameter must be set to\n true.

\n

When updating a compute environment, changing the launch template requires an infrastructure update of the\n compute environment. For more information, see Updating compute environments in the\n Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " + } + }, + "ec2Configuration": { + "target": "com.amazonaws.batch#Ec2ConfigurationList", + "traits": { + "smithy.api#documentation": "

Provides information used to select Amazon Machine Images (AMIs) for EC2 instances in the compute environment.\n If Ec2Configuration isn't specified, the default is ECS_AL2.

\n

When updating a compute environment, changing this setting requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide. To remove the EC2 configuration\n and any custom AMI ID specified in imageIdOverride, set this value to an empty string.

\n

One or two values can be provided.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n " + } + }, + "updateToLatestImageVersion": { + "target": "com.amazonaws.batch#Boolean", + "traits": { + "smithy.api#documentation": "

Specifies whether the AMI ID is updated to the latest one that's supported by Batch when the compute\n environment has an infrastructure update. The default value is false.

\n \n \n

If an AMI ID is specified in the imageId or imageIdOverride parameters or by the\n launch template specified in the launchTemplate parameter, this parameter is ignored. For more\n information on updating AMI IDs during an infrastructure update, see Updating the AMI ID in\n the Batch User Guide.

\n \n \n

When updating a compute environment, changing this setting requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide.

" + } + }, + "type": { + "target": "com.amazonaws.batch#CRType", + "traits": { + "smithy.api#documentation": "

The type of compute environment: EC2, SPOT, FARGATE, or\n FARGATE_SPOT. For more information, see Compute environments in the\n Batch User Guide.

\n

If you choose SPOT, you must also specify an Amazon EC2 Spot Fleet role with the\n spotIamFleetRole parameter. For more information, see Amazon EC2 spot fleet role in the\n Batch User Guide.

\n

When updating a compute environment, changing the type of a compute environment requires an infrastructure\n update of the compute environment. For more information, see Updating compute environments in the\n Batch User Guide.

" + } + }, + "imageId": { + "target": "com.amazonaws.batch#String", + "traits": { + "smithy.api#documentation": "

The Amazon Machine Image (AMI) ID used for instances launched in the compute environment. This parameter is\n overridden by the imageIdOverride member of the Ec2Configuration structure. To remove the\n custom AMI ID and use the default AMI ID, set this value to an empty string.

\n

When updating a compute environment, changing the AMI ID requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the Batch User Guide.

\n \n

This parameter isn't applicable to jobs that are running on Fargate resources, and shouldn't be\n specified.

\n \n \n

The AMI that you choose for a compute environment must match the architecture of the instance types that\n you intend to use for that compute environment. For example, if your compute environment uses A1 instance types,\n the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the\n Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized\n Amazon Linux 2 AMI\n in the Amazon Elastic Container Service Developer Guide.

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

An object representing the attributes of a compute environment that can be updated. For more information, see\n Compute Environments in the\n Batch User Guide.

" + "smithy.api#documentation": "

An object representing the attributes of a compute environment that can be updated. For more information, see\n Updating compute environments\n in the Batch User Guide.

" } }, "com.amazonaws.batch#ContainerDetail": { @@ -780,7 +872,7 @@ "executionRoleArn": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon Resource Name (ARN) of the\n execution\n role that Batch can assume. For more information, see Batch execution IAM role in the\n Batch User Guide.

" + "smithy.api#documentation": "

The Amazon Resource Name (ARN) of the execution role that Batch can assume. For more information, see Batch execution IAM role in the\n Batch User Guide.

" } }, "volumes": { @@ -882,7 +974,7 @@ "logConfiguration": { "target": "com.amazonaws.batch#LogConfiguration", "traits": { - "smithy.api#documentation": "

The log configuration specification for the container.

\n

This parameter maps to LogConfig in the Create a container section of the\n Docker Remote API and the --log-driver option to docker run.\n By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a\n different logging driver than the Docker daemon by specifying a log driver with this parameter in the container\n definition. To use a different logging driver for a container, the log system must be configured properly on the\n container instance. Or, alternatively, it must be configured on a different log server for remote logging options.\n For more information on the options for different supported log drivers, see Configure logging drivers in the Docker\n documentation.

\n \n

Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type). Additional log drivers might be available in future releases of the Amazon ECS\n container agent.

\n \n

This parameter requires version 1.18 of the Docker Remote API or greater on your\n container instance. To check the Docker Remote API version on your container instance, log into your\n container instance and run the following command: sudo docker version | grep \"Server API version\"\n

\n \n

The Amazon ECS container agent running on a container instance must register the logging drivers available on that\n instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that\n instance can use these log configuration options. For more information, see Amazon ECS Container Agent Configuration in the\n Amazon Elastic Container Service Developer Guide.

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

The log configuration specification for the container.

\n

This parameter maps to LogConfig in the Create a container section of the\n Docker Remote API and the --log-driver option to docker run.\n By default, containers use the same logging driver that the Docker daemon uses. However, the container might use a\n different logging driver than the Docker daemon by specifying a log driver with this parameter in the container\n definition. To use a different logging driver for a container, the log system must be configured properly on the\n container instance. Or, alternatively, it must be configured on a different log server for remote logging options.\n For more information on the options for different supported log drivers, see Configure logging drivers in the Docker\n documentation.

\n \n

Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type). Additional log drivers might be available in future releases of the Amazon ECS\n container agent.

\n \n

This parameter requires version 1.18 of the Docker Remote API or greater on your\n container instance. To check the Docker Remote API version on your container instance, log into your\n container instance and run the following command: sudo docker version | grep \"Server API version\"\n

\n \n

The Amazon ECS container agent running on a container instance must register the logging drivers available on that\n instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that\n instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the\n Amazon Elastic Container Service Developer Guide.

\n " } }, "secrets": { @@ -917,7 +1009,7 @@ "smithy.api#deprecated": { "message": "This field is deprecated, use resourceRequirements instead." }, - "smithy.api#documentation": "

This parameter is deprecated, use resourceRequirements to override the vcpus parameter\n that's set in the job definition. It's not supported for jobs running on Fargate resources. For jobs running on EC2\n resources, it overrides the vcpus parameter set in the job definition, but doesn't override any vCPU\n requirement specified in the resourceRequirements structure in the job definition. To override vCPU\n requirements that are specified in the resourceRequirements structure in the job definition,\n resourceRequirements must be specified in the SubmitJob request, with type\n set to VCPU and value set to the new value. For more information, see Can't override\n job definition resource requirements in the Batch User Guide.

" + "smithy.api#documentation": "

This parameter is deprecated, use resourceRequirements to override the vcpus parameter\n that's set in the job definition. It's not supported for jobs running on Fargate resources. For jobs running on EC2\n resources, it overrides the vcpus parameter set in the job definition, but doesn't override any vCPU\n requirement specified in the resourceRequirements structure in the job definition. To override vCPU\n requirements that are specified in the resourceRequirements structure in the job definition,\n resourceRequirements must be specified in the SubmitJob request, with type\n set to VCPU and value set to the new value. For more information, see Can't override job\n definition resource requirements in the Batch User Guide.

" } }, "memory": { @@ -926,7 +1018,7 @@ "smithy.api#deprecated": { "message": "This field is deprecated, use resourceRequirements instead." }, - "smithy.api#documentation": "

This parameter is deprecated, use resourceRequirements to override the memory requirements\n specified in the job definition. It's not supported for jobs running on Fargate resources. For jobs running on EC2\n resources, it overrides the memory parameter set in the job definition, but doesn't override any memory\n requirement specified in the resourceRequirements structure in the job definition. To override memory\n requirements that are specified in the resourceRequirements structure in the job definition,\n resourceRequirements must be specified in the SubmitJob request, with type\n set to MEMORY and value set to the new value. For more information, see Can't override\n job definition resource requirements in the Batch User Guide.

" + "smithy.api#documentation": "

This parameter is deprecated, use resourceRequirements to override the memory requirements\n specified in the job definition. It's not supported for jobs running on Fargate resources. For jobs running on EC2\n resources, it overrides the memory parameter set in the job definition, but doesn't override any memory\n requirement specified in the resourceRequirements structure in the job definition. To override memory\n requirements that are specified in the resourceRequirements structure in the job definition,\n resourceRequirements must be specified in the SubmitJob request, with type\n set to MEMORY and value set to the new value. For more information, see Can't override job\n definition resource requirements in the Batch User Guide.

" } }, "command": { @@ -994,7 +1086,7 @@ "jobRoleArn": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon Resource Name (ARN) of the IAM role that the container can assume for Amazon Web Services permissions. For more information, see\n IAM Roles for Tasks\n in the Amazon Elastic Container Service Developer Guide.

" + "smithy.api#documentation": "

The Amazon Resource Name (ARN) of the IAM role that the container can assume for Amazon Web Services permissions. For more information, see\n IAM roles for tasks\n in the Amazon Elastic Container Service Developer Guide.

" } }, "executionRoleArn": { @@ -1066,7 +1158,7 @@ "logConfiguration": { "target": "com.amazonaws.batch#LogConfiguration", "traits": { - "smithy.api#documentation": "

The log configuration specification for the container.

\n

This parameter maps to LogConfig in the Create a container section of the\n Docker Remote API and the --log-driver option to docker run.\n By default, containers use the same logging driver that the Docker daemon uses. However the container might use a\n different logging driver than the Docker daemon by specifying a log driver with this parameter in the container\n definition. To use a different logging driver for a container, the log system must be configured properly on the\n container instance (or on a different log server for remote logging options). For more information on the options for\n different supported log drivers, see Configure\n logging drivers in the Docker documentation.

\n \n

Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type).

\n \n

This parameter requires version 1.18 of the Docker Remote API or greater on your\n container instance. To check the Docker Remote API version on your container instance, log into your\n container instance and run the following command: sudo docker version | grep \"Server API version\"\n

\n \n

The Amazon ECS container agent running on a container instance must register the logging drivers available on that\n instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that\n instance can use these log configuration options. For more information, see Amazon ECS Container Agent Configuration in the\n Amazon Elastic Container Service Developer Guide.

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

The log configuration specification for the container.

\n

This parameter maps to LogConfig in the Create a container section of the\n Docker Remote API and the --log-driver option to docker run.\n By default, containers use the same logging driver that the Docker daemon uses. However the container might use a\n different logging driver than the Docker daemon by specifying a log driver with this parameter in the container\n definition. To use a different logging driver for a container, the log system must be configured properly on the\n container instance (or on a different log server for remote logging options). For more information on the options for\n different supported log drivers, see Configure\n logging drivers in the Docker documentation.

\n \n

Batch currently supports a subset of the logging drivers available to the Docker daemon (shown in the LogConfiguration data type).

\n \n

This parameter requires version 1.18 of the Docker Remote API or greater on your\n container instance. To check the Docker Remote API version on your container instance, log into your\n container instance and run the following command: sudo docker version | grep \"Server API version\"\n

\n \n

The Amazon ECS container agent running on a container instance must register the logging drivers available on that\n instance with the ECS_AVAILABLE_LOGGING_DRIVERS environment variable before containers placed on that\n instance can use these log configuration options. For more information, see Amazon ECS container agent configuration in the\n Amazon Elastic Container Service Developer Guide.

\n " } }, "secrets": { @@ -1263,7 +1355,7 @@ "computeEnvironmentOrder": { "target": "com.amazonaws.batch#ComputeEnvironmentOrders", "traits": { - "smithy.api#documentation": "

The set of compute environments mapped to a job queue and their order relative to each other. The job scheduler\n uses this parameter to determine which compute environment should run a specific job. Compute environments must be in\n the VALID state before you can associate them with a job queue. You can associate up to three compute\n environments with a job queue. All of the compute environments must be either EC2 (EC2 or\n SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute\n environments can't be mixed.

\n \n

All compute environments that are associated with a job queue must share the same architecture. Batch doesn't\n support mixing compute environment architecture types in a single job queue.

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

The set of compute environments mapped to a job queue and their order relative to each other. The job scheduler\n uses this parameter to determine which compute environment runs a specific job. Compute environments must be in\n the VALID state before you can associate them with a job queue. You can associate up to three compute\n environments with a job queue. All of the compute environments must be either EC2 (EC2 or\n SPOT) or Fargate (FARGATE or FARGATE_SPOT); EC2 and Fargate compute\n environments can't be mixed.

\n \n

All compute environments that are associated with a job queue must share the same architecture. Batch doesn't\n support mixing compute environment architecture types in a single job queue.

\n ", "smithy.api#required": {} } }, @@ -1344,6 +1436,9 @@ "smithy.api#documentation": "

The tags that you apply to the scheduling policy to help you categorize and organize your resources. Each tag\n consists of a key and an optional value. For more information, see Tagging Amazon Web Services Resources in Amazon Web Services General\n Reference.

\n

These tags can be updated or removed using the TagResource and UntagResource API operations.

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

Contains the parameters for CreateSchedulingPolicy.

" } }, "com.amazonaws.batch#CreateSchedulingPolicyResponse": { @@ -1488,6 +1583,9 @@ "smithy.api#required": {} } } + }, + "traits": { + "smithy.api#documentation": "

Contains the parameters for DeleteSchedulingPolicy.

" } }, "com.amazonaws.batch#DeleteSchedulingPolicyResponse": { @@ -1552,7 +1650,7 @@ } ], "traits": { - "smithy.api#documentation": "

Describes one or more of your compute environments.

\n

If you're using an unmanaged compute environment, you can use the DescribeComputeEnvironment\n operation to determine the ecsClusterArn that you should launch your Amazon ECS container instances\n into.

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

Describes one or more of your compute environments.

\n

If you're using an unmanaged compute environment, you can use the DescribeComputeEnvironment\n operation to determine the ecsClusterArn that you launch your Amazon ECS container instances\n into.

", "smithy.api#http": { "method": "POST", "uri": "/v1/describecomputeenvironments", @@ -1852,6 +1950,9 @@ "smithy.api#required": {} } } + }, + "traits": { + "smithy.api#documentation": "

Contains the parameters for DescribeSchedulingPolicies.

" } }, "com.amazonaws.batch#DescribeSchedulingPoliciesResponse": { @@ -1929,13 +2030,13 @@ "accessPointId": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The Amazon EFS access point ID to use. If an access point is specified, the root directory value specified in the\n EFSVolumeConfiguration must either be omitted or set to / which will enforce the path set\n on the EFS access point. If an access point is used, transit encryption must be enabled in the\n EFSVolumeConfiguration. For more information, see Working with Amazon EFS Access Points in the\n Amazon Elastic File System User Guide.

" + "smithy.api#documentation": "

The Amazon EFS access point ID to use. If an access point is specified, the root directory value specified in the\n EFSVolumeConfiguration must either be omitted or set to / which will enforce the path set\n on the EFS access point. If an access point is used, transit encryption must be enabled in the\n EFSVolumeConfiguration. For more information, see Working with Amazon EFS access points in the\n Amazon Elastic File System User Guide.

" } }, "iam": { "target": "com.amazonaws.batch#EFSAuthorizationConfigIAM", "traits": { - "smithy.api#documentation": "

Whether or not to use the Batch job IAM role defined in a job definition when mounting the Amazon EFS file system.\n If enabled, transit encryption must be enabled in the EFSVolumeConfiguration. If this parameter is\n omitted, the default value of DISABLED is used. For more information, see Using Amazon EFS Access Points in the\n Batch User Guide. EFS IAM authorization requires that TransitEncryption be\n ENABLED and that a JobRoleArn is specified.

" + "smithy.api#documentation": "

Whether or not to use the Batch job IAM role defined in a job definition when mounting the Amazon EFS file system.\n If enabled, transit encryption must be enabled in the EFSVolumeConfiguration. If this parameter is\n omitted, the default value of DISABLED is used. For more information, see Using Amazon EFS access points in the\n Batch User Guide. EFS IAM authorization requires that TransitEncryption be\n ENABLED and that a JobRoleArn is specified.

" } } }, @@ -1998,7 +2099,7 @@ "transitEncryptionPort": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you don't specify a\n transit encryption port, it uses the port selection strategy that the Amazon EFS mount helper uses. The value must be\n between 0 and 65,535. For more information, see EFS Mount Helper in the Amazon Elastic File System User Guide.

" + "smithy.api#documentation": "

The port to use when sending encrypted data between the Amazon ECS host and the Amazon EFS server. If you don't specify a\n transit encryption port, it uses the port selection strategy that the Amazon EFS mount helper uses. The value must be\n between 0 and 65,535. For more information, see EFS mount helper in the Amazon Elastic File System User Guide.

" } }, "authorizationConfig": { @@ -2018,14 +2119,14 @@ "imageType": { "target": "com.amazonaws.batch#ImageType", "traits": { - "smithy.api#documentation": "

The image type to match with the instance type to select an AMI. If the imageIdOverride parameter\n isn't specified, then a recent Amazon ECS-optimized Amazon Linux 2 AMI\n (ECS_AL2) is used.

\n
\n
ECS_AL2
\n
\n

\n Amazon Linux\n 2− Default for all non-GPU instance families.

\n
\n
ECS_AL2_NVIDIA
\n
\n

\n Amazon Linux\n 2 (GPU)−Default for all GPU instance families (for example P4 and G4) and\n can be used for all non Amazon Web Services Graviton-based instance types.

\n
\n
ECS_AL1
\n
\n

\n Amazon Linux.\n Amazon Linux is reaching the end-of-life of standard support. For more information, see Amazon Linux AMI.

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

The image type to match with the instance type to select an AMI. If the imageIdOverride parameter\n isn't specified, then a recent Amazon ECS-optimized Amazon Linux 2 AMI\n (ECS_AL2) is used. If a new image type is specified in an update, but neither an imageId nor a imageIdOverride parameter is specified, then the latest Amazon ECS optimized AMI for that image type\n that's supported by Batch is used.

\n
\n
ECS_AL2
\n
\n

\n Amazon Linux\n 2− Default for all non-GPU instance families.

\n
\n
ECS_AL2_NVIDIA
\n
\n

\n Amazon Linux\n 2 (GPU)−Default for all GPU instance families (for example P4 and G4) and\n can be used for all non Amazon Web Services Graviton-based instance types.

\n
\n
ECS_AL1
\n
\n

\n Amazon Linux.\n Amazon Linux is reaching the end-of-life of standard support. For more information, see Amazon Linux AMI.

\n
\n
", "smithy.api#required": {} } }, "imageIdOverride": { "target": "com.amazonaws.batch#ImageIdOverride", "traits": { - "smithy.api#documentation": "

The AMI ID used for instances launched in the compute environment that match the image type. This setting\n overrides the imageId set in the computeResource object.

" + "smithy.api#documentation": "

The AMI ID used for instances launched in the compute environment that match the image type. This setting\n overrides the imageId set in the computeResource object.

\n \n

The AMI that you choose for a compute environment must match the architecture of the instance types that\n you intend to use for that compute environment. For example, if your compute environment uses A1 instance types,\n the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the\n Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized\n Amazon Linux 2 AMI\n in the Amazon Elastic Container Service Developer Guide.

\n " } } }, @@ -2260,7 +2361,7 @@ "parameters": { "target": "com.amazonaws.batch#ParametersMap", "traits": { - "smithy.api#documentation": "

Default parameters or parameter substitution placeholders that are set in the job definition. Parameters are\n specified as a key-value pair mapping. Parameters in a SubmitJob request override any corresponding\n parameter defaults from the job definition. For more information about specifying parameters, see Job Definition Parameters in the\n Batch User Guide.

" + "smithy.api#documentation": "

Default parameters or parameter substitution placeholders that are set in the job definition. Parameters are\n specified as a key-value pair mapping. Parameters in a SubmitJob request override any corresponding\n parameter defaults from the job definition. For more information about specifying parameters, see Job definition parameters in the\n Batch User Guide.

" } }, "retryStrategy": { @@ -2390,7 +2491,7 @@ "status": { "target": "com.amazonaws.batch#JobStatus", "traits": { - "smithy.api#documentation": "

The current status for the job.

\n \n

If your jobs don't progress to STARTING, see Jobs Stuck in RUNNABLE Status in the\n troubleshooting section of the Batch User Guide.

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

The current status for the job.

\n \n

If your jobs don't progress to STARTING, see Jobs stuck in RUNNABLE status in the\n troubleshooting section of the Batch User Guide.

\n ", "smithy.api#required": {} } }, @@ -2452,7 +2553,7 @@ "jobDefinition": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The job definition that's used by this job.

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

The Amazon Resource Name (ARN) of the job definition that's used by this job.

", "smithy.api#required": {} } }, @@ -2521,6 +2622,15 @@ "target": "com.amazonaws.batch#JobDetail" } }, + "com.amazonaws.batch#JobExecutionTimeoutMinutes": { + "type": "long", + "traits": { + "smithy.api#range": { + "min": 1, + "max": 360 + } + } + }, "com.amazonaws.batch#JobQueueDetail": { "type": "structure", "members": { @@ -2789,7 +2899,7 @@ "version": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

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

\n

If the value is $Latest, the latest version of the launch template is used. If the value is\n $Default, the default version of the launch template is used.

\n \n

After the compute environment is created, the launch template version that's used isn't changed, even if the\n $Default or $Latest version for the launch template is updated. To use a new launch\n template version, create a new compute environment, add the new compute environment to the existing job queue,\n remove the old compute environment from the job queue, and delete the old compute environment.

\n \n

Default: $Default.

" + "smithy.api#documentation": "

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

\n

If the value is $Latest, the latest version of the launch template is used. If the value is\n $Default, the default version of the launch template is used.

\n \n

If the AMI ID that's used in a compute environment is from the launch template, the AMI isn't changed when the\n compute environment is updated. It's only changed if the updateToLatestImageVersion parameter for the compute\n environment is set to true. During an infrastructure update, if either $Latest or\n $Default is specified, Batch re-evaluates the launch template version, and it might use a different\n version of the launch template. This is the case even if the launch template isn't specified in the update. When\n updating a compute environment, changing the launch template requires an infrastructure update of the compute\n environment. For more information, see Updating compute environments in the\n Batch User Guide.

\n \n

Default: $Default.

" } } }, @@ -2833,7 +2943,7 @@ "swappiness": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

This allows you to tune a container's memory swappiness behavior. A swappiness value of\n 0 causes swapping not to happen unless absolutely necessary. A swappiness value of\n 100 causes pages to be swapped very aggressively. Accepted values are whole numbers between\n 0 and 100. If the swappiness parameter isn't specified, a default value of\n 60 is used. If a value isn't specified for maxSwap, then this parameter is ignored. If\n maxSwap is set to 0, the container doesn't use swap. This parameter maps to the\n --memory-swappiness option to docker run.

\n

Consider the following when you use a per-container swap configuration.

\n \n \n

This parameter isn't applicable to jobs that are running on Fargate resources and shouldn't be\n provided.

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

This allows you to tune a container's memory swappiness behavior. A swappiness value of\n 0 causes swapping not to happen unless absolutely necessary. A swappiness value of\n 100 causes pages to be swapped very aggressively. Accepted values are whole numbers between\n 0 and 100. If the swappiness parameter isn't specified, a default value of\n 60 is used. If a value isn't specified for maxSwap, then this parameter is ignored. If\n maxSwap is set to 0, the container doesn't use swap. This parameter maps to the\n --memory-swappiness option to docker run.

\n

Consider the following when you use a per-container swap configuration.

\n \n \n

This parameter isn't applicable to jobs that are running on Fargate resources and shouldn't be\n provided.

\n " } } }, @@ -2990,6 +3100,9 @@ "smithy.api#documentation": "

The nextToken value that's returned from a previous paginated ListSchedulingPolicies\n request where maxResults was used and the results exceeded the value of that parameter. Pagination\n continues from the end of the previous results that returned the nextToken value. This value is\n null when there are no more results to\n return.

\n \n

This token should be treated as an opaque identifier that's only used to\n retrieve the next items in a list and not for other programmatic purposes.

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

Contains the parameters for ListSchedulingPolicies.

" } }, "com.amazonaws.batch#ListSchedulingPoliciesResponse": { @@ -3045,6 +3158,9 @@ "smithy.api#required": {} } } + }, + "traits": { + "smithy.api#documentation": "

Contains the parameters for ListTagsForResource.

" } }, "com.amazonaws.batch#ListTagsForResourceResponse": { @@ -3064,7 +3180,7 @@ "logDriver": { "target": "com.amazonaws.batch#LogDriver", "traits": { - "smithy.api#documentation": "

The log driver to use for the container. The valid values listed for this parameter are log drivers that the\n Amazon ECS container agent can communicate with by default.

\n

The supported log drivers are awslogs, fluentd, gelf,\n json-file, journald, logentries, syslog, and\n splunk.

\n \n

Jobs that are running on Fargate resources are restricted to the awslogs and splunk\n log drivers.

\n \n
\n
awslogs
\n
\n

Specifies the Amazon CloudWatch Logs logging driver. For more information, see Using the awslogs Log Driver in the\n Batch User Guide and Amazon CloudWatch Logs logging driver in the Docker documentation.

\n
\n
fluentd
\n
\n

Specifies the Fluentd logging driver. For more information, including usage and options, see Fluentd logging driver in the Docker\n documentation.

\n
\n
gelf
\n
\n

Specifies the Graylog Extended Format (GELF) logging driver. For more information, including usage and\n options, see Graylog Extended Format logging\n driver in the Docker documentation.

\n
\n
journald
\n
\n

Specifies the journald logging driver. For more information, including usage and options, see Journald logging driver in the Docker\n documentation.

\n
\n
json-file
\n
\n

Specifies the JSON file logging driver. For more information, including usage and options, see JSON File logging driver in the Docker\n documentation.

\n
\n
splunk
\n
\n

Specifies the Splunk logging driver. For more information, including usage and options, see Splunk logging driver in the Docker\n documentation.

\n
\n
syslog
\n
\n

Specifies the syslog logging driver. For more information, including usage and options, see Syslog logging driver in the Docker\n documentation.

\n
\n
\n \n

If you have a custom driver that's not listed earlier that you want to work with the Amazon ECS container agent, you\n can fork the Amazon ECS container agent project that's available on\n GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that\n you want to have included. However, Amazon Web Services doesn't currently support running modified copies of this\n software.

\n \n

This parameter requires version 1.18 of the Docker Remote API or greater on your\n container instance. To check the Docker Remote API version on your container instance, log into your\n container instance and run the following command: sudo docker version | grep \"Server API version\"\n

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

The log driver to use for the container. The valid values listed for this parameter are log drivers that the\n Amazon ECS container agent can communicate with by default.

\n

The supported log drivers are awslogs, fluentd, gelf,\n json-file, journald, logentries, syslog, and\n splunk.

\n \n

Jobs that are running on Fargate resources are restricted to the awslogs and splunk\n log drivers.

\n \n
\n
awslogs
\n
\n

Specifies the Amazon CloudWatch Logs logging driver. For more information, see Using the awslogs log driver in the\n Batch User Guide and Amazon CloudWatch Logs logging driver in the Docker documentation.

\n
\n
fluentd
\n
\n

Specifies the Fluentd logging driver. For more information, including usage and options, see Fluentd logging driver in the Docker\n documentation.

\n
\n
gelf
\n
\n

Specifies the Graylog Extended Format (GELF) logging driver. For more information, including usage and\n options, see Graylog Extended Format logging\n driver in the Docker documentation.

\n
\n
journald
\n
\n

Specifies the journald logging driver. For more information, including usage and options, see Journald logging driver in the Docker\n documentation.

\n
\n
json-file
\n
\n

Specifies the JSON file logging driver. For more information, including usage and options, see JSON File logging driver in the Docker\n documentation.

\n
\n
splunk
\n
\n

Specifies the Splunk logging driver. For more information, including usage and options, see Splunk logging driver in the Docker\n documentation.

\n
\n
syslog
\n
\n

Specifies the syslog logging driver. For more information, including usage and options, see Syslog logging driver in the Docker\n documentation.

\n
\n
\n \n

If you have a custom driver that's not listed earlier that you want to work with the Amazon ECS container agent, you\n can fork the Amazon ECS container agent project that's available on\n GitHub and customize it to work with that driver. We encourage you to submit pull requests for changes that\n you want to have included. However, Amazon Web Services doesn't currently support running modified copies of this\n software.

\n \n

This parameter requires version 1.18 of the Docker Remote API or greater on your\n container instance. To check the Docker Remote API version on your container instance, log into your\n container instance and run the following command: sudo docker version | grep \"Server API version\"\n

", "smithy.api#required": {} } }, @@ -3077,7 +3193,7 @@ "secretOptions": { "target": "com.amazonaws.batch#SecretList", "traits": { - "smithy.api#documentation": "

The secrets to pass to the log configuration. For more information, see Specifying Sensitive Data in the\n Batch User Guide.

" + "smithy.api#documentation": "

The secrets to pass to the log configuration. For more information, see Specifying sensitive data in the\n Batch User Guide.

" } } }, @@ -3525,7 +3641,7 @@ "value": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The quantity of the specified resource to reserve for the container. The values vary based on the\n type specified.

\n
\n
type=\"GPU\"
\n
\n

The number of physical GPUs to reserve for the container. The number of GPUs reserved for all containers in a\n job shouldn't exceed the number of available GPUs on the compute resource that the job is launched on.

\n \n

GPUs are not available for jobs that are running on Fargate resources.

\n \n
\n
type=\"MEMORY\"
\n
\n

The memory hard limit (in MiB) present to the container. This parameter is supported for jobs that are\n running on EC2 resources. If your container attempts to exceed the memory specified, the container is terminated.\n This parameter maps to Memory in the Create a container section of the\n Docker Remote API and the --memory option to docker run.\n You must specify at least 4 MiB of memory for a job. This is required but can be specified in several places for\n multi-node parallel (MNP) jobs. It must be specified for each node at least once. This parameter maps to\n Memory in the Create a container section of the Docker Remote API and the\n --memory option to docker run.

\n \n

If you're trying to maximize your resource utilization by providing your jobs as much memory as possible for\n a particular instance type, see Memory\n Management in the Batch User Guide.

\n \n

For jobs that are running on Fargate resources, then value is the hard limit (in MiB), and\n must match one of the supported values and the VCPU values must be one of the values supported for\n that memory value.

\n
\n
value = 512
\n
\n

\n VCPU = 0.25

\n
\n
value = 1024
\n
\n

\n VCPU = 0.25 or 0.5

\n
\n
value = 2048
\n
\n

\n VCPU = 0.25, 0.5, or 1

\n
\n
value = 3072
\n
\n

\n VCPU = 0.5, or 1

\n
\n
value = 4096
\n
\n

\n VCPU = 0.5, 1, or 2

\n
\n
value = 5120, 6144, or 7168
\n
\n

\n VCPU = 1 or 2

\n
\n
value = 8192
\n
\n

\n VCPU = 1, 2, or 4

\n
\n
value = 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384
\n
\n

\n VCPU = 2 or 4

\n
\n
value = 17408, 18432, 19456, 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720
\n
\n

\n VCPU = 4

\n
\n
\n
\n
type=\"VCPU\"
\n
\n

The number of vCPUs reserved for the container. This parameter maps to CpuShares in the\n Create a container section of the Docker Remote API and the --cpu-shares option to\n docker run. Each vCPU is equivalent to 1,024 CPU shares. For EC2\n resources, you must specify at least one vCPU. This is required but can be specified in several places; it must be\n specified for each node at least once.

\n

For jobs that are running on Fargate resources, then value must match one of the supported\n values and the MEMORY values must be one of the values supported for that VCPU value.\n The supported values are 0.25, 0.5, 1, 2, and 4

\n
\n
value = 0.25
\n
\n

\n MEMORY = 512, 1024, or 2048

\n
\n
value = 0.5
\n
\n

\n MEMORY = 1024, 2048, 3072, or 4096

\n
\n
value = 1
\n
\n

\n MEMORY = 2048, 3072, 4096, 5120, 6144, 7168, or 8192

\n
\n
value = 2
\n
\n

\n MEMORY = 4096, 5120, 6144, 7168, 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384

\n
\n
value = 4
\n
\n

\n MEMORY = 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, 16384, 17408, 18432, 19456,\n 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720

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

The quantity of the specified resource to reserve for the container. The values vary based on the\n type specified.

\n
\n
type=\"GPU\"
\n
\n

The number of physical GPUs to reserve for the container. The number of GPUs reserved for all containers in a\n job shouldn't exceed the number of available GPUs on the compute resource that the job is launched on.

\n \n

GPUs are not available for jobs that are running on Fargate resources.

\n \n
\n
type=\"MEMORY\"
\n
\n

The memory hard limit (in MiB) present to the container. This parameter is supported for jobs that are\n running on EC2 resources. If your container attempts to exceed the memory specified, the container is terminated.\n This parameter maps to Memory in the Create a container section of the\n Docker Remote API and the --memory option to docker run.\n You must specify at least 4 MiB of memory for a job. This is required but can be specified in several places for\n multi-node parallel (MNP) jobs. It must be specified for each node at least once. This parameter maps to\n Memory in the Create a container section of the Docker Remote API and the\n --memory option to docker run.

\n \n

If you're trying to maximize your resource utilization by providing your jobs as much memory as possible for\n a particular instance type, see Memory\n management in the Batch User Guide.

\n \n

For jobs that are running on Fargate resources, then value is the hard limit (in MiB), and\n must match one of the supported values and the VCPU values must be one of the values supported for\n that memory value.

\n
\n
value = 512
\n
\n

\n VCPU = 0.25

\n
\n
value = 1024
\n
\n

\n VCPU = 0.25 or 0.5

\n
\n
value = 2048
\n
\n

\n VCPU = 0.25, 0.5, or 1

\n
\n
value = 3072
\n
\n

\n VCPU = 0.5, or 1

\n
\n
value = 4096
\n
\n

\n VCPU = 0.5, 1, or 2

\n
\n
value = 5120, 6144, or 7168
\n
\n

\n VCPU = 1 or 2

\n
\n
value = 8192
\n
\n

\n VCPU = 1, 2, or 4

\n
\n
value = 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384
\n
\n

\n VCPU = 2 or 4

\n
\n
value = 17408, 18432, 19456, 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720
\n
\n

\n VCPU = 4

\n
\n
\n
\n
type=\"VCPU\"
\n
\n

The number of vCPUs reserved for the container. This parameter maps to CpuShares in the\n Create a container section of the Docker Remote API and the --cpu-shares option to\n docker run. Each vCPU is equivalent to 1,024 CPU shares. For EC2\n resources, you must specify at least one vCPU. This is required but can be specified in several places; it must be\n specified for each node at least once.

\n

For jobs that are running on Fargate resources, then value must match one of the supported\n values and the MEMORY values must be one of the values supported for that VCPU value.\n The supported values are 0.25, 0.5, 1, 2, and 4

\n
\n
value = 0.25
\n
\n

\n MEMORY = 512, 1024, or 2048

\n
\n
value = 0.5
\n
\n

\n MEMORY = 1024, 2048, 3072, or 4096

\n
\n
value = 1
\n
\n

\n MEMORY = 2048, 3072, 4096, 5120, 6144, 7168, or 8192

\n
\n
value = 2
\n
\n

\n MEMORY = 4096, 5120, 6144, 7168, 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, or 16384

\n
\n
value = 4
\n
\n

\n MEMORY = 8192, 9216, 10240, 11264, 12288, 13312, 14336, 15360, 16384, 17408, 18432, 19456,\n 20480, 21504, 22528, 23552, 24576, 25600, 26624, 27648, 28672, 29696, or 30720

\n
\n
\n
\n
", "smithy.api#required": {} } }, @@ -3627,7 +3743,7 @@ "tags": { "target": "com.amazonaws.batch#TagrisTagsMap", "traits": { - "smithy.api#documentation": "

The tags that you apply to the scheduling policy to categorize and organize your resources. Each tag consists of\n a key and an optional value. For more information, see Tagging Amazon Web Services Resources in Amazon Web Services General\n Reference.

" + "smithy.api#documentation": "

The tags that you apply to the scheduling policy to categorize and organize your resources. Each tag consists of\n a key and an optional value. For more information, see Tagging Amazon Web Services resources in Amazon Web Services General\n Reference.

" } } }, @@ -3821,7 +3937,7 @@ "containerOverrides": { "target": "com.amazonaws.batch#ContainerOverrides", "traits": { - "smithy.api#documentation": "

A list of container overrides in the JSON format that specify the name of a container in the specified job\n definition and the overrides it should receive. You can override the default command for a container, which is\n specified in the job definition or the Docker image, with a command override. You can also override\n existing environment variables on a container or add new environment variables to it with an environment\n override.

" + "smithy.api#documentation": "

A list of container overrides in the JSON format that specify the name of a container in the specified job\n definition and the overrides it receives. You can override the default command for a container, which is specified in\n the job definition or the Docker image, with a command override. You can also override\n existing environment variables on a container or add new environment variables to it with an environment\n override.

" } }, "nodeOverrides": { @@ -3948,6 +4064,9 @@ "smithy.api#required": {} } } + }, + "traits": { + "smithy.api#documentation": "

Contains the parameters for TagResource.

" } }, "com.amazonaws.batch#TagResourceResponse": { @@ -4151,6 +4270,9 @@ "smithy.api#required": {} } } + }, + "traits": { + "smithy.api#documentation": "

Contains the parameters for UntagResource.

" } }, "com.amazonaws.batch#UntagResourceResponse": { @@ -4201,7 +4323,7 @@ "unmanagedvCpus": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The maximum number of vCPUs expected to be used for an unmanaged compute environment. This parameter should not\n be specified for a managed compute environment. This parameter is only used for fair share scheduling to reserve vCPU\n capacity for new share identifiers. If this parameter is not provided for a fair share job queue, no vCPU capacity\n will be reserved.

" + "smithy.api#documentation": "

The maximum number of vCPUs expected to be used for an unmanaged compute environment. Do not specify this\n parameter for a managed compute environment. This parameter is only used for fair share scheduling to reserve vCPU\n capacity for new share identifiers. If this parameter is not provided for a fair share job queue, no vCPU capacity\n will be reserved.

" } }, "computeResources": { @@ -4213,7 +4335,13 @@ "serviceRole": { "target": "com.amazonaws.batch#String", "traits": { - "smithy.api#documentation": "

The full Amazon Resource Name (ARN) of the IAM role that allows Batch to make calls to other Amazon Web Services services on your behalf.\n For more information, see Batch service IAM\n role in the Batch User Guide.

\n \n

If the compute environment has a service-linked role, it can't be changed to use a regular IAM role.\n Likewise, if the compute environment has a regular IAM role, it can't be changed to use a service-linked\n role.

\n \n

If your specified role has a path other than /, then you must either specify the full role ARN\n (this is recommended) or prefix the role name with the path.

\n \n

Depending on how you created your Batch service role, its ARN might contain the service-role\n path prefix. When you only specify the name of the service role, Batch assumes that your ARN doesn't use the\n service-role path prefix. Because of this, we recommend that you specify the full ARN of your service\n role when you create compute environments.

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

The full Amazon Resource Name (ARN) of the IAM role that allows Batch to make calls to other Amazon Web Services services on your behalf.\n For more information, see Batch service IAM\n role in the Batch User Guide.

\n \n

If the compute environment has a service-linked role, it can't be changed to use a regular IAM role.\n Likewise, if the compute environment has a regular IAM role, it can't be changed to use a service-linked role. To\n update the parameters for the compute environment that require an infrastructure update to change, the AWSServiceRoleForBatch service-linked role must be used. For more information, see\n Updating compute\n environments in the Batch User Guide.

\n \n

If your specified role has a path other than /, then you must either specify the full role ARN\n (recommended) or prefix the role name with the path.

\n \n

Depending on how you created your Batch service role, its ARN might contain the service-role\n path prefix. When you only specify the name of the service role, Batch assumes that your ARN doesn't use the\n service-role path prefix. Because of this, we recommend that you specify the full ARN of your service\n role when you create compute environments.

\n " + } + }, + "updatePolicy": { + "target": "com.amazonaws.batch#UpdatePolicy", + "traits": { + "smithy.api#documentation": "

Specifies the updated infrastructure update policy for the compute environment. For more information about\n infrastructure updates, see Updating\n compute environments in the Batch User Guide.

" } } }, @@ -4288,13 +4416,13 @@ "priority": { "target": "com.amazonaws.batch#Integer", "traits": { - "smithy.api#documentation": "

The priority of the job queue. Job queues with a higher priority (or a higher integer value for the\n priority parameter) are evaluated first when associated with the same compute environment. Priority is\n determined in descending order, for example, a job queue with a priority value of 10 is given scheduling\n preference over a job queue with a priority value of 1. All of the compute environments must be either\n EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT). EC2 and\n Fargate compute environments can't be mixed.

" + "smithy.api#documentation": "

The priority of the job queue. Job queues with a higher priority (or a higher integer value for the\n priority parameter) are evaluated first when associated with the same compute environment. Priority is\n determined in descending order. For example, a job queue with a priority value of 10 is given scheduling\n preference over a job queue with a priority value of 1. All of the compute environments must be either\n EC2 (EC2 or SPOT) or Fargate (FARGATE or FARGATE_SPOT). EC2 and\n Fargate compute environments can't be mixed.

" } }, "computeEnvironmentOrder": { "target": "com.amazonaws.batch#ComputeEnvironmentOrders", "traits": { - "smithy.api#documentation": "

Details the set of compute environments mapped to a job queue and their order relative to each other. This is\n one of the parameters used by the job scheduler to determine which compute environment should run a given job.\n Compute environments must be in the VALID state before you can associate them with a job queue. All of\n the compute environments must be either EC2 (EC2 or SPOT) or Fargate\n (FARGATE or FARGATE_SPOT). EC2 and Fargate compute environments can't be mixed.

\n \n

All compute environments that are associated with a job queue must share the same architecture. Batch doesn't\n support mixing compute environment architecture types in a single job queue.

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

Details the set of compute environments mapped to a job queue and their order relative to each other. This is\n one of the parameters used by the job scheduler to determine which compute environment runs a given job. Compute\n environments must be in the VALID state before you can associate them with a job queue. All of\n the compute environments must be either EC2 (EC2 or SPOT) or Fargate\n (FARGATE or FARGATE_SPOT). EC2 and Fargate compute environments can't be mixed.

\n \n

All compute environments that are associated with a job queue must share the same architecture. Batch doesn't\n support mixing compute environment architecture types in a single job queue.

\n " } } }, @@ -4319,6 +4447,26 @@ } } }, + "com.amazonaws.batch#UpdatePolicy": { + "type": "structure", + "members": { + "terminateJobsOnUpdate": { + "target": "com.amazonaws.batch#Boolean", + "traits": { + "smithy.api#documentation": "

Specifies whether jobs are automatically terminated when the computer environment infrastructure is updated. The\n default value is false.

" + } + }, + "jobExecutionTimeoutMinutes": { + "target": "com.amazonaws.batch#JobExecutionTimeoutMinutes", + "traits": { + "smithy.api#documentation": "

Specifies the job timeout, in minutes, when the compute environment infrastructure is updated. The default value\n is 30.

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

Specifies the infrastructure update policy for the compute environment. For more information about\n infrastructure updates, see Infrastructure updates\n in the Batch User Guide.

" + } + }, "com.amazonaws.batch#UpdateSchedulingPolicy": { "type": "operation", "input": { @@ -4360,6 +4508,9 @@ "smithy.api#documentation": "

The fair share policy.

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

Contains the parameters for UpdateSchedulingPolicy.

" } }, "com.amazonaws.batch#UpdateSchedulingPolicyResponse": { diff --git a/codegen/sdk-codegen/aws-models/cloudwatch.json b/codegen/sdk-codegen/aws-models/cloudwatch.json index 746a63d4042..51733b6f5c5 100644 --- a/codegen/sdk-codegen/aws-models/cloudwatch.json +++ b/codegen/sdk-codegen/aws-models/cloudwatch.json @@ -737,6 +737,9 @@ "input": { "target": "com.amazonaws.cloudwatch#DeleteAlarmsInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.cloudwatch#ResourceNotFound" @@ -1496,6 +1499,9 @@ "input": { "target": "com.amazonaws.cloudwatch#DisableAlarmActionsInput" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Disables the actions for the specified alarms. When an alarm's actions are disabled, the\n\t\t\talarm actions do not execute when the alarm state changes.

" } @@ -1560,6 +1566,9 @@ "input": { "target": "com.amazonaws.cloudwatch#EnableAlarmActionsInput" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Enables the actions for the specified alarms.

" } @@ -2173,7 +2182,7 @@ "StatisticsConfigurations": { "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsConfigurations", "traits": { - "smithy.api#documentation": "

Each entry in this array displays information about one or more metrics that include extended statistics\n\t\t\tin the metric stream. For more information about extended statistics, see \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions.

" + "smithy.api#documentation": "

Each entry in this array displays information about one or more metrics that include additional statistics\n\t\t\tin the metric stream. For more information about the additional statistics, see \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions.

" } } } @@ -3720,20 +3729,20 @@ "IncludeMetrics": { "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsIncludeMetrics", "traits": { - "smithy.api#documentation": "

An array of metric name and namespace pairs that stream the extended statistics listed\n\t\tin the value of the AdditionalStatistics parameter. There can be as many as \n\t\t100 pairs in the array.

\n\t\t

All metrics that match the combination of metric name and namespace will be streamed\n\t\twith the extended statistics, no matter their dimensions.

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

An array of metric name and namespace pairs that stream the additional statistics listed\n\t\tin the value of the AdditionalStatistics parameter. There can be as many as \n\t\t100 pairs in the array.

\n\t\t

All metrics that match the combination of metric name and namespace will be streamed\n\t\twith the additional statistics, no matter their dimensions.

", "smithy.api#required": {} } }, "AdditionalStatistics": { "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsAdditionalStatistics", "traits": { - "smithy.api#documentation": "

The list of extended statistics that are to be streamed for the metrics listed\n\t\tin the IncludeMetrics array in this structure. This list can include as many as 20 statistics.

\n\t\t

If the OutputFormat for the stream is opentelemetry0.7, the only \n\t\t\tvalid values are p??\n percentile statistics such as p90, p99 and so on.

\n\t\t

If the OutputFormat for the stream is json, \n\t\t\tthe valid values are include the abbreviations for all of the extended statistics listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions. For example, this includes\n\t\ttm98, \n wm90, PR(:300), and so on.

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

The list of additional statistics that are to be streamed for the metrics listed\n\t\tin the IncludeMetrics array in this structure. This list can include as many as 20 statistics.

\n\t\t

If the OutputFormat for the stream is opentelemetry0.7, the only \n\t\t\tvalid values are p??\n percentile statistics such as p90, p99 and so on.

\n\t\t

If the OutputFormat for the stream is json, \n\t\t\tthe valid values include the abbreviations for all of the statistics listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions. For example, this includes\n\t\ttm98, \n wm90, PR(:300), and so on.

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

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. This structure contains information for\n\t\t\tone metric that includes extended statistics in the stream. For more information about extended statistics, \n\t\t\tsee CloudWatch, listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions.

" + "smithy.api#documentation": "

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. This structure contains information for\n\t\t\tone metric that includes additional statistics in the stream. For more information about statistics, \n\t\t\tsee CloudWatch, listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions.

" } }, "com.amazonaws.cloudwatch#MetricStreamStatisticsConfigurations": { @@ -3754,7 +3763,7 @@ "Namespace": { "target": "com.amazonaws.cloudwatch#Namespace", "traits": { - "smithy.api#documentation": "

The metric namespace for the metric.

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

The namespace of the metric.

", "smithy.api#required": {} } }, @@ -3767,7 +3776,7 @@ } }, "traits": { - "smithy.api#documentation": "

This object contains the information for one metric that is to streamed with \n\t\textended statistics.

" + "smithy.api#documentation": "

This object contains the information for one metric that is to be streamed with \n\t\tadditional statistics.

" } }, "com.amazonaws.cloudwatch#MetricWidget": { @@ -3956,6 +3965,9 @@ "input": { "target": "com.amazonaws.cloudwatch#PutCompositeAlarmInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.cloudwatch#LimitExceededFault" @@ -4133,6 +4145,9 @@ "input": { "target": "com.amazonaws.cloudwatch#PutMetricAlarmInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.cloudwatch#LimitExceededFault" @@ -4253,7 +4268,7 @@ "TreatMissingData": { "target": "com.amazonaws.cloudwatch#TreatMissingData", "traits": { - "smithy.api#documentation": "

Sets how this alarm is to handle missing data points. If TreatMissingData is omitted, the default behavior of missing is used. \n\t\t\tFor more information, see Configuring How CloudWatch \n\t\t\t\tAlarms Treats Missing Data.

\n\t\t

Valid Values: breaching | notBreaching | ignore | missing\n

" + "smithy.api#documentation": "

Sets how this alarm is to handle missing data points. If TreatMissingData is omitted, the default behavior of missing is used. \n\t\t\tFor more information, see Configuring How CloudWatch \n\t\t\t\tAlarms Treats Missing Data.

\n\t\t

Valid Values: breaching | notBreaching | ignore | missing\n

\n\t\t \n

Alarms that evaluate metrics in the AWS/DynamoDB namespace always ignore\n\t\t\tmissing data even if you choose a different option for TreatMissingData. When an \n\t\t\tAWS/DynamoDB metric has missing data, alarms that evaluate that metric remain in their current state.

\n\t\t " } }, "EvaluateLowSampleCountPercentile": { @@ -4287,6 +4302,9 @@ "input": { "target": "com.amazonaws.cloudwatch#PutMetricDataInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.cloudwatch#InternalServiceFault" @@ -4350,7 +4368,7 @@ } ], "traits": { - "smithy.api#documentation": "

Creates or updates a metric stream. Metric streams can automatically stream CloudWatch metrics \n\t\t\tto Amazon Web Services destinations including\n\t\t\tAmazon S3 and to many third-party solutions.

\n\t\t

For more information, see \n\t\tUsing Metric Streams.

\n\t\t

To create a metric stream, \n\t\t\tyou must be logged on to an account that has the iam:PassRole permission\n\t\t\tand either the CloudWatchFullAccess\n\t\tpolicy or the cloudwatch:PutMetricStream \n\t\tpermission.

\n\t\t

When you create or update a metric stream, you choose one of the following:

\n\t\t \n\t\t\n\t\t

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. You can use the\n\t\t\tStatisticsConfigurations parameter to have \n\t\t\tthe metric stream also send extended statistics in the stream. Streaming extended statistics incurs\n\t\t\tadditional costs. For more information, see Amazon CloudWatch Pricing.

\n\t\t\n\t\t

When you use PutMetricStream to create a new metric stream, the stream \n\t\tis created in the running state. If you use it to update an existing stream, \n\t\tthe state of the stream is not changed.

" + "smithy.api#documentation": "

Creates or updates a metric stream. Metric streams can automatically stream CloudWatch metrics \n\t\t\tto Amazon Web Services destinations including\n\t\t\tAmazon S3 and to many third-party solutions.

\n\t\t

For more information, see \n\t\tUsing Metric Streams.

\n\t\t

To create a metric stream, \n\t\t\tyou must be logged on to an account that has the iam:PassRole permission\n\t\t\tand either the CloudWatchFullAccess\n\t\tpolicy or the cloudwatch:PutMetricStream \n\t\tpermission.

\n\t\t

When you create or update a metric stream, you choose one of the following:

\n\t\t \n\t\t\n\t\t

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. You can use the\n\t\t\tStatisticsConfigurations parameter to have \n\t\t\tthe metric stream also send additional statistics in the stream. Streaming additional statistics incurs\n\t\t\tadditional costs. For more information, see Amazon CloudWatch Pricing.

\n\t\t\n\t\t

When you use PutMetricStream to create a new metric stream, the stream \n\t\tis created in the running state. If you use it to update an existing stream, \n\t\tthe state of the stream is not changed.

" } }, "com.amazonaws.cloudwatch#PutMetricStreamInput": { @@ -4405,7 +4423,7 @@ "StatisticsConfigurations": { "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsConfigurations", "traits": { - "smithy.api#documentation": "

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. You can use this parameter to have \n\t\t\tthe metric stream also send extended statistics in the stream. This \n\t\t\tarray can have up to 100 members.

\n\t\t

For each entry in this array, you specify one or more metrics and the list of extended statistics to stream\n\t\t\tfor those metrics. The extended statistics that you can stream depend on the stream's OutputFormat.\n\t\t\tIf the OutputFormat is json, you can stream any extended statistic that is supported \n\t\t\tby CloudWatch, listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions. If the OutputFormat is \n\t\t\topentelemetry0.7, you can stream percentile statistics (p??).

" + "smithy.api#documentation": "

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. You can use this parameter to have \n\t\t\tthe metric stream also send additional statistics in the stream. This \n\t\t\tarray can have up to 100 members.

\n\t\t

For each entry in this array, you specify one or more metrics and the list of additional statistics to stream\n\t\t\tfor those metrics. The additional statistics that you can stream depend on the stream's OutputFormat.\n\t\t\tIf the OutputFormat is json, you can stream any additional statistic that is supported \n\t\t\tby CloudWatch, listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions. If the OutputFormat is \n\t\t\topentelemetry0.7, you can stream percentile statistics such as p95, p99.9 and so on.

" } } } @@ -4550,6 +4568,9 @@ "input": { "target": "com.amazonaws.cloudwatch#SetAlarmStateInput" }, + "output": { + "target": "smithy.api#Unit" + }, "errors": [ { "target": "com.amazonaws.cloudwatch#InvalidFormatFault" diff --git a/codegen/sdk-codegen/aws-models/ec2.json b/codegen/sdk-codegen/aws-models/ec2.json index 3b76f2454b2..2c469fb7ca1 100644 --- a/codegen/sdk-codegen/aws-models/ec2.json +++ b/codegen/sdk-codegen/aws-models/ec2.json @@ -426,7 +426,7 @@ "target": "com.amazonaws.ec2#AcceptVpcEndpointConnectionsResult" }, "traits": { - "smithy.api#documentation": "

Accepts one or more interface VPC endpoint connection requests to your VPC endpoint\n service.

" + "smithy.api#documentation": "

Accepts one or more interface VPC endpoint connection requests to your VPC endpoint service.

" } }, "com.amazonaws.ec2#AcceptVpcEndpointConnectionsRequest": { @@ -4087,6 +4087,9 @@ "input": { "target": "com.amazonaws.ec2#AssociateDhcpOptionsRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Associates a set of DHCP options (that you've previously created) with the specified VPC, or associates no DHCP options with the VPC.

\n

After you associate the options with the VPC, any existing instances and all new instances that you launch in that VPC use the options. You don't need to restart or relaunch the instances. They automatically pick up the changes within a few hours, depending on how frequently the instance renews its DHCP lease. You can explicitly renew the lease using the operating system on the instance.

\n

For more information, see DHCP options sets\n in the Amazon Virtual Private Cloud User Guide.

" } @@ -4964,6 +4967,9 @@ "input": { "target": "com.amazonaws.ec2#AttachInternetGatewayRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Attaches an internet gateway or a virtual private gateway to a VPC, enabling connectivity between the internet and\n\t\t\tthe VPC. For more information about your VPC and internet gateway, see the Amazon Virtual Private Cloud User Guide.

" } @@ -6697,6 +6703,9 @@ "input": { "target": "com.amazonaws.ec2#CancelConversionRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Cancels an active conversion task. The task can be the import of an instance or volume. The action removes all\n artifacts of the conversion, including a partially uploaded volume or instance. If the conversion is complete or is\n in the process of transferring the final disk image, the command fails and returns an exception.

\n

For more information, see Importing a Virtual Machine Using the Amazon\n EC2 CLI.

" } @@ -6706,6 +6715,9 @@ "input": { "target": "com.amazonaws.ec2#CancelExportTaskRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Cancels an active export task. The request removes all artifacts of the export, including any partially-created\n Amazon S3 objects. If the export task is complete or is in the process of transferring the final disk image, the\n command fails and returns an error.

" } @@ -10485,7 +10497,7 @@ "target": "com.amazonaws.ec2#CreateCustomerGatewayResult" }, "traits": { - "smithy.api#documentation": "

Provides information to Amazon Web Services about your VPN customer gateway device. The\n customer gateway is the appliance at your end of the VPN connection. (The device on the\n Amazon Web Services side of the VPN connection is the virtual private gateway.) You\n must provide the internet-routable IP address of the customer gateway's external\n interface. The IP address must be static and can be behind a device performing network\n address translation (NAT).

\n

For devices that use Border Gateway Protocol (BGP), you can also provide the device's\n BGP Autonomous System Number (ASN). You can use an existing ASN assigned to your\n network. If you don't have an ASN already, you can use a private ASN (in the 64512 -\n 65534 range).

\n \n

Amazon EC2 supports all 4-byte ASN numbers in the range of 1 - 2147483647, with\n the exception of the following:

\n \n \n

For more information, see Amazon Web Services Site-to-Site VPN in the Amazon Web Services Site-to-Site VPN\n User Guide.

\n \n

To create more than one customer gateway with the same VPN type, IP address, and\n BGP ASN, specify a unique device name for each customer gateway. Identical requests\n return information about the existing customer gateway and do not create new\n customer gateways.

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

Provides information to Amazon Web Services about your VPN customer gateway device. The\n customer gateway is the appliance at your end of the VPN connection. (The device on the\n Amazon Web Services side of the VPN connection is the virtual private gateway.) You\n must provide the internet-routable IP address of the customer gateway's external\n interface. The IP address must be static and can be behind a device performing network\n address translation (NAT).

\n

For devices that use Border Gateway Protocol (BGP), you can also provide the device's\n BGP Autonomous System Number (ASN). You can use an existing ASN assigned to your network.\n If you don't have an ASN already, you can use a private ASN. For more information, see \n Customer gateway \n options for your Site-to-Site VPN connection in the Amazon Web Services Site-to-Site VPN User Guide.

\n

To create more than one customer gateway with the same VPN type, IP address, and\n BGP ASN, specify a unique device name for each customer gateway. An identical request\n returns information about the existing customer gateway; it doesn't create a new customer\n gateway.

" } }, "com.amazonaws.ec2#CreateCustomerGatewayRequest": { @@ -11222,7 +11234,7 @@ "target": "com.amazonaws.ec2#CreateImageResult" }, "traits": { - "smithy.api#documentation": "

Creates an Amazon EBS-backed AMI from an Amazon EBS-backed instance \n \tthat is either running or stopped.

\n \n

By default, Amazon EC2 shuts down and reboots the instance before creating the AMI to ensure that everything on \n the instance is stopped and in a consistent state during the creation process. If you're confident that your \n instance is in a consistent state appropriate for AMI creation, use the NoReboot \n parameter to prevent Amazon EC2 from shutting down and rebooting the instance.

\n \n \n \n \n \t\n \t

If you customized your instance with instance store volumes or Amazon EBS volumes in addition to the root device volume, the \n \tnew AMI contains block device mapping information for those volumes. When you launch an instance from this new AMI, \n \tthe instance automatically launches with those additional volumes.

\n \t

For more information, see Creating Amazon EBS-Backed Linux AMIs \n\t\t\t\tin the Amazon Elastic Compute Cloud User Guide.

" + "smithy.api#documentation": "

Creates an Amazon EBS-backed AMI from an Amazon EBS-backed instance \n \tthat is either running or stopped.

\n\t

By default, when Amazon EC2 creates the new AMI, it reboots the instance so that it can \n\t\t\t\t\ttake snapshots of the attached volumes while data is at rest, in order to ensure a consistent \n\t\t\t\t\tstate. You can set the NoReboot parameter to true in the API request, \n\t\t\t\t\tor use the --no-reboot option in the CLI to prevent Amazon EC2 from shutting down and \n\t\t\t\t\trebooting the instance.

\n \t \n\t\t\t\t\t

If you choose to bypass the shutdown and reboot process by setting the NoReboot \n\t\t\t\t\tparameter to true in the API request, or by using the --no-reboot option \n\t\t\t\t\tin the CLI, we can't guarantee the file system integrity of the created image.

\n\t\t\t\t \n \n \n \n \t\n \t

If you customized your instance with instance store volumes or Amazon EBS volumes in addition to the root device volume, the \n \tnew AMI contains block device mapping information for those volumes. When you launch an instance from this new AMI, \n \tthe instance automatically launches with those additional volumes.

\n \t

For more information, see Creating Amazon EBS-Backed Linux AMIs \n\t\t\t\tin the Amazon Elastic Compute Cloud User Guide.

" } }, "com.amazonaws.ec2#CreateImageRequest": { @@ -11274,7 +11286,7 @@ "target": "com.amazonaws.ec2#Boolean", "traits": { "aws.protocols#ec2QueryName": "NoReboot", - "smithy.api#documentation": "

By default, Amazon EC2 attempts to shut down and reboot the instance before creating the image. \n If the No Reboot option is set, Amazon EC2 doesn't shut down the instance before creating \n the image. Without a reboot, the AMI will be crash consistent (all the volumes are snapshotted \n at the same time), but not application consistent (all the operating system buffers are not flushed \n to disk before the snapshots are created).

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

By default, when Amazon EC2 creates the new AMI, it reboots the instance so that it can \n\t\t\t\t\ttake snapshots of the attached volumes while data is at rest, in order to ensure a consistent \n\t\t\t\t\tstate. You can set the NoReboot parameter to true in the API request, \n\t\t\t\t\tor use the --no-reboot option in the CLI to prevent Amazon EC2 from shutting down and \n\t\t\t\t\trebooting the instance.

\n \t \n\t\t\t\t\t

If you choose to bypass the shutdown and reboot process by setting the NoReboot \n\t\t\t\t\tparameter to true in the API request, or by using the --no-reboot option \n\t\t\t\t\tin the CLI, we can't guarantee the file system integrity of the created image.

\n\t\t\t\t \n

Default: false (follow standard reboot process)

", "smithy.api#xmlName": "noReboot" } }, @@ -11488,7 +11500,7 @@ "target": "com.amazonaws.ec2#CreateIpamResult" }, "traits": { - "smithy.api#documentation": "

Create an IPAM. Amazon VCP IP Address Manager (IPAM) is a VPC feature that you can use to automate your IP address management workflows including assigning, tracking, troubleshooting, and auditing IP addresses across Amazon Web Services Regions and accounts throughout your Amazon Web Services Organization.

\n

For more information, see Create an IPAM in the Amazon VPC IPAM User Guide.\n

" + "smithy.api#documentation": "

Create an IPAM. Amazon VPC IP Address Manager (IPAM) is a VPC feature that you can use\n to automate your IP address management workflows including assigning, tracking,\n troubleshooting, and auditing IP addresses across Amazon Web Services Regions and accounts\n throughout your Amazon Web Services Organization.

\n

For more information, see Create an IPAM in the Amazon VPC IPAM User Guide.\n

" } }, "com.amazonaws.ec2#CreateIpamPool": { @@ -11763,7 +11775,7 @@ "KeyType": { "target": "com.amazonaws.ec2#KeyType", "traits": { - "smithy.api#documentation": "

The type of key pair. Note that ED25519 keys are not supported for Windows instances, EC2 Instance Connect, and EC2 Serial Console.

\n

Default: rsa\n

" + "smithy.api#documentation": "

The type of key pair. Note that ED25519 keys are not supported for Windows instances.

\n

Default: rsa\n

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

Creates a launch template. A launch template contains the parameters to launch an\n instance. When you launch an instance using RunInstances, you can\n specify a launch template instead of providing the launch parameters in the request. For\n more information, see Launching an instance from a\n launch template in the Amazon Elastic Compute Cloud User Guide.

" + "smithy.api#documentation": "

Creates a launch template.

\n

A launch template contains the parameters to launch an\n instance. When you launch an instance using RunInstances, you can\n specify a launch template instead of providing the launch parameters in the request. For\n more information, see Launching an instance from a\n launch template in the Amazon Elastic Compute Cloud User Guide.

\n

If you want to clone an existing launch template as the basis for creating a new\n launch template, you can use the Amazon EC2 console. The API, SDKs, and CLI do not support\n cloning a template. For more information, see Create a launch template from an existing launch template in the\n Amazon Elastic Compute Cloud User Guide.

" } }, "com.amazonaws.ec2#CreateLaunchTemplateRequest": { @@ -12219,6 +12231,9 @@ "input": { "target": "com.amazonaws.ec2#CreateNetworkAclEntryRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Creates an entry (a rule) in a network ACL with the specified rule number. Each network ACL has a set of numbered ingress rules \n\t\t and a separate set of numbered egress rules. When determining whether a packet should be allowed in or out of a subnet associated \n\t\t with the ACL, we process the entries in the ACL according to the rule numbers, in ascending order. Each network ACL has a set of \n\t\t ingress rules and a separate set of egress rules.

\n\t\t

We recommend that you leave room between the rule numbers (for example, 100, 110, 120, ...), and not number them one right after the \n\t\t other (for example, 101, 102, 103, ...). This makes it easier to add a rule between existing ones without having to renumber the rules.

\n\t\t

After you add an entry, you can't modify it; you must either replace it, or create an entry and delete the old one.

\n

For more information about network ACLs, see Network ACLs in the Amazon Virtual Private Cloud User Guide.

" } @@ -13729,6 +13744,9 @@ "input": { "target": "com.amazonaws.ec2#CreateTagsRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Adds or overwrites only the specified tags for the specified Amazon EC2 resource or\n resources. When you specify an existing tag key, the value is overwritten with\n the new value. Each resource can have a maximum of 50 tags. Each tag consists of a key and\n optional value. Tag keys must be unique per resource.

\n \n

For more information about tags, see Tagging Your Resources in the\n Amazon Elastic Compute Cloud User Guide. For more information about\n creating IAM policies that control users' access to resources based on tags, see Supported\n Resource-Level Permissions for Amazon EC2 API Actions in the Amazon\n Elastic Compute Cloud User Guide.

" } @@ -14923,7 +14941,7 @@ "target": "com.amazonaws.ec2#CreateVpcEndpointResult" }, "traits": { - "smithy.api#documentation": "

Creates a VPC endpoint for a specified service. An endpoint enables you to create a\n private connection between your VPC and the service. The service may be provided by Amazon Web Services,\n an Amazon Web Services Marketplace Partner, or another Amazon Web Services account. For more information, \n see VPC Endpoints in the\n Amazon Virtual Private Cloud User Guide.

\n

A gateway endpoint serves as a target for a route in your route table for\n traffic destined for the Amazon Web Service. You can specify an endpoint policy to attach \n to the endpoint, which will control access to the service from your VPC. You can also\n specify the VPC route tables that use the endpoint.

\n

An interface endpoint is a network interface in your subnet that\n serves as an endpoint for communicating with the specified service. You can specify the\n subnets in which to create an endpoint, and the security groups to associate with the\n endpoint network interface.

\n

A GatewayLoadBalancer endpoint is a network interface in your subnet that serves an endpoint for communicating with a Gateway Load Balancer that you've configured as a VPC endpoint service.

\n

Use DescribeVpcEndpointServices to get a list of supported\n services.

" + "smithy.api#documentation": "

Creates a VPC endpoint for a specified service. An endpoint enables you to create a\n private connection between your VPC and the service. The service may be provided by Amazon Web Services,\n an Amazon Web Services Marketplace Partner, or another Amazon Web Services account. For more information, \n see the Amazon Web Services PrivateLink Guide.

" } }, "com.amazonaws.ec2#CreateVpcEndpointConnectionNotification": { @@ -15115,7 +15133,7 @@ "target": "com.amazonaws.ec2#CreateVpcEndpointServiceConfigurationResult" }, "traits": { - "smithy.api#documentation": "

Creates a VPC endpoint service configuration to which service consumers (Amazon Web Services accounts,\n IAM users, and IAM roles) can connect.

\n

To create an endpoint service configuration, you must first create one of the\n following for your service:

\n \n

For more information, see VPC Endpoint Services in the\n Amazon Virtual Private Cloud User Guide.

\n

If you set the private DNS name, you must prove that you own the private DNS domain\n name. For more information, see VPC Endpoint Service\n Private DNS Name Verification in the\n Amazon Virtual Private Cloud User Guide.

" + "smithy.api#documentation": "

Creates a VPC endpoint service to which service consumers (Amazon Web Services accounts,\n IAM users, and IAM roles) can connect.

\n

Before you create an endpoint service, you must create one of the following for your service:

\n \n

If you set the private DNS name, you must prove that you own the private DNS domain\n name.

\n\t

For more information, see the Amazon Web Services PrivateLink \n\t Guide.

" } }, "com.amazonaws.ec2#CreateVpcEndpointServiceConfigurationRequest": { @@ -15130,7 +15148,7 @@ "AcceptanceRequired": { "target": "com.amazonaws.ec2#Boolean", "traits": { - "smithy.api#documentation": "

Indicates whether requests from service consumers to create an endpoint to your service must\n be accepted. To accept a request, use AcceptVpcEndpointConnections.

" + "smithy.api#documentation": "

Indicates whether requests from service consumers to create an endpoint to your service must\n be accepted manually.

" } }, "PrivateDnsName": { @@ -15451,6 +15469,9 @@ "input": { "target": "com.amazonaws.ec2#CreateVpnConnectionRouteRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Creates a static route associated with a VPN connection between an existing virtual\n private gateway and a VPN customer gateway. The static route allows traffic to be routed\n from the virtual private gateway to the VPN customer gateway.

\n

For more information, see Amazon Web Services Site-to-Site VPN in the Amazon Web Services Site-to-Site VPN\n User Guide.

" } @@ -15945,6 +15966,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteCustomerGatewayRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified customer gateway. You must delete the VPN connection before you\n can delete the customer gateway.

" } @@ -15977,6 +16001,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteDhcpOptionsRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified set of DHCP options. You must disassociate the set of DHCP options before you can delete it. You can disassociate the set of DHCP options by associating either a new set of options or the default set of options with the VPC.

" } @@ -16366,6 +16393,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteInternetGatewayRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified internet gateway. You must detach the internet gateway from the\n\t\t\tVPC before you can delete it.

" } @@ -16401,7 +16431,7 @@ "target": "com.amazonaws.ec2#DeleteIpamResult" }, "traits": { - "smithy.api#documentation": "

Delete an IPAM. Deleting an IPAM removes all monitored data associated with the IPAM including the historical data for CIDRs.

\n \n

You cannot delete an IPAM if there are CIDRs provisioned to pools or if there are allocations in the pools within the IPAM. To deprovision pool \n CIDRs, see DeprovisionIpamPoolCidr. To release allocations, see ReleaseIpamPoolAllocation.\n

\n \n

For more information, see Delete an IPAM in the Amazon VPC IPAM User Guide.\n

" + "smithy.api#documentation": "

Delete an IPAM. Deleting an IPAM removes all monitored data associated with the IPAM including the historical data for CIDRs.

\n

For more information, see Delete an IPAM in the Amazon VPC IPAM User Guide.\n

" } }, "com.amazonaws.ec2#DeleteIpamPool": { @@ -16532,6 +16562,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteKeyPairRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified key pair, by removing the public key from Amazon EC2.

" } @@ -16948,6 +16981,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteNetworkAclRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified network ACL. You can't delete the ACL if it's associated with any subnets. You can't delete the default network ACL.

" } @@ -16957,6 +16993,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteNetworkAclEntryRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified ingress or egress entry (rule) from the specified network ACL.

" } @@ -17200,6 +17239,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteNetworkInterfaceRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified network interface. You must detach the network interface before you can delete it.

" } @@ -17289,6 +17331,9 @@ "input": { "target": "com.amazonaws.ec2#DeletePlacementGroupRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified placement group. You must terminate all instances in the\n placement group before you can delete the placement group. For more information, see\n Placement groups in the Amazon EC2 User Guide.

" } @@ -17473,6 +17518,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteRouteRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified route from the specified route table.

" } @@ -17526,6 +17574,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteRouteTableRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified route table. You must disassociate the route table from any subnets before you can delete it. You can't delete the main route table.

" } @@ -17557,6 +17608,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteSecurityGroupRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes a security group.

\n

If you attempt to delete a security group that is associated with an instance, or is\n\t\t\t referenced by another security group, the operation fails with\n\t\t\t\tInvalidGroup.InUse in EC2-Classic or\n\t\t\t\tDependencyViolation in EC2-VPC.

" } @@ -17591,6 +17645,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteSnapshotRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified snapshot.

\n

When you make periodic snapshots of a volume, the snapshots are incremental, and only the\n blocks on the device that have changed since your last snapshot are saved in the new snapshot.\n When you delete a snapshot, only the data not needed for any other snapshot is removed. So\n regardless of which prior snapshots have been deleted, all active snapshots will have access\n to all the information needed to restore the volume.

\n

You cannot delete a snapshot of the root device of an EBS volume used by a registered AMI.\n You must first de-register the AMI before you can delete the snapshot.

\n

For more information, see Delete an Amazon EBS snapshot in the\n Amazon Elastic Compute Cloud User Guide.

" } @@ -17620,6 +17677,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteSpotDatafeedSubscriptionRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the data feed for Spot Instances.

" } @@ -17645,6 +17705,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteSubnetRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified subnet. You must terminate all running instances in the subnet before you can delete the subnet.

" } @@ -17717,6 +17780,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteTagsRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified set of tags from the specified set of resources.

\n

To list the current tags, use DescribeTags. For more information about tags, see \n Tagging Your Resources \n in the Amazon Elastic Compute Cloud User Guide.

" } @@ -18329,6 +18395,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteVolumeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified EBS volume. The volume must be in the available state\n (not attached to an instance).

\n

The volume can remain in the deleting state for several minutes.

\n

For more information, see Delete an Amazon EBS volume in the\n Amazon Elastic Compute Cloud User Guide.

" } @@ -18358,6 +18427,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteVpcRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

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

" } @@ -18572,6 +18644,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteVpnConnectionRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified VPN connection.

\n

If you're deleting the VPC and its associated components, we recommend that you detach\n the virtual private gateway from the VPC and delete the VPC before deleting the VPN\n connection. If you believe that the tunnel credentials for your VPN connection have been\n compromised, you can delete the VPN connection and create a new one that has new keys,\n without needing to delete the VPC or virtual private gateway. If you create a new VPN\n connection, you must reconfigure the customer gateway device using the new configuration\n information returned with the new VPN connection ID.

\n

For certificate-based authentication, delete all Certificate Manager (ACM) private\n certificates used for the Amazon Web Services-side tunnel endpoints for the VPN\n connection before deleting the VPN connection.

" } @@ -18604,6 +18679,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteVpnConnectionRouteRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified static route associated with a VPN connection between an\n existing virtual private gateway and a VPN customer gateway. The static route allows\n traffic to be routed from the virtual private gateway to the VPN customer\n gateway.

" } @@ -18635,6 +18713,9 @@ "input": { "target": "com.amazonaws.ec2#DeleteVpnGatewayRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deletes the specified virtual private gateway. You must first detach the virtual\n private gateway from the VPC. Note that you don't need to delete the virtual private\n gateway if you plan to delete and recreate the VPN connection between your VPC and your\n network.

" } @@ -18826,6 +18907,9 @@ "input": { "target": "com.amazonaws.ec2#DeregisterImageRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Deregisters the specified AMI. After you deregister an AMI, it can't be used to \n launch new instances.

\n \n \n

If you deregister an AMI that matches a Recycle Bin retention rule, the AMI is \n retained in the Recycle Bin for the specified retention period. For more information, \n see Recycle\n Bin in the Amazon Elastic Compute Cloud User Guide.

\n \n

When you deregister an AMI, it doesn't affect any instances that you've already \n launched from the AMI. You'll continue to incur usage costs for those instances until \n you terminate them.

\n \t

When you deregister an Amazon EBS-backed AMI, it doesn't affect the snapshot that was\n\t\t\tcreated for the root volume of the instance during the AMI creation process. When you\n\t\t\tderegister an instance store-backed AMI, it doesn't affect the files that you uploaded\n\t\t\tto Amazon S3 when you created the AMI.

" } @@ -22395,7 +22479,7 @@ "Filters": { "target": "com.amazonaws.ec2#FilterList", "traits": { - "smithy.api#documentation": "

The filters.

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

The filters.

\n ", "smithy.api#xmlName": "Filter" } }, @@ -24374,7 +24458,7 @@ "Filters": { "target": "com.amazonaws.ec2#FilterList", "traits": { - "smithy.api#documentation": "

One or more filters.

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

One or more filters.

\n ", "smithy.api#xmlName": "Filter" } }, @@ -30611,6 +30695,9 @@ "input": { "target": "com.amazonaws.ec2#DetachInternetGatewayRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Detaches an internet gateway from a VPC, disabling connectivity between the internet\n\t\t\tand the VPC. The VPC must not contain any running instances with Elastic IP addresses or\n\t\t\tpublic IPv4 addresses.

" } @@ -30651,6 +30738,9 @@ "input": { "target": "com.amazonaws.ec2#DetachNetworkInterfaceRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Detaches a network interface from an instance.

" } @@ -30743,6 +30833,9 @@ "input": { "target": "com.amazonaws.ec2#DetachVpnGatewayRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Detaches a virtual private gateway from a VPC. You do this if you're planning to turn\n off the VPC and not use it anymore. You can confirm a virtual private gateway has been\n completely detached from a VPC by describing the virtual private gateway (any\n attachments to the virtual private gateway are also described).

\n

You must wait for the attachment's state to switch to detached before you\n can delete the VPC or attach a different VPC to the virtual private gateway.

" } @@ -31506,6 +31599,9 @@ "input": { "target": "com.amazonaws.ec2#DisableVgwRoutePropagationRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Disables a virtual private gateway (VGW) from propagating routes to a specified route\n table of a VPC.

" } @@ -31627,6 +31723,9 @@ "input": { "target": "com.amazonaws.ec2#DisassociateAddressRequest" }, + "output": { + "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.

" } @@ -31854,6 +31953,9 @@ "input": { "target": "com.amazonaws.ec2#DisassociateRouteTableRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Disassociates a subnet or gateway from a route table.

\n\t\t

After you perform this action, the subnet no longer uses the routes in the route table.\n\t\t\t\tInstead, it uses the routes in the VPC's main route table. For more information\n\t\t\t\tabout route tables, see Route\n\t\t\t\ttables in the Amazon Virtual Private Cloud User Guide.

" } @@ -32539,7 +32641,7 @@ "target": "com.amazonaws.ec2#String", "traits": { "aws.protocols#ec2QueryName": "OutpostArn", - "smithy.api#documentation": "

The ARN of the Outpost on which the snapshot is stored.

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

The ARN of the Outpost on which the snapshot is stored.

\n

This parameter is only supported on BlockDeviceMapping objects called \n by \n CreateImage.

", "smithy.api#xmlName": "outpostArn" } }, @@ -33793,6 +33895,9 @@ "input": { "target": "com.amazonaws.ec2#EnableVgwRoutePropagationRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Enables a virtual private gateway (VGW) to propagate routes to the specified route\n table of a VPC.

" } @@ -33830,6 +33935,9 @@ "input": { "target": "com.amazonaws.ec2#EnableVolumeIORequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Enables I/O operations for a volume that had I/O operations disabled because the data on\n the volume was potentially inconsistent.

" } @@ -53788,6 +53896,9 @@ "input": { "target": "com.amazonaws.ec2#ModifyIdFormatRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies the ID format for the specified resource on a per-Region basis. You can\n specify that resources should receive longer IDs (17-character IDs) when they are\n created.

\n

This request can only be used to modify longer ID settings for resource types that\n are within the opt-in period. Resources currently in their opt-in period include:\n bundle | conversion-task | customer-gateway | dhcp-options |\n elastic-ip-allocation | elastic-ip-association |\n export-task | flow-log | image |\n import-task | internet-gateway | network-acl\n | network-acl-association | network-interface |\n network-interface-attachment | prefix-list |\n route-table | route-table-association |\n security-group | subnet |\n subnet-cidr-block-association | vpc |\n vpc-cidr-block-association | vpc-endpoint | vpc-peering-connection | vpn-connection | vpn-gateway.

\n

This setting applies to the IAM user who makes the request; it does not apply to the\n entire Amazon Web Services account. By default, an IAM user defaults to the same settings as the root user. If\n you're using this action as the root user, then these settings apply to the entire account,\n unless an IAM user explicitly overrides these settings for themselves. For more information,\n see Resource IDs \n in the Amazon Elastic Compute Cloud User Guide.

\n

Resources created with longer IDs are visible to all IAM roles and users, regardless\n of these settings and provided that they have permission to use the relevant\n Describe command for the resource type.

" } @@ -53816,6 +53927,9 @@ "input": { "target": "com.amazonaws.ec2#ModifyIdentityIdFormatRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies the ID format of a resource for a specified IAM user, IAM role, or the root\n user for an account; or all IAM users, IAM roles, and the root user for an account. You can\n specify that resources should receive longer IDs (17-character IDs) when they are created.

\n

This request can only be used to modify longer ID settings for resource types that are\n within the opt-in period. Resources currently in their opt-in period include:\n bundle | conversion-task | customer-gateway | dhcp-options |\n elastic-ip-allocation | elastic-ip-association |\n export-task | flow-log | image |\n import-task | internet-gateway | network-acl\n | network-acl-association | network-interface |\n network-interface-attachment | prefix-list |\n route-table | route-table-association |\n security-group | subnet |\n subnet-cidr-block-association | vpc |\n vpc-cidr-block-association | vpc-endpoint | vpc-peering-connection | vpn-connection | vpn-gateway.

\n

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

\n

This setting applies to the principal specified in the request; it does not apply to the\n principal that makes the request.

\n

Resources created with longer IDs are visible to all IAM roles and users, regardless of these\n settings and provided that they have permission to use the relevant Describe\n command for the resource type.

" } @@ -53857,6 +53971,9 @@ "input": { "target": "com.amazonaws.ec2#ModifyImageAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies the specified attribute of the specified AMI. You can specify only one attribute at a time.\n You can use the Attribute parameter to specify the attribute or one of the following parameters: \n Description or LaunchPermission.

\n \t

Images with an Amazon Web Services Marketplace product code cannot be made public.

\n

To enable the SriovNetSupport enhanced networking attribute of an image, enable SriovNetSupport on an instance \n and create an AMI from the instance.

" } @@ -53954,6 +54071,9 @@ "input": { "target": "com.amazonaws.ec2#ModifyInstanceAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies the specified attribute of the specified instance. You can specify only one\n attribute at a time.

\n

\n Note: Using this action to change the security groups\n associated with an elastic network interface (ENI) attached to an instance in a VPC can\n result in an error if the instance has more than one ENI. To change the security groups\n associated with an ENI attached to an instance that has multiple ENIs, we recommend that\n you use the ModifyNetworkInterfaceAttribute action.

\n

To modify some attributes, the instance must be stopped. For more information, see\n Modify a stopped instance in the\n Amazon EC2 User Guide.

" } @@ -54956,6 +55076,9 @@ "input": { "target": "com.amazonaws.ec2#ModifyNetworkInterfaceAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies the specified network interface attribute. You can specify only one\n attribute at a time. You can use this action to attach and detach security groups from\n an existing EC2 instance.

" } @@ -55192,6 +55315,9 @@ "input": { "target": "com.amazonaws.ec2#ModifySnapshotAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Adds or removes permission settings for the specified snapshot. You may add or remove\n specified Amazon Web Services account IDs from a snapshot's list of create volume permissions, but you cannot\n do both in a single operation. If you need to both add and remove account IDs for a snapshot,\n you must use multiple operations. You can make up to 500 modifications to a snapshot in a single operation.

\n

Encrypted snapshots and snapshots with Amazon Web Services Marketplace product codes cannot be made\n public. Snapshots encrypted with your default KMS key cannot be shared with other accounts.

\n

For more information about modifying snapshot permissions, see Share a snapshot in the\n Amazon Elastic Compute Cloud User Guide.

" } @@ -55390,6 +55516,9 @@ "input": { "target": "com.amazonaws.ec2#ModifySubnetAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies a subnet attribute. You can only modify one attribute at a time.

\n\t \n\t

Use this action to modify subnets on Amazon Web Services Outposts.

\n \n\t \n\t

For more information about Amazon Web Services Outposts, see the following:

\n\t \n\t " } @@ -55989,7 +56118,7 @@ "target": "com.amazonaws.ec2#ModifyVolumeResult" }, "traits": { - "smithy.api#documentation": "

You can modify several parameters of an existing EBS volume, including volume size, volume\n type, and IOPS capacity. If your EBS volume is attached to a current-generation EC2 instance\n type, you might be able to apply these changes without stopping the instance or detaching the\n volume from it. For more information about modifying EBS volumes, see Amazon EBS Elastic Volumes (Linux instances) \n or Amazon EBS Elastic Volumes (Windows instances).

\n

When you complete a resize operation on your volume, you need to extend the volume's\n file-system size to take advantage of the new storage capacity. For more information, see Extend a Linux file system or \n Extend a Windows file system.

\n

You can use CloudWatch Events to check the status of a modification to an EBS volume. For\n information about CloudWatch Events, see the Amazon CloudWatch Events User Guide. You can also track the status of a\n modification using DescribeVolumesModifications. For information\n about tracking status changes using either method, see Monitor the progress of volume modifications.

\n

With previous-generation instance types, resizing an EBS volume might require detaching and\n reattaching the volume or stopping and restarting the instance.

\n

If you reach the maximum volume modification rate per volume limit, you must wait\n at least six hours before applying further modifications to the affected EBS volume.

" + "smithy.api#documentation": "

You can modify several parameters of an existing EBS volume, including volume size, volume\n type, and IOPS capacity. If your EBS volume is attached to a current-generation EC2 instance\n type, you might be able to apply these changes without stopping the instance or detaching the\n volume from it. For more information about modifying EBS volumes, see Amazon EBS Elastic Volumes (Linux instances) \n or Amazon EBS Elastic Volumes (Windows instances).

\n

When you complete a resize operation on your volume, you need to extend the volume's\n file-system size to take advantage of the new storage capacity. For more information, see Extend a Linux file system or \n Extend a Windows file system.

\n

You can use CloudWatch Events to check the status of a modification to an EBS volume. For\n information about CloudWatch Events, see the Amazon CloudWatch Events User Guide. You can also track the status of a\n modification using DescribeVolumesModifications. For information\n about tracking status changes using either method, see Monitor the progress of volume modifications.

\n

With previous-generation instance types, resizing an EBS volume might require detaching and\n reattaching the volume or stopping and restarting the instance.

\n

After modifying a volume, you must wait at least six hours and ensure that the volume \n is in the in-use or available state before you can modify the same \n volume. This is sometimes referred to as a cooldown period.

" } }, "com.amazonaws.ec2#ModifyVolumeAttribute": { @@ -55997,6 +56126,9 @@ "input": { "target": "com.amazonaws.ec2#ModifyVolumeAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies a volume attribute.

\n

By default, all I/O operations for the volume are suspended when the data on the volume is\n determined to be potentially inconsistent, to prevent undetectable, latent data corruption.\n The I/O access to the volume can be resumed by first enabling I/O access and then checking the\n data consistency on your volume.

\n

You can change the default behavior to resume I/O operations. We recommend that you change\n this only for boot volumes or for volumes that are stateless or disposable.

" } @@ -56093,6 +56225,9 @@ "input": { "target": "com.amazonaws.ec2#ModifyVpcAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Modifies the specified attribute of the specified VPC.

" } @@ -56132,7 +56267,7 @@ "target": "com.amazonaws.ec2#ModifyVpcEndpointResult" }, "traits": { - "smithy.api#documentation": "

Modifies attributes of a specified VPC endpoint. The attributes that you can modify\n depend on the type of VPC endpoint (interface, gateway, or Gateway Load Balancer). For more information, see\n VPC\n Endpoints in the Amazon Virtual Private Cloud User Guide.

" + "smithy.api#documentation": "

Modifies attributes of a specified VPC endpoint. The attributes that you can modify\n depend on the type of VPC endpoint (interface, gateway, or Gateway Load Balancer). For more information, \n see the Amazon Web Services PrivateLink \n Guide.

" } }, "com.amazonaws.ec2#ModifyVpcEndpointConnectionNotification": { @@ -56293,7 +56428,7 @@ "target": "com.amazonaws.ec2#ModifyVpcEndpointServiceConfigurationResult" }, "traits": { - "smithy.api#documentation": "

Modifies the attributes of your VPC endpoint service configuration. You can change the\n Network Load Balancers or Gateway Load Balancers for your service, and you can specify whether acceptance is\n required for requests to connect to your endpoint service through an interface VPC\n endpoint.

\n\t

If you set or modify the private DNS name, you must prove that you own the private DNS\n domain name. For more information, see VPC Endpoint Service\n Private DNS Name Verification in the\n Amazon Virtual Private Cloud User Guide.

" + "smithy.api#documentation": "

Modifies the attributes of your VPC endpoint service configuration. You can change the\n Network Load Balancers or Gateway Load Balancers for your service, and you can specify whether acceptance is\n required for requests to connect to your endpoint service through an interface VPC\n endpoint.

\n\t

If you set or modify the private DNS name, you must prove that you own the private DNS\n domain name.

" } }, "com.amazonaws.ec2#ModifyVpcEndpointServiceConfigurationRequest": { @@ -56432,7 +56567,7 @@ "target": "com.amazonaws.ec2#ModifyVpcEndpointServicePermissionsResult" }, "traits": { - "smithy.api#documentation": "

Modifies the permissions for your VPC endpoint service. You can add or remove permissions for service consumers (IAM users, \n\t IAM roles, and Amazon Web Services accounts) to connect to your endpoint service.

\n\t

If you grant permissions to all principals, the service is public. Any users who know the name of a\n\t public service can send a request to attach an endpoint. If the service does not require manual approval,\n\t attachments are automatically approved.

" + "smithy.api#documentation": "

Modifies the permissions for your VPC endpoint service. You can add or remove permissions for service consumers \n\t (IAM users, IAM roles, and Amazon Web Services accounts) to connect to your endpoint service.

\n\t

If you grant permissions to all principals, the service is public. Any users who know the name of a\n\t public service can send a request to attach an endpoint. If the service does not require manual approval,\n\t attachments are automatically approved.

" } }, "com.amazonaws.ec2#ModifyVpcEndpointServicePermissionsRequest": { @@ -60937,7 +61072,7 @@ } }, "traits": { - "smithy.api#documentation": "

Information about the private DNS name for the service endpoint. For more information\n about these parameters, see VPC Endpoint Service\n Private DNS Name Verification in the\n Amazon Virtual Private Cloud User Guide.

" + "smithy.api#documentation": "

Information about the private DNS name for the service endpoint.

" } }, "com.amazonaws.ec2#PrivateDnsNameOptionsOnLaunch": { @@ -62042,6 +62177,9 @@ "input": { "target": "com.amazonaws.ec2#RebootInstancesRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Requests a reboot of the specified instances. This operation is asynchronous; it only\n queues a request to reboot the specified instances. The operation succeeds if the\n instances are valid and belong to you. Requests to reboot terminated instances are\n ignored.

\n

If an instance does not cleanly shut down within a few minutes, Amazon EC2 performs a\n hard reboot.

\n

For more information about troubleshooting, see Troubleshoot an unreachable\n instance in the Amazon EC2 User Guide.

" } @@ -62777,6 +62915,9 @@ "input": { "target": "com.amazonaws.ec2#ReleaseAddressRequest" }, + "output": { + "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.

" } @@ -63074,6 +63215,9 @@ "input": { "target": "com.amazonaws.ec2#ReplaceNetworkAclEntryRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Replaces an entry (rule) in a network ACL. For more information, see Network ACLs in the\n\t\t\t\tAmazon Virtual Private Cloud User Guide.

" } @@ -63280,6 +63424,9 @@ "input": { "target": "com.amazonaws.ec2#ReplaceRouteRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Replaces an existing route within a route table in a VPC. You must provide only one of\n the following: internet gateway, virtual private gateway, NAT instance, NAT gateway, VPC\n peering connection, network interface, egress-only internet gateway, or transit\n gateway.

\n

For more information, see Route tables in the\n Amazon Virtual Private Cloud User Guide.

" } @@ -63601,6 +63748,9 @@ "input": { "target": "com.amazonaws.ec2#ReportInstanceStatusRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Submits feedback about the status of an instance. The instance must be in the\n running state. If your experience with the instance differs from the\n instance status returned by DescribeInstanceStatus, use ReportInstanceStatus to report your experience with the instance. Amazon\n EC2 collects this information to improve the accuracy of status checks.

\n

Use of this action does not change the value returned by DescribeInstanceStatus.

" } @@ -63936,7 +64086,7 @@ } }, "traits": { - "smithy.api#documentation": "

The information to include in the launch template.

" + "smithy.api#documentation": "

The information to include in the launch template.

\n \n

You must specify at least one parameter for the launch template data.

\n " } }, "com.amazonaws.ec2#RequestSpotFleet": { @@ -65329,6 +65479,9 @@ "input": { "target": "com.amazonaws.ec2#ResetImageAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Resets an attribute of an AMI to its default value.

" } @@ -65379,6 +65532,9 @@ "input": { "target": "com.amazonaws.ec2#ResetInstanceAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Resets an attribute of an instance to its default value. To reset the\n kernel or ramdisk, the instance must be in a stopped\n state. To reset the sourceDestCheck, the instance can be either running or\n stopped.

\n

The sourceDestCheck attribute controls whether source/destination\n checking is enabled. The default value is true, which means checking is\n enabled. This value must be false for a NAT instance to perform NAT. For\n more information, see NAT Instances in the\n Amazon VPC User Guide.

" } @@ -65419,6 +65575,9 @@ "input": { "target": "com.amazonaws.ec2#ResetNetworkInterfaceAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Resets a network interface attribute. You can specify only one attribute at a time.

" } @@ -65461,6 +65620,9 @@ "input": { "target": "com.amazonaws.ec2#ResetSnapshotAttributeRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Resets permission settings for the specified snapshot.

\n

For more information about modifying snapshot permissions, see Share a snapshot in the\n Amazon Elastic Compute Cloud User Guide.

" } @@ -67344,7 +67506,7 @@ "UserData": { "target": "com.amazonaws.ec2#String", "traits": { - "smithy.api#documentation": "

The user data to make available to the instance. For more information, see Run commands on\n your Linux instance at launch and Run commands on your\n Windows instance at launch. If you are using a command line tool,\n base64-encoding is performed for you, and you can load the text from a file. Otherwise,\n you must provide base64-encoded text. User data is limited to 16 KB.

" + "smithy.api#documentation": "

The user data script to make available to the instance. For more information, see Run commands\n on your Linux instance at launch and Run commands on your Windows instance at launch. If you are using a command line tool,\n base64-encoding is performed for you, and you can load the text from a file. Otherwise,\n you must provide base64-encoded text. User data is limited to 16 KB.

" } }, "AdditionalInfo": { @@ -69042,6 +69204,9 @@ "input": { "target": "com.amazonaws.ec2#SendDiagnosticInterruptRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Sends a diagnostic interrupt to the specified Amazon EC2 instance to trigger a\n kernel panic (on Linux instances), or a blue\n screen/stop error (on Windows instances). For\n instances based on Intel and AMD processors, the interrupt is received as a\n non-maskable interrupt (NMI).

\n\n

In general, the operating system crashes and reboots when a kernel panic or stop error\n is triggered. The operating system can also be configured to perform diagnostic tasks,\n such as generating a memory dump file, loading a secondary kernel, or obtaining a call\n trace.

\n\n

Before sending a diagnostic interrupt to your instance, ensure that its operating\n system is configured to perform the required diagnostic tasks.

\n\n

For more information about configuring your operating system to generate a crash dump\n when a kernel panic or stop error occurs, see Send a diagnostic interrupt\n (for advanced users) (Linux instances) or Send a diagnostic\n interrupt (for advanced users) (Windows instances).

" } @@ -71696,7 +71861,7 @@ "target": "com.amazonaws.ec2#StartVpcEndpointServicePrivateDnsVerificationResult" }, "traits": { - "smithy.api#documentation": "

Initiates the verification process to prove that the service provider owns the private\n DNS name domain for the endpoint service.

\n

The service provider must successfully perform the verification before the consumer can use the name to access the service.

\n

Before the service provider runs this command, they must add a record to the DNS server. For more information, see Adding a TXT Record to Your Domain's DNS Server in the Amazon VPC User Guide.

" + "smithy.api#documentation": "

Initiates the verification process to prove that the service provider owns the private\n DNS name domain for the endpoint service.

\n

The service provider must successfully perform the verification before the consumer can use the name to access the service.

\n

Before the service provider runs this command, they must add a record to the DNS server.

" } }, "com.amazonaws.ec2#StartVpcEndpointServicePrivateDnsVerificationRequest": { @@ -76531,6 +76696,9 @@ "input": { "target": "com.amazonaws.ec2#UnassignPrivateIpAddressesRequest" }, + "output": { + "target": "smithy.api#Unit" + }, "traits": { "smithy.api#documentation": "

Unassigns one or more secondary private IP addresses, or IPv4 Prefix Delegation prefixes from a network interface.

" } diff --git a/codegen/sdk-codegen/aws-models/glue.json b/codegen/sdk-codegen/aws-models/glue.json index ddd4c8d73f8..9b1c77d06c2 100644 --- a/codegen/sdk-codegen/aws-models/glue.json +++ b/codegen/sdk-codegen/aws-models/glue.json @@ -13646,6 +13646,12 @@ "traits": { "smithy.api#documentation": "

Glue version determines the versions of Apache Spark and Python that Glue supports. The Python version indicates the version supported for jobs of type Spark.

\n \n

For more information about the available Glue versions and corresponding Spark and Python versions, see Glue version in the developer guide.

\n\t \n\t

Jobs that are created without specifying a Glue version default to Glue 0.9.

" } + }, + "DPUSeconds": { + "target": "com.amazonaws.glue#NullableDouble", + "traits": { + "smithy.api#documentation": "

This field populates only when an Auto Scaling job run completes, and represents the total time each executor ran during the lifecycle of a job run in seconds, multiplied by a DPU factor (1 for G.1X and 2 for G.2X workers). This value may be different than the executionEngineRuntime * MaxCapacity as in the case of Auto Scaling jobs, as the number of executors running at a given time may be less than the MaxCapacity. Therefore, it is possible that the value of DPUSeconds is less than executionEngineRuntime * MaxCapacity.

" + } } }, "traits": {