botocore 1.38.17__tar.gz → 1.38.18__tar.gz

{botocore-1.38.17/botocore.egg-info → botocore-1.38.18}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: botocore
-Version: 1.38.17
+Version: 1.38.18
 Summary: Low-level, data-driven core of boto 3.
 Home-page: https://github.com/boto/botocore
 Author: Amazon Web Services

{botocore-1.38.17 → botocore-1.38.18}/botocore/__init__.py

@@ -16,7 +16,7 @@ import logging
 import os
 import re
 
-__version__ = '1.38.17'
+__version__ = '1.38.18'
 
 
 class NullHandler(logging.Handler):

{botocore-1.38.17 → botocore-1.38.18}/botocore/data/bedrock-data-automation/2023-07-26/service-2.json

@@ -1275,7 +1275,8 @@
       "enum":[
         "DOCUMENT",
         "IMAGE",
-        "AUDIO"
+        "AUDIO",
+        "VIDEO"
       ]
     },
     "UntagResourceRequest":{

{botocore-1.38.17 → botocore-1.38.18}/botocore/data/bedrock-data-automation-runtime/2024-06-13/service-2.json

@@ -24,8 +24,8 @@
       "input":{"shape":"GetDataAutomationStatusRequest"},
       "output":{"shape":"GetDataAutomationStatusResponse"},
       "errors":[
-        {"shape":"AccessDeniedException"},
         {"shape":"ValidationException"},
+        {"shape":"AccessDeniedException"},
         {"shape":"InternalServerException"},
         {"shape":"ThrottlingException"},
         {"shape":"ResourceNotFoundException"}
@@ -42,8 +42,8 @@
       "output":{"shape":"InvokeDataAutomationAsyncResponse"},
       "errors":[
         {"shape":"ServiceQuotaExceededException"},
-        {"shape":"AccessDeniedException"},
         {"shape":"ValidationException"},
+        {"shape":"AccessDeniedException"},
         {"shape":"InternalServerException"},
         {"shape":"ThrottlingException"}
       ],
@@ -59,11 +59,11 @@
       "input":{"shape":"ListTagsForResourceRequest"},
       "output":{"shape":"ListTagsForResourceResponse"},
       "errors":[
-        {"shape":"AccessDeniedException"},
         {"shape":"ValidationException"},
+        {"shape":"AccessDeniedException"},
         {"shape":"InternalServerException"},
-        {"shape":"ThrottlingException"},
-        {"shape":"ResourceNotFoundException"}
+        {"shape":"ResourceNotFoundException"},
+        {"shape":"ThrottlingException"}
       ],
       "documentation":"<p>List tags for an Amazon Bedrock Data Automation resource</p>"
     },
@@ -77,11 +77,11 @@
       "output":{"shape":"TagResourceResponse"},
       "errors":[
         {"shape":"ServiceQuotaExceededException"},
-        {"shape":"AccessDeniedException"},
         {"shape":"ValidationException"},
+        {"shape":"AccessDeniedException"},
         {"shape":"InternalServerException"},
-        {"shape":"ThrottlingException"},
-        {"shape":"ResourceNotFoundException"}
+        {"shape":"ResourceNotFoundException"},
+        {"shape":"ThrottlingException"}
       ],
       "documentation":"<p>Tag an Amazon Bedrock Data Automation resource</p>"
     },
@@ -94,11 +94,11 @@
       "input":{"shape":"UntagResourceRequest"},
       "output":{"shape":"UntagResourceResponse"},
       "errors":[
-        {"shape":"AccessDeniedException"},
         {"shape":"ValidationException"},
+        {"shape":"AccessDeniedException"},
         {"shape":"InternalServerException"},
-        {"shape":"ThrottlingException"},
-        {"shape":"ResourceNotFoundException"}
+        {"shape":"ResourceNotFoundException"},
+        {"shape":"ThrottlingException"}
       ],
       "documentation":"<p>Untag an Amazon Bedrock Data Automation resource</p>"
     }
@@ -112,6 +112,16 @@
       "documentation":"<p>This exception will be thrown when customer does not have access to API.</p>",
       "exception":true
     },
