From 059ee7f70a30471c4bfa120060df813a8f81a1f1 Mon Sep 17 00:00:00 2001 From: aws-sdk-python-automation Date: Wed, 24 Jan 2024 19:14:06 +0000 Subject: [PATCH 1/7] Update changelog based on model updates --- .changes/next-release/api-change-ec2-59820.json | 5 +++++ .changes/next-release/api-change-ecs-58523.json | 5 +++++ .changes/next-release/api-change-outposts-80719.json | 5 +++++ .changes/next-release/api-change-rds-16557.json | 5 +++++ .changes/next-release/api-change-storagegateway-93555.json | 5 +++++ 5 files changed, 25 insertions(+) create mode 100644 .changes/next-release/api-change-ec2-59820.json create mode 100644 .changes/next-release/api-change-ecs-58523.json create mode 100644 .changes/next-release/api-change-outposts-80719.json create mode 100644 .changes/next-release/api-change-rds-16557.json create mode 100644 .changes/next-release/api-change-storagegateway-93555.json diff --git a/.changes/next-release/api-change-ec2-59820.json b/.changes/next-release/api-change-ec2-59820.json new file mode 100644 index 000000000000..439e86140563 --- /dev/null +++ b/.changes/next-release/api-change-ec2-59820.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``ec2``", + "description": "Introduced a new clientToken request parameter on CreateNetworkAcl and CreateRouteTable APIs. The clientToken parameter allows idempotent operations on the APIs." +} diff --git a/.changes/next-release/api-change-ecs-58523.json b/.changes/next-release/api-change-ecs-58523.json new file mode 100644 index 000000000000..a2658e033523 --- /dev/null +++ b/.changes/next-release/api-change-ecs-58523.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``ecs``", + "description": "Documentation updates for Amazon ECS." +} diff --git a/.changes/next-release/api-change-outposts-80719.json b/.changes/next-release/api-change-outposts-80719.json new file mode 100644 index 000000000000..e5b32a387a41 --- /dev/null +++ b/.changes/next-release/api-change-outposts-80719.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``outposts``", + "description": "DeviceSerialNumber parameter is now optional in StartConnection API" +} diff --git a/.changes/next-release/api-change-rds-16557.json b/.changes/next-release/api-change-rds-16557.json new file mode 100644 index 000000000000..a058bb70337d --- /dev/null +++ b/.changes/next-release/api-change-rds-16557.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``rds``", + "description": "This release adds support for Aurora Limitless Database." +} diff --git a/.changes/next-release/api-change-storagegateway-93555.json b/.changes/next-release/api-change-storagegateway-93555.json new file mode 100644 index 000000000000..4c8b340ac423 --- /dev/null +++ b/.changes/next-release/api-change-storagegateway-93555.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``storagegateway``", + "description": "Add DeprecationDate and SoftwareVersion to response of ListGateways." +} From 6bf8018d1ee3b26f940e1b9e7d5be3cb6e02ba62 Mon Sep 17 00:00:00 2001 From: aws-sdk-python-automation Date: Wed, 24 Jan 2024 19:14:06 +0000 Subject: [PATCH 2/7] Bumping version to 1.32.27 --- .changes/1.32.27.json | 27 +++++++++++++++++++ .../next-release/api-change-ec2-59820.json | 5 ---- .../next-release/api-change-ecs-58523.json | 5 ---- .../api-change-outposts-80719.json | 5 ---- .../next-release/api-change-rds-16557.json | 5 ---- .../api-change-storagegateway-93555.json | 5 ---- CHANGELOG.rst | 10 +++++++ awscli/__init__.py | 2 +- doc/source/conf.py | 2 +- setup.cfg | 2 +- setup.py | 2 +- 11 files changed, 41 insertions(+), 29 deletions(-) create mode 100644 .changes/1.32.27.json delete mode 100644 .changes/next-release/api-change-ec2-59820.json delete mode 100644 .changes/next-release/api-change-ecs-58523.json delete mode 100644 .changes/next-release/api-change-outposts-80719.json delete mode 100644 .changes/next-release/api-change-rds-16557.json delete mode 100644 .changes/next-release/api-change-storagegateway-93555.json diff --git a/.changes/1.32.27.json b/.changes/1.32.27.json new file mode 100644 index 000000000000..7d910fe6f2d7 --- /dev/null +++ b/.changes/1.32.27.json @@ -0,0 +1,27 @@ +[ + { + "category": "``ec2``", + "description": "Introduced a new clientToken request parameter on CreateNetworkAcl and CreateRouteTable APIs. The clientToken parameter allows idempotent operations on the APIs.", + "type": "api-change" + }, + { + "category": "``ecs``", + "description": "Documentation updates for Amazon ECS.", + "type": "api-change" + }, + { + "category": "``outposts``", + "description": "DeviceSerialNumber parameter is now optional in StartConnection API", + "type": "api-change" + }, + { + "category": "``rds``", + "description": "This release adds support for Aurora Limitless Database.", + "type": "api-change" + }, + { + "category": "``storagegateway``", + "description": "Add DeprecationDate and SoftwareVersion to response of ListGateways.", + "type": "api-change" + } +] \ No newline at end of file diff --git a/.changes/next-release/api-change-ec2-59820.json b/.changes/next-release/api-change-ec2-59820.json deleted file mode 100644 index 439e86140563..000000000000 --- a/.changes/next-release/api-change-ec2-59820.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "type": "api-change", - "category": "``ec2``", - "description": "Introduced a new clientToken request parameter on CreateNetworkAcl and CreateRouteTable APIs. The clientToken parameter allows idempotent operations on the APIs." -} diff --git a/.changes/next-release/api-change-ecs-58523.json b/.changes/next-release/api-change-ecs-58523.json deleted file mode 100644 index a2658e033523..000000000000 --- a/.changes/next-release/api-change-ecs-58523.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "type": "api-change", - "category": "``ecs``", - "description": "Documentation updates for Amazon ECS." -} diff --git a/.changes/next-release/api-change-outposts-80719.json b/.changes/next-release/api-change-outposts-80719.json deleted file mode 100644 index e5b32a387a41..000000000000 --- a/.changes/next-release/api-change-outposts-80719.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "type": "api-change", - "category": "``outposts``", - "description": "DeviceSerialNumber parameter is now optional in StartConnection API" -} diff --git a/.changes/next-release/api-change-rds-16557.json b/.changes/next-release/api-change-rds-16557.json deleted file mode 100644 index a058bb70337d..000000000000 --- a/.changes/next-release/api-change-rds-16557.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "type": "api-change", - "category": "``rds``", - "description": "This release adds support for Aurora Limitless Database." -} diff --git a/.changes/next-release/api-change-storagegateway-93555.json b/.changes/next-release/api-change-storagegateway-93555.json deleted file mode 100644 index 4c8b340ac423..000000000000 --- a/.changes/next-release/api-change-storagegateway-93555.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "type": "api-change", - "category": "``storagegateway``", - "description": "Add DeprecationDate and SoftwareVersion to response of ListGateways." -} diff --git a/CHANGELOG.rst b/CHANGELOG.rst index d75a6958ee33..de1e90c8bbdc 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -2,6 +2,16 @@ CHANGELOG ========= +1.32.27 +======= + +* api-change:``ec2``: Introduced a new clientToken request parameter on CreateNetworkAcl and CreateRouteTable APIs. The clientToken parameter allows idempotent operations on the APIs. +* api-change:``ecs``: Documentation updates for Amazon ECS. +* api-change:``outposts``: DeviceSerialNumber parameter is now optional in StartConnection API +* api-change:``rds``: This release adds support for Aurora Limitless Database. +* api-change:``storagegateway``: Add DeprecationDate and SoftwareVersion to response of ListGateways. + + 1.32.26 ======= diff --git a/awscli/__init__.py b/awscli/__init__.py index 939ddcdf909b..783796868f0e 100644 --- a/awscli/__init__.py +++ b/awscli/__init__.py @@ -17,7 +17,7 @@ """ import os -__version__ = '1.32.26' +__version__ = '1.32.27' # # Get our data path to be added to botocore's search path diff --git a/doc/source/conf.py b/doc/source/conf.py index adc3d4ca6ee0..e5465e4d49e8 100644 --- a/doc/source/conf.py +++ b/doc/source/conf.py @@ -52,7 +52,7 @@ # The short X.Y version. version = '1.32.' # The full version, including alpha/beta/rc tags. -release = '1.32.26' +release = '1.32.27' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/setup.cfg b/setup.cfg index b309ae61cf0e..493b6445219f 100644 --- a/setup.cfg +++ b/setup.cfg @@ -3,7 +3,7 @@ universal = 0 [metadata] requires_dist = - botocore==1.34.26 + botocore==1.34.27 docutils>=0.10,<0.17 s3transfer>=0.10.0,<0.11.0 PyYAML>=3.10,<6.1 diff --git a/setup.py b/setup.py index 243f21082126..86adf50e9d47 100644 --- a/setup.py +++ b/setup.py @@ -24,7 +24,7 @@ def find_version(*file_paths): install_requires = [ - 'botocore==1.34.26', + 'botocore==1.34.27', 'docutils>=0.10,<0.17', 's3transfer>=0.10.0,<0.11.0', 'PyYAML>=3.10,<6.1', From 0f17dab394cb5ae0b72f6e74cd53a73e17424dec Mon Sep 17 00:00:00 2001 From: jonathan343 <43360731+jonathan343@users.noreply.github.com> Date: Wed, 24 Jan 2024 15:05:29 -0800 Subject: [PATCH 3/7] update closed issue message; relax stale issue timing (#8504) --- .github/workflows/closed-issue-message.yml | 5 ++--- .github/workflows/stale_issue.yml | 4 ++-- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/.github/workflows/closed-issue-message.yml b/.github/workflows/closed-issue-message.yml index 4788c53cd2ac..895153ce2567 100644 --- a/.github/workflows/closed-issue-message.yml +++ b/.github/workflows/closed-issue-message.yml @@ -11,6 +11,5 @@ jobs: # These inputs are both required repo-token: "${{ secrets.GITHUB_TOKEN }}" message: | - ### ⚠️COMMENT VISIBILITY WARNING⚠️ - Comments on closed issues are hard for our team to see. - If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so. + This issue is now closed. Comments on closed issues are hard for our team to see. + If you need more assistance, please open a new issue that references this one. diff --git a/.github/workflows/stale_issue.yml b/.github/workflows/stale_issue.yml index bb88b16614aa..8e523b47b432 100644 --- a/.github/workflows/stale_issue.yml +++ b/.github/workflows/stale_issue.yml @@ -29,8 +29,8 @@ jobs: closed-for-staleness-label: closed-for-staleness # Issue timing - days-before-stale: 5 - days-before-close: 2 + days-before-stale: 10 + days-before-close: 4 # If you don't want to mark a issue as being ancient based on a # threshold of "upvotes", you can set this here. An "upvote" is From 0302b9eb8bf74c48b328eb99373c0b01fa1dc2a6 Mon Sep 17 00:00:00 2001 From: aws-sdk-python-automation Date: Thu, 25 Jan 2024 19:20:19 +0000 Subject: [PATCH 4/7] Update changelog based on model updates --- .changes/next-release/api-change-acmpca-39417.json | 5 +++++ .changes/next-release/api-change-lightsail-7268.json | 5 +++++ 2 files changed, 10 insertions(+) create mode 100644 .changes/next-release/api-change-acmpca-39417.json create mode 100644 .changes/next-release/api-change-lightsail-7268.json diff --git a/.changes/next-release/api-change-acmpca-39417.json b/.changes/next-release/api-change-acmpca-39417.json new file mode 100644 index 000000000000..44963bc66afb --- /dev/null +++ b/.changes/next-release/api-change-acmpca-39417.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``acm-pca``", + "description": "AWS Private CA now supports an option to omit the CDP extension from issued certificates, when CRL revocation is enabled." +} diff --git a/.changes/next-release/api-change-lightsail-7268.json b/.changes/next-release/api-change-lightsail-7268.json new file mode 100644 index 000000000000..96b25106a74a --- /dev/null +++ b/.changes/next-release/api-change-lightsail-7268.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``lightsail``", + "description": "This release adds support for IPv6-only instance plans." +} From 16e7e107e3e40ac6f6a81ddca57269620807caeb Mon Sep 17 00:00:00 2001 From: aws-sdk-python-automation Date: Thu, 25 Jan 2024 19:20:20 +0000 Subject: [PATCH 5/7] Bumping version to 1.32.28 --- .changes/1.32.28.json | 12 ++++++++++++ .changes/next-release/api-change-acmpca-39417.json | 5 ----- .changes/next-release/api-change-lightsail-7268.json | 5 ----- CHANGELOG.rst | 7 +++++++ awscli/__init__.py | 2 +- doc/source/conf.py | 2 +- setup.cfg | 2 +- setup.py | 2 +- 8 files changed, 23 insertions(+), 14 deletions(-) create mode 100644 .changes/1.32.28.json delete mode 100644 .changes/next-release/api-change-acmpca-39417.json delete mode 100644 .changes/next-release/api-change-lightsail-7268.json diff --git a/.changes/1.32.28.json b/.changes/1.32.28.json new file mode 100644 index 000000000000..714df0b502d4 --- /dev/null +++ b/.changes/1.32.28.json @@ -0,0 +1,12 @@ +[ + { + "category": "``acm-pca``", + "description": "AWS Private CA now supports an option to omit the CDP extension from issued certificates, when CRL revocation is enabled.", + "type": "api-change" + }, + { + "category": "``lightsail``", + "description": "This release adds support for IPv6-only instance plans.", + "type": "api-change" + } +] \ No newline at end of file diff --git a/.changes/next-release/api-change-acmpca-39417.json b/.changes/next-release/api-change-acmpca-39417.json deleted file mode 100644 index 44963bc66afb..000000000000 --- a/.changes/next-release/api-change-acmpca-39417.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "type": "api-change", - "category": "``acm-pca``", - "description": "AWS Private CA now supports an option to omit the CDP extension from issued certificates, when CRL revocation is enabled." -} diff --git a/.changes/next-release/api-change-lightsail-7268.json b/.changes/next-release/api-change-lightsail-7268.json deleted file mode 100644 index 96b25106a74a..000000000000 --- a/.changes/next-release/api-change-lightsail-7268.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "type": "api-change", - "category": "``lightsail``", - "description": "This release adds support for IPv6-only instance plans." -} diff --git a/CHANGELOG.rst b/CHANGELOG.rst index de1e90c8bbdc..e8099f494a97 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -2,6 +2,13 @@ CHANGELOG ========= +1.32.28 +======= + +* api-change:``acm-pca``: AWS Private CA now supports an option to omit the CDP extension from issued certificates, when CRL revocation is enabled. +* api-change:``lightsail``: This release adds support for IPv6-only instance plans. + + 1.32.27 ======= diff --git a/awscli/__init__.py b/awscli/__init__.py index 783796868f0e..3866ede8c6b9 100644 --- a/awscli/__init__.py +++ b/awscli/__init__.py @@ -17,7 +17,7 @@ """ import os -__version__ = '1.32.27' +__version__ = '1.32.28' # # Get our data path to be added to botocore's search path diff --git a/doc/source/conf.py b/doc/source/conf.py index e5465e4d49e8..88325931936a 100644 --- a/doc/source/conf.py +++ b/doc/source/conf.py @@ -52,7 +52,7 @@ # The short X.Y version. version = '1.32.' # The full version, including alpha/beta/rc tags. -release = '1.32.27' +release = '1.32.28' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/setup.cfg b/setup.cfg index 493b6445219f..a258fe754c1a 100644 --- a/setup.cfg +++ b/setup.cfg @@ -3,7 +3,7 @@ universal = 0 [metadata] requires_dist = - botocore==1.34.27 + botocore==1.34.28 docutils>=0.10,<0.17 s3transfer>=0.10.0,<0.11.0 PyYAML>=3.10,<6.1 diff --git a/setup.py b/setup.py index 86adf50e9d47..2ddc9d66b9cb 100644 --- a/setup.py +++ b/setup.py @@ -24,7 +24,7 @@ def find_version(*file_paths): install_requires = [ - 'botocore==1.34.27', + 'botocore==1.34.28', 'docutils>=0.10,<0.17', 's3transfer>=0.10.0,<0.11.0', 'PyYAML>=3.10,<6.1', From 8933cd609fd1edc863fa41a49daa763ce194617d Mon Sep 17 00:00:00 2001 From: cli-v2-merge Date: Thu, 25 Jan 2024 20:34:45 +0000 Subject: [PATCH 6/7] Update to latest models Pulled in models from botocore 1.34.27 to 1.34.28 --- .../2017-08-22/endpoint-rule-set-1.json | 44 +-- .../data/acm-pca/2017-08-22/service-2.json | 30 +- .../data/acm-pca/2017-08-22/waiters-2.json | 2 +- .../data/ec2/2016-11-15/service-2.json | 30 +- .../data/ecs/2014-11-13/service-2.json | 21 +- .../data/lightsail/2016-11-28/service-2.json | 8 + .../2019-12-03/endpoint-rule-set-1.json | 44 +-- .../data/outposts/2019-12-03/service-2.json | 2 - .../data/rds/2014-10-31/service-2.json | 354 +++++++++++++++++- .../2013-06-30/endpoint-rule-set-1.json | 40 +- .../storagegateway/2013-06-30/service-2.json | 16 +- 11 files changed, 496 insertions(+), 95 deletions(-) diff --git a/awscli/botocore/data/acm-pca/2017-08-22/endpoint-rule-set-1.json b/awscli/botocore/data/acm-pca/2017-08-22/endpoint-rule-set-1.json index 32fd04c4617b..94cc1c481020 100644 --- a/awscli/botocore/data/acm-pca/2017-08-22/endpoint-rule-set-1.json +++ b/awscli/botocore/data/acm-pca/2017-08-22/endpoint-rule-set-1.json @@ -40,7 +40,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -83,7 +82,8 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -96,7 +96,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -110,7 +109,6 @@ "assign": "PartitionResult" } ], - "type": "tree", "rules": [ { "conditions": [ @@ -133,7 +131,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -168,7 +165,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -179,14 +175,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS and DualStack are enabled, but this partition does not support one or both", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -200,14 +198,12 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ - true, { "fn": "getAttr", "argv": [ @@ -216,18 +212,17 @@ }, "supportsFIPS" ] - } + }, + true ] } ], - "type": "tree", "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ - "aws-us-gov", { "fn": "getAttr", "argv": [ @@ -236,7 +231,8 @@ }, "name" ] - } + }, + "aws-us-gov" ] } ], @@ -256,14 +252,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS is enabled but this partition does not support FIPS", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -277,7 +275,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -297,7 +294,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -308,14 +304,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "DualStack is enabled but this partition does not support DualStack", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [], @@ -326,9 +324,11 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" } - ] + ], + "type": "tree" }, { "conditions": [], diff --git a/awscli/botocore/data/acm-pca/2017-08-22/service-2.json b/awscli/botocore/data/acm-pca/2017-08-22/service-2.json index 62fbca99dbca..8a7365ac146c 100644 --- a/awscli/botocore/data/acm-pca/2017-08-22/service-2.json +++ b/awscli/botocore/data/acm-pca/2017-08-22/service-2.json @@ -551,7 +551,7 @@ "type":"string", "max":200, "min":5, - "pattern":"arn:[\\w+=/,.@-]+:[\\w+=/,.@-]+:[\\w+=/,.@-]*:[0-9]*:[\\w+=,.@-]+(/[\\w+=,.@-]+)*" + "pattern":"arn:[\\w+=/,.@-]+:acm-pca:[\\w+=/,.@-]*:[0-9]*:[\\w+=,.@-]+(/[\\w+=,.@-]+)*" }, "AuditReportId":{ "type":"string", @@ -882,9 +882,25 @@ "S3ObjectAcl":{ "shape":"S3ObjectAcl", "documentation":"

