From be71f136cb25b0f15cb49e34dee9a51c79cd9b2c Mon Sep 17 00:00:00 2001 From: aws-sdk-python-automation Date: Fri, 12 Apr 2024 18:05:36 +0000 Subject: [PATCH] Update to latest models --- .../api-change-cloudformation-60104.json | 5 + .../next-release/api-change-config-23095.json | 5 + .../next-release/api-change-glue-22808.json | 5 + .../api-change-healthlake-98449.json | 5 + .../api-change-iotfleethub-59928.json | 5 + .../next-release/api-change-kms-7898.json | 5 + .../api-change-mediatailor-52018.json | 5 + .../api-change-neptunegraph-69154.json | 5 + .../api-change-outposts-88601.json | 5 + .../api-change-redshift-2491.json | 5 + .../api-change-transfer-89170.json | 5 + .../cloudformation/2010-05-15/service-2.json | 44 ++++- .../data/config/2014-11-12/service-2.json | 10 +- botocore/data/glue/2017-03-31/service-2.json | 16 +- .../data/healthlake/2017-07-01/service-2.json | 33 +++- .../2020-11-03/endpoint-rule-set-1.json | 40 ++-- .../iotfleethub/2020-11-03/service-2.json | 26 +-- .../data/kms/2014-11-01/paginators-1.json | 7 + botocore/data/kms/2014-11-01/service-2.json | 173 +++++++++++++++++- .../mediatailor/2018-04-23/service-2.json | 24 +++ .../neptune-graph/2023-11-29/service-2.json | 6 +- .../data/outposts/2019-12-03/service-2.json | 3 +- .../data/redshift/2012-12-01/service-2.json | 4 + .../data/transfer/2018-11-05/service-2.json | 9 +- 24 files changed, 389 insertions(+), 61 deletions(-) create mode 100644 .changes/next-release/api-change-cloudformation-60104.json create mode 100644 .changes/next-release/api-change-config-23095.json create mode 100644 .changes/next-release/api-change-glue-22808.json create mode 100644 .changes/next-release/api-change-healthlake-98449.json create mode 100644 .changes/next-release/api-change-iotfleethub-59928.json create mode 100644 .changes/next-release/api-change-kms-7898.json create mode 100644 .changes/next-release/api-change-mediatailor-52018.json create mode 100644 .changes/next-release/api-change-neptunegraph-69154.json create mode 100644 .changes/next-release/api-change-outposts-88601.json create mode 100644 .changes/next-release/api-change-redshift-2491.json create mode 100644 .changes/next-release/api-change-transfer-89170.json diff --git a/.changes/next-release/api-change-cloudformation-60104.json b/.changes/next-release/api-change-cloudformation-60104.json new file mode 100644 index 0000000000..f51af448be --- /dev/null +++ b/.changes/next-release/api-change-cloudformation-60104.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``cloudformation``", + "description": "Adding support for the new parameter \"IncludePropertyValues\" in the CloudFormation DescribeChangeSet API. When this parameter is included, the DescribeChangeSet response will include more detailed information such as before and after values for the resource properties that will change." +} diff --git a/.changes/next-release/api-change-config-23095.json b/.changes/next-release/api-change-config-23095.json new file mode 100644 index 0000000000..c763ef6fba --- /dev/null +++ b/.changes/next-release/api-change-config-23095.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``config``", + "description": "Updates documentation for AWS Config" +} diff --git a/.changes/next-release/api-change-glue-22808.json b/.changes/next-release/api-change-glue-22808.json new file mode 100644 index 0000000000..0f197c2812 --- /dev/null +++ b/.changes/next-release/api-change-glue-22808.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``glue``", + "description": "Modifying request for GetUnfilteredTableMetadata for view-related fields." +} diff --git a/.changes/next-release/api-change-healthlake-98449.json b/.changes/next-release/api-change-healthlake-98449.json new file mode 100644 index 0000000000..6e07fa3559 --- /dev/null +++ b/.changes/next-release/api-change-healthlake-98449.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``healthlake``", + "description": "Added new CREATE_FAILED status for data stores. Added new errorCause to DescribeFHIRDatastore API and ListFHIRDatastores API response for additional insights into data store creation and deletion workflows." +} diff --git a/.changes/next-release/api-change-iotfleethub-59928.json b/.changes/next-release/api-change-iotfleethub-59928.json new file mode 100644 index 0000000000..14d23bba50 --- /dev/null +++ b/.changes/next-release/api-change-iotfleethub-59928.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``iotfleethub``", + "description": "Documentation updates for AWS IoT Fleet Hub to clarify that Fleet Hub supports organization instance of IAM Identity Center." +} diff --git a/.changes/next-release/api-change-kms-7898.json b/.changes/next-release/api-change-kms-7898.json new file mode 100644 index 0000000000..b855c0b79a --- /dev/null +++ b/.changes/next-release/api-change-kms-7898.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``kms``", + "description": "This feature supports the ability to specify a custom rotation period for automatic key rotations, the ability to perform on-demand key rotations, and visibility into your key material rotations." +} diff --git a/.changes/next-release/api-change-mediatailor-52018.json b/.changes/next-release/api-change-mediatailor-52018.json new file mode 100644 index 0000000000..852b1cfe70 --- /dev/null +++ b/.changes/next-release/api-change-mediatailor-52018.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``mediatailor``", + "description": "Added InsertionMode to PlaybackConfigurations. This setting controls whether players can use stitched or guided ad insertion. The default for players that do not specify an insertion mode is stitched." +} diff --git a/.changes/next-release/api-change-neptunegraph-69154.json b/.changes/next-release/api-change-neptunegraph-69154.json new file mode 100644 index 0000000000..6b873da2bc --- /dev/null +++ b/.changes/next-release/api-change-neptunegraph-69154.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``neptune-graph``", + "description": "Update to API documentation to resolve customer reported issues." +} diff --git a/.changes/next-release/api-change-outposts-88601.json b/.changes/next-release/api-change-outposts-88601.json new file mode 100644 index 0000000000..95468e3881 --- /dev/null +++ b/.changes/next-release/api-change-outposts-88601.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``outposts``", + "description": "This release adds EXPEDITORS as a valid shipment carrier." +} diff --git a/.changes/next-release/api-change-redshift-2491.json b/.changes/next-release/api-change-redshift-2491.json new file mode 100644 index 0000000000..2a7353205f --- /dev/null +++ b/.changes/next-release/api-change-redshift-2491.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``redshift``", + "description": "Adds support for Amazon Redshift DescribeClusterSnapshots API to include Snapshot ARN response field." +} diff --git a/.changes/next-release/api-change-transfer-89170.json b/.changes/next-release/api-change-transfer-89170.json new file mode 100644 index 0000000000..dc4f95c163 --- /dev/null +++ b/.changes/next-release/api-change-transfer-89170.json @@ -0,0 +1,5 @@ +{ + "type": "api-change", + "category": "``transfer``", + "description": "This change releases support for importing self signed certificates to the Transfer Family for sending outbound file transfers over TLS/HTTPS." +} diff --git a/botocore/data/cloudformation/2010-05-15/service-2.json b/botocore/data/cloudformation/2010-05-15/service-2.json index 000cb7458f..e5aac03c4d 100644 --- a/botocore/data/cloudformation/2010-05-15/service-2.json +++ b/botocore/data/cloudformation/2010-05-15/service-2.json @@ -1447,6 +1447,8 @@ } } }, + "AfterContext":{"type":"string"}, + "AfterValue":{"type":"string"}, "AllowedValue":{"type":"string"}, "AllowedValues":{ "type":"list", @@ -1465,6 +1467,14 @@ "exception":true }, "Arn":{"type":"string"}, + "AttributeChangeType":{ + "type":"string", + "enum":[ + "Add", + "Remove", + "Modify" + ] + }, "AutoDeployment":{ "type":"structure", "members":{ @@ -1530,6 +1540,8 @@ } } }, + "BeforeContext":{"type":"string"}, + "BeforeValue":{"type":"string"}, "BoxedInteger":{ "type":"integer", "box":true @@ -1606,7 +1618,7 @@ "members":{ "Type":{ "shape":"ChangeType", - "documentation":"