+    "AssetProcessingConfiguration":{
+      "type":"structure",
+      "members":{
+        "video":{
+          "shape":"VideoAssetProcessingConfiguration",
+          "documentation":"<p>Video asset processing configuration</p>"
+        }
+      },
+      "documentation":"<p>Config containing asset processing related knobs for all modalities</p>"
+    },
     "AutomationJobStatus":{
       "type":"string",
       "documentation":"<p>List of status supported by automation jobs</p>",
@@ -309,6 +319,10 @@
         "s3Uri":{
           "shape":"S3Uri",
           "documentation":"<p>S3 uri.</p>"
+        },
+        "assetProcessingConfiguration":{
+          "shape":"AssetProcessingConfiguration",
+          "documentation":"<p>Asset processing configuration</p>"
         }
       },
       "documentation":"<p>Input configuration.</p>"
@@ -528,6 +542,34 @@
       "documentation":"<p>This exception will be thrown when customer reached API TPS limit.</p>",
       "exception":true
     },
+    "TimestampSegment":{
+      "type":"structure",
+      "required":[
+        "startTimeMillis",
+        "endTimeMillis"
+      ],
+      "members":{
+        "startTimeMillis":{
+          "shape":"TimestampSegmentStartTimeMillisLong",
+          "documentation":"<p>Start timestamp in milliseconds</p>"
+        },
+        "endTimeMillis":{
+          "shape":"TimestampSegmentEndTimeMillisLong",
+          "documentation":"<p>End timestamp in milliseconds</p>"
+        }
+      },
+      "documentation":"<p>Timestamp segment</p>"
+    },
+    "TimestampSegmentEndTimeMillisLong":{
+      "type":"long",
+      "box":true,
+      "min":300000
+    },
+    "TimestampSegmentStartTimeMillisLong":{
+      "type":"long",
+      "box":true,
+      "min":0
+    },
     "UntagResourceRequest":{
       "type":"structure",
       "required":[
@@ -551,6 +593,27 @@
       },
       "documentation":"<p>This exception will be thrown when customer provided invalid parameters.</p>",
       "exception":true
+    },
+    "VideoAssetProcessingConfiguration":{
+      "type":"structure",
+      "members":{
+        "segmentConfiguration":{
+          "shape":"VideoSegmentConfiguration",
+          "documentation":"<p>Delimits the segment of the input that will be processed</p>"
+        }
+      },
+      "documentation":"<p>Video asset processing configuration</p>"
+    },
+    "VideoSegmentConfiguration":{
+      "type":"structure",
+      "members":{
+        "timestampSegment":{
+          "shape":"TimestampSegment",
+          "documentation":"<p>Timestamp segment</p>"
+        }
+      },
+      "documentation":"<p>Delimits the segment of the input that will be processed</p>",
+      "union":true
     }
   },
   "documentation":"<p>Amazon Bedrock Data Automation Runtime</p>"

{botocore-1.38.17 → botocore-1.38.18}/botocore/data/codepipeline/2015-07-09/paginators-1.json

@@ -40,6 +40,12 @@
       "output_token": "nextToken",
       "limit_key": "maxResults",
       "result_key": "ruleExecutionDetails"
+    },
+    "ListDeployActionExecutionTargets": {
+      "input_token": "nextToken",
+      "output_token": "nextToken",
+      "limit_key": "maxResults",
+      "result_key": "targets"
     }
   }
 }

{botocore-1.38.17 → botocore-1.38.18}/botocore/data/codepipeline/2015-07-09/service-2.json

@@ -285,6 +285,22 @@
       ],
       "documentation":"<p>Gets a summary of all CodePipeline action types associated with your account.</p>"
     },
+    "ListDeployActionExecutionTargets":{
+      "name":"ListDeployActionExecutionTargets",
+      "http":{
+        "method":"POST",
+        "requestUri":"/"
+      },
+      "input":{"shape":"ListDeployActionExecutionTargetsInput"},
+      "output":{"shape":"ListDeployActionExecutionTargetsOutput"},
+      "errors":[
+        {"shape":"ValidationException"},
+        {"shape":"PipelineNotFoundException"},
+        {"shape":"InvalidNextTokenException"},
+        {"shape":"ActionExecutionNotFoundException"}
+      ],
+      "documentation":"<p>Lists the targets for the deploy action.</p>"
+    },
     "ListPipelineExecutions":{
       "name":"ListPipelineExecutions",
       "http":{
@@ -1108,6 +1124,14 @@
       },
       "documentation":"<p>Input information used for an action execution.</p>"
     },