Determines whether the CRL will be publicly readable or privately held in the CRL Amazon S3 bucket. If you choose PUBLIC_READ, the CRL will be accessible over the public internet. If you choose BUCKET_OWNER_FULL_CONTROL, only the owner of the CRL S3 bucket can access the CRL, and your PKI clients may need an alternative method of access.

If no value is specified, the default is PUBLIC_READ.

Note: This default can cause CA creation to fail in some circumstances. If you have have enabled the Block Public Access (BPA) feature in your S3 account, then you must specify the value of this parameter as BUCKET_OWNER_FULL_CONTROL, and not doing so results in an error. If you have disabled BPA in S3, then you can specify either BUCKET_OWNER_FULL_CONTROL or PUBLIC_READ as the value.

For more information, see Blocking public access to the S3 bucket.

" + }, + "CrlDistributionPointExtensionConfiguration":{ + "shape":"CrlDistributionPointExtensionConfiguration", + "documentation":"

Configures the behavior of the CRL Distribution Point extension for certificates issued by your certificate authority. If this field is not provided, then the CRl Distribution Point Extension will be present and contain the default CRL URL.

" } }, - "documentation":"

Contains configuration information for a certificate revocation list (CRL). Your private certificate authority (CA) creates base CRLs. Delta CRLs are not supported. You can enable CRLs for your new or an existing private CA by setting the Enabled parameter to true. Your private CA writes CRLs to an S3 bucket that you specify in the S3BucketName parameter. You can hide the name of your bucket by specifying a value for the CustomCname parameter. Your private CA copies the CNAME or the S3 bucket name to the CRL Distribution Points extension of each certificate it issues. Your S3 bucket policy must give write permission to Amazon Web Services Private CA.

