Merge branch 'release-1.35.53' into develop

* release-1.35.53:
  Bumping version to 1.35.53
  Update endpoints model
  Update to latest models

.changes/1.35.53.json

@@ -0,0 +1,37 @@
+[
+  {
+    "category": "``amp``",
+    "description": "Added support for UpdateScraper API, to enable updating collector configuration in-place",
+    "type": "api-change"
+  },
+  {
+    "category": "``autoscaling``",
+    "description": "Adds bake time for Auto Scaling group Instance Refresh",
+    "type": "api-change"
+  },
+  {
+    "category": "``batch``",
+    "description": "Add `podNamespace` to `EksAttemptDetail` and `containerID` to `EksAttemptContainerDetail`.",
+    "type": "api-change"
+  },
+  {
+    "category": "``elbv2``",
+    "description": "Add UDP support for AWS PrivateLink and dual-stack Network Load Balancers",
+    "type": "api-change"
+  },
+  {
+    "category": "``glue``",
+    "description": "Add schedule support for AWS Glue column statistics",
+    "type": "api-change"
+  },
+  {
+    "category": "``sagemaker``",
+    "description": "SageMaker HyperPod adds scale-down at instance level via BatchDeleteClusterNodes API and group level via UpdateCluster API. SageMaker Training exposes secondary job status in TrainingJobSummary from ListTrainingJobs API. SageMaker now supports G6, G6e, P5e instances for HyperPod and Training.",
+    "type": "api-change"
+  },
+  {
+    "category": "``sesv2``",
+    "description": "This release enables customers to provide the email template content in the SESv2 SendEmail and SendBulkEmail APIs instead of the name or the ARN of a stored email template.",
+    "type": "api-change"
+  }
+]

CHANGELOG.rst

@@ -2,6 +2,18 @@
 CHANGELOG
 =========
 
+1.35.53
+=======
+
+* api-change:``amp``: Added support for UpdateScraper API, to enable updating collector configuration in-place
+* api-change:``autoscaling``: Adds bake time for Auto Scaling group Instance Refresh
+* api-change:``batch``: Add `podNamespace` to `EksAttemptDetail` and `containerID` to `EksAttemptContainerDetail`.
+* api-change:``elbv2``: Add UDP support for AWS PrivateLink and dual-stack Network Load Balancers
+* api-change:``glue``: Add schedule support for AWS Glue column statistics
+* api-change:``sagemaker``: SageMaker HyperPod adds scale-down at instance level via BatchDeleteClusterNodes API and group level via UpdateCluster API. SageMaker Training exposes secondary job status in TrainingJobSummary from ListTrainingJobs API. SageMaker now supports G6, G6e, P5e instances for HyperPod and Training.
+* api-change:``sesv2``: This release enables customers to provide the email template content in the SESv2 SendEmail and SendBulkEmail APIs instead of the name or the ARN of a stored email template.
+
+
 1.35.52
 =======
 

botocore/__init__.py

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

botocore/data/autoscaling/2011-01-01/service-2.json

@@ -1656,6 +1656,11 @@
       "type":"list",
       "member":{"shape":"XmlStringMaxLen255"}
     },