+    "ActionExecutionNotFoundException":{
+      "type":"structure",
+      "members":{
+        "message":{"shape":"Message"}
+      },
+      "documentation":"<p>The action execution was not found.</p>",
+      "exception":true
+    },
     "ActionExecutionOutput":{
       "type":"structure",
       "members":{
@@ -2095,6 +2119,84 @@
       "type":"structure",
       "members":{}
     },
+    "DeployActionExecutionTarget":{
+      "type":"structure",
+      "members":{
+        "targetId":{
+          "shape":"String",
+          "documentation":"<p>The ID of the target for the deploy action.</p>"
+        },
+        "targetType":{
+          "shape":"String",
+          "documentation":"<p>The type of target for the deploy action.</p>"
+        },
+        "status":{
+          "shape":"String",
+          "documentation":"<p>The status of the deploy action.</p>"
+        },
+        "startTime":{
+          "shape":"Timestamp",
+          "documentation":"<p>The start time for the deploy action.</p>"
+        },
+        "endTime":{
+          "shape":"Timestamp",
+          "documentation":"<p>The end time for the deploy action.</p>"
+        },
+        "events":{
+          "shape":"DeployTargetEventList",
+          "documentation":"<p>The lifecycle events for the deploy action.</p>"
+        }
+      },
+      "documentation":"<p>The target for the deploy action.</p>"
+    },
+    "DeployActionExecutionTargetList":{
+      "type":"list",
+      "member":{"shape":"DeployActionExecutionTarget"}
+    },
+    "DeployTargetEvent":{
+      "type":"structure",
+      "members":{
+        "name":{
+          "shape":"String",
+          "documentation":"<p>The name of the event for the deploy action.</p>"
+        },
+        "status":{
+          "shape":"String",
+          "documentation":"<p>The status of the event for the deploy action.</p>"
+        },
+        "startTime":{
+          "shape":"Timestamp",
+          "documentation":"<p>The start time for the event for the deploy action.</p>"
+        },
+        "endTime":{
+          "shape":"Timestamp",
+          "documentation":"<p>The end time for the event for the deploy action.</p>"
+        },
+        "context":{
+          "shape":"DeployTargetEventContext",
+          "documentation":"<p>The context for the event for the deploy action.</p>"
+        }
+      },
+      "documentation":"<p>A lifecycle event for the deploy action.</p>"
+    },
+    "DeployTargetEventContext":{
+      "type":"structure",
+      "members":{
+        "ssmCommandId":{
+          "shape":"String",
+          "documentation":"<p>The command ID for the event for the deploy action.</p>"
+        },
+        "message":{
+          "shape":"String",
+          "documentation":"<p>The context message for the event for the deploy action.</p>"
+        }
+      },
+      "documentation":"<p>The context for the event for the deploy action.</p>"
+    },
+    "DeployTargetEventList":{
+      "type":"list",
+      "member":{"shape":"DeployTargetEvent"}
+    },
     "DeregisterWebhookWithThirdPartyInput":{
       "type":"structure",
       "members":{
@@ -3089,6 +3191,45 @@
       },
       "documentation":"<p>Represents the output of a <code>ListActionTypes</code> action.</p>"
     },
+    "ListDeployActionExecutionTargetsInput":{
+      "type":"structure",
+      "required":["actionExecutionId"],
+      "members":{
+        "pipelineName":{
+          "shape":"PipelineName",
+          "documentation":"<p>The name of the pipeline with the deploy action.</p>"
+        },
+        "actionExecutionId":{
+          "shape":"ActionExecutionId",
+          "documentation":"<p>The execution ID for the deploy action.</p>"
+        },
+        "filters":{
+          "shape":"TargetFilterList",
+          "documentation":"<p>Filters the targets for a specified deploy action.</p>"
+        },
+        "maxResults":{
+          "shape":"MaxResults",
+          "documentation":"<p>The maximum number of results to return in a single call. To retrieve the remaining results, make another call with the returned nextToken value.</p>"
+        },
+        "nextToken":{
+          "shape":"NextToken",
+          "documentation":"<p>An identifier that was returned from the previous list action types call, which can be used to return the next set of action types in the list.</p>"
+        }
+      }
+    },
+    "ListDeployActionExecutionTargetsOutput":{
+      "type":"structure",
+      "members":{
+        "targets":{
+          "shape":"DeployActionExecutionTargetList",
+          "documentation":"<p>The targets for the deploy action.</p>"
+        },
+        "nextToken":{
+          "shape":"NextToken",
+          "documentation":"<p>An identifier that was returned from the previous list action types call, which can be used to return the next set of action types in the list.</p>"
+        }
+      }
+    },
     "ListPipelineExecutionsInput":{
       "type":"structure",
       "required":["pipelineName"],
@@ -5309,6 +5450,36 @@
       "max":256,
       "min":0
     },
+    "TargetFilter":{
+      "type":"structure",
+      "members":{
+        "name":{
+          "shape":"TargetFilterName",
+          "documentation":"<p>The name on which to filter.</p>"
+        },
+        "values":{
+          "shape":"TargetFilterValueList",
+          "documentation":"<p>The values on which to filter.</p>"
+        }
+      },
+      "documentation":"<p>Filters the list of targets.</p>"
+    },
+    "TargetFilterList":{
+      "type":"list",
+      "member":{"shape":"TargetFilter"}
+    },
+    "TargetFilterName":{
+      "type":"string",
+      "enum":["TARGET_STATUS"]
+    },
+    "TargetFilterValue":{
+      "type":"string",
+      "min":1
+    },
+    "TargetFilterValueList":{
+      "type":"list",
+      "member":{"shape":"TargetFilterValue"}
+    },
     "ThirdPartyJob":{
       "type":"structure",
       "members":{

{botocore-1.38.17 → botocore-1.38.18}/botocore/data/ecs/2014-11-13/service-2.json

@@ -731,7 +731,7 @@
         {"shape":"BlockedException"},
         {"shape":"ConflictException"}
       ],
-      "documentation":"<p>Starts a new task using the specified task definition.</p> <note> <p>On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.</p> </note> <note> <p>Amazon Elastic Inference (EI) is no longer available to customers.</p> </note> <p>You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places tasks using placement constraints and placement strategies. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html\">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>Alternatively, you can use <code>StartTask</code> to use your own scheduler or place tasks manually on specific container instances.</p> <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or updating a service. For more infomation, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types\">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>The Amazon ECS API follows an eventual consistency model. This is because of the distributed nature of the system supporting the API. This means that the result of an API command you run that affects your Amazon ECS resources might not be immediately visible to all subsequent commands you run. Keep this in mind when you carry out an API command that immediately follows a previous API command.</p> <p>To manage eventual consistency, you can do the following:</p> <ul> <li> <p>Confirm the state of the resource before you run a command to modify it. Run the DescribeTasks command using an exponential backoff algorithm to ensure that you allow enough time for the previous command to propagate through the system. To do this, run the DescribeTasks command repeatedly, starting with a couple of seconds of wait time and increasing gradually up to five minutes of wait time.</p> </li> <li> <p>Add wait time between subsequent commands, even if the DescribeTasks command returns an accurate response. Apply an exponential backoff algorithm starting with a couple of seconds of wait time, and increase gradually up to about five minutes of wait time.</p> </li> </ul> <p>If you get a <code>ConflictException</code> error, the <code>RunTask</code> request could not be processed due to conflicts. The provided <code>clientToken</code> is already in use with a different <code>RunTask</code> request. The <code>resourceIds</code> are the existing task ARNs which are already associated with the <code>clientToken</code>. </p> <p>To fix this issue:</p> <ul> <li> <p>Run <code>RunTask</code> with a unique <code>clientToken</code>.</p> </li> <li> <p>Run <code>RunTask</code> with the <code>clientToken</code> and the original set of parameters</p> </li> </ul>"
+      "documentation":"<p>Starts a new task using the specified task definition.</p> <note> <p>On March 21, 2024, a change was made to resolve the task definition revision before authorization. When a task definition revision is not specified, authorization will occur using the latest revision of a task definition.</p> </note> <note> <p>Amazon Elastic Inference (EI) is no longer available to customers.</p> </note> <p>You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places tasks using placement constraints and placement strategies. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduling_tasks.html\">Scheduling Tasks</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>Alternatively, you can use <code>StartTask</code> to use your own scheduler or place tasks manually on specific container instances.</p> <p>You can attach Amazon EBS volumes to Amazon ECS tasks by configuring the volume when creating or updating a service. For more infomation, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-types\">Amazon EBS volumes</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>The Amazon ECS API follows an eventual consistency model. This is because of the distributed nature of the system supporting the API. This means that the result of an API command you run that affects your Amazon ECS resources might not be immediately visible to all subsequent commands you run. Keep this in mind when you carry out an API command that immediately follows a previous API command.</p> <p>To manage eventual consistency, you can do the following:</p> <ul> <li> <p>Confirm the state of the resource before you run a command to modify it. Run the DescribeTasks command using an exponential backoff algorithm to ensure that you allow enough time for the previous command to propagate through the system. To do this, run the DescribeTasks command repeatedly, starting with a couple of seconds of wait time and increasing gradually up to five minutes of wait time.</p> </li> <li> <p>Add wait time between subsequent commands, even if the DescribeTasks command returns an accurate response. Apply an exponential backoff algorithm starting with a couple of seconds of wait time, and increase gradually up to about five minutes of wait time.</p> </li> </ul> <p>If you get a <code>ConflictException</code> error, the <code>RunTask</code> request could not be processed due to conflicts. The provided <code>clientToken</code> is already in use with a different <code>RunTask</code> request. The <code>resourceIds</code> are the existing task ARNs which are already associated with the <code>clientToken</code>. </p> <p>To fix this issue:</p> <ul> <li> <p>Run <code>RunTask</code> with a unique <code>clientToken</code>.</p> </li> <li> <p>Run <code>RunTask</code> with the <code>clientToken</code> and the original set of parameters</p> </li> </ul> <p>If you get a <code>ClientException</code>error, the <code>RunTask</code> could not be processed because you use managed scaling and there is a capacity error because the quota of tasks in the <code>PROVISIONING</code> per cluster has been reached. For information about the service quotas, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html\">Amazon ECS service quotas</a>.</p>"
     },
     "StartTask":{
       "name":"StartTask",
@@ -767,7 +767,7 @@
         {"shape":"ServiceDeploymentNotFoundException"},
         {"shape":"UnsupportedFeatureException"}
       ],
-      "documentation":"<p>Stops an ongoing service deployment.</p> <note> <p>StopServiceDeployment isn't currently supported.</p> </note>"
+      "documentation":"<p>Stops an ongoing service deployment.</p> <p>The following stop types are avaiable:</p> <ul> <li> <p>ROLLBACK - This option rolls back the service deployment to the previous service revision. </p> <p>You can use this option even if you didn't configure the service deployment for the rollback option. </p> </li> </ul> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/stop-service-deployment.html\">Stopping Amazon ECS service deployments</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>"
     },
     "StopTask":{
       "name":"StopTask",
@@ -1346,7 +1346,7 @@
           "documentation":"<p> Message that describes the cause of the exception.</p>"
         }
       },