Amazon Web Services Private CA assets that are stored in Amazon S3 can be protected with encryption. For more information, see Encrypting Your CRLs.

Your private CA uses the value in the ExpirationInDays parameter to calculate the nextUpdate field in the CRL. The CRL is refreshed prior to a certificate's expiration date or when a certificate is revoked. When a certificate is revoked, it appears in the CRL until the certificate expires, and then in one additional CRL after expiration, and it always appears in the audit report.

A CRL is typically updated approximately 30 minutes after a certificate is revoked. If for any reason a CRL update fails, Amazon Web Services Private CA makes further attempts every 15 minutes.

CRLs contain the following fields:

  • Version: The current version number defined in RFC 5280 is V2. The integer value is 0x1.

  • Signature Algorithm: The name of the algorithm used to sign the CRL.

  • Issuer: The X.500 distinguished name of your private CA that issued the CRL.

  • Last Update: The issue date and time of this CRL.

  • Next Update: The day and time by which the next CRL will be issued.

  • Revoked Certificates: List of revoked certificates. Each list item contains the following information.

    • Serial Number: The serial number, in hexadecimal format, of the revoked certificate.

    • Revocation Date: Date and time the certificate was revoked.

    • CRL Entry Extensions: Optional extensions for the CRL entry.

      • X509v3 CRL Reason Code: Reason the certificate was revoked.

  • CRL Extensions: Optional extensions for the CRL.

    • X509v3 Authority Key Identifier: Identifies the public key associated with the private key used to sign the certificate.

    • X509v3 CRL Number:: Decimal sequence number for the CRL.

  • Signature Algorithm: Algorithm used by your private CA to sign the CRL.

  • Signature Value: Signature computed over the CRL.

Certificate revocation lists created by Amazon Web Services Private CA are DER-encoded. You can use the following OpenSSL command to list a CRL.

openssl crl -inform DER -text -in crl_path -noout

For more information, see Planning a certificate revocation list (CRL) in the Amazon Web Services Private Certificate Authority User Guide

" + "documentation":"

Contains configuration information for a certificate revocation list (CRL). Your private certificate authority (CA) creates base CRLs. Delta CRLs are not supported. You can enable CRLs for your new or an existing private CA by setting the Enabled parameter to true. Your private CA writes CRLs to an S3 bucket that you specify in the S3BucketName parameter. You can hide the name of your bucket by specifying a value for the CustomCname parameter. Your private CA by default copies the CNAME or the S3 bucket name to the CRL Distribution Points extension of each certificate it issues. If you want to configure this default behavior to be something different, you can set the CrlDistributionPointExtensionConfiguration parameter. Your S3 bucket policy must give write permission to Amazon Web Services Private CA.

Amazon Web Services Private CA assets that are stored in Amazon S3 can be protected with encryption. For more information, see Encrypting Your CRLs.

Your private CA uses the value in the ExpirationInDays parameter to calculate the nextUpdate field in the CRL. The CRL is refreshed prior to a certificate's expiration date or when a certificate is revoked. When a certificate is revoked, it appears in the CRL until the certificate expires, and then in one additional CRL after expiration, and it always appears in the audit report.

A CRL is typically updated approximately 30 minutes after a certificate is revoked. If for any reason a CRL update fails, Amazon Web Services Private CA makes further attempts every 15 minutes.

CRLs contain the following fields:

  • Version: The current version number defined in RFC 5280 is V2. The integer value is 0x1.

  • Signature Algorithm: The name of the algorithm used to sign the CRL.

  • Issuer: The X.500 distinguished name of your private CA that issued the CRL.

  • Last Update: The issue date and time of this CRL.

  • Next Update: The day and time by which the next CRL will be issued.

  • Revoked Certificates: List of revoked certificates. Each list item contains the following information.

    • Serial Number: The serial number, in hexadecimal format, of the revoked certificate.

    • Revocation Date: Date and time the certificate was revoked.

    • CRL Entry Extensions: Optional extensions for the CRL entry.

      • X509v3 CRL Reason Code: Reason the certificate was revoked.

  • CRL Extensions: Optional extensions for the CRL.

    • X509v3 Authority Key Identifier: Identifies the public key associated with the private key used to sign the certificate.

    • X509v3 CRL Number:: Decimal sequence number for the CRL.

  • Signature Algorithm: Algorithm used by your private CA to sign the CRL.

  • Signature Value: Signature computed over the CRL.

Certificate revocation lists created by Amazon Web Services Private CA are DER-encoded. You can use the following OpenSSL command to list a CRL.

openssl crl -inform DER -text -in crl_path -noout

For more information, see Planning a certificate revocation list (CRL) in the Amazon Web Services Private Certificate Authority User Guide

" + }, + "CrlDistributionPointExtensionConfiguration":{ + "type":"structure", + "required":["OmitExtension"], + "members":{ + "OmitExtension":{ + "shape":"Boolean", + "documentation":"

Configures whether the CRL Distribution Point extension should be populated with the default URL to the CRL. If set to true, then the CDP extension will not be present in any certificates issued by that CA unless otherwise specified through CSR or API passthrough.

Only set this if you have another way to distribute the CRL Distribution Points ffor certificates issued by your CA, such as the Matter Distributed Compliance Ledger

This configuration cannot be enabled with a custom CNAME set.

", + "box":true + } + }, + "documentation":"

Contains configuration information for the default behavior of the CRL Distribution Point (CDP) extension in certificates issued by your CA. This extension contains a link to download the CRL, so you can check whether a certificate has been revoked. To choose whether you want this extension omitted or not in certificates issued by your CA, you can set the OmitExtension parameter.

" }, "CsrBlob":{ "type":"blob", @@ -927,7 +943,7 @@ "CustomAttributeList":{ "type":"list", "member":{"shape":"CustomAttribute"}, - "max":30, + "max":150, "min":1 }, "CustomExtension":{ @@ -956,7 +972,7 @@ "CustomExtensionList":{ "type":"list", "member":{"shape":"CustomExtension"}, - "max":20, + "max":150, "min":1 }, "CustomObjectIdentifier":{ @@ -1185,7 +1201,7 @@ "GeneralNameList":{ "type":"list", "member":{"shape":"GeneralName"}, - "max":20, + "max":150, "min":1 }, "GetCertificateAuthorityCertificateRequest":{ @@ -1494,7 +1510,7 @@ }, "MaxResults":{ "shape":"MaxResults", - "documentation":"

Use this parameter when paginating results to specify the maximum number of items to return in the response on each page. If additional items exist beyond the number you specify, the NextToken element is sent in the response. Use this NextToken value in a subsequent request to retrieve additional items.

" + "documentation":"

Use this parameter when paginating results to specify the maximum number of items to return in the response on each page. If additional items exist beyond the number you specify, the NextToken element is sent in the response. Use this NextToken value in a subsequent request to retrieve additional items.

Although the maximum value is 1000, the action only returns a maximum of 100 items.

" }, "ResourceOwner":{ "shape":"ResourceOwner", @@ -1608,7 +1624,7 @@ }, "NextToken":{ "type":"string", - "max":500, + "max":43739, "min":1 }, "OcspConfiguration":{ diff --git a/awscli/botocore/data/acm-pca/2017-08-22/waiters-2.json b/awscli/botocore/data/acm-pca/2017-08-22/waiters-2.json index 79bf399b9909..245186cadf81 100644 --- a/awscli/botocore/data/acm-pca/2017-08-22/waiters-2.json +++ b/awscli/botocore/data/acm-pca/2017-08-22/waiters-2.json @@ -22,7 +22,7 @@ "CertificateIssued": { "description": "Wait until a certificate is issued", "operation": "GetCertificate", - "delay": 3, + "delay": 1, "maxAttempts": 60, "acceptors": [ { diff --git a/awscli/botocore/data/ec2/2016-11-15/service-2.json b/awscli/botocore/data/ec2/2016-11-15/service-2.json index c3bf7edf5a72..c9826397f868 100644 --- a/awscli/botocore/data/ec2/2016-11-15/service-2.json +++ b/awscli/botocore/data/ec2/2016-11-15/service-2.json @@ -9245,7 +9245,8 @@ "available", "information", "impaired", - "unavailable" + "unavailable", + "constrained" ] }, "AvailabilityZoneStringList":{ @@ -12595,7 +12596,7 @@ "members":{ "ClientToken":{ "shape":"String", - "documentation":"

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see How to ensure idempotency.

" + "documentation":"

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see Ensuring idempotency.

" }, "DryRun":{ "shape":"Boolean", @@ -13674,7 +13675,7 @@ }, "ClientToken":{ "shape":"String", - "documentation":"

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see How to ensure idempotency.

Constraint: Maximum 64 ASCII characters.

", + "documentation":"

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see Ensuring idempotency.

Constraint: Maximum 64 ASCII characters.

", "idempotencyToken":true }, "DryRun":{ @@ -13809,6 +13810,11 @@ "shape":"TagSpecificationList", "documentation":"

The tags to assign to the network ACL.

", "locationName":"TagSpecification" + }, + "ClientToken":{ + "shape":"String", + "documentation":"

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see Ensuring idempotency.

", + "idempotencyToken":true } } }, @@ -13819,6 +13825,11 @@ "shape":"NetworkAcl", "documentation":"

Information about the network ACL.

", "locationName":"networkAcl" + }, + "ClientToken":{ + "shape":"String", + "documentation":"

Unique, case-sensitive identifier to ensure the idempotency of the request. Only returned if a client token was provided in the request.

", + "locationName":"clientToken" } } }, @@ -14384,6 +14395,11 @@ "shape":"TagSpecificationList", "documentation":"

The tags to assign to the route table.

", "locationName":"TagSpecification" + }, + "ClientToken":{ + "shape":"String", + "documentation":"

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see Ensuring idempotency.

", + "idempotencyToken":true } } }, @@ -14394,6 +14410,11 @@ "shape":"RouteTable", "documentation":"

Information about the route table.

", "locationName":"routeTable" + }, + "ClientToken":{ + "shape":"String", + "documentation":"

Unique, case-sensitive identifier to ensure the idempotency of the request. Only returned if a client token was provided in the request.