+    "BakeTime":{
+      "type":"integer",
+      "max":172800,
+      "min":0
+    },
     "BareMetal":{
       "type":"string",
       "enum":[
@@ -3174,7 +3179,7 @@
         },
         "Status":{
           "shape":"InstanceRefreshStatus",
-          "documentation":"<p>The current status for the instance refresh operation:</p> <ul> <li> <p> <code>Pending</code> - The request was created, but the instance refresh has not started.</p> </li> <li> <p> <code>InProgress</code> - An instance refresh is in progress.</p> </li> <li> <p> <code>Successful</code> - An instance refresh completed successfully.</p> </li> <li> <p> <code>Failed</code> - An instance refresh failed to complete. You can troubleshoot using the status reason and the scaling activities. </p> </li> <li> <p> <code>Cancelling</code> - An ongoing instance refresh is being cancelled.</p> </li> <li> <p> <code>Cancelled</code> - The instance refresh is cancelled. </p> </li> <li> <p> <code>RollbackInProgress</code> - An instance refresh is being rolled back.</p> </li> <li> <p> <code>RollbackFailed</code> - The rollback failed to complete. You can troubleshoot using the status reason and the scaling activities.</p> </li> <li> <p> <code>RollbackSuccessful</code> - The rollback completed successfully.</p> </li> </ul>"
+          "documentation":"<p>The current status for the instance refresh operation:</p> <ul> <li> <p> <code>Pending</code> - The request was created, but the instance refresh has not started.</p> </li> <li> <p> <code>InProgress</code> - An instance refresh is in progress.</p> </li> <li> <p> <code>Successful</code> - An instance refresh completed successfully.</p> </li> <li> <p> <code>Failed</code> - An instance refresh failed to complete. You can troubleshoot using the status reason and the scaling activities. </p> </li> <li> <p> <code>Cancelling</code> - An ongoing instance refresh is being cancelled.</p> </li> <li> <p> <code>Cancelled</code> - The instance refresh is cancelled. </p> </li> <li> <p> <code>RollbackInProgress</code> - An instance refresh is being rolled back.</p> </li> <li> <p> <code>RollbackFailed</code> - The rollback failed to complete. You can troubleshoot using the status reason and the scaling activities.</p> </li> <li> <p> <code>RollbackSuccessful</code> - The rollback completed successfully.</p> </li> <li> <p> <code>Baking</code> - Waiting the specified bake time after an instance refresh has finished updating instances.</p> </li> </ul>"
         },
         "StatusReason":{
           "shape":"XmlStringMaxLen1023",
@@ -3271,7 +3276,8 @@
         "Cancelled",
         "RollbackInProgress",
         "RollbackFailed",
-        "RollbackSuccessful"
+        "RollbackSuccessful",
+        "Baking"
       ]
     },
     "InstanceRefreshWarmPoolProgress":{
@@ -4794,6 +4800,10 @@
         "MaxHealthyPercentage":{
           "shape":"IntPercent100To200",
           "documentation":"<p>Specifies the maximum percentage of the group that can be in service and healthy, or pending, to support your workload when replacing instances. The value is expressed as a percentage of the desired capacity of the Auto Scaling group. Value range is 100 to 200.</p> <p>If you specify <code>MaxHealthyPercentage</code>, you must also specify <code>MinHealthyPercentage</code>, and the difference between them cannot be greater than 100. A larger range increases the number of instances that can be replaced at the same time.</p> <p>If you do not specify this property, the default is 100 percent, or the percentage set in the instance maintenance policy for the Auto Scaling group, if defined.</p>"
+        },
+        "BakeTime":{
+          "shape":"BakeTime",
+          "documentation":"<p> The amount of time, in seconds, to wait at the end of an instance refresh before the instance refresh is considered complete. </p>"
         }
       },
       "documentation":"<p>Describes the preferences for an instance refresh.</p>"
@@ -5262,7 +5272,7 @@
         },
         "Preferences":{
           "shape":"RefreshPreferences",
-          "documentation":"<p>Sets your preferences for the instance refresh so that it performs as expected when you start it. Includes the instance warmup time, the minimum and maximum healthy percentages, and the behaviors that you want Amazon EC2 Auto Scaling to use if instances that are in <code>Standby</code> state or protected from scale in are found. You can also choose to enable additional features, such as the following:</p> <ul> <li> <p>Auto rollback</p> </li> <li> <p>Checkpoints</p> </li> <li> <p>CloudWatch alarms</p> </li> <li> <p>Skip matching</p> </li> </ul>"
+          "documentation":"<p>Sets your preferences for the instance refresh so that it performs as expected when you start it. Includes the instance warmup time, the minimum and maximum healthy percentages, and the behaviors that you want Amazon EC2 Auto Scaling to use if instances that are in <code>Standby</code> state or protected from scale in are found. You can also choose to enable additional features, such as the following:</p> <ul> <li> <p>Auto rollback</p> </li> <li> <p>Checkpoints</p> </li> <li> <p>CloudWatch alarms</p> </li> <li> <p>Skip matching</p> </li> <li> <p>Bake time</p> </li> </ul>"
         }
       }
     },

botocore/data/batch/2016-08-10/service-2.json