-      "documentation":"<p>These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might be specifying an identifier that isn't valid.</p> <p>The following list includes additional causes for the error:</p> <ul> <li> <p>The <code>RunTask</code> could not be processed because you use managed scaling and there is a capacity error because the quota of tasks in the <code>PROVISIONING</code> per cluster has been reached. For information about the service quotas, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html\">Amazon ECS service quotas</a>.</p> </li> </ul>",
+      "documentation":"<p>These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might be specifying an identifier that isn't valid.</p>",
       "exception":true
     },
     "Cluster":{
@@ -1585,7 +1585,7 @@
         },
         "reason":{
           "shape":"String",
-          "documentation":"<p>A short (255 max characters) human-readable string to provide additional details about a running or stopped container.</p>"
+          "documentation":"<p>A short (1024 max characters) human-readable string to provide additional details about a running or stopped container.</p>"
         },
         "networkBindings":{
           "shape":"NetworkBindings",
@@ -2359,7 +2359,7 @@
         },
         "principalArn":{
           "shape":"String",
-          "documentation":"<p>The Amazon Resource Name (ARN) of the principal. It can be an user, role, or the root user. If you specify the root user, it disables the account setting for all users, roles, and the root user of the account unless a user or role explicitly overrides these settings. If this field is omitted, the setting is changed only for the authenticated user.</p>"
+          "documentation":"<p>The Amazon Resource Name (ARN) of the principal. It can be a user, role, or the root user. If you specify the root user, it disables the account setting for all users, roles, and the root user of the account unless a user or role explicitly overrides these settings. If this field is omitted, the setting is changed only for the authenticated user.</p> <p>In order to use this parameter, you must be the root user, or the principal.</p>"
         }
       }
     },