", + "locationName":"clientToken" } } }, @@ -54690,7 +54711,8 @@ "type":"string", "enum":[ "pending", - "available" + "available", + "unavailable" ] }, "Subscription":{ diff --git a/awscli/botocore/data/ecs/2014-11-13/service-2.json b/awscli/botocore/data/ecs/2014-11-13/service-2.json index 174e2a494f41..3b0cda1575a6 100644 --- a/awscli/botocore/data/ecs/2014-11-13/service-2.json +++ b/awscli/botocore/data/ecs/2014-11-13/service-2.json @@ -88,7 +88,7 @@ {"shape":"ServiceNotActiveException"}, {"shape":"NamespaceNotFoundException"} ], - "documentation":"

Create a task set in the specified cluster and service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide.

You can create a maximum of 5 tasks sets for a deployment.

" + "documentation":"

Create a task set in the specified cluster and service. This is used when a service uses the EXTERNAL deployment controller type. For more information, see Amazon ECS deployment types in the Amazon Elastic Container Service Developer Guide.

For information about the maximum number of task sets and otther quotas, see Amazon ECS service quotas in the Amazon Elastic Container Service Developer Guide.

" }, "DeleteAccountSetting":{ "name":"DeleteAccountSetting", @@ -1135,7 +1135,7 @@ "documentation":"

Whether the task's elastic network interface receives a public IP address. The default value is DISABLED.

" } }, - "documentation":"

An object representing the networking details for a task or service.

" + "documentation":"