@@ -596,7 +596,7 @@
         },
         "reason":{
           "shape":"String",
-          "documentation":"<p>A message to attach to the job that explains the reason for canceling it. This message is returned by future <a>DescribeJobs</a> operations on the job. This message is also recorded in the Batch activity logs.</p>"
+          "documentation":"<p>A message to attach to the job that explains the reason for canceling it. This message is returned by future <a>DescribeJobs</a> operations on the job. It is also recorded in the Batch activity logs.</p> <p>This parameter has as limit of 1024 characters.</p>"
         }
       },
       "documentation":"<p>Contains the parameters for <code>CancelJob</code>.</p>"
@@ -1219,7 +1219,7 @@
         },
         "schedulingPolicyArn":{
           "shape":"String",
-          "documentation":"<p>The Amazon Resource Name (ARN) of the fair share scheduling policy. If this parameter is specified, the job queue uses a fair share scheduling policy. If this parameter isn't specified, the job queue uses a first in, first out (FIFO) scheduling policy. After a job queue is created, you can replace but can't remove the fair share scheduling policy. The format is <code>aws:<i>Partition</i>:batch:<i>Region</i>:<i>Account</i>:scheduling-policy/<i>Name</i> </code>. An example is <code>aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy</code>.</p>"
+          "documentation":"<p>The Amazon Resource Name (ARN) of the fair share scheduling policy. Job queues that don't have a scheduling policy are scheduled in a first-in, first-out (FIFO) model. After a job queue has a scheduling policy, it can be replaced but can't be removed.</p> <p>The format is <code>aws:<i>Partition</i>:batch:<i>Region</i>:<i>Account</i>:scheduling-policy/<i>Name</i> </code>.</p> <p>An example is <code>aws:aws:batch:us-west-2:123456789012:scheduling-policy/MySchedulingPolicy</code>.</p> <p>A job queue without a scheduling policy is scheduled as a FIFO job queue and can't have a scheduling policy added. Jobs queues with a scheduling policy can have a maximum of 500 active fair share identifiers. When the limit has been reached, submissions of any jobs that add a new fair share identifier fail.</p>"
         },
         "priority":{
           "shape":"Integer",
@@ -1235,7 +1235,7 @@
         },
         "jobStateTimeLimitActions":{
           "shape":"JobStateTimeLimitActions",
-          "documentation":"<p>The set of actions that Batch performs on jobs that remain at the head of the job queue in the specified state longer than specified times. Batch will perform each action after <code>maxTimeSeconds</code> has passed.</p>"
+          "documentation":"<p>The set of actions that Batch performs on jobs that remain at the head of the job queue in the specified state longer than specified times. Batch will perform each action after <code>maxTimeSeconds</code> has passed. (<b>Note</b>: The minimum value for maxTimeSeconds is 600 (10 minutes) and its maximum value is 86,400 (24 hours).)</p>"
         }
       },
       "documentation":"<p>Contains the parameters for <code>CreateJobQueue</code>.</p>"
@@ -1616,7 +1616,7 @@
       "members":{
         "taskProperties":{
           "shape":"ListEcsTaskProperties",
-          "documentation":"<p>An object that contains the properties for the Amazon ECS task definition of a job.</p> <note> <p>This object is currently limited to one element.</p> </note>"
+          "documentation":"<p>An object that contains the properties for the Amazon ECS task definition of a job.</p> <note> <p>This object is currently limited to one task element. However, the task element can run up to 10 containers.</p> </note>"
         }
       },
       "documentation":"<p>An object that contains the properties for the Amazon ECS resources of a job.</p>"
@@ -1749,6 +1749,10 @@
           "shape":"String",
           "documentation":"<p>The name of a container.</p>"
         },
+        "containerID":{
+          "shape":"String",
+          "documentation":"<p>The ID for the container.</p>"
+        },
         "exitCode":{
           "shape":"Integer",
           "documentation":"<p>The exit code returned for the job attempt. A non-zero exit code is considered failed.</p>"
@@ -1783,6 +1787,10 @@
           "shape":"String",
           "documentation":"<p>The name of the pod for this job attempt.</p>"
         },