@@ -3750,7 +3750,7 @@
         },
         "principalArn":{
           "shape":"String",
-          "documentation":"<p>The ARN of the principal, which can be a user, role, or the root user. If this field is omitted, the account settings are listed only for the authenticated user.</p> <note> <p>Federated users assume the account setting of the root user and can't have explicit account settings set for them.</p> </note>"
+          "documentation":"<p>The ARN of the principal, which can be a user, role, or the root user. If this field is omitted, the account settings are listed only for the authenticated user.</p> <p>In order to use this parameter, you must be the root user, or the principal.</p> <note> <p>Federated users assume the account setting of the root user and can't have explicit account settings set for them.</p> </note>"
         },
         "effectiveSettings":{
           "shape":"Boolean",
@@ -4708,7 +4708,7 @@
         },
         "principalArn":{
           "shape":"String",
-          "documentation":"<p>The ARN of the principal, which can be a user, role, or the root user. If you specify the root user, it modifies the account setting for all users, roles, and the root user of the account unless a user or role explicitly overrides these settings. If this field is omitted, the setting is changed only for the authenticated user.</p> <note> <p>You must use the root user when you set the Fargate wait time (<code>fargateTaskRetirementWaitPeriod</code>). </p> <p>Federated users assume the account setting of the root user and can't have explicit account settings set for them.</p> </note>"
+          "documentation":"<p>The ARN of the principal, which can be a user, role, or the root user. If you specify the root user, it modifies the account setting for all users, roles, and the root user of the account unless a user or role explicitly overrides these settings. If this field is omitted, the setting is changed only for the authenticated user.</p> <p>In order to use this parameter, you must be the root user, or the principal.</p> <note> <p>You must use the root user when you set the Fargate wait time (<code>fargateTaskRetirementWaitPeriod</code>). </p> <p>Federated users assume the account setting of the root user and can't have explicit account settings set for them.</p> </note>"
         }
       }
     },