An object representing the networking details for a task or service. For example awsvpcConfiguration={subnets=[\"subnet-12344321\"],securityGroups=[\"sg-12344321\"]}

" }, "BlockedException":{ "type":"structure", @@ -1687,7 +1687,7 @@ }, "ulimits":{ "shape":"UlimitList", - "documentation":"

A list of ulimits to set in the container. If a ulimit value is specified in a task definition, it overrides the default values set by Docker. This parameter maps to Ulimits in the Create a container section of the Docker Remote API and the --ulimit option to docker run. Valid naming values are displayed in the Ulimit data type.

Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and the default hard limit is 4096.

This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

This parameter is not supported for Windows containers.

" + "documentation":"

A list of ulimits to set in the container. If a ulimit value is specified in a task definition, it overrides the default values set by Docker. This parameter maps to Ulimits in the Create a container section of the Docker Remote API and the --ulimit option to docker run. Valid naming values are displayed in the Ulimit data type.

Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and the default hard limit is 65535.

This parameter requires version 1.18 of the Docker Remote API or greater on your container instance. To check the Docker Remote API version on your container instance, log in to your container instance and run the following command: sudo docker version --format '{{.Server.APIVersion}}'

This parameter is not supported for Windows containers.

" }, "logConfiguration":{ "shape":"LogConfiguration", @@ -1740,7 +1740,7 @@ "documentation":"

The dependency condition of the container. The following are the available conditions and their behavior:

  • START - This condition emulates the behavior of links and volumes today. It validates that a dependent container is started before permitting other containers to start.

  • COMPLETE - This condition validates that a dependent container runs to completion (exits) before permitting other containers to start. This can be useful for nonessential containers that run a script and then exit. This condition can't be set on an essential container.

  • SUCCESS - This condition is the same as COMPLETE, but it also requires that the container exits with a zero status. This condition can't be set on an essential container.

  • HEALTHY - This condition validates that the dependent container passes its Docker health check before permitting other containers to start. This requires that the dependent container has health checks configured. This condition is confirmed only at task startup.

" } }, - "documentation":"

The dependencies defined for container startup and shutdown. A container can contain multiple dependencies. When a dependency is defined for container startup, for container shutdown it is reversed.

Your Amazon ECS container instances require at least version 1.26.0 of the container agent to use container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide. If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init. For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide.

For tasks that use the Fargate launch type, the task or service requires the following platforms:

  • Linux platform version 1.3.0 or later.

  • Windows platform version 1.0.0 or later.

" + "documentation":"

The dependencies defined for container startup and shutdown. A container can contain multiple dependencies. When a dependency is defined for container startup, for container shutdown it is reversed.

Your Amazon ECS container instances require at least version 1.26.0 of the container agent to use container dependencies. However, we recommend using the latest container agent version. For information about checking your agent version and updating to the latest version, see Updating the Amazon ECS Container Agent in the Amazon Elastic Container Service Developer Guide. If you're using an Amazon ECS-optimized Linux AMI, your instance needs at least version 1.26.0-1 of the ecs-init package. If your container instances are launched from version 20190301 or later, then they contain the required versions of the container agent and ecs-init. For more information, see Amazon ECS-optimized Linux AMI in the Amazon Elastic Container Service Developer Guide.

For tasks that use the Fargate launch type, the task or service requires the following platforms:

  • Linux platform version 1.3.0 or later.

  • Windows platform version 1.0.0 or later.

For more information about how to create a container dependency, see Container dependency in the Amazon Elastic Container Service Developer Guide.

" }, "ContainerInstance":{ "type":"structure", @@ -2502,7 +2502,7 @@ }, "minimumHealthyPercent":{ "shape":"BoxedInteger", - "documentation":"

If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.

For services that do not use a load balancer, the following should be noted:

  • A service is considered healthy if all essential containers within the tasks in the service pass their health checks.

  • If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.

  • If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.

For services are that do use a load balancer, the following should be noted:

  • If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

  • If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

" + "documentation":"

If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.

For services that do not use a load balancer, the following should be noted:

  • A service is considered healthy if all essential containers within the tasks in the service pass their health checks.

  • If a task has no essential containers with a health check defined, the service scheduler will wait for 40 seconds after a task reaches a RUNNING state before the task is counted towards the minimum healthy percent total.

  • If a task has one or more essential containers with a health check defined, the service scheduler will wait for the task to reach a healthy status before counting it towards the minimum healthy percent total. A task is considered healthy when all essential containers within the task have passed their health checks. The amount of time the service scheduler can wait for is determined by the container health check settings.

For services that do use a load balancer, the following should be noted:

  • If a task has no essential containers with a health check defined, the service scheduler will wait for the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

  • If a task has an essential container with a health check defined, the service scheduler will wait for both the task to reach a healthy status and the load balancer target group health check to return a healthy status before counting the task towards the minimum healthy percent total.

If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the EC2 launch type, the minimum healthy percent value is set to the default value and is used to define the lower limit on the number of the tasks in the service that remain in the RUNNING state while the container instances are in the DRAINING state. If a service is using either the blue/green (CODE_DEPLOY) or EXTERNAL deployment types and is running tasks that use the Fargate launch type, the minimum healthy percent value is not used, although it is returned when describing your service.

" }, "alarms":{ "shape":"DeploymentAlarms", @@ -5114,7 +5114,10 @@ "shape":"TimeoutConfiguration", "documentation":"

A reference to an object that represents the configured timeouts for Service Connect.

" }, - "tls":{"shape":"ServiceConnectTlsConfiguration"} + "tls":{ + "shape":"ServiceConnectTlsConfiguration", + "documentation":"

A reference to an object that represents a Transport Layer Security (TLS) configuration.

" + } }, "documentation":"

The Service Connect service object configuration. For more information, see Service Connect in the Amazon Elastic Container Service Developer Guide.

" }, @@ -5480,7 +5483,7 @@ }, "reason":{ "shape":"String", - "documentation":"

An optional message specified when a task is stopped. For example, if you're using a custom scheduler, you can use this parameter to specify the reason for stopping the task here, and the message appears in subsequent DescribeTasks API operations on this task. Up to 255 characters are allowed in this message.

" + "documentation":"

An optional message specified when a task is stopped. For example, if you're using a custom scheduler, you can use this parameter to specify the reason for stopping the task here, and the message appears in subsequent DescribeTasks API operations on this task.

" } } }, @@ -5833,7 +5836,7 @@ }, "stopCode":{ "shape":"TaskStopCode", - "documentation":"

The stop code indicating why a task was stopped. The stoppedReason might contain additional details.

For more information about stop code, see Stopped tasks error codes in the Amazon ECS User Guide.

The following are valid values:

  • TaskFailedToStart

  • EssentialContainerExited

  • UserInitiated

  • TerminationNotice

  • ServiceSchedulerInitiated

  • SpotInterruption

" + "documentation":"

The stop code indicating why a task was stopped. The stoppedReason might contain additional details.

For more information about stop code, see Stopped tasks error codes in the Amazon ECS User Guide.

" }, "stoppedAt":{ "shape":"Timestamp", @@ -6358,7 +6361,7 @@ "documentation":"

The hard limit for the ulimit type.

" } }, - "documentation":"

The ulimit settings to pass to the container.

Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and the default hard limit is 4096.

You can specify the ulimit settings for a container in a task definition.

" + "documentation":"

The ulimit settings to pass to the container.

Amazon ECS tasks hosted on Fargate use the default resource limit values set by the operating system with the exception of the nofile resource limit parameter which Fargate overrides. The nofile resource limit sets a restriction on the number of open files that a container can use. The default nofile soft limit is 1024 and the default hard limit is 65535.

You can specify the ulimit settings for a container in a task definition.

" }, "UlimitList":{ "type":"list", diff --git a/awscli/botocore/data/lightsail/2016-11-28/service-2.json b/awscli/botocore/data/lightsail/2016-11-28/service-2.json index e3a459b53d63..ea9d9a766f8a 100644 --- a/awscli/botocore/data/lightsail/2016-11-28/service-2.json +++ b/awscli/botocore/data/lightsail/2016-11-28/service-2.json @@ -3832,6 +3832,10 @@ "supportedAppCategories":{ "shape":"AppCategoryList", "documentation":"

Virtual computer blueprints that are supported by a Lightsail for Research bundle.

This parameter only applies to Lightsail for Research resources.

" + }, + "publicIpv4AddressCount":{ + "shape":"integer", + "documentation":"

An integer that indicates the public ipv4 address count included in the bundle, the value is either 0 or 1.

" } }, "documentation":"

Describes a bundle, which is a set of specs describing your virtual private server (or instance).

" @@ -8849,6 +8853,10 @@ "shape":"IpAddress", "documentation":"

The public IP address of the Amazon Lightsail instance.

" }, + "ipv6Addresses":{ + "shape":"Ipv6AddressList", + "documentation":"

The IPv6 address of the Amazon Lightsail instance.

" + }, "password":{ "shape":"string", "documentation":"

For RDP access, the password for your Amazon Lightsail instance. Password will be an empty string if the password for your new instance is not ready yet. When you create an instance, it can take up to 15 minutes for the instance to be ready.

If you create an instance using any key pair other than the default (LightsailDefaultKeyPair), password will always be an empty string.

If you change the Administrator password on the instance, Lightsail will continue to return the original password value. When accessing the instance using RDP, you need to manually enter the Administrator password after changing it from the default.

" diff --git a/awscli/botocore/data/outposts/2019-12-03/endpoint-rule-set-1.json b/awscli/botocore/data/outposts/2019-12-03/endpoint-rule-set-1.json index bca1f55e1e5c..840c00e4b8ff 100644 --- a/awscli/botocore/data/outposts/2019-12-03/endpoint-rule-set-1.json +++ b/awscli/botocore/data/outposts/2019-12-03/endpoint-rule-set-1.json @@ -40,7 +40,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -83,7 +82,8 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -96,7 +96,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -110,7 +109,6 @@ "assign": "PartitionResult" } ], - "type": "tree", "rules": [ { "conditions": [ @@ -133,7 +131,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -168,7 +165,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -179,14 +175,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS and DualStack are enabled, but this partition does not support one or both", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -200,14 +198,12 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ - true, { "fn": "getAttr", "argv": [ @@ -216,18 +212,17 @@ }, "supportsFIPS" ] - } + }, + true ] } ], - "type": "tree", "rules": [ { "conditions": [ { "fn": "stringEquals", "argv": [ - "aws-us-gov", { "fn": "getAttr", "argv": [ @@ -236,7 +231,8 @@ }, "name" ] - } + }, + "aws-us-gov" ] } ], @@ -256,14 +252,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS is enabled but this partition does not support FIPS", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -277,7 +275,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -297,7 +294,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -308,14 +304,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "DualStack is enabled but this partition does not support DualStack", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [], @@ -326,9 +324,11 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" } - ] + ], + "type": "tree" }, { "conditions": [], diff --git a/awscli/botocore/data/outposts/2019-12-03/service-2.json b/awscli/botocore/data/outposts/2019-12-03/service-2.json index f1aadf41456e..82acb0c945ad 100644 --- a/awscli/botocore/data/outposts/2019-12-03/service-2.json +++ b/awscli/botocore/data/outposts/2019-12-03/service-2.json @@ -1309,7 +1309,6 @@ }, "LineItemQuantity":{ "type":"integer", - "max":20, "min":1 }, "LineItemRequest":{ @@ -2048,7 +2047,6 @@ "StartConnectionRequest":{ "type":"structure", "required":[ - "DeviceSerialNumber", "AssetId", "ClientPublicKey", "NetworkInterfaceDeviceIndex" diff --git a/awscli/botocore/data/rds/2014-10-31/service-2.json b/awscli/botocore/data/rds/2014-10-31/service-2.json index f0d86b3eef6b..e9f1eca55620 100644 --- a/awscli/botocore/data/rds/2014-10-31/service-2.json +++ b/awscli/botocore/data/rds/2014-10-31/service-2.json @@ -534,6 +534,28 @@ ], "documentation":"

Creates a new DB security group. DB security groups control access to a DB instance.

A DB security group controls access to EC2-Classic DB instances that are not in a VPC.

EC2-Classic was retired on August 15, 2022. If you haven't migrated from EC2-Classic to a VPC, we recommend that you migrate as soon as possible. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide, the blog EC2-Classic Networking is Retiring – Here’s How to Prepare, and Moving a DB instance not in a VPC into a VPC in the Amazon RDS User Guide.

" }, + "CreateDBShardGroup":{ + "name":"CreateDBShardGroup", + "http":{ + "method":"POST", + "requestUri":"/" + }, + "input":{"shape":"CreateDBShardGroupMessage"}, + "output":{ + "shape":"DBShardGroup", + "resultWrapper":"CreateDBShardGroupResult" + }, + "errors":[ + {"shape":"DBShardGroupAlreadyExistsFault"}, + {"shape":"DBClusterNotFoundFault"}, + {"shape":"MaxDBShardGroupLimitReached"}, + {"shape":"InvalidDBClusterStateFault"}, + {"shape":"InvalidMaxAcuFault"}, + {"shape":"UnsupportedDBEngineVersionFault"}, + {"shape":"InvalidVPCNetworkStateFault"} + ], + "documentation":"

Creates a new DB shard group for Aurora Limitless Database. You must enable Aurora Limitless Database to create a DB shard group.

Valid for: Aurora DB clusters only

" + }, "CreateDBSnapshot":{ "name":"CreateDBSnapshot", "http":{ @@ -889,6 +911,24 @@ ], "documentation":"

Deletes a DB security group.

The specified DB security group must not be associated with any DB instances.

EC2-Classic was retired on August 15, 2022. If you haven't migrated from EC2-Classic to a VPC, we recommend that you migrate as soon as possible. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide, the blog EC2-Classic Networking is Retiring – Here’s How to Prepare, and Moving a DB instance not in a VPC into a VPC in the Amazon RDS User Guide.

" }, + "DeleteDBShardGroup":{ + "name":"DeleteDBShardGroup", + "http":{ + "method":"POST", + "requestUri":"/" + }, + "input":{"shape":"DeleteDBShardGroupMessage"}, + "output":{ + "shape":"DBShardGroup", + "resultWrapper":"DeleteDBShardGroupResult" + }, + "errors":[ + {"shape":"DBShardGroupNotFoundFault"}, + {"shape":"InvalidDBShardGroupStateFault"}, + {"shape":"InvalidDBClusterStateFault"} + ], + "documentation":"

Deletes an Aurora Limitless Database DB shard group.

" + }, "DeleteDBSnapshot":{ "name":"DeleteDBSnapshot", "http":{ @@ -1388,6 +1428,23 @@ ], "documentation":"

Returns a list of DBSecurityGroup descriptions. If a DBSecurityGroupName is specified, the list will contain only the descriptions of the specified DB security group.

EC2-Classic was retired on August 15, 2022. If you haven't migrated from EC2-Classic to a VPC, we recommend that you migrate as soon as possible. For more information, see Migrate from EC2-Classic to a VPC in the Amazon EC2 User Guide, the blog EC2-Classic Networking is Retiring – Here’s How to Prepare, and Moving a DB instance not in a VPC into a VPC in the Amazon RDS User Guide.

" }, + "DescribeDBShardGroups":{ + "name":"DescribeDBShardGroups", + "http":{ + "method":"POST", + "requestUri":"/" + }, + "input":{"shape":"DescribeDBShardGroupsMessage"}, + "output":{ + "shape":"DescribeDBShardGroupsResponse", + "resultWrapper":"DescribeDBShardGroupsResult" + }, + "errors":[ + {"shape":"DBShardGroupNotFoundFault"}, + {"shape":"DBClusterNotFoundFault"} + ], + "documentation":"

Describes existing Aurora Limitless Database DB shard groups.

" + }, "DescribeDBSnapshotAttributes":{ "name":"DescribeDBSnapshotAttributes", "http":{ @@ -1771,7 +1828,7 @@ {"shape":"InvalidDBClusterStateFault"}, {"shape":"InvalidDBInstanceStateFault"} ], - "documentation":"

Forces a failover for a DB cluster.

For an Aurora DB cluster, failover for a DB cluster promotes one of the Aurora Replicas (read-only instances) in the DB cluster to be the primary DB instance (the cluster writer).

For a Multi-AZ DB cluster, failover for a DB cluster promotes one of the readable standby DB instances (read-only instances) in the DB cluster to be the primary DB instance (the cluster writer).

An Amazon Aurora DB cluster automatically fails over to an Aurora Replica, if one exists, when the primary DB instance fails. A Multi-AZ DB cluster automatically fails over to a readable standby DB instance when the primary DB instance fails.

To simulate a failure of a primary instance for testing, you can force a failover. Because each instance in a DB cluster has its own endpoint address, make sure to clean up and re-establish any existing connections that use those endpoint addresses when the failover is complete.

For more information on Amazon Aurora DB clusters, see What is Amazon Aurora? in the Amazon Aurora User Guide.

For more information on Multi-AZ DB clusters, see Multi-AZ DB cluster deployments in the Amazon RDS User Guide.

" + "documentation":"

Forces a failover for a DB cluster.

For an Aurora DB cluster, failover for a DB cluster promotes one of the Aurora Replicas (read-only instances) in the DB cluster to be the primary DB instance (the cluster writer).

For a Multi-AZ DB cluster, after RDS terminates the primary DB instance, the internal monitoring system detects that the primary DB instance is unhealthy and promotes a readable standby (read-only instances) in the DB cluster to be the primary DB instance (the cluster writer). Failover times are typically less than 35 seconds.

An Amazon Aurora DB cluster automatically fails over to an Aurora Replica, if one exists, when the primary DB instance fails. A Multi-AZ DB cluster automatically fails over to a readable standby DB instance when the primary DB instance fails.

To simulate a failure of a primary instance for testing, you can force a failover. Because each instance in a DB cluster has its own endpoint address, make sure to clean up and re-establish any existing connections that use those endpoint addresses when the failover is complete.

For more information on Amazon Aurora DB clusters, see What is Amazon Aurora? in the Amazon Aurora User Guide.

For more information on Multi-AZ DB clusters, see Multi-AZ DB cluster deployments in the Amazon RDS User Guide.

" }, "FailoverGlobalCluster":{ "name":"FailoverGlobalCluster", @@ -2092,6 +2149,25 @@ "errors":[], "documentation":"

Updates the recommendation status and recommended action status for the specified recommendation.

" }, + "ModifyDBShardGroup":{ + "name":"ModifyDBShardGroup", + "http":{ + "method":"POST", + "requestUri":"/" + }, + "input":{"shape":"ModifyDBShardGroupMessage"}, + "output":{ + "shape":"DBShardGroup", + "resultWrapper":"ModifyDBShardGroupResult" + }, + "errors":[ + {"shape":"InvalidDBClusterStateFault"}, + {"shape":"DBShardGroupAlreadyExistsFault"}, + {"shape":"DBShardGroupNotFoundFault"}, + {"shape":"InvalidMaxAcuFault"} + ], + "documentation":"

Modifies the settings of an Aurora Limitless Database DB shard group. You can change one or more settings by specifying these parameters and the new values in the request.

" + }, "ModifyDBSnapshot":{ "name":"ModifyDBSnapshot", "http":{ @@ -2309,6 +2385,23 @@ ], "documentation":"

You might need to reboot your DB instance, usually for maintenance reasons. For example, if you make certain modifications, or if you change the DB parameter group associated with the DB instance, you must reboot the instance for the changes to take effect.

Rebooting a DB instance restarts the database engine service. Rebooting a DB instance results in a momentary outage, during which the DB instance status is set to rebooting.

For more information about rebooting, see Rebooting a DB Instance in the Amazon RDS User Guide.

This command doesn't apply to RDS Custom.

If your DB instance is part of a Multi-AZ DB cluster, you can reboot the DB cluster with the RebootDBCluster operation.

" }, + "RebootDBShardGroup":{ + "name":"RebootDBShardGroup", + "http":{ + "method":"POST", + "requestUri":"/" + }, + "input":{"shape":"RebootDBShardGroupMessage"}, + "output":{ + "shape":"DBShardGroup", + "resultWrapper":"RebootDBShardGroupResult" + }, + "errors":[ + {"shape":"DBShardGroupNotFoundFault"}, + {"shape":"InvalidDBShardGroupStateFault"} + ], + "documentation":"

You might need to reboot your DB shard group, usually for maintenance reasons. For example, if you make certain modifications, reboot the DB shard group for the changes to take effect.

This operation applies only to Aurora Limitless Database DBb shard groups.

" + }, "RegisterDBProxyTargets":{ "name":"RegisterDBProxyTargets", "http":{ @@ -3877,7 +3970,7 @@ }, "TargetDBInstanceClass":{ "shape":"TargetDBInstanceClass", - "documentation":"

Specify the DB instance class for the databases in the green environment.

" + "documentation":"

Specify the DB instance class for the databases in the green environment.

This parameter only applies to RDS DB instances, because DB instances within an Aurora DB cluster can have multiple different instance classes. If you're creating a blue/green deployment from an Aurora DB cluster, don't specify this parameter. After the green environment is created, you can individually modify the instance classes of the DB instances within the green DB cluster.

" }, "UpgradeTargetStorageConfig":{ "shape":"BooleanOptional", @@ -4174,6 +4267,10 @@ "shape":"IntegerOptional", "documentation":"

The number of days to retain Performance Insights data.

Valid for Cluster Type: Multi-AZ DB clusters only

Valid Values:

  • 7

  • month * 31, where month is a number of months from 1-23. Examples: 93 (3 months * 31), 341 (11 months * 31), 589 (19 months * 31)

  • 731

Default: 7 days

If you specify a retention period that isn't valid, such as 94, Amazon RDS issues an error.

" }, + "EnableLimitlessDatabase":{ + "shape":"BooleanOptional", + "documentation":"

Specifies whether to enable Aurora Limitless Database. You must enable Aurora Limitless Database to create a DB shard group.

Valid for: Aurora DB clusters only

" + }, "ServerlessV2ScalingConfiguration":{"shape":"ServerlessV2ScalingConfiguration"}, "NetworkType":{ "shape":"String", @@ -4877,6 +4974,36 @@ "DBSecurityGroup":{"shape":"DBSecurityGroup"} } }, + "CreateDBShardGroupMessage":{ + "type":"structure", + "required":[ + "DBShardGroupIdentifier", + "DBClusterIdentifier", + "MaxACU" + ], + "members":{ + "DBShardGroupIdentifier":{ + "shape":"String", + "documentation":"

The name of the DB shard group.

" + }, + "DBClusterIdentifier":{ + "shape":"String", + "documentation":"

The name of the primary DB cluster for the DB shard group.

" + }, + "ComputeRedundancy":{ + "shape":"IntegerOptional", + "documentation":"

Specifies whether to create standby instances for the DB shard group. Valid values are the following:

  • 0 - Creates a single, primary DB instance for each physical shard. This is the default value, and the only one supported for the preview.

  • 1 - Creates a primary DB instance and a standby instance in a different Availability Zone (AZ) for each physical shard.

  • 2 - Creates a primary DB instance and two standby instances in different AZs for each physical shard.

" + }, + "MaxACU":{ + "shape":"DoubleOptional", + "documentation":"

The maximum capacity of the DB shard group in Aurora capacity units (ACUs).

" + }, + "PubliclyAccessible":{ + "shape":"BooleanOptional", + "documentation":"

Specifies whether the DB shard group is publicly accessible.

When the DB shard group is publicly accessible, its Domain Name System (DNS) endpoint resolves to the private IP address from within the DB shard group's virtual private cloud (VPC). It resolves to the public IP address from outside of the DB shard group's VPC. Access to the DB shard group is ultimately controlled by the security group it uses. That public access is not permitted if the security group assigned to the DB shard group doesn't permit it.

When the DB shard group isn't publicly accessible, it is an internal DB shard group with a DNS name that resolves to a private IP address.

Default: The default behavior varies depending on whether DBSubnetGroupName is specified.

If DBSubnetGroupName isn't specified, and PubliclyAccessible isn't specified, the following applies:

  • If the default VPC in the target Region doesn’t have an internet gateway attached to it, the DB shard group is private.

  • If the default VPC in the target Region has an internet gateway attached to it, the DB shard group is public.

If DBSubnetGroupName is specified, and PubliclyAccessible isn't specified, the following applies:

  • If the subnets are part of a VPC that doesn’t have an internet gateway attached to it, the DB shard group is private.

  • If the subnets are part of a VPC that has an internet gateway attached to it, the DB shard group is public.

" + } + } + }, "CreateDBSnapshotMessage":{ "type":"structure", "required":[ @@ -4948,7 +5075,7 @@ }, "SnsTopicArn":{ "shape":"String", - "documentation":"

The Amazon Resource Name (ARN) of the SNS topic created for event notification. The ARN is created by Amazon SNS when you create a topic and subscribe to it.

" + "documentation":"

The Amazon Resource Name (ARN) of the SNS topic created for event notification. SNS automatically creates the ARN when you create a topic and subscribe to it.

RDS doesn't support FIFO (first in, first out) topics. For more information, see Message ordering and deduplication (FIFO topics) in the Amazon Simple Notification Service Developer Guide.

" }, "SourceType":{ "shape":"String", @@ -5511,6 +5638,10 @@ "AwsBackupRecoveryPointArn":{ "shape":"String", "documentation":"

The Amazon Resource Name (ARN) of the recovery point in Amazon Web Services Backup.

" + }, + "LimitlessDatabase":{ + "shape":"LimitlessDatabase", + "documentation":"

The details for Aurora Limitless Database.

" } }, "documentation":"

Contains the details of an Amazon Aurora DB cluster or Multi-AZ DB cluster.

For an Amazon Aurora DB cluster, this data type is used as a response element in the operations CreateDBCluster, DeleteDBCluster, DescribeDBClusters, FailoverDBCluster, ModifyDBCluster, PromoteReadReplicaDBCluster, RestoreDBClusterFromS3, RestoreDBClusterFromSnapshot, RestoreDBClusterToPointInTime, StartDBCluster, and StopDBCluster.

For a Multi-AZ DB cluster, this data type is used as a response element in the operations CreateDBCluster, DeleteDBCluster, DescribeDBClusters, FailoverDBCluster, ModifyDBCluster, RebootDBCluster, RestoreDBClusterFromSnapshot, and RestoreDBClusterToPointInTime.

For more information on Amazon Aurora DB clusters, see What is Amazon Aurora? in the Amazon Aurora User Guide.

For more information on Multi-AZ DB clusters, see Multi-AZ deployments with two readable standby DB instances in the Amazon RDS User Guide.

", @@ -7877,6 +8008,74 @@ "locationName":"DBSecurityGroup" } }, + "DBShardGroup":{ + "type":"structure", + "members":{ + "DBShardGroupResourceId":{ + "shape":"String", + "documentation":"

The Amazon Web Services Region-unique, immutable identifier for the DB shard group.

" + }, + "DBShardGroupIdentifier":{ + "shape":"String", + "documentation":"

The name of the DB shard group.

" + }, + "DBClusterIdentifier":{ + "shape":"String", + "documentation":"

The name of the primary DB cluster for the DB shard group.

" + }, + "MaxACU":{ + "shape":"DoubleOptional", + "documentation":"

The maximum capacity of the DB shard group in Aurora capacity units (ACUs).

" + }, + "ComputeRedundancy":{ + "shape":"IntegerOptional", + "documentation":"

Specifies whether to create standby instances for the DB shard group. Valid values are the following:

  • 0 - Creates a single, primary DB instance for each physical shard. This is the default value, and the only one supported for the preview.

  • 1 - Creates a primary DB instance and a standby instance in a different Availability Zone (AZ) for each physical shard.

  • 2 - Creates a primary DB instance and two standby instances in different AZs for each physical shard.

" + }, + "Status":{ + "shape":"String", + "documentation":"

The status of the DB shard group.

" + }, + "PubliclyAccessible":{ + "shape":"BooleanOptional", + "documentation":"

Indicates whether the DB shard group is publicly accessible.

When the DB shard group is publicly accessible, its Domain Name System (DNS) endpoint resolves to the private IP address from within the DB shard group's virtual private cloud (VPC). It resolves to the public IP address from outside of the DB shard group's VPC. Access to the DB shard group is ultimately controlled by the security group it uses. That public access isn't permitted if the security group assigned to the DB shard group doesn't permit it.

When the DB shard group isn't publicly accessible, it is an internal DB shard group with a DNS name that resolves to a private IP address.

For more information, see CreateDBShardGroup.

This setting is only for Aurora Limitless Database.

" + }, + "Endpoint":{ + "shape":"String", + "documentation":"

The connection endpoint for the DB shard group.

" + } + } + }, + "DBShardGroupAlreadyExistsFault":{ + "type":"structure", + "members":{ + }, + "documentation":"

The specified DB shard group name must be unique in your Amazon Web Services account in the specified Amazon Web Services Region.

", + "error":{ + "code":"DBShardGroupAlreadyExists", + "httpStatusCode":400, + "senderFault":true + }, + "exception":true + }, + "DBShardGroupNotFoundFault":{ + "type":"structure", + "members":{ + }, + "documentation":"

The specified DB shard group name wasn't found.

", + "error":{ + "code":"DBShardGroupNotFound", + "httpStatusCode":404, + "senderFault":true + }, + "exception":true + }, + "DBShardGroupsList":{ + "type":"list", + "member":{ + "shape":"DBShardGroup", + "locationName":"DBShardGroup" + } + }, "DBSnapshot":{ "type":"structure", "members":{ @@ -8570,6 +8769,16 @@ }, "documentation":"

" }, + "DeleteDBShardGroupMessage":{ + "type":"structure", + "required":["DBShardGroupIdentifier"], + "members":{ + "DBShardGroupIdentifier":{ + "shape":"String", + "documentation":"

Teh name of the DB shard group to delete.

" + } + } + }, "DeleteDBSnapshotMessage":{ "type":"structure", "required":["DBSnapshotIdentifier"], @@ -8970,7 +9179,7 @@ }, "MaxRecords":{ "shape":"IntegerOptional", - "documentation":"

The maximum number of records to include in the response. If more records exist than the specified MaxRecords value, a pagination token called a marker is included in the response so you can retrieve the remaining results.

Default: 100

Constraints: Minimum 20, maximum 100.

" + "documentation":"

The maximum number of records to include in the response. If more records exist than the specified MaxRecords value, a pagination token called a marker is included in the response so you can retrieve the remaining results.

Default: 100

Constraints: Minimum 20, maximum 100

" }, "Marker":{ "shape":"String", @@ -9403,6 +9612,40 @@ }, "documentation":"

" }, + "DescribeDBShardGroupsMessage":{ + "type":"structure", + "members":{ + "DBShardGroupIdentifier":{ + "shape":"String", + "documentation":"

The user-supplied DB shard group identifier or the Amazon Resource Name (ARN) of the DB shard group. If this parameter is specified, information for only the specific DB shard group is returned. This parameter isn't case-sensitive.

Constraints:

  • If supplied, must match an existing DB shard group identifier.

" + }, + "Filters":{ + "shape":"FilterList", + "documentation":"

A filter that specifies one or more DB shard groups to describe.

" + }, + "Marker":{ + "shape":"String", + "documentation":"

An optional pagination token provided by a previous DescribeDBShardGroups request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords.

" + }, + "MaxRecords":{ + "shape":"MaxRecords", + "documentation":"

The maximum number of records to include in the response. If more records exist than the specified MaxRecords value, a pagination token called a marker is included in the response so you can retrieve the remaining results.

Default: 100

Constraints: Minimum 20, maximum 100

" + } + } + }, + "DescribeDBShardGroupsResponse":{ + "type":"structure", + "members":{ + "DBShardGroups":{ + "shape":"DBShardGroupsList", + "documentation":"

Contains a list of DB shard groups for the user.

" + }, + "Marker":{ + "shape":"String", + "documentation":"

A pagination token that can be used in a later DescribeDBClusters request.

" + } + } + }, "DescribeDBSnapshotAttributesMessage":{ "type":"structure", "required":["DBSnapshotIdentifier"], @@ -11285,6 +11528,18 @@ }, "exception":true }, + "InvalidDBShardGroupStateFault":{ + "type":"structure", + "members":{ + }, + "documentation":"

The DB shard group must be in the available state.

", + "error":{ + "code":"InvalidDBShardGroupState", + "httpStatusCode":400, + "senderFault":true + }, + "exception":true + }, "InvalidDBSnapshotStateFault":{ "type":"structure", "members":{ @@ -11405,6 +11660,18 @@ }, "exception":true }, + "InvalidMaxAcuFault":{ + "type":"structure", + "members":{ + }, + "documentation":"

The maximum capacity of the DB shard group must be 48-7168 Aurora capacity units (ACUs).

", + "error":{ + "code":"InvalidMaxAcu", + "httpStatusCode":400, + "senderFault":true + }, + "exception":true + }, "InvalidOptionGroupStateFault":{ "type":"structure", "members":{ @@ -11509,6 +11776,33 @@ "min":1, "pattern":"[a-zA-Z0-9_:\\-\\/]+" }, + "LimitlessDatabase":{ + "type":"structure", + "members":{ + "Status":{ + "shape":"LimitlessDatabaseStatus", + "documentation":"

The status of Aurora Limitless Database.

" + }, + "MinRequiredACU":{ + "shape":"DoubleOptional", + "documentation":"

The minimum required capacity for Aurora Limitless Database in Aurora capacity units (ACUs).

" + } + }, + "documentation":"

Contains details for Aurora Limitless Database.

" + }, + "LimitlessDatabaseStatus":{ + "type":"string", + "enum":[ + "active", + "not-in-use", + "enabled", + "disabled", + "enabling", + "disabling", + "modifying-max-capacity", + "error" + ] + }, "ListTagsForResourceMessage":{ "type":"structure", "required":["ResourceName"], @@ -11563,6 +11857,18 @@ }, "documentation":"

Contains the secret managed by RDS in Amazon Web Services Secrets Manager for the master user password.

For more information, see Password management with Amazon Web Services Secrets Manager in the Amazon RDS User Guide and Password management with Amazon Web Services Secrets Manager in the Amazon Aurora User Guide.

" }, + "MaxDBShardGroupLimitReached":{ + "type":"structure", + "members":{ + }, + "documentation":"

The maximum number of DB shard groups for your Amazon Web Services account in the specified Amazon Web Services Region has been reached.

", + "error":{ + "code":"MaxDBShardGroupLimitReached", + "httpStatusCode":400, + "senderFault":true + }, + "exception":true + }, "MaxRecords":{ "type":"integer", "max":100, @@ -11945,6 +12251,10 @@ "AwsBackupRecoveryPointArn":{ "shape":"AwsBackupRecoveryPointArn", "documentation":"

The Amazon Resource Name (ARN) of the recovery point in Amazon Web Services Backup.

" + }, + "EnableLimitlessDatabase":{ + "shape":"BooleanOptional", + "documentation":"

Specifies whether to enable Aurora Limitless Database. You must enable Aurora Limitless Database to create a DB shard group.

Valid for: Aurora DB clusters only

" } }, "documentation":"

" @@ -12406,6 +12716,20 @@ } } }, + "ModifyDBShardGroupMessage":{ + "type":"structure", + "required":["DBShardGroupIdentifier"], + "members":{ + "DBShardGroupIdentifier":{ + "shape":"String", + "documentation":"

The name of the DB shard group to modify.

" + }, + "MaxACU":{ + "shape":"DoubleOptional", + "documentation":"

The maximum capacity of the DB shard group in Aurora capacity units (ACUs).

" + } + } + }, "ModifyDBSnapshotAttributeMessage":{ "type":"structure", "required":[ @@ -13749,6 +14073,16 @@ "DBInstance":{"shape":"DBInstance"} } }, + "RebootDBShardGroupMessage":{ + "type":"structure", + "required":["DBShardGroupIdentifier"], + "members":{ + "DBShardGroupIdentifier":{ + "shape":"String", + "documentation":"

The name of the DB shard group to reboot.

" + } + } + }, "RecommendedAction":{ "type":"structure", "members":{ @@ -16303,6 +16637,18 @@ }, "documentation":"

A time zone associated with a DBInstance or a DBSnapshot. This data type is an element in the response to the DescribeDBInstances, the DescribeDBSnapshots, and the DescribeDBEngineVersions actions.

" }, + "UnsupportedDBEngineVersionFault":{ + "type":"structure", + "members":{ + }, + "documentation":"

The specified DB engine version isn't supported for Aurora Limitless Database.

", + "error":{ + "code":"UnsupportedDBEngineVersion", + "httpStatusCode":400, + "senderFault":true + }, + "exception":true + }, "UpgradeTarget":{ "type":"structure", "members":{ diff --git a/awscli/botocore/data/storagegateway/2013-06-30/endpoint-rule-set-1.json b/awscli/botocore/data/storagegateway/2013-06-30/endpoint-rule-set-1.json index 9f3c8e2c2b97..b0a53a28b972 100644 --- a/awscli/botocore/data/storagegateway/2013-06-30/endpoint-rule-set-1.json +++ b/awscli/botocore/data/storagegateway/2013-06-30/endpoint-rule-set-1.json @@ -40,7 +40,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -83,7 +82,8 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -96,7 +96,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -110,7 +109,6 @@ "assign": "PartitionResult" } ], - "type": "tree", "rules": [ { "conditions": [ @@ -133,7 +131,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -168,7 +165,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -179,14 +175,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS and DualStack are enabled, but this partition does not support one or both", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -200,14 +198,12 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ - true, { "fn": "getAttr", "argv": [ @@ -216,11 +212,11 @@ }, "supportsFIPS" ] - } + }, + true ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -231,14 +227,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS is enabled but this partition does not support FIPS", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -252,7 +250,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -272,7 +269,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -283,14 +279,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "DualStack is enabled but this partition does not support DualStack", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [], @@ -301,9 +299,11 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" } - ] + ], + "type": "tree" }, { "conditions": [], diff --git a/awscli/botocore/data/storagegateway/2013-06-30/service-2.json b/awscli/botocore/data/storagegateway/2013-06-30/service-2.json index 153f65c18cf2..f86ef02157a4 100644 --- a/awscli/botocore/data/storagegateway/2013-06-30/service-2.json +++ b/awscli/botocore/data/storagegateway/2013-06-30/service-2.json @@ -656,7 +656,7 @@ {"shape":"InvalidGatewayRequestException"}, {"shape":"InternalServerError"} ], - "documentation":"

