Merge branch 'release-1.21.30'

* release-1.21.30:
  Bumping version to 1.21.30
  Add changelog entries from botocore
  Add warning about TLS 1.3 support (#3204)
  Fix first code block in README (#3205)

Author: aws-sdk-python-automation

.changes/1.21.30.json

@@ -0,0 +1,27 @@
+[
+  {
+    "category": "``iot-data``",
+    "description": "[``botocore``] Update the default AWS IoT Core Data Plane endpoint from VeriSign signed to ATS signed. If you have firewalls with strict egress rules, configure the rules to grant you access to data-ats.iot.[region].amazonaws.com or data-ats.iot.[region].amazonaws.com.cn.",
+    "type": "api-change"
+  },
+  {
+    "category": "``ec2``",
+    "description": "[``botocore``] This release simplifies the auto-recovery configuration process enabling customers to set the recovery behavior to disabled or default",
+    "type": "api-change"
+  },
+  {
+    "category": "``fms``",
+    "description": "[``botocore``] AWS Firewall Manager now supports the configuration of third-party policies that can use either the centralized or distributed deployment models.",
+    "type": "api-change"
+  },
+  {
+    "category": "``fsx``",
+    "description": "[``botocore``] This release adds support for modifying throughput capacity for FSx for ONTAP file systems.",
+    "type": "api-change"
+  },
+  {
+    "category": "``iot``",
+    "description": "[``botocore``] Doc only update for IoT that fixes customer-reported issues.",
+    "type": "api-change"
+  }
+]

CHANGELOG.rst

@@ -2,6 +2,16 @@
 CHANGELOG
 =========
 
+1.21.30
+=======
+
+* api-change:``iot-data``: [``botocore``] Update the default AWS IoT Core Data Plane endpoint from VeriSign signed to ATS signed. If you have firewalls with strict egress rules, configure the rules to grant you access to data-ats.iot.[region].amazonaws.com or data-ats.iot.[region].amazonaws.com.cn.
+* api-change:``ec2``: [``botocore``] This release simplifies the auto-recovery configuration process enabling customers to set the recovery behavior to disabled or default
+* api-change:``fms``: [``botocore``] AWS Firewall Manager now supports the configuration of third-party policies that can use either the centralized or distributed deployment models.
+* api-change:``fsx``: [``botocore``] This release adds support for modifying throughput capacity for FSx for ONTAP file systems.
+* api-change:``iot``: [``botocore``] Doc only update for IoT that fixes customer-reported issues.
+
+
 1.21.29
 =======
 

README.rst

@@ -43,7 +43,8 @@ Getting Started
 Assuming that you have a supported version of Python installed, you can first
 set up your environment with:
 
-..code-block:: sh
+.. code-block:: sh
+
     $ python -m venv .venv
     ...
     $ . .venv/bin/activate

boto3/__init__.py

@@ -17,7 +17,7 @@
 from boto3.session import Session
 
 __author__ = 'Amazon Web Services'
-__version__ = '1.21.29'
+__version__ = '1.21.30'
 
 
 # The default Boto3 session; autoloaded when needed.

docs/source/guide/security.rst

@@ -230,6 +230,11 @@ To confirm this new version of Python does not negotiate a version earlier than
 Enforcing TLS 1.3
 ------------------
 
+.. note::
+    Some AWS Services do not yet support TLS 1.3, configuring this as your minimum version may affect SDK interoperability.
+    We recommend testing this change with each service prior to production deployment.
+
+
 The process of ensuring the AWS SDK for Python uses no TLS version earlier than TLS 1.3 is the same as the instructions in the `Enforcing TLS 1.2`_ section with some minor modifications, primarily adding the ``no-tls1_2`` flag to the openssl build configuration.
 
 The following are the modified build instructions::

setup.cfg

@@ -3,7 +3,7 @@ universal = 0
 
 [metadata]
 requires_dist =
-    botocore>=1.24.29,<1.25.0
+    botocore>=1.24.30,<1.25.0
     jmespath>=0.7.1,<2.0.0
     s3transfer>=0.5.0,<0.6.0
 

setup.py

@@ -13,7 +13,7 @@
 
 
 requires = [
-    'botocore>=1.24.29,<1.25.0',
+    'botocore>=1.24.30,<1.25.0',
     'jmespath>=0.7.1,<2.0.0',
     's3transfer>=0.5.0,<0.6.0',
 ]