The type of entity that CloudFormation changes. Currently, the only entity type is Resource.

" + "documentation":"

The type of entity that CloudFormation changes.

" }, "HookInvocationCount":{ "shape":"HookInvocationCount", @@ -2572,6 +2584,10 @@ "NextToken":{ "shape":"NextToken", "documentation":"

A string (provided by the DescribeChangeSet response output) that identifies the next page of information that you want to retrieve.

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

If true, the returned changes include detailed changes in the property values.

" } }, "documentation":"

The input for the DescribeChangeSet action.

" @@ -3890,6 +3906,7 @@ "min":0 }, "IncludeNestedStacks":{"type":"boolean"}, + "IncludePropertyValues":{"type":"boolean"}, "InsufficientCapabilitiesException":{ "type":"structure", "members":{ @@ -5371,6 +5388,14 @@ "ModuleInfo":{ "shape":"ModuleInfo", "documentation":"

Contains information about the module from which the resource was created, if the resource was created from a module included in the stack template.

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

An encoded JSON string containing the context of the resource before the change is executed.

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

An encoded JSON string containing the context of the resource after the change is executed.

" } }, "documentation":"

The ResourceChange structure describes the resource and the action that CloudFormation will perform on it if you execute this change set.

" @@ -5515,6 +5540,7 @@ "min":1 }, "ResourceProperties":{"type":"string"}, + "ResourcePropertyPath":{"type":"string"}, "ResourceScanId":{"type":"string"}, "ResourceScanInProgressException":{ "type":"structure", @@ -5654,6 +5680,22 @@ "RequiresRecreation":{ "shape":"RequiresRecreation", "documentation":"

If the Attribute value is Properties, indicates whether a change to this property causes the resource to be recreated. The value can be Never, Always, or Conditionally. To determine the conditions for a Conditionally recreation, see the update behavior for that property in the CloudFormation User Guide.

" + }, + "Path":{ + "shape":"ResourcePropertyPath", + "documentation":"

The property path of the property.

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

The value of the property before the change is executed. Large values can be truncated.

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

The value of the property after the change is executed. Large values can be truncated.

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

The type of change to be made to the property if the change is executed.

" } }, "documentation":"

The field that CloudFormation will change, such as the name of a resource's property, and whether the resource will be recreated.

" diff --git a/botocore/data/config/2014-11-12/service-2.json b/botocore/data/config/2014-11-12/service-2.json index 6219aeebed..4b17ca2c8e 100644 --- a/botocore/data/config/2014-11-12/service-2.json +++ b/botocore/data/config/2014-11-12/service-2.json @@ -1823,7 +1823,7 @@ }, "configurationItemDeliveryTime":{ "shape":"ConfigurationItemDeliveryTime", - "documentation":"

The time when configuration changes for the resource were delivered.

" + "documentation":"

The time when configuration changes for the resource were delivered.

This field is optional and is not guaranteed to be present in a configuration item (CI). If you are using daily recording, this field will be populated. However, if you are using continuous recording, this field will be omitted since the delivery time is instantaneous as the CI is available right away. For more information on daily recording and continuous recording, see Recording Frequency in the Config Developer Guide.

" } }, "documentation":"

The detailed configurations of a specified resource.

" @@ -2421,7 +2421,7 @@ }, "configurationItemDeliveryTime":{ "shape":"ConfigurationItemDeliveryTime", - "documentation":"

The time when configuration changes for the resource were delivered.

" + "documentation":"

The time when configuration changes for the resource were delivered.

This field is optional and is not guaranteed to be present in a configuration item (CI). If you are using daily recording, this field will be populated. However, if you are using continuous recording, this field will be omitted since the delivery time is instantaneous as the CI is available right away. For more information on daily recording and continuous recording, see Recording Frequency in the Config Developer Guide.

" } }, "documentation":"

A list that contains detailed configurations of a specified resource.

" @@ -3408,7 +3408,7 @@ }, "Limit":{ "shape":"RuleLimit", - "documentation":"

The number of rule evaluation results that you want returned.

This parameter is required if the rule limit for your account is more than the default of 150 rules.

For information about requesting a rule limit increase, see Config Limits in the Amazon Web Services General Reference Guide.

" + "documentation":"

The number of rule evaluation results that you want returned.

