Merge branch 'release-1.34.13'

* release-1.34.13:
  Bumping version to 1.34.13
  Update to latest models

.changes/1.34.13.json

@@ -0,0 +1,47 @@
+[
+  {
+    "category": "``config``",
+    "description": "Updated ResourceType enum with new resource types onboarded by AWS Config in November and December 2023.",
+    "type": "api-change"
+  },
+  {
+    "category": "``docdb``",
+    "description": "Adding PerformanceInsightsEnabled and PerformanceInsightsKMSKeyId fields to DescribeDBInstances Response.",
+    "type": "api-change"
+  },
+  {
+    "category": "``ecs``",
+    "description": "This release adds support for managed instance draining which facilitates graceful termination of Amazon ECS instances.",
+    "type": "api-change"
+  },
+  {
+    "category": "``es``",
+    "description": "This release adds support for new or existing Amazon OpenSearch domains to enable TLS 1.3 or TLS 1.2 with perfect forward secrecy cipher suites for domain endpoints.",
+    "type": "api-change"
+  },
+  {
+    "category": "``lightsail``",
+    "description": "This release adds support to set up an HTTPS endpoint on an instance.",
+    "type": "api-change"
+  },
+  {
+    "category": "``opensearch``",
+    "description": "This release adds support for new or existing Amazon OpenSearch domains to enable TLS 1.3 or TLS 1.2 with perfect forward secrecy cipher suites for domain endpoints.",
+    "type": "api-change"
+  },
+  {
+    "category": "``sagemaker``",
+    "description": "Adding support for provisioned throughput mode for SageMaker Feature Groups",
+    "type": "api-change"
+  },
+  {
+    "category": "``servicecatalog``",
+    "description": "Added Idempotency token support to Service Catalog  AssociateServiceActionWithProvisioningArtifact, DisassociateServiceActionFromProvisioningArtifact, DeleteServiceAction API",
+    "type": "api-change"
+  },
+  {
+    "category": "``endpoint-rules``",
+    "description": "Update endpoint-rules client to latest version",
+    "type": "api-change"
+  }
+]

CHANGELOG.rst

@@ -2,6 +2,20 @@
 CHANGELOG
 =========
 
+1.34.13
+=======
+
+* api-change:``config``: Updated ResourceType enum with new resource types onboarded by AWS Config in November and December 2023.
+* api-change:``docdb``: Adding PerformanceInsightsEnabled and PerformanceInsightsKMSKeyId fields to DescribeDBInstances Response.
+* api-change:``ecs``: This release adds support for managed instance draining which facilitates graceful termination of Amazon ECS instances.
+* api-change:``es``: This release adds support for new or existing Amazon OpenSearch domains to enable TLS 1.3 or TLS 1.2 with perfect forward secrecy cipher suites for domain endpoints.
+* api-change:``lightsail``: This release adds support to set up an HTTPS endpoint on an instance.
+* api-change:``opensearch``: This release adds support for new or existing Amazon OpenSearch domains to enable TLS 1.3 or TLS 1.2 with perfect forward secrecy cipher suites for domain endpoints.
+* api-change:``sagemaker``: Adding support for provisioned throughput mode for SageMaker Feature Groups
+* api-change:``servicecatalog``: Added Idempotency token support to Service Catalog  AssociateServiceActionWithProvisioningArtifact, DisassociateServiceActionFromProvisioningArtifact, DeleteServiceAction API
+* api-change:``endpoint-rules``: Update endpoint-rules client to latest version
+
+
 1.34.12
 =======
 

botocore/__init__.py

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

botocore/data/config/2014-11-12/service-2.json

@@ -2460,7 +2460,7 @@
         },
         "recordingMode":{
           "shape":"RecordingMode",
-          "documentation":"<p>Specifies the default recording frequency that Config uses to record configuration changes. Config supports <i>Continuous recording</i> and <i>Daily recording</i>.</p> <ul> <li> <p>Continuous recording allows you to record configuration changes continuously whenever a change occurs.</p> </li> <li> <p>Daily recording allows you record configuration data once every 24 hours, only if a change has occurred.</p> </li> </ul> <note> <p>Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.</p> </note> <p>You can also override the recording frequency for specific resource types.</p>"
+          "documentation":"<p>Specifies the default recording frequency that Config uses to record configuration changes. Config supports <i>Continuous recording</i> and <i>Daily recording</i>.</p> <ul> <li> <p>Continuous recording allows you to record configuration changes continuously whenever a change occurs.</p> </li> <li> <p>Daily recording allows you to receive a configuration item (CI) representing the most recent state of your resources over the last 24-hour period, only if it’s different from the previous CI recorded. </p> </li> </ul> <note> <p>Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.</p> </note> <p>You can also override the recording frequency for specific resource types.</p>"
         }
       },
       "documentation":"<p>Records configuration changes to your specified resource types. For more information about the configuration recorder, see <a href=\"https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html\"> <b>Managing the Configuration Recorder</b> </a> in the <i>Config Developer Guide</i>.</p>"