@@ -4866,7 +4866,7 @@
         },
         "cpu":{
           "shape":"String",
-          "documentation":"<p>The number of CPU units used by the task. It can be expressed as an integer using CPU units (for example, <code>1024</code>) or as a string using vCPUs (for example, <code>1 vCPU</code> or <code>1 vcpu</code>) in a task definition. String values are converted to an integer indicating the CPU units when the task definition is registered.</p> <note> <p>Task-level CPU and memory parameters are ignored for Windows containers. We recommend specifying container-level resources for Windows containers.</p> </note> <p>If you're using the EC2 launch type or external launch type, this field is optional. Supported values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>196608</code> CPU units (<code>192</code> vCPUs). If you do not specify a value, the parameter is ignored.</p> <p>If you're using the Fargate launch type, this field is required and you must use one of the following values, which determines your range of supported values for the <code>memory</code> parameter:</p> <p>The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.</p> <ul> <li> <p>256 (.25 vCPU) - Available <code>memory</code> values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)</p> </li> <li> <p>512 (.5 vCPU) - Available <code>memory</code> values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)</p> </li> <li> <p>1024 (1 vCPU) - Available <code>memory</code> values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)</p> </li> <li> <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p> </li> <li> <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p> </li> <li> <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p> <p>This option requires Linux platform <code>1.4.0</code> or later.</p> </li> <li> <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p> <p>This option requires Linux platform <code>1.4.0</code> or later.</p> </li> </ul>"
+          "documentation":"<p>The number of CPU units used by the task. It can be expressed as an integer using CPU units (for example, <code>1024</code>) or as a string using vCPUs (for example, <code>1 vCPU</code> or <code>1 vcpu</code>) in a task definition. String values are converted to an integer indicating the CPU units when the task definition is registered.</p> <note> <p>Task-level CPU and memory parameters are ignored for Windows containers. We recommend specifying container-level resources for Windows containers.</p> </note> <p>If you're using the EC2 launch type or external launch type, this field is optional. Supported values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>196608</code> CPU units (<code>192</code> vCPUs). If you do not specify a value, the parameter is ignored.</p> <p>This field is required for Fargate. For information about the valid values, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_size\">Task size</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>"
         },
         "memory":{
           "shape":"String",
@@ -6061,7 +6061,7 @@
         },
         "stopType":{
           "shape":"StopServiceDeploymentStopType",
-          "documentation":"<p>How you want Amazon ECS to stop the service. </p> <p>The ROLLBACK and ABORT stopType aren't supported.</p>"
+          "documentation":"<p>How you want Amazon ECS to stop the service. </p> <p>The valid values are <code>ROLLBACK</code>.</p>"
         }
       }
     },