This parameter is required if the rule limit for your account is more than the default of 1000 rules.

For information about requesting a rule limit increase, see Config Limits in the Amazon Web Services General Reference Guide.

" } }, "documentation":"

" @@ -5353,7 +5353,7 @@ "type":"structure", "members":{ }, - "documentation":"

Failed to add the Config rule because the account already contains the maximum number of 150 rules. Consider deleting any deactivated rules before you add new rules.

", + "documentation":"

Failed to add the Config rule because the account already contains the maximum number of 1000 rules. Consider deleting any deactivated rules before you add new rules.

", "exception":true }, "MaxNumberOfConfigurationRecordersExceededException":{ @@ -7099,7 +7099,7 @@ "members":{ "EvaluationMode":{ "shape":"EvaluationMode", - "documentation":"

Filters all resource evaluations results based on an evaluation mode. the valid value for this API is Proactive.

" + "documentation":"

Filters all resource evaluations results based on an evaluation mode.

Currently, DECTECTIVE is not supported as a valid value. Ignore other documentation stating otherwise.

" }, "TimeWindow":{ "shape":"TimeWindow", diff --git a/botocore/data/glue/2017-03-31/service-2.json b/botocore/data/glue/2017-03-31/service-2.json index 9692bd70f2..7d07dde954 100644 --- a/botocore/data/glue/2017-03-31/service-2.json +++ b/botocore/data/glue/2017-03-31/service-2.json @@ -2190,7 +2190,7 @@ {"shape":"FederationSourceException"}, {"shape":"FederationSourceRetryableException"} ], - "documentation":"

Retrieves table metadata from the Data Catalog that contains unfiltered metadata.

For IAM authorization, the public IAM action associated with this API is glue:GetTable.

" + "documentation":"

Allows a third-party analytical engine to retrieve unfiltered table metadata from the Data Catalog.

For IAM authorization, the public IAM action associated with this API is glue:GetTable.

" }, "GetUserDefinedFunction":{ "name":"GetUserDefinedFunction", @@ -13026,7 +13026,15 @@ }, "SupportedPermissionTypes":{ "shape":"PermissionTypeList", - "documentation":"

(Required) A list of supported permission types.

" + "documentation":"

Indicates the level of filtering a third-party analytical engine is capable of enforcing when calling the GetUnfilteredTableMetadata API operation. Accepted values are:

Note: Each of these permission types follows a hierarchical order where each subsequent permission type includes all permission of the previous type.

Important: If you provide a supported permission type that doesn't match the user's level of permissions on the table, then Lake Formation raises an exception. For example, if the third-party engine calling the GetUnfilteredTableMetadata operation can enforce only column-level filtering, and the user has nested cell filtering applied on the table, Lake Formation throws an exception, and will not return unfiltered table metadata and data access credentials.

" + }, + "ParentResourceArn":{ + "shape":"ArnString", + "documentation":"

The resource ARN of the view.

" + }, + "RootResourceArn":{ + "shape":"ArnString", + "documentation":"

The resource ARN of the root view in a chain of nested views.

" }, "SupportedDialect":{ "shape":"SupportedDialect", @@ -14604,11 +14612,11 @@ }, "MaxFetchTimeInMs":{ "shape":"BoxedNonNegativeLong", - "documentation":"

The maximum time spent in the job executor to fetch a record from the Kinesis data stream per shard, specified in milliseconds (ms). The default value is 1000.

" + "documentation":"

The maximum time spent for the job executor to read records for the current batch from the Kinesis data stream, specified in milliseconds (ms). Multiple GetRecords API calls may be made within this time. The default value is 1000.

" }, "MaxFetchRecordsPerShard":{ "shape":"BoxedNonNegativeLong", - "documentation":"

The maximum number of records to fetch per shard in the Kinesis data stream. The default value is 100000.

" + "documentation":"

The maximum number of records to fetch per shard in the Kinesis data stream per microbatch. Note: The client can exceed this limit if the streaming job has already read extra records from Kinesis (in the same get-records call). If MaxFetchRecordsPerShard needs to be strict then it needs to be a multiple of MaxRecordPerRead. The default value is 100000.

" }, "MaxRecordPerRead":{ "shape":"BoxedNonNegativeLong", diff --git a/botocore/data/healthlake/2017-07-01/service-2.json b/botocore/data/healthlake/2017-07-01/service-2.json index bfc582a261..8980124fef 100644 --- a/botocore/data/healthlake/2017-07-01/service-2.json +++ b/botocore/data/healthlake/2017-07-01/service-2.json @@ -422,6 +422,10 @@ "IdentityProviderConfiguration":{ "shape":"IdentityProviderConfiguration", "documentation":"

The identity provider that you selected when you created the data store.

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

The error cause for the current data store operation.

" } }, "documentation":"

Displays the properties of the data store, including the ID, ARN, name, and the status of the data store.

" @@ -436,7 +440,8 @@ "CREATING", "ACTIVE", "DELETING", - "DELETED" + "DELETED", + "CREATE_FAILED" ] }, "DeleteFHIRDatastoreRequest":{ @@ -556,6 +561,32 @@ "min":1, "pattern":"(arn:aws((-us-gov)|(-iso)|(-iso-b)|(-cn))?:kms:)?([a-z]{2}-[a-z]+(-[a-z]+)?-\\d:)?(\\d{12}:)?(((key/)?[a-zA-Z0-9-_]+)|(alias/[a-zA-Z0-9:/_-]+))" }, + "ErrorCategory":{ + "type":"string", + "enum":[ + "RETRYABLE_ERROR", + "NON_RETRYABLE_ERROR" + ] + }, + "ErrorCause":{ + "type":"structure", + "members":{ + "ErrorMessage":{ + "shape":"ErrorMessage", + "documentation":"

The text of the error message.

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

The error category of the create/delete data store operation. Possible statuses are RETRYABLE_ERROR or NON_RETRYABLE_ERROR.

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

The error info of the create/delete data store operation.