@@ -6668,7 +6668,7 @@
           "documentation":"<p>An array of <code>recordingModeOverride</code> objects for you to specify your overrides for the recording mode. The <code>recordingModeOverride</code> object in the <code>recordingModeOverrides</code> array consists of three fields: a <code>description</code>, the new <code>recordingFrequency</code>, and an array of <code>resourceTypes</code> to override.</p>"
         }
       },
-      "documentation":"<p>Specifies the default recording frequency that Config uses to record configuration changes. Config supports <i>Continuous recording</i> and <i>Daily recording</i>.</p> <ul> <li> <p>Continuous recording allows you to record configuration changes continuously whenever a change occurs.</p> </li> <li> <p>Daily recording allows you record configuration data once every 24 hours, only if a change has occurred.</p> </li> </ul> <note> <p>Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.</p> </note> <p>You can also override the recording frequency for specific resource types.</p>"
+      "documentation":"<p>Specifies the default recording frequency that Config uses to record configuration changes. Config supports <i>Continuous recording</i> and <i>Daily recording</i>.</p> <ul> <li> <p>Continuous recording allows you to record configuration changes continuously whenever a change occurs.</p> </li> <li> <p>Daily recording allows you to receive a configuration item (CI) representing the most recent state of your resources over the last 24-hour period, only if it’s different from the previous CI recorded. </p> </li> </ul> <note> <p>Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.</p> </note> <p>You can also override the recording frequency for specific resource types.</p>"
     },
     "RecordingModeOverride":{
       "type":"structure",
@@ -6687,7 +6687,7 @@
         },
         "recordingFrequency":{
           "shape":"RecordingFrequency",
-          "documentation":"<p>The recording frequency that will be applied to all the resource types specified in the override.</p> <ul> <li> <p>Continuous recording allows you to record configuration changes continuously whenever a change occurs.</p> </li> <li> <p>Daily recording allows you record configuration data once every 24 hours, only if a change has occurred.</p> </li> </ul> <note> <p>Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.</p> </note>"
+          "documentation":"<p>The recording frequency that will be applied to all the resource types specified in the override.</p> <ul> <li> <p>Continuous recording allows you to record configuration changes continuously whenever a change occurs.</p> </li> <li> <p>Daily recording allows you to receive a configuration item (CI) representing the most recent state of your resources over the last 24-hour period, only if it’s different from the previous CI recorded. </p> </li> </ul> <note> <p>Firewall Manager depends on continuous recording to monitor your resources. If you are using Firewall Manager, it is recommended that you set the recording frequency to Continuous.</p> </note>"
         }
       },
       "documentation":"<p>An object for you to specify your overrides for the recording mode.</p>"
@@ -6804,7 +6804,7 @@
         },
         "RetryAttemptSeconds":{
           "shape":"AutoRemediationAttemptSeconds",
-          "documentation":"<p>Maximum time in seconds that Config runs auto-remediation. If you do not select a number, the default is 60 seconds. </p> <p>For example, if you specify RetryAttemptSeconds as 50 seconds and MaximumAutomaticAttempts as 5, Config will run auto-remediations 5 times within 50 seconds before throwing an exception.</p>"
+          "documentation":"<p>Time window to determine whether or not to add a remediation exception to prevent infinite remediation attempts. If <code>MaximumAutomaticAttempts</code> remediation attempts have been made under <code>RetryAttemptSeconds</code>, a remediation exception will be added to the resource. If you do not select a number, the default is 60 seconds. </p> <p>For example, if you specify <code>RetryAttemptSeconds</code> as 50 seconds and <code>MaximumAutomaticAttempts</code> as 5, Config will run auto-remediations 5 times within 50 seconds before adding a remediation exception to the resource.</p>"
         },
         "Arn":{
           "shape":"StringWithCharLimit1024",
@@ -7629,7 +7629,25 @@
         "AWS::KafkaConnect::Connector",
         "AWS::Lambda::CodeSigningConfig",
         "AWS::NetworkManager::ConnectPeer",
-        "AWS::ResourceExplorer2::Index"
+        "AWS::ResourceExplorer2::Index",
+        "AWS::AppStream::Fleet",
+        "AWS::Cognito::UserPool",
+        "AWS::Cognito::UserPoolClient",
+        "AWS::Cognito::UserPoolGroup",
+        "AWS::EC2::NetworkInsightsAccessScope",
+        "AWS::EC2::NetworkInsightsAnalysis",
+        "AWS::Grafana::Workspace",
+        "AWS::GroundStation::DataflowEndpointGroup",
+        "AWS::ImageBuilder::ImageRecipe",
+        "AWS::KMS::Alias",
+        "AWS::M2::Environment",
+        "AWS::QuickSight::DataSource",
+        "AWS::QuickSight::Template",
+        "AWS::QuickSight::Theme",
+        "AWS::RDS::OptionGroup",
+        "AWS::Redshift::EndpointAccess",
+        "AWS::Route53Resolver::FirewallRuleGroup",
+        "AWS::SSM::Document"
       ]
     },
     "ResourceTypeList":{

botocore/data/docdb/2014-10-31/service-2.json

@@ -2294,6 +2294,14 @@
         "CertificateDetails":{
           "shape":"CertificateDetails",
           "documentation":"<p>The details of the DB instance's server certificate.</p>"
+        },
+        "PerformanceInsightsEnabled":{
+          "shape":"BooleanOptional",
+          "documentation":"<p>Set to <code>true</code> if Amazon RDS Performance Insights is enabled for the DB instance, and otherwise <code>false</code>.</p>"
+        },
+        "PerformanceInsightsKMSKeyId":{
+          "shape":"String",
+          "documentation":"<p>The KMS key identifier for encryption of Performance Insights data. The KMS key ID is the Amazon Resource Name (ARN), KMS key identifier, or the KMS key alias for the KMS encryption key.</p>"
         }
       },
       "documentation":"<p>Detailed information about an instance. </p>",