Returns a description of the specified Amazon Resource Name (ARN) of virtual tapes. If a TapeARN is not specified, returns a description of all virtual tapes associated with the specified gateway. This operation is only supported in the tape gateway type.

" + "documentation":"

Returns a description of virtual tapes that correspond to the specified Amazon Resource Names (ARNs). If TapeARN is not specified, returns a description of the virtual tapes associated with the specified gateway. This operation is only supported for the tape gateway type.

The operation supports pagination. By default, the operation returns a maximum of up to 100 tapes. You can optionally specify the Limit field in the body to limit the number of tapes in the response. If the number of tapes returned in the response is truncated, the response includes a Marker field. You can use this Marker value in your subsequent request to retrieve the next set of tapes.

" }, "DescribeUploadBuffer":{ "name":"DescribeUploadBuffer", @@ -922,7 +922,7 @@ {"shape":"InvalidGatewayRequestException"}, {"shape":"InternalServerError"} ], - "documentation":"

Sends you notification through CloudWatch Events when all files written to your file share have been uploaded to S3. Amazon S3.

Storage Gateway can send a notification through Amazon CloudWatch Events when all files written to your file share up to that point in time have been uploaded to Amazon S3. These files include files written to the file share up to the time that you make a request for notification. When the upload is done, Storage Gateway sends you notification through an Amazon CloudWatch Event. You can configure CloudWatch Events to send the notification through event targets such as Amazon SNS or Lambda function. This operation is only supported for S3 File Gateways.