" + }, + "ErrorMessage":{ + "type":"string", + "max":4096, + "min":1 + }, "ExportJobProperties":{ "type":"structure", "required":[ diff --git a/botocore/data/iotfleethub/2020-11-03/endpoint-rule-set-1.json b/botocore/data/iotfleethub/2020-11-03/endpoint-rule-set-1.json index 5431059d2f..bd6d7696a9 100644 --- a/botocore/data/iotfleethub/2020-11-03/endpoint-rule-set-1.json +++ b/botocore/data/iotfleethub/2020-11-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,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/botocore/data/iotfleethub/2020-11-03/service-2.json b/botocore/data/iotfleethub/2020-11-03/service-2.json index 48da59f76f..c82ff6be8e 100644 --- a/botocore/data/iotfleethub/2020-11-03/service-2.json +++ b/botocore/data/iotfleethub/2020-11-03/service-2.json @@ -27,7 +27,7 @@ {"shape":"ThrottlingException"}, {"shape":"LimitExceededException"} ], - "documentation":"

Creates a Fleet Hub for AWS IoT Device Management web application.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Creates a Fleet Hub for IoT Device Management web application.

When creating a Fleet Hub application, you must create an organization instance of IAM Identity Center if you don't already have one. The Fleet Hub application you create must also be in the same Amazon Web Services Region of the organization instance of IAM Identity Center. For more information see Enabling IAM Identity Center and Organization instances of IAM Identity Center.

" }, "DeleteApplication":{ "name":"DeleteApplication", @@ -44,7 +44,7 @@ {"shape":"InternalFailureException"}, {"shape":"ThrottlingException"} ], - "documentation":"

Deletes a Fleet Hub for AWS IoT Device Management web application.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Deletes a Fleet Hub for IoT Device Management web application.

" }, "DescribeApplication":{ "name":"DescribeApplication", @@ -61,7 +61,7 @@ {"shape":"InternalFailureException"}, {"shape":"ThrottlingException"} ], - "documentation":"

Gets information about a Fleet Hub for AWS IoT Device Management web application.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Gets information about a Fleet Hub for IoT Device Management web application.

" }, "ListApplications":{ "name":"ListApplications", @@ -77,7 +77,7 @@ {"shape":"InternalFailureException"}, {"shape":"ThrottlingException"} ], - "documentation":"

Gets a list of Fleet Hub for AWS IoT Device Management web applications for the current account.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Gets a list of Fleet Hub for IoT Device Management web applications for the current account.

" }, "ListTagsForResource":{ "name":"ListTagsForResource", @@ -92,7 +92,7 @@ {"shape":"InvalidRequestException"}, {"shape":"ResourceNotFoundException"} ], - "documentation":"

Lists the tags for the specified resource.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Lists the tags for the specified resource.

" }, "TagResource":{ "name":"TagResource", @@ -107,7 +107,7 @@ {"shape":"InvalidRequestException"}, {"shape":"ResourceNotFoundException"} ], - "documentation":"

Adds to or modifies the tags of the specified resource. Tags are metadata which can be used to manage a resource.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Adds to or modifies the tags of the specified resource. Tags are metadata which can be used to manage a resource.

" }, "UntagResource":{ "name":"UntagResource", @@ -122,7 +122,7 @@ {"shape":"InvalidRequestException"}, {"shape":"ResourceNotFoundException"} ], - "documentation":"

Removes the specified tags (metadata) from the resource.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Removes the specified tags (metadata) from the resource.

" }, "UpdateApplication":{ "name":"UpdateApplication", @@ -140,7 +140,7 @@ {"shape":"ConflictException"}, {"shape":"ThrottlingException"} ], - "documentation":"

Updates information about a Fleet Hub for a AWS IoT Device Management web application.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

Updates information about a Fleet Hub for IoT Device Management web application.

" } }, "shapes":{ @@ -195,7 +195,7 @@ "documentation":"

The current state of the web application.

" } }, - "documentation":"

A summary of information about a AWS IoT Device Management web application.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

A summary of information about a Fleet Hub for IoT Device Management web application.

" }, "Arn":{ "type":"string", @@ -240,7 +240,7 @@ }, "roleArn":{ "shape":"Arn", - "documentation":"

The ARN of the role that the web application assumes when it interacts with AWS IoT Core.

The name of the role must be in the form AWSIotFleetHub_random_string .

" + "documentation":"

The ARN of the role that the web application assumes when it interacts with Amazon Web Services IoT Core.

The name of the role must be in the form AWSIotFleetHub_random_string .

" }, "tags":{ "shape":"TagMap", @@ -348,7 +348,7 @@ }, "roleArn":{ "shape":"Arn", - "documentation":"

The ARN of the role that the web application assumes when it interacts with AWS IoT Core.

" + "documentation":"

The ARN of the role that the web application assumes when it interacts with Amazon Web Services IoT Core.

" }, "ssoClientId":{ "shape":"SsoClientId", @@ -356,7 +356,7 @@ }, "errorMessage":{ "shape":"ErrorMessage", - "documentation":"

A message indicating why the DescribeApplication API failed.

" + "documentation":"

A message that explains any failures included in the applicationState response field. This message explains failures in the CreateApplication and DeleteApplication actions.

" }, "tags":{ "shape":"TagMap", @@ -593,5 +593,5 @@ }, "errorMessage":{"type":"string"} }, - "documentation":"

With Fleet Hub for AWS IoT Device Management you can build stand-alone web applications for monitoring the health of your device fleets.

Fleet Hub for AWS IoT Device Management is in public preview and is subject to change.

" + "documentation":"

With Fleet Hub for IoT Device Management you can build stand-alone web applications for monitoring the health of your device fleets.

" } diff --git a/botocore/data/kms/2014-11-01/paginators-1.json b/botocore/data/kms/2014-11-01/paginators-1.json index dc6690f5eb..0c48130a98 100644 --- a/botocore/data/kms/2014-11-01/paginators-1.json +++ b/botocore/data/kms/2014-11-01/paginators-1.json @@ -48,6 +48,13 @@ "more_results": "Truncated", "output_token": "NextMarker", "result_key": "Grants" + }, + "ListKeyRotations": { + "input_token": "Marker", + "limit_key": "Limit", + "more_results": "Truncated", + "output_token": "NextMarker", + "result_key": "Rotations" } } } diff --git a/botocore/data/kms/2014-11-01/service-2.json b/botocore/data/kms/2014-11-01/service-2.json index ee4084467b..06121c4b71 100644 --- a/botocore/data/kms/2014-11-01/service-2.json +++ b/botocore/data/kms/2014-11-01/service-2.json @@ -274,7 +274,7 @@ {"shape":"KMSInvalidStateException"}, {"shape":"UnsupportedOperationException"} ], - "documentation":"