botocore/data/ecs/2014-11-13/service-2.json

@@ -88,7 +88,7 @@
         {"shape":"ServiceNotActiveException"},
         {"shape":"NamespaceNotFoundException"}
       ],
-      "documentation":"<p>Create a task set in the specified cluster and service. This is used when a service uses the <code>EXTERNAL</code> deployment controller type. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html\">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p>"
+      "documentation":"<p>Create a task set in the specified cluster and service. This is used when a service uses the <code>EXTERNAL</code> deployment controller type. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html\">Amazon ECS deployment types</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.</p> <p>You can create a maximum of 5 tasks sets for a deployment.</p>"
     },
     "DeleteAccountSetting":{
       "name":"DeleteAccountSetting",
@@ -1090,6 +1090,10 @@
         "managedTerminationProtection":{
           "shape":"ManagedTerminationProtection",
           "documentation":"<p>The managed termination protection setting to use for the Auto Scaling group capacity provider. This determines whether the Auto Scaling group has managed termination protection. The default is off.</p> <important> <p>When using managed termination protection, managed scaling must also be used otherwise managed termination protection doesn't work.</p> </important> <p>When managed termination protection is on, Amazon ECS prevents the Amazon EC2 instances in an Auto Scaling group that contain tasks from being terminated during a scale-in action. The Auto Scaling group and each instance in the Auto Scaling group must have instance protection from scale-in actions on as well. For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection\">Instance Protection</a> in the <i>Auto Scaling User Guide</i>.</p> <p>When managed termination protection is off, your Amazon EC2 instances aren't protected from termination when the Auto Scaling group scales in.</p>"
+        },
+        "managedDraining":{
+          "shape":"ManagedDraining",
+          "documentation":"<p>The managed draining option for the Auto Scaling group capacity provider. When you enable this, Amazon ECS manages and gracefully drains the EC2 container instances that are in the Auto Scaling group capacity provider.</p> <p>The default is <code>ENABLED</code>.</p>"
         }
       },
       "documentation":"<p>The details of the Auto Scaling group for the capacity provider.</p>"
@@ -1104,6 +1108,10 @@
         "managedTerminationProtection":{
           "shape":"ManagedTerminationProtection",
           "documentation":"<p>The managed termination protection setting to use for the Auto Scaling group capacity provider. This determines whether the Auto Scaling group has managed termination protection.</p> <important> <p>When using managed termination protection, managed scaling must also be used otherwise managed termination protection doesn't work.</p> </important> <p>When managed termination protection is on, Amazon ECS prevents the Amazon EC2 instances in an Auto Scaling group that contain tasks from being terminated during a scale-in action. The Auto Scaling group and each instance in the Auto Scaling group must have instance protection from scale-in actions on. For more information, see <a href=\"https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection\">Instance Protection</a> in the <i>Auto Scaling User Guide</i>.</p> <p>When managed termination protection is off, your Amazon EC2 instances aren't protected from termination when the Auto Scaling group scales in.</p>"
+        },
+        "managedDraining":{
+          "shape":"ManagedDraining",
+          "documentation":"<p>The managed draining option for the Auto Scaling group capacity provider. When you enable this, Amazon ECS manages and gracefully drains the EC2 container instances that are in the Auto Scaling group capacity provider.</p> <p>The default is <code>ENABLED</code>.</p>"
         }
       },
       "documentation":"<p>The details of the Auto Scaling group capacity provider to update.</p>"
@@ -1250,7 +1258,10 @@
     "ClientException":{
       "type":"structure",
       "members":{
-        "message":{"shape":"String"}
+        "message":{
+          "shape":"String",
+          "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>",
       "exception":true
@@ -3949,6 +3960,13 @@
       "type":"list",
       "member":{"shape":"ManagedAgent"}
     },
+    "ManagedDraining":{
+      "type":"string",
+      "enum":[
+        "ENABLED",
+        "DISABLED"
+      ]
+    },
     "ManagedScaling":{
       "type":"structure",
       "members":{
@@ -4843,7 +4861,10 @@
     "ServerException":{
       "type":"structure",
       "members":{
-        "message":{"shape":"String"}
+        "message":{
+          "shape":"String",
+          "documentation":"<p> Message that describes the cause of the exception.</p>"
+        }
       },
       "documentation":"<p>These errors are usually caused by a server issue.</p>",
       "exception":true,