@@ -6373,7 +6373,7 @@
         },
         "cpu":{
           "shape":"String",
-          "documentation":"<p>The number of CPU units used by the task as expressed in a task definition. It can be expressed as an integer using CPU units (for example, <code>1024</code>). It can also be expressed as a string using vCPUs (for example, <code>1 vCPU</code> or <code>1 vcpu</code>). String values are converted to an integer that indicates the CPU units when the task definition is registered.</p> <p>If you're using the EC2 launch type or the external launch type, this field is optional. Supported values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>196608</code> CPU units (<code>192</code> vCPUs). If you do not specify a value, the parameter is ignored.</p> <p>If you're using the Fargate launch type, this field is required. You must use one of the following values. These values determine the range of supported values for the <code>memory</code> parameter:</p> <p>The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.</p> <ul> <li> <p>256 (.25 vCPU) - Available <code>memory</code> values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)</p> </li> <li> <p>512 (.5 vCPU) - Available <code>memory</code> values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)</p> </li> <li> <p>1024 (1 vCPU) - Available <code>memory</code> values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)</p> </li> <li> <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p> </li> <li> <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p> </li> <li> <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p> <p>This option requires Linux platform <code>1.4.0</code> or later.</p> </li> <li> <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p> <p>This option requires Linux platform <code>1.4.0</code> or later.</p> </li> </ul>"
+          "documentation":"<p>The number of CPU units used by the task as expressed in a task definition. It can be expressed as an integer using CPU units (for example, <code>1024</code>). It can also be expressed as a string using vCPUs (for example, <code>1 vCPU</code> or <code>1 vcpu</code>). String values are converted to an integer that indicates the CPU units when the task definition is registered.</p> <p>If you're using the EC2 launch type or the external launch type, this field is optional. Supported values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>196608</code> CPU units (<code>192</code> vCPUs). If you do not specify a value, the parameter is ignored.</p> <p>This field is required for Fargate. For information about the valid values, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_size\">Task size</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>"
         },
         "createdAt":{
           "shape":"Timestamp",
@@ -6547,7 +6547,7 @@
         },
         "cpu":{
           "shape":"String",
-          "documentation":"<p>The number of <code>cpu</code> units used by the task. If you use the EC2 launch type, this field is optional. Any value can be used. If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines your range of valid values for the <code>memory</code> parameter.</p> <p>If you're using the EC2 launch type or the external launch type, this field is optional. Supported values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>196608</code> CPU units (<code>192</code> vCPUs). The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.</p> <ul> <li> <p>256 (.25 vCPU) - Available <code>memory</code> values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)</p> </li> <li> <p>512 (.5 vCPU) - Available <code>memory</code> values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)</p> </li> <li> <p>1024 (1 vCPU) - Available <code>memory</code> values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)</p> </li> <li> <p>2048 (2 vCPU) - Available <code>memory</code> values: 4096 (4 GB) and 16384 (16 GB) in increments of 1024 (1 GB)</p> </li> <li> <p>4096 (4 vCPU) - Available <code>memory</code> values: 8192 (8 GB) and 30720 (30 GB) in increments of 1024 (1 GB)</p> </li> <li> <p>8192 (8 vCPU) - Available <code>memory</code> values: 16 GB and 60 GB in 4 GB increments</p> <p>This option requires Linux platform <code>1.4.0</code> or later.</p> </li> <li> <p>16384 (16vCPU) - Available <code>memory</code> values: 32GB and 120 GB in 8 GB increments</p> <p>This option requires Linux platform <code>1.4.0</code> or later.</p> </li> </ul>"
+          "documentation":"<p>The number of <code>cpu</code> units used by the task. If you use the EC2 launch type, this field is optional. Any value can be used. If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines your range of valid values for the <code>memory</code> parameter.</p> <p>If you're using the EC2 launch type or the external launch type, this field is optional. Supported values are between <code>128</code> CPU units (<code>0.125</code> vCPUs) and <code>196608</code> CPU units (<code>192</code> vCPUs). </p> <p>This field is required for Fargate. For information about the valid values, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#task_size\">Task size</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>"
         },
         "memory":{
           "shape":"String",