For more information, see Getting file upload notification in the Amazon S3 File Gateway User Guide.

" + "documentation":"

Sends you notification through CloudWatch Events when all files written to your file share have been uploaded to Amazon S3.

Storage Gateway can send a notification through Amazon CloudWatch Events when all files written to your file share up to that point in time have been uploaded to Amazon S3. These files include files written to the file share up to the time that you make a request for notification. When the upload is done, Storage Gateway sends you notification through an Amazon CloudWatch Event. You can configure CloudWatch Events to send the notification through event targets such as Amazon SNS or Lambda function. This operation is only supported for S3 File Gateways.

For more information, see Getting file upload notification in the Amazon S3 File Gateway User Guide.

" }, "RefreshCache":{ "name":"RefreshCache", @@ -936,7 +936,7 @@ {"shape":"InvalidGatewayRequestException"}, {"shape":"InternalServerError"} ], - "documentation":"

Refreshes the cached inventory of objects for the specified file share. This operation finds objects in the Amazon S3 bucket that were added, removed, or replaced since the gateway last listed the bucket's contents and cached the results. This operation does not import files into the S3 File Gateway cache storage. It only updates the cached inventory to reflect changes in the inventory of the objects in the S3 bucket. This operation is only supported in the S3 File Gateway types.

You can subscribe to be notified through an Amazon CloudWatch event when your RefreshCache operation completes. For more information, see Getting notified about file operations in the Storage Gateway User Guide. This operation is Only supported for S3 File Gateways.