+        "podNamespace":{
+          "shape":"String",
+          "documentation":"<p>The namespace of the Amazon EKS cluster that the pod exists in.</p>"
+        },
         "nodeName":{
           "shape":"String",
           "documentation":"<p>The name of the node for this job attempt.</p>"
@@ -2109,11 +2117,11 @@
         },
         "containers":{
           "shape":"EksContainers",
-          "documentation":"<p>The properties of the container that's used on the Amazon EKS pod.</p>"
+          "documentation":"<p>The properties of the container that's used on the Amazon EKS pod.</p> <note> <p>This object is limited to 10 elements.</p> </note>"
         },
         "initContainers":{
           "shape":"EksContainers",
-          "documentation":"<p>These containers run before application containers, always runs to completion, and must complete successfully before the next container starts. These containers are registered with the Amazon EKS Connector agent and persists the registration information in the Kubernetes backend data store. For more information, see <a href=\"https://kubernetes.io/docs/concepts/workloads/pods/init-containers/\">Init Containers</a> in the <i>Kubernetes documentation</i>.</p> <note> <p>This object is limited to 10 elements</p> </note>"
+          "documentation":"<p>These containers run before application containers, always runs to completion, and must complete successfully before the next container starts. These containers are registered with the Amazon EKS Connector agent and persists the registration information in the Kubernetes backend data store. For more information, see <a href=\"https://kubernetes.io/docs/concepts/workloads/pods/init-containers/\">Init Containers</a> in the <i>Kubernetes documentation</i>.</p> <note> <p>This object is limited to 10 elements.</p> </note>"
         },
         "volumes":{
           "shape":"EksVolumes",
@@ -2189,7 +2197,7 @@
         },
         "initContainers":{
           "shape":"EksContainerOverrideList",
-          "documentation":"<p>The overrides for the conatainers defined in the Amazon EKS pod. These containers run before application containers, always runs to completion, and must complete successfully before the next container starts. These containers are registered with the Amazon EKS Connector agent and persists the registration information in the Kubernetes backend data store. For more information, see <a href=\"https://kubernetes.io/docs/concepts/workloads/pods/init-containers/\">Init Containers</a> in the <i>Kubernetes documentation</i>.</p> <note> <p>This object is limited to 10 elements</p> </note>"
+          "documentation":"<p>The overrides for the <code>initContainers</code> defined in the Amazon EKS pod. These containers run before application containers, always runs to completion, and must complete successfully before the next container starts. These containers are registered with the Amazon EKS Connector agent and persists the registration information in the Kubernetes backend data store. For more information, see <a href=\"https://kubernetes.io/docs/concepts/workloads/pods/init-containers/\">Init Containers</a> in the <i>Kubernetes documentation</i>.</p>"
         },
         "metadata":{
           "shape":"EksMetadata",
@@ -3973,7 +3981,7 @@
         },
         "reason":{
           "shape":"String",
-          "documentation":"<p>A message to attach to the job that explains the reason for canceling it. This message is returned by future <a>DescribeJobs</a> operations on the job. This message is also recorded in the Batch activity logs.</p>"
+          "documentation":"<p>A message to attach to the job that explains the reason for canceling it. This message is returned by future <a>DescribeJobs</a> operations on the job. It is also recorded in the Batch activity logs.</p> <p>This parameter has as limit of 1024 characters.</p>"
         }
       },
       "documentation":"<p>Contains the parameters for <code>TerminateJob</code>.</p>"
@@ -4137,7 +4145,7 @@
         },
         "jobStateTimeLimitActions":{
           "shape":"JobStateTimeLimitActions",
-          "documentation":"<p>The set of actions that Batch perform on jobs that remain at the head of the job queue in the specified state longer than specified times. Batch will perform each action after <code>maxTimeSeconds</code> has passed.</p>"
+          "documentation":"<p>The set of actions that Batch perform on jobs that remain at the head of the job queue in the specified state longer than specified times. Batch will perform each action after <code>maxTimeSeconds</code> has passed. (<b>Note</b>: The minimum value for maxTimeSeconds is 600 (10 minutes) and its maximum value is 86,400 (24 hours).)</p>"
         }
       },
       "documentation":"<p>Contains the parameters for <code>UpdateJobQueue</code>.</p>"