Disables automatic rotation of the key material of the specified symmetric encryption KMS key.

Automatic key rotation is supported only on symmetric encryption KMS keys. You cannot enable automatic rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.

You can enable (EnableKeyRotation) and disable automatic rotation of the key material in customer managed KMS keys. Key material rotation of Amazon Web Services managed KMS keys is not configurable. KMS always rotates the key material for every year. Rotation of Amazon Web Services owned KMS keys varies.

In May 2022, KMS changed the rotation schedule for Amazon Web Services managed keys from every three years to every year. For details, see EnableKeyRotation.

The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide.

Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.

Required permissions: kms:DisableKeyRotation (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" + "documentation":"

Disables automatic rotation of the key material of the specified symmetric encryption KMS key.

Automatic key rotation is supported only on symmetric encryption KMS keys. You cannot enable automatic rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.

You can enable (EnableKeyRotation) and disable automatic rotation of the key material in customer managed KMS keys. Key material rotation of Amazon Web Services managed KMS keys is not configurable. KMS always rotates the key material for every year. Rotation of Amazon Web Services owned KMS keys varies.

In May 2022, KMS changed the rotation schedule for Amazon Web Services managed keys from every three years to every year. For details, see EnableKeyRotation.

The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide.

Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.

Required permissions: kms:DisableKeyRotation (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" }, "DisconnectCustomKeyStore":{ "name":"DisconnectCustomKeyStore", @@ -324,7 +324,7 @@ {"shape":"KMSInvalidStateException"}, {"shape":"UnsupportedOperationException"} ], - "documentation":"

Enables automatic rotation of the key material of the specified symmetric encryption KMS key.

When you enable automatic rotation of a customer managed KMS key, KMS rotates the key material of the KMS key one year (approximately 365 days) from the enable date and every year thereafter. You can monitor rotation of the key material for your KMS keys in CloudTrail and Amazon CloudWatch. To disable rotation of the key material in a customer managed KMS key, use the DisableKeyRotation operation.

Automatic key rotation is supported only on symmetric encryption KMS keys. You cannot enable automatic rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.

You cannot enable or disable automatic rotation Amazon Web Services managed KMS keys. KMS always rotates the key material of Amazon Web Services managed keys every year. Rotation of Amazon Web Services owned KMS keys varies.

In May 2022, KMS changed the rotation schedule for Amazon Web Services managed keys from every three years (approximately 1,095 days) to every year (approximately 365 days).

New Amazon Web Services managed keys are automatically rotated one year after they are created, and approximately every year thereafter.

Existing Amazon Web Services managed keys are automatically rotated one year after their most recent rotation, and every year thereafter.

The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide.

Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.

Required permissions: kms:EnableKeyRotation (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" + "documentation":"

Enables automatic rotation of the key material of the specified symmetric encryption KMS key.

By default, when you enable automatic rotation of a customer managed KMS key, KMS rotates the key material of the KMS key one year (approximately 365 days) from the enable date and every year thereafter. You can use the optional RotationPeriodInDays parameter to specify a custom rotation period when you enable key rotation, or you can use RotationPeriodInDays to modify the rotation period of a key that you previously enabled automatic key rotation on.

You can monitor rotation of the key material for your KMS keys in CloudTrail and Amazon CloudWatch. To disable rotation of the key material in a customer managed KMS key, use the DisableKeyRotation operation. You can use the GetKeyRotationStatus operation to identify any in progress rotations. You can use the ListKeyRotations operation to view the details of completed rotations.

Automatic key rotation is supported only on symmetric encryption KMS keys. You cannot enable automatic rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.

You cannot enable or disable automatic rotation of Amazon Web Services managed KMS keys. KMS always rotates the key material of Amazon Web Services managed keys every year. Rotation of Amazon Web Services owned KMS keys is managed by the Amazon Web Services service that owns the key.

In May 2022, KMS changed the rotation schedule for Amazon Web Services managed keys from every three years (approximately 1,095 days) to every year (approximately 365 days).

New Amazon Web Services managed keys are automatically rotated one year after they are created, and approximately every year thereafter.

Existing Amazon Web Services managed keys are automatically rotated one year after their most recent rotation, and every year thereafter.

The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide.

Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.

Required permissions: kms:EnableKeyRotation (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" }, "Encrypt":{ "name":"Encrypt", @@ -503,7 +503,7 @@ {"shape":"KMSInvalidStateException"}, {"shape":"UnsupportedOperationException"} ], - "documentation":"

Gets a Boolean value that indicates whether automatic rotation of the key material is enabled for the specified KMS key.

When you enable automatic rotation for customer managed KMS keys, KMS rotates the key material of the KMS key one year (approximately 365 days) from the enable date and every year thereafter. You can monitor rotation of the key material for your KMS keys in CloudTrail and Amazon CloudWatch.

Automatic key rotation is supported only on symmetric encryption KMS keys. You cannot enable automatic rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key..

You can enable (EnableKeyRotation) and disable automatic rotation (DisableKeyRotation) of the key material in customer managed KMS keys. Key material rotation of Amazon Web Services managed KMS keys is not configurable. KMS always rotates the key material in Amazon Web Services managed KMS keys every year. The key rotation status for Amazon Web Services managed KMS keys is always true.

In May 2022, KMS changed the rotation schedule for Amazon Web Services managed keys from every three years to every year. For details, see EnableKeyRotation.

The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide.

Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key ARN in the value of the KeyId parameter.

Required permissions: kms:GetKeyRotationStatus (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" + "documentation":"

Provides detailed information about the rotation status for a KMS key, including whether automatic rotation of the key material is enabled for the specified KMS key, the rotation period, and the next scheduled rotation date.

Automatic key rotation is supported only on symmetric encryption KMS keys. You cannot enable automatic rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key..

You can enable (EnableKeyRotation) and disable automatic rotation (DisableKeyRotation) of the key material in customer managed KMS keys. Key material rotation of Amazon Web Services managed KMS keys is not configurable. KMS always rotates the key material in Amazon Web Services managed KMS keys every year. The key rotation status for Amazon Web Services managed KMS keys is always true.

You can perform on-demand (RotateKeyOnDemand) rotation of the key material in customer managed KMS keys, regardless of whether or not automatic key rotation is enabled. You can use GetKeyRotationStatus to identify the date and time that an in progress on-demand rotation was initiated. You can use ListKeyRotations to view the details of completed rotations.

In May 2022, KMS changed the rotation schedule for Amazon Web Services managed keys from every three years to every year. For details, see EnableKeyRotation.

The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide.

Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key ARN in the value of the KeyId parameter.

Required permissions: kms:GetKeyRotationStatus (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" }, "GetParametersForImport":{ "name":"GetParametersForImport", @@ -620,6 +620,24 @@ ], "documentation":"

Gets the names of the key policies that are attached to a KMS key. This operation is designed to get policy names that you can use in a GetKeyPolicy operation. However, the only valid policy name is default.

Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.

Required permissions: kms:ListKeyPolicies (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" }, + "ListKeyRotations":{ + "name":"ListKeyRotations", + "http":{ + "method":"POST", + "requestUri":"/" + }, + "input":{"shape":"ListKeyRotationsRequest"}, + "output":{"shape":"ListKeyRotationsResponse"}, + "errors":[ + {"shape":"NotFoundException"}, + {"shape":"InvalidArnException"}, + {"shape":"InvalidMarkerException"}, + {"shape":"KMSInternalException"}, + {"shape":"KMSInvalidStateException"}, + {"shape":"UnsupportedOperationException"} + ], + "documentation":"

Returns information about all completed key material rotations for the specified KMS key.

You must specify the KMS key in all requests. You can refine the key rotations list by limiting the number of rotations returned.

For detailed information about automatic and on-demand key rotations, see Rotating KMS keys in the Key Management Service Developer Guide.

Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.

Required permissions: kms:ListKeyRotations (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" + }, "ListKeys":{ "name":"ListKeys", "http":{ @@ -769,6 +787,27 @@ ], "documentation":"

Deletes the specified grant. You revoke a grant to terminate the permissions that the grant allows. For more information, see Retiring and revoking grants in the Key Management Service Developer Guide .

When you create, retire, or revoke a grant, there might be a brief delay, usually less than five minutes, until the grant is available throughout KMS. This state is known as eventual consistency. For details, see Eventual consistency in the Key Management Service Developer Guide .

For detailed information about grants, including grant terminology, see Grants in KMS in the Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.

Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key ARN in the value of the KeyId parameter.

Required permissions: kms:RevokeGrant (key policy).

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" }, + "RotateKeyOnDemand":{ + "name":"RotateKeyOnDemand", + "http":{ + "method":"POST", + "requestUri":"/" + }, + "input":{"shape":"RotateKeyOnDemandRequest"}, + "output":{"shape":"RotateKeyOnDemandResponse"}, + "errors":[ + {"shape":"NotFoundException"}, + {"shape":"DisabledException"}, + {"shape":"InvalidArnException"}, + {"shape":"DependencyTimeoutException"}, + {"shape":"KMSInternalException"}, + {"shape":"KMSInvalidStateException"}, + {"shape":"UnsupportedOperationException"}, + {"shape":"LimitExceededException"}, + {"shape":"ConflictException"} + ], + "documentation":"

Immediately initiates rotation of the key material of the specified symmetric encryption KMS key.

You can perform on-demand rotation of the key material in customer managed KMS keys, regardless of whether or not automatic key rotation is enabled. On-demand rotations do not change existing automatic rotation schedules. For example, consider a KMS key that has automatic key rotation enabled with a rotation period of 730 days. If the key is scheduled to automatically rotate on April 14, 2024, and you perform an on-demand rotation on April 10, 2024, the key will automatically rotate, as scheduled, on April 14, 2024 and every 730 days thereafter.

You can perform on-demand key rotation a maximum of 10 times per KMS key. You can use the KMS console to view the number of remaining on-demand rotations available for a KMS key.

You can use GetKeyRotationStatus to identify any in progress on-demand rotations. You can use ListKeyRotations to identify the date that completed on-demand rotations were performed. You can monitor rotation of the key material for your KMS keys in CloudTrail and Amazon CloudWatch.

On-demand key rotation is supported only on symmetric encryption KMS keys. You cannot perform on-demand rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To perform on-demand rotation of a set of related multi-Region keys, invoke the on-demand rotation on the primary key.

You cannot initiate on-demand rotation of Amazon Web Services managed KMS keys. KMS always rotates the key material of Amazon Web Services managed keys every year. Rotation of Amazon Web Services owned KMS keys is managed by the Amazon Web Services service that owns the key.

The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide.

Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.

Required permissions: kms:RotateKeyOnDemand (key policy)

Related operations:

Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.

" + }, "ScheduleKeyDeletion":{ "name":"ScheduleKeyDeletion", "http":{ @@ -1099,6 +1138,14 @@ "documentation":"

The request was rejected because the specified CloudHSM cluster has a different cluster certificate than the original cluster. You cannot use the operation to specify an unrelated cluster for an CloudHSM key store.

Specify an CloudHSM cluster that shares a backup history with the original cluster. This includes clusters that were created from a backup of the current cluster, and clusters that were created from the same backup that produced the current cluster.

CloudHSM clusters that share a backup history have the same cluster certificate. To view the cluster certificate of an CloudHSM cluster, use the DescribeClusters operation.

", "exception":true }, + "ConflictException":{ + "type":"structure", + "members":{ + "message":{"shape":"ErrorMessageType"} + }, + "documentation":"

The request was rejected because an automatic rotation of this key is currently in progress or scheduled to begin within the next 20 minutes.

", + "exception":true + }, "ConnectCustomKeyStoreRequest":{ "type":"structure", "required":["CustomKeyStoreId"], @@ -1603,7 +1650,7 @@ }, "Truncated":{ "shape":"BooleanType", - "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in thisresponse to the Marker parameter in a subsequent request.

" + "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in this response to the Marker parameter in a subsequent request.

" } } }, @@ -1703,6 +1750,10 @@ "KeyId":{ "shape":"KeyIdType", "documentation":"

Identifies a symmetric encryption KMS key. You cannot enable automatic rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.

Specify the key ID or key ARN of the KMS key.

For example:

To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.

" + }, + "RotationPeriodInDays":{ + "shape":"RotationPeriodInDaysType", + "documentation":"

Use this parameter to specify a custom period of time between each rotation date. If no value is specified, the default value is 365 days.

The rotation period defines the number of days after you enable automatic key rotation that KMS will rotate your key material, and the number of days between each automatic rotation thereafter.

You can use the kms:RotationPeriodInDays condition key to further constrain the values that principals can specify in the RotationPeriodInDays parameter.

" } } }, @@ -2122,6 +2173,22 @@ "KeyRotationEnabled":{ "shape":"BooleanType", "documentation":"

A Boolean value that specifies whether key rotation is enabled.

" + }, + "KeyId":{ + "shape":"KeyIdType", + "documentation":"

Identifies the specified symmetric encryption KMS key.

" + }, + "RotationPeriodInDays":{ + "shape":"RotationPeriodInDaysType", + "documentation":"

The number of days between each automatic rotation. The default value is 365 days.

" + }, + "NextRotationDate":{ + "shape":"DateType", + "documentation":"

The next date that KMS will automatically rotate the key material.

" + }, + "OnDemandRotationStartDate":{ + "shape":"DateType", + "documentation":"

Identifies the date and time that an in progress on-demand rotation was initiated.

The KMS API follows an eventual consistency model due to the distributed nature of the system. As a result, there might be a slight delay between initiating on-demand key rotation and the rotation's completion. Once the on-demand rotation is complete, use ListKeyRotations to view the details of the on-demand rotation.

" } } }, @@ -2716,7 +2783,7 @@ }, "Truncated":{ "shape":"BooleanType", - "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in thisresponse to the Marker parameter in a subsequent request.

" + "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in this response to the Marker parameter in a subsequent request.

" } } }, @@ -2759,7 +2826,7 @@ }, "Truncated":{ "shape":"BooleanType", - "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in thisresponse to the Marker parameter in a subsequent request.

" + "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in this response to the Marker parameter in a subsequent request.

" } } }, @@ -2794,7 +2861,42 @@ }, "Truncated":{ "shape":"BooleanType", - "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in thisresponse to the Marker parameter in a subsequent request.

" + "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in this response to the Marker parameter in a subsequent request.

" + } + } + }, + "ListKeyRotationsRequest":{ + "type":"structure", + "required":["KeyId"], + "members":{ + "KeyId":{ + "shape":"KeyIdType", + "documentation":"

Gets the key rotations for the specified KMS key.

Specify the key ID or key ARN of the KMS key.

For example:

To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.

" + }, + "Limit":{ + "shape":"LimitType", + "documentation":"

Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.

This value is optional. If you include a value, it must be between 1 and 1000, inclusive. If you do not include a value, it defaults to 100.

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

Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

" + } + } + }, + "ListKeyRotationsResponse":{ + "type":"structure", + "members":{ + "Rotations":{ + "shape":"RotationsList", + "documentation":"

A list of completed key material rotations.

" + }, + "NextMarker":{ + "shape":"MarkerType", + "documentation":"

When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

" + }, + "Truncated":{ + "shape":"BooleanType", + "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in this response to the Marker parameter in a subsequent request.

" } } }, @@ -2824,7 +2926,7 @@ }, "Truncated":{ "shape":"BooleanType", - "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in thisresponse to the Marker parameter in a subsequent request.

" + "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in this response to the Marker parameter in a subsequent request.

" } } }, @@ -2859,7 +2961,7 @@ }, "Truncated":{ "shape":"BooleanType", - "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in thisresponse to the Marker parameter in a subsequent request.

" + "documentation":"

A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker element in this response to the Marker parameter in a subsequent request.

" } } }, @@ -3226,6 +3328,59 @@ } } }, + "RotateKeyOnDemandRequest":{ + "type":"structure", + "required":["KeyId"], + "members":{ + "KeyId":{ + "shape":"KeyIdType", + "documentation":"

Identifies a symmetric encryption KMS key. You cannot perform on-demand rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To perform on-demand rotation of a set of related multi-Region keys, invoke the on-demand rotation on the primary key.

Specify the key ID or key ARN of the KMS key.

For example:

To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.

" + } + } + }, + "RotateKeyOnDemandResponse":{ + "type":"structure", + "members":{ + "KeyId":{ + "shape":"KeyIdType", + "documentation":"

Identifies the symmetric encryption KMS key that you initiated on-demand rotation on.

" + } + } + }, + "RotationPeriodInDaysType":{ + "type":"integer", + "max":2560, + "min":90 + }, + "RotationType":{ + "type":"string", + "enum":[ + "AUTOMATIC", + "ON_DEMAND" + ] + }, + "RotationsList":{ + "type":"list", + "member":{"shape":"RotationsListEntry"} + }, + "RotationsListEntry":{ + "type":"structure", + "members":{ + "KeyId":{ + "shape":"KeyIdType", + "documentation":"

Unique identifier of the key.

" + }, + "RotationDate":{ + "shape":"DateType", + "documentation":"

Date and time that the key material rotation completed. Formatted as Unix time.

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

Identifies whether the key material rotation was a scheduled automatic rotation or an on-demand rotation.

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

Contains information about completed key material rotations.

" + }, "ScheduleKeyDeletionRequest":{ "type":"structure", "required":["KeyId"], diff --git a/botocore/data/mediatailor/2018-04-23/service-2.json b/botocore/data/mediatailor/2018-04-23/service-2.json index 30acf52ef7..4f3850ec88 100644 --- a/botocore/data/mediatailor/2018-04-23/service-2.json +++ b/botocore/data/mediatailor/2018-04-23/service-2.json @@ -2103,6 +2103,10 @@ "shape":"HlsConfiguration", "documentation":"

The configuration for HLS content.

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

The setting that controls whether players can use stitched or guided ad insertion. The default, STITCHED_ONLY, forces all player sessions to use stitched (server-side) ad insertion. Choosing PLAYER_SELECT allows players to select either stitched or guided ad insertion at session-initialization time. The default for players that do not specify an insertion mode is stitched.

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

The configuration for pre-roll ad insertion.

" @@ -2267,6 +2271,14 @@ "member":{"shape":"HttpPackageConfiguration"}, "documentation":"

The VOD source's HTTP package configuration settings.

" }, + "InsertionMode":{ + "type":"string", + "documentation":"

Insertion Mode controls whether players can use stitched or guided ad insertion.

", + "enum":[ + "STITCHED_ONLY", + "PLAYER_SELECT" + ] + }, "Integer":{ "type":"integer", "box":true @@ -2710,6 +2722,10 @@ "shape":"HlsConfiguration", "documentation":"

The configuration for HLS content.

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

The setting that controls whether players can use stitched or guided ad insertion. The default, STITCHED_ONLY, forces all player sessions to use stitched (server-side) ad insertion. Choosing PLAYER_SELECT allows players to select either stitched or guided ad insertion at session-initialization time. The default for players that do not specify an insertion mode is stitched.

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

The configuration for pre-roll ad insertion.

" @@ -2896,6 +2912,10 @@ "shape":"DashConfigurationForPut", "documentation":"

The configuration for DASH content.

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

The setting that controls whether players can use stitched or guided ad insertion. The default, STITCHED_ONLY, forces all player sessions to use stitched (server-side) ad insertion. Choosing PLAYER_SELECT allows players to select either stitched or guided ad insertion at session-initialization time. The default for players that do not specify an insertion mode is stitched.

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

The configuration for pre-roll ad insertion.

" @@ -2962,6 +2982,10 @@ "shape":"HlsConfiguration", "documentation":"

The configuration for HLS content.

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

The setting that controls whether players can use stitched or guided ad insertion. The default, STITCHED_ONLY, forces all player sessions to use stitched (server-side) ad insertion. Choosing PLAYER_SELECT allows players to select either stitched or guided ad insertion at session-initialization time. The default for players that do not specify an insertion mode is stitched.

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

The configuration for pre-roll ad insertion.

" diff --git a/botocore/data/neptune-graph/2023-11-29/service-2.json b/botocore/data/neptune-graph/2023-11-29/service-2.json index 84445ae2e6..58f09b07ad 100644 --- a/botocore/data/neptune-graph/2023-11-29/service-2.json +++ b/botocore/data/neptune-graph/2023-11-29/service-2.json @@ -760,7 +760,7 @@ }, "replicaCount":{ "shape":"ReplicaCount", - "documentation":"

The number of replicas in other AZs. Min =0, Max = 2, Default = 1.

" + "documentation":"

The number of replicas in other AZs. Min =0, Max = 2, Default = 1.

Additional charges equivalent to the m-NCUs selected for the graph apply for each replica.

" }, "deletionProtection":{ "shape":"Boolean", @@ -931,7 +931,7 @@ }, "replicaCount":{ "shape":"ReplicaCount", - "documentation":"

The number of replicas in other AZs to provision on the new graph after import. Default = 0, Min = 0, Max = 2.

" + "documentation":"

The number of replicas in other AZs to provision on the new graph after import. Default = 0, Min = 0, Max = 2.

Additional charges equivalent to the m-NCUs selected for the graph apply for each replica.

" }, "deletionProtection":{ "shape":"Boolean", @@ -2538,7 +2538,7 @@ }, "replicaCount":{ "shape":"ReplicaCount", - "documentation":"

The number of replicas in other AZs. Min =0, Max = 2, Default =1

" + "documentation":"

The number of replicas in other AZs. Min =0, Max = 2, Default =1

Additional charges equivalent to the m-NCUs selected for the graph apply for each replica.

" }, "publicConnectivity":{ "shape":"Boolean", diff --git a/botocore/data/outposts/2019-12-03/service-2.json b/botocore/data/outposts/2019-12-03/service-2.json index 82acb0c945..2b94cd8af6 100644 --- a/botocore/data/outposts/2019-12-03/service-2.json +++ b/botocore/data/outposts/2019-12-03/service-2.json @@ -1952,7 +1952,8 @@ "DHL", "DBS", "FEDEX", - "UPS" + "UPS", + "EXPEDITORS" ] }, "ShipmentInformation":{ diff --git a/botocore/data/redshift/2012-12-01/service-2.json b/botocore/data/redshift/2012-12-01/service-2.json index 69ee7efa68..8f13bcdb4f 100644 --- a/botocore/data/redshift/2012-12-01/service-2.json +++ b/botocore/data/redshift/2012-12-01/service-2.json @@ -10637,6 +10637,10 @@ "MasterPasswordSecretKmsKeyId":{ "shape":"String", "documentation":"

The ID of the Key Management Service (KMS) key used to encrypt and store the cluster's admin credentials secret.

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

The Amazon Resource Name (ARN) of the snapshot.

" } }, "documentation":"

Describes a snapshot.

", diff --git a/botocore/data/transfer/2018-11-05/service-2.json b/botocore/data/transfer/2018-11-05/service-2.json index 5e838f5a21..5f16e4af44 100644 --- a/botocore/data/transfer/2018-11-05/service-2.json +++ b/botocore/data/transfer/2018-11-05/service-2.json @@ -1149,7 +1149,8 @@ "type":"string", "enum":[ "SIGNING", - "ENCRYPTION" + "ENCRYPTION", + "TLS" ] }, "CompressionEnum":{ @@ -2170,7 +2171,7 @@ }, "Usage":{ "shape":"CertificateUsageType", - "documentation":"

Specifies whether this certificate is used for signing or encryption.

" + "documentation":"

Specifies how this certificate is used. It can be used in the following ways:

" }, "Status":{ "shape":"CertificateStatusType", @@ -2917,7 +2918,7 @@ "members":{ "Usage":{ "shape":"CertificateUsageType", - "documentation":"

Specifies whether this certificate is used for signing or encryption.

" + "documentation":"

Specifies how this certificate is used. It can be used in the following ways:

" }, "Certificate":{ "shape":"CertificateBodyType", @@ -3554,7 +3555,7 @@ }, "Usage":{ "shape":"CertificateUsageType", - "documentation":"

Specifies whether this certificate is used for signing or encryption.

" + "documentation":"

Specifies how this certificate is used. It can be used in the following ways:

" }, "Status":{ "shape":"CertificateStatusType",