When this API is called, it only initiates the refresh operation. When the API call completes and returns a success code, it doesn't necessarily mean that the file refresh has completed. You should use the refresh-complete notification to determine that the operation has completed before you check for new files on the gateway file share. You can subscribe to be notified through a CloudWatch event when your RefreshCache operation completes.

Throttle limit: This API is asynchronous, so the gateway will accept no more than two refreshes at any time. We recommend using the refresh-complete CloudWatch event notification before issuing additional requests. For more information, see Getting notified about file operations in the Storage Gateway User Guide.

  • Wait at least 60 seconds between consecutive RefreshCache API requests.

  • If you invoke the RefreshCache API when two requests are already being processed, any new request will cause an InvalidGatewayRequestException error because too many requests were sent to the server.

The S3 bucket name does not need to be included when entering the list of folders in the FolderList parameter.

For more information, see Getting notified about file operations in the Storage Gateway User Guide.

" + "documentation":"

Refreshes the cached inventory of objects for the specified file share. This operation finds objects in the Amazon S3 bucket that were added, removed, or replaced since the gateway last listed the bucket's contents and cached the results. This operation does not import files into the S3 File Gateway cache storage. It only updates the cached inventory to reflect changes in the inventory of the objects in the S3 bucket. This operation is only supported in the S3 File Gateway types.

You can subscribe to be notified through an Amazon CloudWatch event when your RefreshCache operation completes. For more information, see Getting notified about file operations in the Amazon S3 File Gateway User Guide. This operation is Only supported for S3 File Gateways.

When this API is called, it only initiates the refresh operation. When the API call completes and returns a success code, it doesn't necessarily mean that the file refresh has completed. You should use the refresh-complete notification to determine that the operation has completed before you check for new files on the gateway file share. You can subscribe to be notified through a CloudWatch event when your RefreshCache operation completes.

Throttle limit: This API is asynchronous, so the gateway will accept no more than two refreshes at any time. We recommend using the refresh-complete CloudWatch event notification before issuing additional requests. For more information, see Getting notified about file operations in the Amazon S3 File Gateway User Guide.

  • Wait at least 60 seconds between consecutive RefreshCache API requests.

  • If you invoke the RefreshCache API when two requests are already being processed, any new request will cause an InvalidGatewayRequestException error because too many requests were sent to the server.

The S3 bucket name does not need to be included when entering the list of folders in the FolderList parameter.

For more information, see Getting notified about file operations in the Amazon S3 File Gateway User Guide.

" }, "RemoveTagsFromResource":{ "name":"RemoveTagsFromResource", @@ -1034,7 +1034,7 @@ {"shape":"InvalidGatewayRequestException"}, {"shape":"InternalServerError"} ], - "documentation":"

Shuts down a gateway. To specify which gateway to shut down, use the Amazon Resource Name (ARN) of the gateway in the body of your request.

The operation shuts down the gateway service component running in the gateway's virtual machine (VM) and not the host VM.

If you want to shut down the VM, it is recommended that you first shut down the gateway component in the VM to avoid unpredictable conditions.

After the gateway is shutdown, you cannot call any other API except StartGateway, DescribeGatewayInformation, and ListGateways. For more information, see ActivateGateway. Your applications cannot read from or write to the gateway's storage volumes, and there are no snapshots taken.

When you make a shutdown request, you will get a 200 OK success response immediately. However, it might take some time for the gateway to shut down. You can call the DescribeGatewayInformation API to check the status. For more information, see ActivateGateway.

If do not intend to use the gateway again, you must delete the gateway (using DeleteGateway) to no longer pay software charges associated with the gateway.

" + "documentation":"

Shuts down a Tape Gateway or Volume Gateway. To specify which gateway to shut down, use the Amazon Resource Name (ARN) of the gateway in the body of your request.

This API action cannot be used to shut down S3 File Gateway or FSx File Gateway.

The operation shuts down the gateway service component running in the gateway's virtual machine (VM) and not the host VM.

If you want to shut down the VM, it is recommended that you first shut down the gateway component in the VM to avoid unpredictable conditions.

After the gateway is shutdown, you cannot call any other API except StartGateway, DescribeGatewayInformation, and ListGateways. For more information, see ActivateGateway. Your applications cannot read from or write to the gateway's storage volumes, and there are no snapshots taken.

When you make a shutdown request, you will get a 200 OK success response immediately. However, it might take some time for the gateway to shut down. You can call the DescribeGatewayInformation API to check the status. For more information, see ActivateGateway.

If do not intend to use the gateway again, you must delete the gateway (using DeleteGateway) to no longer pay software charges associated with the gateway.

" }, "StartAvailabilityMonitorTest":{ "name":"StartAvailabilityMonitorTest", @@ -3808,6 +3808,14 @@ "HostEnvironmentId":{ "shape":"HostEnvironmentId", "documentation":"

A unique identifier for the specific instance of the host platform running the gateway. This value is only available for certain host environments, and its format depends on the host environment type.

" + }, + "DeprecationDate":{ + "shape":"DeprecationDate", + "documentation":"

Date after which this gateway will not receive software updates for new features and bug fixes.

" + }, + "SoftwareVersion":{ + "shape":"SoftwareVersion", + "documentation":"

The version number of the software running on the gateway appliance.

" } }, "documentation":"

Describes a gateway object.

" From c1d38165edb6191d3f24075345eca3182fc053bd Mon Sep 17 00:00:00 2001 From: cli-v2-merge Date: Thu, 25 Jan 2024 20:34:47 +0000 Subject: [PATCH 7/7] Add changelog entries from latest v1 releases Pulled in changes from 1.32.27 to 1.32.28 --- .changes/next-release/apichange-acmpca-41635.json | 5 +++++ .changes/next-release/apichange-ec2-68071.json | 5 +++++ .changes/next-release/apichange-ecs-65084.json | 5 +++++ .changes/next-release/apichange-lightsail-81317.json | 5 +++++ .changes/next-release/apichange-outposts-79081.json | 5 +++++ .changes/next-release/apichange-rds-23447.json | 5 +++++ .changes/next-release/apichange-storagegateway-78897.json | 5 +++++ 7 files changed, 35 insertions(+) create mode 100644 .changes/next-release/apichange-acmpca-41635.json create mode 100644 .changes/next-release/apichange-ec2-68071.json create mode 100644 .changes/next-release/apichange-ecs-65084.json create mode 100644 .changes/next-release/apichange-lightsail-81317.json create mode 100644 .changes/next-release/apichange-outposts-79081.json create mode 100644 .changes/next-release/apichange-rds-23447.json create mode 100644 .changes/next-release/apichange-storagegateway-78897.json diff --git a/.changes/next-release/apichange-acmpca-41635.json b/.changes/next-release/apichange-acmpca-41635.json new file mode 100644 index 000000000000..e47e0e7fd4b3 --- /dev/null +++ b/.changes/next-release/apichange-acmpca-41635.json @@ -0,0 +1,5 @@ +{ + "category": "``acm-pca``", + "description": "AWS Private CA now supports an option to omit the CDP extension from issued certificates, when CRL revocation is enabled.", + "type": "api-change" +} \ No newline at end of file diff --git a/.changes/next-release/apichange-ec2-68071.json b/.changes/next-release/apichange-ec2-68071.json new file mode 100644 index 000000000000..02a8dbb678f2 --- /dev/null +++ b/.changes/next-release/apichange-ec2-68071.json @@ -0,0 +1,5 @@ +{ + "category": "``ec2``", + "description": "Introduced a new clientToken request parameter on CreateNetworkAcl and CreateRouteTable APIs. The clientToken parameter allows idempotent operations on the APIs.", + "type": "api-change" +} \ No newline at end of file diff --git a/.changes/next-release/apichange-ecs-65084.json b/.changes/next-release/apichange-ecs-65084.json new file mode 100644 index 000000000000..173c893815d4 --- /dev/null +++ b/.changes/next-release/apichange-ecs-65084.json @@ -0,0 +1,5 @@ +{ + "category": "``ecs``", + "description": "Documentation updates for Amazon ECS.", + "type": "api-change" +} \ No newline at end of file diff --git a/.changes/next-release/apichange-lightsail-81317.json b/.changes/next-release/apichange-lightsail-81317.json new file mode 100644 index 000000000000..85df2c1a604e --- /dev/null +++ b/.changes/next-release/apichange-lightsail-81317.json @@ -0,0 +1,5 @@ +{ + "category": "``lightsail``", + "description": "This release adds support for IPv6-only instance plans.", + "type": "api-change" +} \ No newline at end of file diff --git a/.changes/next-release/apichange-outposts-79081.json b/.changes/next-release/apichange-outposts-79081.json new file mode 100644 index 000000000000..edd704441862 --- /dev/null +++ b/.changes/next-release/apichange-outposts-79081.json @@ -0,0 +1,5 @@ +{ + "category": "``outposts``", + "description": "DeviceSerialNumber parameter is now optional in StartConnection API", + "type": "api-change" +} \ No newline at end of file diff --git a/.changes/next-release/apichange-rds-23447.json b/.changes/next-release/apichange-rds-23447.json new file mode 100644 index 000000000000..010489411c6d --- /dev/null +++ b/.changes/next-release/apichange-rds-23447.json @@ -0,0 +1,5 @@ +{ + "category": "``rds``", + "description": "This release adds support for Aurora Limitless Database.", + "type": "api-change" +} \ No newline at end of file diff --git a/.changes/next-release/apichange-storagegateway-78897.json b/.changes/next-release/apichange-storagegateway-78897.json new file mode 100644 index 000000000000..ffd086231886 --- /dev/null +++ b/.changes/next-release/apichange-storagegateway-78897.json @@ -0,0 +1,5 @@ +{ + "category": "``storagegateway``", + "description": "Add DeprecationDate and SoftwareVersion to response of ListGateways.", + "type": "api-change" +} \ No newline at end of file