From f824e6ceaeb020571ceb6e826127d1d3f1469ac8 Mon Sep 17 00:00:00 2001 From: awstools Date: Fri, 15 Dec 2023 19:36:07 +0000 Subject: [PATCH] docs(client-kms): Documentation updates for AWS Key Management Service --- .../src/commands/CancelKeyDeletionCommand.ts | 3 + .../commands/ConnectCustomKeyStoreCommand.ts | 3 + .../src/commands/CreateAliasCommand.ts | 3 + .../commands/CreateCustomKeyStoreCommand.ts | 6 +- .../src/commands/CreateGrantCommand.ts | 7 +- .../src/commands/CreateKeyCommand.ts | 3 + .../client-kms/src/commands/DecryptCommand.ts | 9 +- .../src/commands/DeleteAliasCommand.ts | 3 + .../commands/DeleteCustomKeyStoreCommand.ts | 3 + .../DeleteImportedKeyMaterialCommand.ts | 3 + .../DescribeCustomKeyStoresCommand.ts | 3 + .../src/commands/DescribeKeyCommand.ts | 13 +- .../src/commands/DisableKeyCommand.ts | 3 + .../src/commands/DisableKeyRotationCommand.ts | 3 + .../DisconnectCustomKeyStoreCommand.ts | 3 + .../src/commands/EnableKeyCommand.ts | 3 + .../src/commands/EnableKeyRotationCommand.ts | 5 +- .../client-kms/src/commands/EncryptCommand.ts | 7 +- .../src/commands/GenerateDataKeyCommand.ts | 7 +- .../commands/GenerateDataKeyPairCommand.ts | 9 +- ...erateDataKeyPairWithoutPlaintextCommand.ts | 7 +- .../GenerateDataKeyWithoutPlaintextCommand.ts | 7 +- .../src/commands/GenerateMacCommand.ts | 7 +- .../src/commands/GenerateRandomCommand.ts | 3 + .../src/commands/GetKeyPolicyCommand.ts | 5 +- .../commands/GetKeyRotationStatusCommand.ts | 3 + .../commands/GetParametersForImportCommand.ts | 13 +- .../src/commands/GetPublicKeyCommand.ts | 3 + .../src/commands/ImportKeyMaterialCommand.ts | 3 + .../src/commands/ListAliasesCommand.ts | 3 + .../src/commands/ListGrantsCommand.ts | 3 + .../src/commands/ListKeyPoliciesCommand.ts | 5 +- .../src/commands/ListKeysCommand.ts | 3 + .../src/commands/ListResourceTagsCommand.ts | 3 + .../commands/ListRetirableGrantsCommand.ts | 14 ++- .../src/commands/PutKeyPolicyCommand.ts | 3 + .../src/commands/ReEncryptCommand.ts | 7 +- .../src/commands/ReplicateKeyCommand.ts | 5 +- .../src/commands/RetireGrantCommand.ts | 9 +- .../src/commands/RevokeGrantCommand.ts | 7 +- .../commands/ScheduleKeyDeletionCommand.ts | 6 +- .../client-kms/src/commands/SignCommand.ts | 7 +- .../src/commands/TagResourceCommand.ts | 3 + .../src/commands/UntagResourceCommand.ts | 3 + .../src/commands/UpdateAliasCommand.ts | 3 + .../commands/UpdateCustomKeyStoreCommand.ts | 6 +- .../commands/UpdateKeyDescriptionCommand.ts | 3 + .../commands/UpdatePrimaryRegionCommand.ts | 3 + .../client-kms/src/commands/VerifyCommand.ts | 7 +- .../src/commands/VerifyMacCommand.ts | 7 +- clients/client-kms/src/models/models_0.ts | 26 ++-- codegen/sdk-codegen/aws-models/kms.json | 116 +++++++++--------- 52 files changed, 265 insertions(+), 137 deletions(-) diff --git a/clients/client-kms/src/commands/CancelKeyDeletionCommand.ts b/clients/client-kms/src/commands/CancelKeyDeletionCommand.ts index cbd3a082a742..177dd8da9383 100644 --- a/clients/client-kms/src/commands/CancelKeyDeletionCommand.ts +++ b/clients/client-kms/src/commands/CancelKeyDeletionCommand.ts @@ -50,6 +50,9 @@ export interface CancelKeyDeletionCommandOutput extends CancelKeyDeletionRespons *

* Related operations: ScheduleKeyDeletion *

+ *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ConnectCustomKeyStoreCommand.ts b/clients/client-kms/src/commands/ConnectCustomKeyStoreCommand.ts index f061a0c86f4f..0e942f67cf94 100644 --- a/clients/client-kms/src/commands/ConnectCustomKeyStoreCommand.ts +++ b/clients/client-kms/src/commands/ConnectCustomKeyStoreCommand.ts @@ -124,6 +124,9 @@ export interface ConnectCustomKeyStoreCommandOutput extends ConnectCustomKeyStor *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/CreateAliasCommand.ts b/clients/client-kms/src/commands/CreateAliasCommand.ts index f57b19d92a79..4288958789af 100644 --- a/clients/client-kms/src/commands/CreateAliasCommand.ts +++ b/clients/client-kms/src/commands/CreateAliasCommand.ts @@ -94,6 +94,9 @@ export interface CreateAliasCommandOutput extends __MetadataBearer {} *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/CreateCustomKeyStoreCommand.ts b/clients/client-kms/src/commands/CreateCustomKeyStoreCommand.ts index bb18cdfe646b..b39c40f72585 100644 --- a/clients/client-kms/src/commands/CreateCustomKeyStoreCommand.ts +++ b/clients/client-kms/src/commands/CreateCustomKeyStoreCommand.ts @@ -130,6 +130,9 @@ export interface CreateCustomKeyStoreCommandOutput extends CreateCustomKeyStoreR *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -280,8 +283,7 @@ export interface CreateCustomKeyStoreCommandOutput extends CreateCustomKeyStoreR * @throws {@link XksProxyVpcEndpointServiceInvalidConfigurationException} (client fault) *

The request was rejected because the Amazon VPC endpoint service configuration does not fulfill * the requirements for an external key store proxy. For details, see the exception message and - * review the - * requirements for Amazon VPC endpoint service connectivity for an external key + * review the requirements for Amazon VPC endpoint service connectivity for an external key * store.

* * @throws {@link XksProxyVpcEndpointServiceNotFoundException} (client fault) diff --git a/clients/client-kms/src/commands/CreateGrantCommand.ts b/clients/client-kms/src/commands/CreateGrantCommand.ts index c5106dad90af..34d98624f15b 100644 --- a/clients/client-kms/src/commands/CreateGrantCommand.ts +++ b/clients/client-kms/src/commands/CreateGrantCommand.ts @@ -99,6 +99,9 @@ export interface CreateGrantCommandOutput extends CreateGrantResponse, __Metadat *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -149,9 +152,7 @@ export interface CreateGrantCommandOutput extends CreateGrantResponse, __Metadat *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link InvalidArnException} (client fault) *

The request was rejected because a specified ARN, or an ARN in a key policy, is not diff --git a/clients/client-kms/src/commands/CreateKeyCommand.ts b/clients/client-kms/src/commands/CreateKeyCommand.ts index b86609a4fcd5..1b8d1e534d8a 100644 --- a/clients/client-kms/src/commands/CreateKeyCommand.ts +++ b/clients/client-kms/src/commands/CreateKeyCommand.ts @@ -201,6 +201,9 @@ export interface CreateKeyCommandOutput extends CreateKeyResponse, __MetadataBea *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DecryptCommand.ts b/clients/client-kms/src/commands/DecryptCommand.ts index caae8cb07edf..16adb3b9d1d4 100644 --- a/clients/client-kms/src/commands/DecryptCommand.ts +++ b/clients/client-kms/src/commands/DecryptCommand.ts @@ -97,7 +97,7 @@ export interface DecryptCommandOutput extends DecryptResponse, __MetadataBearer * the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient parameter to provide the * attestation document for the enclave. Instead of the plaintext data, the response includes the * plaintext data encrypted with the public key from the attestation document - * (CiphertextForRecipient).For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide..

+ * (CiphertextForRecipient). For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

*

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.

*

@@ -131,6 +131,9 @@ export interface DecryptCommandOutput extends DecryptResponse, __MetadataBearer *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -178,9 +181,7 @@ export interface DecryptCommandOutput extends DecryptResponse, __MetadataBearer *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link IncorrectKeyException} (client fault) *

The request was rejected because the specified KMS key cannot decrypt the data. The diff --git a/clients/client-kms/src/commands/DeleteAliasCommand.ts b/clients/client-kms/src/commands/DeleteAliasCommand.ts index 774e9f0423bd..746092fa2f97 100644 --- a/clients/client-kms/src/commands/DeleteAliasCommand.ts +++ b/clients/client-kms/src/commands/DeleteAliasCommand.ts @@ -85,6 +85,9 @@ export interface DeleteAliasCommandOutput extends __MetadataBearer {} *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DeleteCustomKeyStoreCommand.ts b/clients/client-kms/src/commands/DeleteCustomKeyStoreCommand.ts index 0fced8bc87a9..c10419dc3f30 100644 --- a/clients/client-kms/src/commands/DeleteCustomKeyStoreCommand.ts +++ b/clients/client-kms/src/commands/DeleteCustomKeyStoreCommand.ts @@ -96,6 +96,9 @@ export interface DeleteCustomKeyStoreCommandOutput extends DeleteCustomKeyStoreR *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DeleteImportedKeyMaterialCommand.ts b/clients/client-kms/src/commands/DeleteImportedKeyMaterialCommand.ts index 798d91f37fbe..f254a959d343 100644 --- a/clients/client-kms/src/commands/DeleteImportedKeyMaterialCommand.ts +++ b/clients/client-kms/src/commands/DeleteImportedKeyMaterialCommand.ts @@ -65,6 +65,9 @@ export interface DeleteImportedKeyMaterialCommandOutput extends __MetadataBearer *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DescribeCustomKeyStoresCommand.ts b/clients/client-kms/src/commands/DescribeCustomKeyStoresCommand.ts index e0de792be119..ef2a21944c1a 100644 --- a/clients/client-kms/src/commands/DescribeCustomKeyStoresCommand.ts +++ b/clients/client-kms/src/commands/DescribeCustomKeyStoresCommand.ts @@ -100,6 +100,9 @@ export interface DescribeCustomKeyStoresCommandOutput extends DescribeCustomKeyS *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DescribeKeyCommand.ts b/clients/client-kms/src/commands/DescribeKeyCommand.ts index 760632847204..20e72915945e 100644 --- a/clients/client-kms/src/commands/DescribeKeyCommand.ts +++ b/clients/client-kms/src/commands/DescribeKeyCommand.ts @@ -45,12 +45,10 @@ export interface DescribeKeyCommandOutput extends DescribeKeyResponse, __Metadat * It includes fields, like KeySpec, that help you distinguish different types of * KMS keys. It also displays the key usage (encryption, signing, or generating and verifying * MACs) and the algorithms that the KMS key supports.

- *

For multi-Region keys, - * DescribeKey displays the primary key and all related replica keys. For KMS keys - * in CloudHSM key stores, it includes - * information about the key store, such as the key store ID and the CloudHSM cluster ID. For KMS - * keys in external key stores, it - * includes the custom key store ID and the ID of the external key.

+ *

For multi-Region keys, DescribeKey displays the primary key and all + * related replica keys. For KMS keys in CloudHSM key stores, it includes information + * about the key store, such as the key store ID and the CloudHSM cluster ID. For KMS keys in external key stores, + * it includes the custom key store ID and the ID of the external key.

*

* DescribeKey does not return the following information:

* + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DisableKeyCommand.ts b/clients/client-kms/src/commands/DisableKeyCommand.ts index 6588640660d9..9ba4bd22de3d 100644 --- a/clients/client-kms/src/commands/DisableKeyCommand.ts +++ b/clients/client-kms/src/commands/DisableKeyCommand.ts @@ -52,6 +52,9 @@ export interface DisableKeyCommandOutput extends __MetadataBearer {} *

* Related operations: EnableKey *

+ *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DisableKeyRotationCommand.ts b/clients/client-kms/src/commands/DisableKeyRotationCommand.ts index 3a08ec61c620..e239c8277022 100644 --- a/clients/client-kms/src/commands/DisableKeyRotationCommand.ts +++ b/clients/client-kms/src/commands/DisableKeyRotationCommand.ts @@ -70,6 +70,9 @@ export interface DisableKeyRotationCommandOutput extends __MetadataBearer {} *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/DisconnectCustomKeyStoreCommand.ts b/clients/client-kms/src/commands/DisconnectCustomKeyStoreCommand.ts index 38ec63a72c65..77a3a6f4865d 100644 --- a/clients/client-kms/src/commands/DisconnectCustomKeyStoreCommand.ts +++ b/clients/client-kms/src/commands/DisconnectCustomKeyStoreCommand.ts @@ -89,6 +89,9 @@ export interface DisconnectCustomKeyStoreCommandOutput extends DisconnectCustomK *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/EnableKeyCommand.ts b/clients/client-kms/src/commands/EnableKeyCommand.ts index 7c8179d11b22..1c235a643444 100644 --- a/clients/client-kms/src/commands/EnableKeyCommand.ts +++ b/clients/client-kms/src/commands/EnableKeyCommand.ts @@ -48,6 +48,9 @@ export interface EnableKeyCommandOutput extends __MetadataBearer {} *

* Related operations: DisableKey *

+ *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/EnableKeyRotationCommand.ts b/clients/client-kms/src/commands/EnableKeyRotationCommand.ts index e2a50f10b684..e0fae076dc05 100644 --- a/clients/client-kms/src/commands/EnableKeyRotationCommand.ts +++ b/clients/client-kms/src/commands/EnableKeyRotationCommand.ts @@ -39,7 +39,7 @@ export interface EnableKeyRotationCommandOutput extends __MetadataBearer {} * @public *

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

- *

When you enable automatic rotation of acustomer managed KMS key, KMS + *

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 @@ -78,6 +78,9 @@ export interface EnableKeyRotationCommandOutput extends __MetadataBearer {} *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/EncryptCommand.ts b/clients/client-kms/src/commands/EncryptCommand.ts index d70e3af51ca0..5541c12ae940 100644 --- a/clients/client-kms/src/commands/EncryptCommand.ts +++ b/clients/client-kms/src/commands/EncryptCommand.ts @@ -146,6 +146,9 @@ export interface EncryptCommandOutput extends EncryptResponse, __MetadataBearer *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -188,9 +191,7 @@ export interface EncryptCommandOutput extends EncryptResponse, __MetadataBearer *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link InvalidGrantTokenException} (client fault) *

The request was rejected because the specified grant token is not valid.

diff --git a/clients/client-kms/src/commands/GenerateDataKeyCommand.ts b/clients/client-kms/src/commands/GenerateDataKeyCommand.ts index d41e404d193e..7e24f6042136 100644 --- a/clients/client-kms/src/commands/GenerateDataKeyCommand.ts +++ b/clients/client-kms/src/commands/GenerateDataKeyCommand.ts @@ -144,6 +144,9 @@ export interface GenerateDataKeyCommandOutput extends GenerateDataKeyResponse, _ *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -191,9 +194,7 @@ export interface GenerateDataKeyCommandOutput extends GenerateDataKeyResponse, _ *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link InvalidGrantTokenException} (client fault) *

The request was rejected because the specified grant token is not valid.

diff --git a/clients/client-kms/src/commands/GenerateDataKeyPairCommand.ts b/clients/client-kms/src/commands/GenerateDataKeyPairCommand.ts index 08d4a51b50e6..fbd2a60d7188 100644 --- a/clients/client-kms/src/commands/GenerateDataKeyPairCommand.ts +++ b/clients/client-kms/src/commands/GenerateDataKeyPairCommand.ts @@ -45,7 +45,7 @@ export interface GenerateDataKeyPairCommandOutput extends GenerateDataKeyPairRes * a plaintext public key, a plaintext private key, and a copy of the private key that is * encrypted under the symmetric encryption KMS key you specify. You can use the data key pair to * perform asymmetric cryptography and implement digital signatures outside of KMS. The bytes - * in the keys are random; they not related to the caller or to the KMS key that is used to + * in the keys are random; they are not related to the caller or to the KMS key that is used to * encrypt the private key.

*

You can use the public key that GenerateDataKeyPair returns to encrypt data * or verify a signature outside of KMS. Then, store the encrypted private key with the data. @@ -123,6 +123,9 @@ export interface GenerateDataKeyPairCommandOutput extends GenerateDataKeyPairRes *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -171,9 +174,7 @@ export interface GenerateDataKeyPairCommandOutput extends GenerateDataKeyPairRes *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link InvalidGrantTokenException} (client fault) *

The request was rejected because the specified grant token is not valid.

diff --git a/clients/client-kms/src/commands/GenerateDataKeyPairWithoutPlaintextCommand.ts b/clients/client-kms/src/commands/GenerateDataKeyPairWithoutPlaintextCommand.ts index 812872c35868..ee7f3f9b7bc9 100644 --- a/clients/client-kms/src/commands/GenerateDataKeyPairWithoutPlaintextCommand.ts +++ b/clients/client-kms/src/commands/GenerateDataKeyPairWithoutPlaintextCommand.ts @@ -109,6 +109,9 @@ export interface GenerateDataKeyPairWithoutPlaintextCommandOutput *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -151,9 +154,7 @@ export interface GenerateDataKeyPairWithoutPlaintextCommandOutput *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link InvalidGrantTokenException} (client fault) *

The request was rejected because the specified grant token is not valid.

diff --git a/clients/client-kms/src/commands/GenerateDataKeyWithoutPlaintextCommand.ts b/clients/client-kms/src/commands/GenerateDataKeyWithoutPlaintextCommand.ts index 3e349dba3756..7f455aa54d36 100644 --- a/clients/client-kms/src/commands/GenerateDataKeyWithoutPlaintextCommand.ts +++ b/clients/client-kms/src/commands/GenerateDataKeyWithoutPlaintextCommand.ts @@ -115,6 +115,9 @@ export interface GenerateDataKeyWithoutPlaintextCommandOutput *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -156,9 +159,7 @@ export interface GenerateDataKeyWithoutPlaintextCommandOutput *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link InvalidGrantTokenException} (client fault) *

The request was rejected because the specified grant token is not valid.

diff --git a/clients/client-kms/src/commands/GenerateMacCommand.ts b/clients/client-kms/src/commands/GenerateMacCommand.ts index 17a1f3067570..6fb8f387fb04 100644 --- a/clients/client-kms/src/commands/GenerateMacCommand.ts +++ b/clients/client-kms/src/commands/GenerateMacCommand.ts @@ -66,6 +66,9 @@ export interface GenerateMacCommandOutput extends GenerateMacResponse, __Metadat *

* Related operations: VerifyMac *

+ *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -101,9 +104,7 @@ export interface GenerateMacCommandOutput extends GenerateMacResponse, __Metadat *

The request was rejected because the specified KMS key is not enabled.

* * @throws {@link DryRunOperationException} (client fault) - *

- * The request was rejected because the DryRun parameter was specified. - *

+ *

The request was rejected because the DryRun parameter was specified.

* * @throws {@link InvalidGrantTokenException} (client fault) *

The request was rejected because the specified grant token is not valid.

diff --git a/clients/client-kms/src/commands/GenerateRandomCommand.ts b/clients/client-kms/src/commands/GenerateRandomCommand.ts index 9f92c1397b3c..33f71139a4d3 100644 --- a/clients/client-kms/src/commands/GenerateRandomCommand.ts +++ b/clients/client-kms/src/commands/GenerateRandomCommand.ts @@ -62,6 +62,9 @@ export interface GenerateRandomCommandOutput extends GenerateRandomResponse, __M * keys.

*

* Required permissions: kms:GenerateRandom (IAM policy)

+ *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/GetKeyPolicyCommand.ts b/clients/client-kms/src/commands/GetKeyPolicyCommand.ts index f1c6a2effab7..c1ce5e943cf6 100644 --- a/clients/client-kms/src/commands/GetKeyPolicyCommand.ts +++ b/clients/client-kms/src/commands/GetKeyPolicyCommand.ts @@ -43,8 +43,11 @@ export interface GetKeyPolicyCommandOutput extends GetKeyPolicyResponse, __Metad *

* Required permissions: kms:GetKeyPolicy (key policy)

*

- * Related operations: PutKeyPolicy + * Related operations: PutKeyPolicy *

+ *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/GetKeyRotationStatusCommand.ts b/clients/client-kms/src/commands/GetKeyRotationStatusCommand.ts index 04562c79e1f2..ad8cc45d006c 100644 --- a/clients/client-kms/src/commands/GetKeyRotationStatusCommand.ts +++ b/clients/client-kms/src/commands/GetKeyRotationStatusCommand.ts @@ -90,6 +90,9 @@ export interface GetKeyRotationStatusCommandOutput extends GetKeyRotationStatusR *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/GetParametersForImportCommand.ts b/clients/client-kms/src/commands/GetParametersForImportCommand.ts index 8e9864b67370..c19e044edf70 100644 --- a/clients/client-kms/src/commands/GetParametersForImportCommand.ts +++ b/clients/client-kms/src/commands/GetParametersForImportCommand.ts @@ -53,10 +53,12 @@ export interface GetParametersForImportCommandOutput extends GetParametersForImp * operation with an Origin value of EXTERNAL to create a KMS key with * no key material. You can import key material for a symmetric encryption KMS key, HMAC KMS key, * asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material - * into a multi-Region key of - * any supported type. However, you can't import key material into a KMS key in a custom key store. You can also use - * GetParametersForImport to get a public key and import token to reimport the original key - * material into a KMS key whose key material expired or was deleted.

+ * into a multi-Region key of + * any supported type. However, you can't import key material into a KMS key in a custom key + * store. You can also use GetParametersForImport to get a public key and + * import token to reimport + * the original key material into a KMS key whose key material expired or was + * deleted.

*

* GetParametersForImport returns the items that you need to import your key * material.

@@ -115,6 +117,9 @@ export interface GetParametersForImportCommandOutput extends GetParametersForImp *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/GetPublicKeyCommand.ts b/clients/client-kms/src/commands/GetPublicKeyCommand.ts index 87f389ca3371..b580d2aedbbb 100644 --- a/clients/client-kms/src/commands/GetPublicKeyCommand.ts +++ b/clients/client-kms/src/commands/GetPublicKeyCommand.ts @@ -85,6 +85,9 @@ export interface GetPublicKeyCommandOutput extends GetPublicKeyResponse, __Metad *

* Related operations: CreateKey *

+ *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ImportKeyMaterialCommand.ts b/clients/client-kms/src/commands/ImportKeyMaterialCommand.ts index 3a9c276ca971..6af8d30a2383 100644 --- a/clients/client-kms/src/commands/ImportKeyMaterialCommand.ts +++ b/clients/client-kms/src/commands/ImportKeyMaterialCommand.ts @@ -139,6 +139,9 @@ export interface ImportKeyMaterialCommandOutput extends ImportKeyMaterialRespons *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ListAliasesCommand.ts b/clients/client-kms/src/commands/ListAliasesCommand.ts index 148a0a44314e..20f8e759b99b 100644 --- a/clients/client-kms/src/commands/ListAliasesCommand.ts +++ b/clients/client-kms/src/commands/ListAliasesCommand.ts @@ -78,6 +78,9 @@ export interface ListAliasesCommandOutput extends ListAliasesResponse, __Metadat *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ListGrantsCommand.ts b/clients/client-kms/src/commands/ListGrantsCommand.ts index 0189149bcf0d..078c62624d3d 100644 --- a/clients/client-kms/src/commands/ListGrantsCommand.ts +++ b/clients/client-kms/src/commands/ListGrantsCommand.ts @@ -82,6 +82,9 @@ export interface ListGrantsCommandOutput extends ListGrantsResponse, __MetadataB *

* * + *

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

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ListKeyPoliciesCommand.ts b/clients/client-kms/src/commands/ListKeyPoliciesCommand.ts index 33ea62640b43..480d603f27a9 100644 --- a/clients/client-kms/src/commands/ListKeyPoliciesCommand.ts +++ b/clients/client-kms/src/commands/ListKeyPoliciesCommand.ts @@ -55,10 +55,13 @@ export interface ListKeyPoliciesCommandOutput extends ListKeyPoliciesResponse, _ * *
  • *

    - * PutKeyPolicy + * PutKeyPolicy *

    *
    • * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ListKeysCommand.ts b/clients/client-kms/src/commands/ListKeysCommand.ts index b81a433044ef..95994248a57b 100644 --- a/clients/client-kms/src/commands/ListKeysCommand.ts +++ b/clients/client-kms/src/commands/ListKeysCommand.ts @@ -67,6 +67,9 @@ export interface ListKeysCommandOutput extends ListKeysResponse, __MetadataBeare *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ListResourceTagsCommand.ts b/clients/client-kms/src/commands/ListResourceTagsCommand.ts index 8b516a9deb99..ca5c97805745 100644 --- a/clients/client-kms/src/commands/ListResourceTagsCommand.ts +++ b/clients/client-kms/src/commands/ListResourceTagsCommand.ts @@ -71,6 +71,9 @@ export interface ListResourceTagsCommandOutput extends ListResourceTagsResponse, *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ListRetirableGrantsCommand.ts b/clients/client-kms/src/commands/ListRetirableGrantsCommand.ts index 6813a9927685..4e9a62b387cd 100644 --- a/clients/client-kms/src/commands/ListRetirableGrantsCommand.ts +++ b/clients/client-kms/src/commands/ListRetirableGrantsCommand.ts @@ -49,12 +49,21 @@ export interface ListRetirableGrantsCommandOutput extends ListGrantsResponse, __ * programming languages, see Programming grants.

    *

    * Cross-account use: You must specify a principal in your - * Amazon Web Services account. However, this operation can return grants in any Amazon Web Services account. You do not need + * Amazon Web Services account. This operation returns a list of grants where the retiring principal specified + * in the ListRetirableGrants request is the same retiring principal on the grant. + * This can include grants on KMS keys owned by other Amazon Web Services accounts, but you do not need * kms:ListRetirableGrants permission (or any other additional permission) in any * Amazon Web Services account other than your own.

    *

    * Required permissions: kms:ListRetirableGrants (IAM policy) in your * Amazon Web Services account.

    + * + *

    KMS authorizes ListRetirableGrants requests by evaluating the caller + * account's kms:ListRetirableGrants permissions. The authorized resource in + * ListRetirableGrants calls is the retiring principal specified in the request. + * KMS does not evaluate the caller's permissions to verify their access to any KMS keys or + * grants that might be returned by the ListRetirableGrants call.

    + *     *

    * Related operations: *

    @@ -80,6 +89,9 @@ export interface ListRetirableGrantsCommandOutput extends ListGrantsResponse, __ *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/PutKeyPolicyCommand.ts b/clients/client-kms/src/commands/PutKeyPolicyCommand.ts index a607b9464189..d18106b9dd66 100644 --- a/clients/client-kms/src/commands/PutKeyPolicyCommand.ts +++ b/clients/client-kms/src/commands/PutKeyPolicyCommand.ts @@ -50,6 +50,9 @@ export interface PutKeyPolicyCommandOutput extends __MetadataBearer {} *

    * Related operations: GetKeyPolicy *

    + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/ReEncryptCommand.ts b/clients/client-kms/src/commands/ReEncryptCommand.ts index 1620659663dd..2e47ebfe44cf 100644 --- a/clients/client-kms/src/commands/ReEncryptCommand.ts +++ b/clients/client-kms/src/commands/ReEncryptCommand.ts @@ -132,6 +132,9 @@ export interface ReEncryptCommandOutput extends ReEncryptResponse, __MetadataBea *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -181,9 +184,7 @@ export interface ReEncryptCommandOutput extends ReEncryptResponse, __MetadataBea *

    The request was rejected because the specified KMS key is not enabled.

    * * @throws {@link DryRunOperationException} (client fault) - *

    - * The request was rejected because the DryRun parameter was specified. - *

    + *

    The request was rejected because the DryRun parameter was specified.

    * * @throws {@link IncorrectKeyException} (client fault) *

    The request was rejected because the specified KMS key cannot decrypt the data. The diff --git a/clients/client-kms/src/commands/ReplicateKeyCommand.ts b/clients/client-kms/src/commands/ReplicateKeyCommand.ts index e8fc4f0f0b2e..9b875c1235da 100644 --- a/clients/client-kms/src/commands/ReplicateKeyCommand.ts +++ b/clients/client-kms/src/commands/ReplicateKeyCommand.ts @@ -76,7 +76,7 @@ export interface ReplicateKeyCommandOutput extends ReplicateKeyResponse, __Metad * ReplicateKey operation in the primary key's Region and a CreateKey operation in the replica key's Region.

    *

    If you replicate a multi-Region primary key with imported key material, the replica key is * created with no key material. You must import the same key material that you imported into the - * primary key. For details, see Importing key material into multi-Region keys in the Key Management Service Developer Guide.

    + * primary key. For details, see Importing key material into multi-Region keys in the Key Management Service Developer Guide.

    *

    To convert a replica key to a primary key, use the UpdatePrimaryRegion * operation.

    * @@ -120,6 +120,9 @@ export interface ReplicateKeyCommandOutput extends ReplicateKeyResponse, __Metad *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/RetireGrantCommand.ts b/clients/client-kms/src/commands/RetireGrantCommand.ts index ec0506191f7b..7a2023e166e0 100644 --- a/clients/client-kms/src/commands/RetireGrantCommand.ts +++ b/clients/client-kms/src/commands/RetireGrantCommand.ts @@ -55,7 +55,7 @@ export interface RetireGrantCommandOutput extends __MetadataBearer {} * Cross-account use: Yes. You can retire a grant on a KMS * key in a different Amazon Web Services account.

    *

    - * Required permissions::Permission to retire a grant is + * Required permissions: Permission to retire a grant is * determined primarily by the grant. For details, see Retiring and revoking grants in * the Key Management Service Developer Guide.

    *

    @@ -83,6 +83,9 @@ export interface RetireGrantCommandOutput extends __MetadataBearer {} *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -112,9 +115,7 @@ export interface RetireGrantCommandOutput extends __MetadataBearer {} * request.

    * * @throws {@link DryRunOperationException} (client fault) - *

    - * The request was rejected because the DryRun parameter was specified. - *

    + *

    The request was rejected because the DryRun parameter was specified.

    * * @throws {@link InvalidArnException} (client fault) *

    The request was rejected because a specified ARN, or an ARN in a key policy, is not diff --git a/clients/client-kms/src/commands/RevokeGrantCommand.ts b/clients/client-kms/src/commands/RevokeGrantCommand.ts index 7a8c6a04c046..457cdd175abf 100644 --- a/clients/client-kms/src/commands/RevokeGrantCommand.ts +++ b/clients/client-kms/src/commands/RevokeGrantCommand.ts @@ -81,6 +81,9 @@ export interface RevokeGrantCommandOutput extends __MetadataBearer {} *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -109,9 +112,7 @@ export interface RevokeGrantCommandOutput extends __MetadataBearer {} * request.

    * * @throws {@link DryRunOperationException} (client fault) - *

    - * The request was rejected because the DryRun parameter was specified. - *

    + *

    The request was rejected because the DryRun parameter was specified.

    * * @throws {@link InvalidArnException} (client fault) *

    The request was rejected because a specified ARN, or an ARN in a key policy, is not diff --git a/clients/client-kms/src/commands/ScheduleKeyDeletionCommand.ts b/clients/client-kms/src/commands/ScheduleKeyDeletionCommand.ts index fe3d398aede5..2de79b7845ac 100644 --- a/clients/client-kms/src/commands/ScheduleKeyDeletionCommand.ts +++ b/clients/client-kms/src/commands/ScheduleKeyDeletionCommand.ts @@ -48,8 +48,7 @@ export interface ScheduleKeyDeletionCommandOutput extends ScheduleKeyDeletionRes * *

    Deleting a KMS key is a destructive and potentially dangerous operation. When a KMS key * is deleted, all data that was encrypted under the KMS key is unrecoverable. (The only - * exception is a multi-Region replica - * key, or an asymmetric or HMAC KMS + * exception is a multi-Region replica key, or an asymmetric or HMAC KMS * key with imported key material.) To prevent the use of a KMS key without deleting * it, use DisableKey.

    * @@ -95,6 +94,9 @@ export interface ScheduleKeyDeletionCommandOutput extends ScheduleKeyDeletionRes *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/SignCommand.ts b/clients/client-kms/src/commands/SignCommand.ts index 1b4e724fdebf..8edbdc1625f9 100644 --- a/clients/client-kms/src/commands/SignCommand.ts +++ b/clients/client-kms/src/commands/SignCommand.ts @@ -89,6 +89,9 @@ export interface SignCommandOutput extends SignResponse, __MetadataBearer {} *

    * Related operations: Verify *

    + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -129,9 +132,7 @@ export interface SignCommandOutput extends SignResponse, __MetadataBearer {} *

    The request was rejected because the specified KMS key is not enabled.

    * * @throws {@link DryRunOperationException} (client fault) - *

    - * The request was rejected because the DryRun parameter was specified. - *

    + *

    The request was rejected because the DryRun parameter was specified.

    * * @throws {@link InvalidGrantTokenException} (client fault) *

    The request was rejected because the specified grant token is not valid.

    diff --git a/clients/client-kms/src/commands/TagResourceCommand.ts b/clients/client-kms/src/commands/TagResourceCommand.ts index 66cf81bc0aa3..5dab4355ed28 100644 --- a/clients/client-kms/src/commands/TagResourceCommand.ts +++ b/clients/client-kms/src/commands/TagResourceCommand.ts @@ -84,6 +84,9 @@ export interface TagResourceCommandOutput extends __MetadataBearer {} *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/UntagResourceCommand.ts b/clients/client-kms/src/commands/UntagResourceCommand.ts index 096c4ec0013c..1f010f7e0c86 100644 --- a/clients/client-kms/src/commands/UntagResourceCommand.ts +++ b/clients/client-kms/src/commands/UntagResourceCommand.ts @@ -79,6 +79,9 @@ export interface UntagResourceCommandOutput extends __MetadataBearer {} *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/UpdateAliasCommand.ts b/clients/client-kms/src/commands/UpdateAliasCommand.ts index 6856f23d8e20..a67c66c51819 100644 --- a/clients/client-kms/src/commands/UpdateAliasCommand.ts +++ b/clients/client-kms/src/commands/UpdateAliasCommand.ts @@ -100,6 +100,9 @@ export interface UpdateAliasCommandOutput extends __MetadataBearer {} *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/UpdateCustomKeyStoreCommand.ts b/clients/client-kms/src/commands/UpdateCustomKeyStoreCommand.ts index c0b075e8d2cb..72963cd1b279 100644 --- a/clients/client-kms/src/commands/UpdateCustomKeyStoreCommand.ts +++ b/clients/client-kms/src/commands/UpdateCustomKeyStoreCommand.ts @@ -134,6 +134,9 @@ export interface UpdateCustomKeyStoreCommandOutput extends UpdateCustomKeyStoreR *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -313,8 +316,7 @@ export interface UpdateCustomKeyStoreCommandOutput extends UpdateCustomKeyStoreR * @throws {@link XksProxyVpcEndpointServiceInvalidConfigurationException} (client fault) *

    The request was rejected because the Amazon VPC endpoint service configuration does not fulfill * the requirements for an external key store proxy. For details, see the exception message and - * review the - * requirements for Amazon VPC endpoint service connectivity for an external key + * review the requirements for Amazon VPC endpoint service connectivity for an external key * store.

    * * @throws {@link XksProxyVpcEndpointServiceNotFoundException} (client fault) diff --git a/clients/client-kms/src/commands/UpdateKeyDescriptionCommand.ts b/clients/client-kms/src/commands/UpdateKeyDescriptionCommand.ts index 6b1ea2d4a6d7..add6abfeb0a4 100644 --- a/clients/client-kms/src/commands/UpdateKeyDescriptionCommand.ts +++ b/clients/client-kms/src/commands/UpdateKeyDescriptionCommand.ts @@ -59,6 +59,9 @@ export interface UpdateKeyDescriptionCommandOutput extends __MetadataBearer {} *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/UpdatePrimaryRegionCommand.ts b/clients/client-kms/src/commands/UpdatePrimaryRegionCommand.ts index 0528155965fc..e7b11b7515a2 100644 --- a/clients/client-kms/src/commands/UpdatePrimaryRegionCommand.ts +++ b/clients/client-kms/src/commands/UpdatePrimaryRegionCommand.ts @@ -102,6 +102,9 @@ export interface UpdatePrimaryRegionCommandOutput extends __MetadataBearer {} *

    * * + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript diff --git a/clients/client-kms/src/commands/VerifyCommand.ts b/clients/client-kms/src/commands/VerifyCommand.ts index 319bf72930db..6293f97d9544 100644 --- a/clients/client-kms/src/commands/VerifyCommand.ts +++ b/clients/client-kms/src/commands/VerifyCommand.ts @@ -72,6 +72,9 @@ export interface VerifyCommandOutput extends VerifyResponse, __MetadataBearer {} *

    * Related operations: Sign *

    + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -113,9 +116,7 @@ export interface VerifyCommandOutput extends VerifyResponse, __MetadataBearer {} *

    The request was rejected because the specified KMS key is not enabled.

    * * @throws {@link DryRunOperationException} (client fault) - *

    - * The request was rejected because the DryRun parameter was specified. - *

    + *

    The request was rejected because the DryRun parameter was specified.

    * * @throws {@link InvalidGrantTokenException} (client fault) *

    The request was rejected because the specified grant token is not valid.

    diff --git a/clients/client-kms/src/commands/VerifyMacCommand.ts b/clients/client-kms/src/commands/VerifyMacCommand.ts index 4cd900d28eef..77e9a9ac770a 100644 --- a/clients/client-kms/src/commands/VerifyMacCommand.ts +++ b/clients/client-kms/src/commands/VerifyMacCommand.ts @@ -58,6 +58,9 @@ export interface VerifyMacCommandOutput extends VerifyMacResponse, __MetadataBea *

    * Related operations: GenerateMac *

    + *

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

    * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript @@ -94,9 +97,7 @@ export interface VerifyMacCommandOutput extends VerifyMacResponse, __MetadataBea *

    The request was rejected because the specified KMS key is not enabled.

    * * @throws {@link DryRunOperationException} (client fault) - *

    - * The request was rejected because the DryRun parameter was specified. - *

    + *

    The request was rejected because the DryRun parameter was specified.

    * * @throws {@link InvalidGrantTokenException} (client fault) *

    The request was rejected because the specified grant token is not valid.

    diff --git a/clients/client-kms/src/models/models_0.ts b/clients/client-kms/src/models/models_0.ts index d835c1c0110d..4a574321527c 100644 --- a/clients/client-kms/src/models/models_0.ts +++ b/clients/client-kms/src/models/models_0.ts @@ -1060,8 +1060,7 @@ export class XksProxyVpcEndpointServiceInUseException extends __BaseException { * @public *

    The request was rejected because the Amazon VPC endpoint service configuration does not fulfill * the requirements for an external key store proxy. For details, see the exception message and - * review the - * requirements for Amazon VPC endpoint service connectivity for an external key + * review the requirements for Amazon VPC endpoint service connectivity for an external key * store.

    */ export class XksProxyVpcEndpointServiceInvalidConfigurationException extends __BaseException { @@ -1347,9 +1346,7 @@ export class DisabledException extends __BaseException { /** * @public - *

    - * The request was rejected because the DryRun parameter was specified. - *

    + *

    The request was rejected because the DryRun parameter was specified.

    */ export class DryRunOperationException extends __BaseException { readonly name: "DryRunOperationException" = "DryRunOperationException"; @@ -1745,7 +1742,8 @@ export interface CreateKeyRequest { *

    For more information, see Default key policy in the Key Management Service Developer Guide.

    * *

    Use this parameter only when you intend to prevent the principal that is making the - * request from making a subsequent PutKeyPolicy request on the KMS key.

    + * request from making a subsequent PutKeyPolicy + * request on the KMS key.

    */ BypassPolicyLockoutSafetyCheck?: boolean; @@ -2857,9 +2855,9 @@ export interface DecryptRequest { /** * @public - *

    A signed attestation document from - * an Amazon Web Services Nitro enclave and the encryption algorithm to use with the enclave's public key. The - * only valid encryption algorithm is RSAES_OAEP_SHA_256.

    + *

    A signed attestation + * document from an Amazon Web Services Nitro enclave and the encryption algorithm to use with the + * enclave's public key. The only valid encryption algorithm is RSAES_OAEP_SHA_256.

    *

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To include this * parameter, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK.

    *

    When you use this parameter, instead of returning the plaintext data, KMS encrypts the @@ -4212,8 +4210,8 @@ export interface GetParametersForImportRequest { * *

  • *

    - * RSAES_PKCS1_V1_5 (Deprecated) — Supported only - * for symmetric encryption key material (and only in legacy mode).

    + * RSAES_PKCS1_V1_5 (Deprecated) — As of October + * 10, 2023, KMS does not support the RSAES_PKCS1_V1_5 wrapping algorithm.

    *
    • * */ @@ -5118,7 +5116,8 @@ export interface PutKeyPolicyRequest { *

    For more information, see Default key policy in the Key Management Service Developer Guide.

    * *

    Use this parameter only when you intend to prevent the principal that is making the - * request from making a subsequent PutKeyPolicy request on the KMS key.

    + * request from making a subsequent PutKeyPolicy + * request on the KMS key.

    */ BypassPolicyLockoutSafetyCheck?: boolean; } @@ -5401,7 +5400,8 @@ export interface ReplicateKeyRequest { *

    For more information, see Default key policy in the Key Management Service Developer Guide.

    * *

    Use this parameter only when you intend to prevent the principal that is making the - * request from making a subsequent PutKeyPolicy request on the KMS key.

    + * request from making a subsequent PutKeyPolicy + * request on the KMS key.

    */ BypassPolicyLockoutSafetyCheck?: boolean; diff --git a/codegen/sdk-codegen/aws-models/kms.json b/codegen/sdk-codegen/aws-models/kms.json index 9c69159afdf2..b92b6900c074 100644 --- a/codegen/sdk-codegen/aws-models/kms.json +++ b/codegen/sdk-codegen/aws-models/kms.json @@ -188,7 +188,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Cancels the deletion of a KMS key. When this operation succeeds, the key state of the KMS\n key is Disabled. To enable the KMS key, use EnableKey.

    \n

    For more information about scheduling and canceling deletion of a KMS key, see Deleting KMS keys in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:CancelKeyDeletion (key policy)

    \n

    \n Related operations: ScheduleKeyDeletion\n

    ", + "smithy.api#documentation": "

    Cancels the deletion of a KMS key. When this operation succeeds, the key state of the KMS\n key is Disabled. To enable the KMS key, use EnableKey.

    \n

    For more information about scheduling and canceling deletion of a KMS key, see Deleting KMS keys in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:CancelKeyDeletion (key policy)

    \n

    \n Related operations: ScheduleKeyDeletion\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To cancel deletion of a KMS key", @@ -362,7 +362,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Connects or reconnects a custom key store to its backing key store. For an CloudHSM key\n store, ConnectCustomKeyStore connects the key store to its associated CloudHSM\n cluster. For an external key store, ConnectCustomKeyStore connects the key store\n to the external key store proxy that communicates with your external key manager.

    \n

    The custom key store must be connected before you can create KMS keys in the key store or\n use the KMS keys it contains. You can disconnect and reconnect a custom key store at any\n time.

    \n

    The connection process for a custom key store can take an extended amount of time to\n complete. This operation starts the connection process, but it does not wait for it to\n complete. When it succeeds, this operation quickly returns an HTTP 200 response and a JSON\n object with no properties. However, this response does not indicate that the custom key store\n is connected. To get the connection state of the custom key store, use the DescribeCustomKeyStores operation.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    The ConnectCustomKeyStore operation might fail for various reasons. To find\n the reason, use the DescribeCustomKeyStores operation and see the\n ConnectionErrorCode in the response. For help interpreting the\n ConnectionErrorCode, see CustomKeyStoresListEntry.

    \n

    To fix the failure, use the DisconnectCustomKeyStore operation to\n disconnect the custom key store, correct the error, use the UpdateCustomKeyStore operation if necessary, and then use\n ConnectCustomKeyStore again.

    \n

    \n CloudHSM key store\n

    \n

    During the connection process for an CloudHSM key store, KMS finds the CloudHSM cluster that\n is associated with the custom key store, creates the connection infrastructure, connects to\n the cluster, logs into the CloudHSM client as the kmsuser CU, and rotates its\n password.

    \n

    To connect an CloudHSM key store, its associated CloudHSM cluster must have at least one active\n HSM. To get the number of active HSMs in a cluster, use the DescribeClusters operation. To add HSMs\n to the cluster, use the CreateHsm operation. Also, the \n kmsuser crypto\n user (CU) must not be logged into the cluster. This prevents KMS from using this\n account to log in.

    \n

    If you are having trouble connecting or disconnecting a CloudHSM key store, see Troubleshooting an CloudHSM key\n store in the Key Management Service Developer Guide.

    \n

    \n External key store\n

    \n

    When you connect an external key store that uses public endpoint connectivity, KMS tests\n its ability to communicate with your external key manager by sending a request via the\n external key store proxy.

    \n

    When you connect to an external key store that uses VPC endpoint service connectivity,\n KMS establishes the networking elements that it needs to communicate with your external key\n manager via the external key store proxy. This includes creating an interface endpoint to the\n VPC endpoint service and a private hosted zone for traffic between KMS and the VPC endpoint\n service.

    \n

    To connect an external key store, KMS must be able to connect to the external key store\n proxy, the external key store proxy must be able to communicate with your external key\n manager, and the external key manager must be available for cryptographic operations.

    \n

    If you are having trouble connecting or disconnecting an external key store, see Troubleshooting an external\n key store in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:ConnectCustomKeyStore (IAM policy)

    \n

    \n Related operations\n

    \n ", + "smithy.api#documentation": "

    Connects or reconnects a custom key store to its backing key store. For an CloudHSM key\n store, ConnectCustomKeyStore connects the key store to its associated CloudHSM\n cluster. For an external key store, ConnectCustomKeyStore connects the key store\n to the external key store proxy that communicates with your external key manager.

    \n

    The custom key store must be connected before you can create KMS keys in the key store or\n use the KMS keys it contains. You can disconnect and reconnect a custom key store at any\n time.

    \n

    The connection process for a custom key store can take an extended amount of time to\n complete. This operation starts the connection process, but it does not wait for it to\n complete. When it succeeds, this operation quickly returns an HTTP 200 response and a JSON\n object with no properties. However, this response does not indicate that the custom key store\n is connected. To get the connection state of the custom key store, use the DescribeCustomKeyStores operation.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    The ConnectCustomKeyStore operation might fail for various reasons. To find\n the reason, use the DescribeCustomKeyStores operation and see the\n ConnectionErrorCode in the response. For help interpreting the\n ConnectionErrorCode, see CustomKeyStoresListEntry.

    \n

    To fix the failure, use the DisconnectCustomKeyStore operation to\n disconnect the custom key store, correct the error, use the UpdateCustomKeyStore operation if necessary, and then use\n ConnectCustomKeyStore again.

    \n

    \n CloudHSM key store\n

    \n

    During the connection process for an CloudHSM key store, KMS finds the CloudHSM cluster that\n is associated with the custom key store, creates the connection infrastructure, connects to\n the cluster, logs into the CloudHSM client as the kmsuser CU, and rotates its\n password.

    \n

    To connect an CloudHSM key store, its associated CloudHSM cluster must have at least one active\n HSM. To get the number of active HSMs in a cluster, use the DescribeClusters operation. To add HSMs\n to the cluster, use the CreateHsm operation. Also, the \n kmsuser crypto\n user (CU) must not be logged into the cluster. This prevents KMS from using this\n account to log in.

    \n

    If you are having trouble connecting or disconnecting a CloudHSM key store, see Troubleshooting an CloudHSM key\n store in the Key Management Service Developer Guide.

    \n

    \n External key store\n

    \n

    When you connect an external key store that uses public endpoint connectivity, KMS tests\n its ability to communicate with your external key manager by sending a request via the\n external key store proxy.

    \n

    When you connect to an external key store that uses VPC endpoint service connectivity,\n KMS establishes the networking elements that it needs to communicate with your external key\n manager via the external key store proxy. This includes creating an interface endpoint to the\n VPC endpoint service and a private hosted zone for traffic between KMS and the VPC endpoint\n service.

    \n

    To connect an external key store, KMS must be able to connect to the external key store\n proxy, the external key store proxy must be able to communicate with your external key\n manager, and the external key manager must be available for cryptographic operations.

    \n

    If you are having trouble connecting or disconnecting an external key store, see Troubleshooting an external\n key store in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:ConnectCustomKeyStore (IAM policy)

    \n

    \n Related operations\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To connect a custom key store", @@ -577,7 +577,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Creates a friendly name for a KMS key.

    \n \n

    Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    You can use an alias to identify a KMS key in the KMS console, in the DescribeKey operation and in cryptographic operations, such as Encrypt and\n GenerateDataKey. You can also change the KMS key that's associated with\n the alias (UpdateAlias) or delete the alias (DeleteAlias)\n at any time. These operations don't affect the underlying KMS key.

    \n

    You can associate the alias with any customer managed key in the same Amazon Web Services Region. Each\n alias is associated with only one KMS key at a time, but a KMS key can have multiple aliases.\n A valid KMS key is required. You can't create an alias without a KMS key.

    \n

    The alias must be unique in the account and Region, but you can have aliases with the same\n name in different Regions. For detailed information about aliases, see Using aliases in the\n Key Management Service Developer Guide.

    \n

    This operation does not return a response. To get the alias that you created, use the\n ListAliases operation.

    \n

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

    \n

    \n Cross-account use: No. You cannot perform this operation on an alias in a different Amazon Web Services account.

    \n

    \n Required permissions\n

    \n \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Creates a friendly name for a KMS key.

    \n \n

    Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    You can use an alias to identify a KMS key in the KMS console, in the DescribeKey operation and in cryptographic operations, such as Encrypt and\n GenerateDataKey. You can also change the KMS key that's associated with\n the alias (UpdateAlias) or delete the alias (DeleteAlias)\n at any time. These operations don't affect the underlying KMS key.

    \n

    You can associate the alias with any customer managed key in the same Amazon Web Services Region. Each\n alias is associated with only one KMS key at a time, but a KMS key can have multiple aliases.\n A valid KMS key is required. You can't create an alias without a KMS key.

    \n

    The alias must be unique in the account and Region, but you can have aliases with the same\n name in different Regions. For detailed information about aliases, see Using aliases in the\n Key Management Service Developer Guide.

    \n

    This operation does not return a response. To get the alias that you created, use the\n ListAliases operation.

    \n

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

    \n

    \n Cross-account use: No. You cannot perform this operation on an alias in a different Amazon Web Services account.

    \n

    \n Required permissions\n

    \n \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To create an alias", @@ -674,7 +674,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Creates a custom key store backed by a key store that you own and manage. When you use a\n KMS key in a custom key store for a cryptographic operation, the cryptographic operation is\n actually performed in your key store using your keys. KMS supports CloudHSM key stores\n backed by an CloudHSM cluster\n and external key\n stores backed by an external key store proxy and external key manager outside of\n Amazon Web Services.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    Before you create the custom key store, the required elements must be in place and\n operational. We recommend that you use the test tools that KMS provides to verify the\n configuration your external key store proxy. For details about the required elements and\n verification tests, see Assemble the prerequisites (for\n CloudHSM key stores) or Assemble the prerequisites (for\n external key stores) in the Key Management Service Developer Guide.

    \n

    To create a custom key store, use the following parameters.

    \n \n \n

    For external key stores:

    \n

    Some external key managers provide a simpler method for creating an external key store.\n For details, see your external key manager documentation.

    \n

    When creating an external key store in the KMS console, you can upload a JSON-based\n proxy configuration file with the desired values. You cannot use a proxy configuration with\n the CreateCustomKeyStore operation. However, you can use the values in the file\n to help you determine the correct values for the CreateCustomKeyStore\n parameters.

    \n     \n

    When the operation completes successfully, it returns the ID of the new custom key store.\n Before you can use your new custom key store, you need to use the ConnectCustomKeyStore operation to connect a new CloudHSM key store to its CloudHSM\n cluster, or to connect a new external key store to the external key store proxy for your\n external key manager. Even if you are not going to use your custom key store immediately, you\n might want to connect it to verify that all settings are correct and then disconnect it until\n you are ready to use it.

    \n

    For help with failures, see Troubleshooting a custom key store in the\n Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:CreateCustomKeyStore (IAM policy).

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Creates a custom key store backed by a key store that you own and manage. When you use a\n KMS key in a custom key store for a cryptographic operation, the cryptographic operation is\n actually performed in your key store using your keys. KMS supports CloudHSM key stores\n backed by an CloudHSM cluster\n and external key\n stores backed by an external key store proxy and external key manager outside of\n Amazon Web Services.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    Before you create the custom key store, the required elements must be in place and\n operational. We recommend that you use the test tools that KMS provides to verify the\n configuration your external key store proxy. For details about the required elements and\n verification tests, see Assemble the prerequisites (for\n CloudHSM key stores) or Assemble the prerequisites (for\n external key stores) in the Key Management Service Developer Guide.

    \n

    To create a custom key store, use the following parameters.

    \n \n \n

    For external key stores:

    \n

    Some external key managers provide a simpler method for creating an external key store.\n For details, see your external key manager documentation.

    \n

    When creating an external key store in the KMS console, you can upload a JSON-based\n proxy configuration file with the desired values. You cannot use a proxy configuration with\n the CreateCustomKeyStore operation. However, you can use the values in the file\n to help you determine the correct values for the CreateCustomKeyStore\n parameters.

    \n     \n

    When the operation completes successfully, it returns the ID of the new custom key store.\n Before you can use your new custom key store, you need to use the ConnectCustomKeyStore operation to connect a new CloudHSM key store to its CloudHSM\n cluster, or to connect a new external key store to the external key store proxy for your\n external key manager. Even if you are not going to use your custom key store immediately, you\n might want to connect it to verify that all settings are correct and then disconnect it until\n you are ready to use it.

    \n

    For help with failures, see Troubleshooting a custom key store in the\n Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:CreateCustomKeyStore (IAM policy).

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To create an AWS CloudHSM key store", @@ -813,7 +813,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Adds a grant to a KMS key.

    \n

    A grant is a policy instrument that allows Amazon Web Services principals to use\n KMS keys in cryptographic operations. It also can allow them to view a KMS key (DescribeKey) and create and manage grants. When authorizing access to a KMS key,\n grants are considered along with key policies and IAM policies. Grants are often used for\n temporary permissions because you can create one, use its permissions, and delete it without\n changing your key policies or IAM policies.

    \n

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

    \n

    The CreateGrant operation returns a GrantToken and a\n GrantId.

    \n \n

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

    \n

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

    \n

    \n Required permissions: kms:CreateGrant (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Adds a grant to a KMS key.

    \n

    A grant is a policy instrument that allows Amazon Web Services principals to use\n KMS keys in cryptographic operations. It also can allow them to view a KMS key (DescribeKey) and create and manage grants. When authorizing access to a KMS key,\n grants are considered along with key policies and IAM policies. Grants are often used for\n temporary permissions because you can create one, use its permissions, and delete it without\n changing your key policies or IAM policies.

    \n

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

    \n

    The CreateGrant operation returns a GrantToken and a\n GrantId.

    \n \n

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

    \n

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

    \n

    \n Required permissions: kms:CreateGrant (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To create a grant", @@ -960,7 +960,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Creates a unique customer managed KMS key in your Amazon Web Services account and Region.\n You can use a KMS key in cryptographic operations, such as encryption and signing. Some Amazon Web Services\n services let you use KMS keys that you create and manage to protect your service\n resources.

    \n

    A KMS key is a logical representation of a cryptographic key. In addition to the key\n material used in cryptographic operations, a KMS key includes metadata, such as the key ID,\n key policy, creation date, description, and key state. For details, see Managing keys in the\n Key Management Service Developer Guide\n

    \n

    Use the parameters of CreateKey to specify the type of KMS key, the source of\n its key material, its key policy, description, tags, and other properties.

    \n \n

    KMS has replaced the term customer master key (CMK) with KMS key and KMS key. The concept has not changed. To prevent breaking changes, KMS is keeping some variations of this term.

    \n     \n

    To create different types of KMS keys, use the following guidance:

    \n
    \n
    Symmetric encryption KMS key
    \n
    \n

    By default, CreateKey creates a symmetric encryption KMS key with key\n material that KMS generates. This is the basic and most widely used type of KMS key, and\n provides the best performance.

    \n

    To create a symmetric encryption KMS key, you don't need to specify any parameters.\n The default value for KeySpec, SYMMETRIC_DEFAULT, the default\n value for KeyUsage, ENCRYPT_DECRYPT, and the default value for\n Origin, AWS_KMS, create a symmetric encryption KMS key with\n KMS key material.

    \n

    If you need a key for basic encryption and decryption or you are creating a KMS key\n to protect your resources in an Amazon Web Services service, create a symmetric encryption KMS key.\n The key material in a symmetric encryption key never leaves KMS unencrypted. You can\n use a symmetric encryption KMS key to encrypt and decrypt data up to 4,096 bytes, but\n they are typically used to generate data keys and data keys pairs. For details, see\n GenerateDataKey and GenerateDataKeyPair.

    \n

    \n
    \n
    Asymmetric KMS keys
    \n
    \n

    To create an asymmetric KMS key, use the KeySpec parameter to specify\n the type of key material in the KMS key. Then, use the KeyUsage parameter\n to determine whether the KMS key will be used to encrypt and decrypt or sign and verify.\n You can't change these properties after the KMS key is created.

    \n

    Asymmetric KMS keys contain an RSA key pair, Elliptic Curve (ECC) key pair, or an\n SM2 key pair (China Regions only). The private key in an asymmetric KMS key never leaves\n KMS unencrypted. However, you can use the GetPublicKey operation to\n download the public key so it can be used outside of KMS. KMS keys with RSA or SM2 key\n pairs can be used to encrypt or decrypt data or sign and verify messages (but not both).\n KMS keys with ECC key pairs can be used only to sign and verify messages. For\n information about asymmetric KMS keys, see Asymmetric KMS keys in the\n Key Management Service Developer Guide.

    \n

    \n
    \n
    HMAC KMS key
    \n
    \n

    To create an HMAC KMS key, set the KeySpec parameter to a key spec\n value for HMAC KMS keys. Then set the KeyUsage parameter to\n GENERATE_VERIFY_MAC. You must set the key usage even though\n GENERATE_VERIFY_MAC is the only valid key usage value for HMAC KMS keys.\n You can't change these properties after the KMS key is created.

    \n

    HMAC KMS keys are symmetric keys that never leave KMS unencrypted. You can use\n HMAC keys to generate (GenerateMac) and verify (VerifyMac) HMAC codes for messages up to 4096 bytes.

    \n

    \n
    \n
    Multi-Region primary keys
    \n
    Imported key material
    \n
    \n

    To create a multi-Region primary key in the local Amazon Web Services Region,\n use the MultiRegion parameter with a value of True. To create\n a multi-Region replica key, that is, a KMS key with the same key ID\n and key material as a primary key, but in a different Amazon Web Services Region, use the ReplicateKey operation. To change a replica key to a primary key, and its\n primary key to a replica key, use the UpdatePrimaryRegion\n operation.

    \n

    You can create multi-Region KMS keys for all supported KMS key types: symmetric\n encryption KMS keys, HMAC KMS keys, asymmetric encryption KMS keys, and asymmetric\n signing KMS keys. You can also create multi-Region keys with imported key material.\n However, you can't create multi-Region keys in a custom key store.

    \n

    This operation supports multi-Region keys, an KMS feature that lets you create multiple\n interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key\n material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt\n it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    \n
    \n
    \n

    To import your own key material into a KMS key, begin by creating a KMS key with no\n key material. To do this, use the Origin parameter of\n CreateKey with a value of EXTERNAL. Next, use GetParametersForImport operation to get a public key and import token. Use\n the wrapping public key to encrypt your key material. Then, use ImportKeyMaterial with your import token to import the key material. For\n step-by-step instructions, see Importing Key Material in the \n Key Management Service Developer Guide\n .

    \n

    You can import key material into KMS keys of all supported KMS key types: symmetric\n encryption KMS keys, HMAC KMS keys, asymmetric encryption KMS keys, and asymmetric\n signing KMS keys. You can also create multi-Region keys with imported key material.\n However, you can't import key material into a KMS key in a custom key store.

    \n

    To create a multi-Region primary key with imported key material, use the\n Origin parameter of CreateKey with a value of\n EXTERNAL and the MultiRegion parameter with a value of\n True. To create replicas of the multi-Region primary key, use the ReplicateKey operation. For instructions, see Importing key material into\n multi-Region keys. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    \n
    \n
    Custom key store
    \n
    \n

    A custom key store lets you protect your Amazon Web Services resources using keys in a backing key\n store that you own and manage. When you request a cryptographic operation with a KMS key\n in a custom key store, the operation is performed in the backing key store using its\n cryptographic keys.

    \n

    KMS supports CloudHSM key stores backed by an CloudHSM cluster and external key stores backed by an\n external key manager outside of Amazon Web Services. When you create a KMS key in an CloudHSM key store,\n KMS generates an encryption key in the CloudHSM cluster and associates it with the KMS\n key. When you create a KMS key in an external key store, you specify an existing\n encryption key in the external key manager.

    \n \n

    Some external key managers provide a simpler method for creating a KMS key in an\n external key store. For details, see your external key manager documentation.

    \n     \n

    Before you create a KMS key in a custom key store, the ConnectionState\n of the key store must be CONNECTED. To connect the custom key store, use\n the ConnectCustomKeyStore operation. To find the\n ConnectionState, use the DescribeCustomKeyStores\n operation.

    \n

    To create a KMS key in a custom key store, use the CustomKeyStoreId.\n Use the default KeySpec value, SYMMETRIC_DEFAULT, and the\n default KeyUsage value, ENCRYPT_DECRYPT to create a symmetric\n encryption key. No other key type is supported in a custom key store.

    \n

    To create a KMS key in an CloudHSM key store, use the\n Origin parameter with a value of AWS_CLOUDHSM. The CloudHSM\n cluster that is associated with the custom key store must have at least two active HSMs\n in different Availability Zones in the Amazon Web Services Region.

    \n

    To create a KMS key in an external key store, use the\n Origin parameter with a value of EXTERNAL_KEY_STORE and an\n XksKeyId parameter that identifies an existing external key.

    \n \n

    Some external key managers provide a simpler method for creating a KMS key in an\n external key store. For details, see your external key manager documentation.

    \n     \n
    \n
    \n

    \n Cross-account use: No. You cannot use this operation to\n create a KMS key in a different Amazon Web Services account.

    \n

    \n Required permissions: kms:CreateKey (IAM policy). To use the\n Tags parameter, kms:TagResource (IAM policy). For examples and information about related\n permissions, see Allow a user to create\n KMS keys in the Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n " + "smithy.api#documentation": "

    Creates a unique customer managed KMS key in your Amazon Web Services account and Region.\n You can use a KMS key in cryptographic operations, such as encryption and signing. Some Amazon Web Services\n services let you use KMS keys that you create and manage to protect your service\n resources.

    \n

    A KMS key is a logical representation of a cryptographic key. In addition to the key\n material used in cryptographic operations, a KMS key includes metadata, such as the key ID,\n key policy, creation date, description, and key state. For details, see Managing keys in the\n Key Management Service Developer Guide\n

    \n

    Use the parameters of CreateKey to specify the type of KMS key, the source of\n its key material, its key policy, description, tags, and other properties.

    \n \n

    KMS has replaced the term customer master key (CMK) with KMS key and KMS key. The concept has not changed. To prevent breaking changes, KMS is keeping some variations of this term.

    \n     \n

    To create different types of KMS keys, use the following guidance:

    \n
    \n
    Symmetric encryption KMS key
    \n
    \n

    By default, CreateKey creates a symmetric encryption KMS key with key\n material that KMS generates. This is the basic and most widely used type of KMS key, and\n provides the best performance.

    \n

    To create a symmetric encryption KMS key, you don't need to specify any parameters.\n The default value for KeySpec, SYMMETRIC_DEFAULT, the default\n value for KeyUsage, ENCRYPT_DECRYPT, and the default value for\n Origin, AWS_KMS, create a symmetric encryption KMS key with\n KMS key material.

    \n

    If you need a key for basic encryption and decryption or you are creating a KMS key\n to protect your resources in an Amazon Web Services service, create a symmetric encryption KMS key.\n The key material in a symmetric encryption key never leaves KMS unencrypted. You can\n use a symmetric encryption KMS key to encrypt and decrypt data up to 4,096 bytes, but\n they are typically used to generate data keys and data keys pairs. For details, see\n GenerateDataKey and GenerateDataKeyPair.

    \n

    \n
    \n
    Asymmetric KMS keys
    \n
    \n

    To create an asymmetric KMS key, use the KeySpec parameter to specify\n the type of key material in the KMS key. Then, use the KeyUsage parameter\n to determine whether the KMS key will be used to encrypt and decrypt or sign and verify.\n You can't change these properties after the KMS key is created.

    \n

    Asymmetric KMS keys contain an RSA key pair, Elliptic Curve (ECC) key pair, or an\n SM2 key pair (China Regions only). The private key in an asymmetric KMS key never leaves\n KMS unencrypted. However, you can use the GetPublicKey operation to\n download the public key so it can be used outside of KMS. KMS keys with RSA or SM2 key\n pairs can be used to encrypt or decrypt data or sign and verify messages (but not both).\n KMS keys with ECC key pairs can be used only to sign and verify messages. For\n information about asymmetric KMS keys, see Asymmetric KMS keys in the\n Key Management Service Developer Guide.

    \n

    \n
    \n
    HMAC KMS key
    \n
    \n

    To create an HMAC KMS key, set the KeySpec parameter to a key spec\n value for HMAC KMS keys. Then set the KeyUsage parameter to\n GENERATE_VERIFY_MAC. You must set the key usage even though\n GENERATE_VERIFY_MAC is the only valid key usage value for HMAC KMS keys.\n You can't change these properties after the KMS key is created.

    \n

    HMAC KMS keys are symmetric keys that never leave KMS unencrypted. You can use\n HMAC keys to generate (GenerateMac) and verify (VerifyMac) HMAC codes for messages up to 4096 bytes.

    \n

    \n
    \n
    Multi-Region primary keys
    \n
    Imported key material
    \n
    \n

    To create a multi-Region primary key in the local Amazon Web Services Region,\n use the MultiRegion parameter with a value of True. To create\n a multi-Region replica key, that is, a KMS key with the same key ID\n and key material as a primary key, but in a different Amazon Web Services Region, use the ReplicateKey operation. To change a replica key to a primary key, and its\n primary key to a replica key, use the UpdatePrimaryRegion\n operation.

    \n

    You can create multi-Region KMS keys for all supported KMS key types: symmetric\n encryption KMS keys, HMAC KMS keys, asymmetric encryption KMS keys, and asymmetric\n signing KMS keys. You can also create multi-Region keys with imported key material.\n However, you can't create multi-Region keys in a custom key store.

    \n

    This operation supports multi-Region keys, an KMS feature that lets you create multiple\n interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key\n material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt\n it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    \n
    \n
    \n

    To import your own key material into a KMS key, begin by creating a KMS key with no\n key material. To do this, use the Origin parameter of\n CreateKey with a value of EXTERNAL. Next, use GetParametersForImport operation to get a public key and import token. Use\n the wrapping public key to encrypt your key material. Then, use ImportKeyMaterial with your import token to import the key material. For\n step-by-step instructions, see Importing Key Material in the \n Key Management Service Developer Guide\n .

    \n

    You can import key material into KMS keys of all supported KMS key types: symmetric\n encryption KMS keys, HMAC KMS keys, asymmetric encryption KMS keys, and asymmetric\n signing KMS keys. You can also create multi-Region keys with imported key material.\n However, you can't import key material into a KMS key in a custom key store.

    \n

    To create a multi-Region primary key with imported key material, use the\n Origin parameter of CreateKey with a value of\n EXTERNAL and the MultiRegion parameter with a value of\n True. To create replicas of the multi-Region primary key, use the ReplicateKey operation. For instructions, see Importing key material into\n multi-Region keys. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    \n
    \n
    Custom key store
    \n
    \n

    A custom key store lets you protect your Amazon Web Services resources using keys in a backing key\n store that you own and manage. When you request a cryptographic operation with a KMS key\n in a custom key store, the operation is performed in the backing key store using its\n cryptographic keys.

    \n

    KMS supports CloudHSM key stores backed by an CloudHSM cluster and external key stores backed by an\n external key manager outside of Amazon Web Services. When you create a KMS key in an CloudHSM key store,\n KMS generates an encryption key in the CloudHSM cluster and associates it with the KMS\n key. When you create a KMS key in an external key store, you specify an existing\n encryption key in the external key manager.

    \n \n

    Some external key managers provide a simpler method for creating a KMS key in an\n external key store. For details, see your external key manager documentation.

    \n     \n

    Before you create a KMS key in a custom key store, the ConnectionState\n of the key store must be CONNECTED. To connect the custom key store, use\n the ConnectCustomKeyStore operation. To find the\n ConnectionState, use the DescribeCustomKeyStores\n operation.

    \n

    To create a KMS key in a custom key store, use the CustomKeyStoreId.\n Use the default KeySpec value, SYMMETRIC_DEFAULT, and the\n default KeyUsage value, ENCRYPT_DECRYPT to create a symmetric\n encryption key. No other key type is supported in a custom key store.

    \n

    To create a KMS key in an CloudHSM key store, use the\n Origin parameter with a value of AWS_CLOUDHSM. The CloudHSM\n cluster that is associated with the custom key store must have at least two active HSMs\n in different Availability Zones in the Amazon Web Services Region.

    \n

    To create a KMS key in an external key store, use the\n Origin parameter with a value of EXTERNAL_KEY_STORE and an\n XksKeyId parameter that identifies an existing external key.

    \n \n

    Some external key managers provide a simpler method for creating a KMS key in an\n external key store. For details, see your external key manager documentation.

    \n     \n
    \n
    \n

    \n Cross-account use: No. You cannot use this operation to\n create a KMS key in a different Amazon Web Services account.

    \n

    \n Required permissions: kms:CreateKey (IAM policy). To use the\n Tags parameter, kms:TagResource (IAM policy). For examples and information about related\n permissions, see Allow a user to create\n KMS keys in the Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n \n

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

    " } }, "com.amazonaws.kms#CreateKeyRequest": { @@ -1015,7 +1015,7 @@ "target": "com.amazonaws.kms#BooleanType", "traits": { "smithy.api#default": false, - "smithy.api#documentation": "

    Skips (\"bypasses\") the key policy lockout safety check. The default value is false.

    \n \n

    Setting this value to true increases the risk that the KMS key becomes unmanageable. Do\n not set this value to true indiscriminately.

    \n

    For more information, see Default key policy in the Key Management Service Developer Guide.

    \n     \n

    Use this parameter only when you intend to prevent the principal that is making the\n request from making a subsequent PutKeyPolicy request on the KMS key.

    " + "smithy.api#documentation": "

    Skips (\"bypasses\") the key policy lockout safety check. The default value is false.

    \n \n

    Setting this value to true increases the risk that the KMS key becomes unmanageable. Do\n not set this value to true indiscriminately.

    \n

    For more information, see Default key policy in the Key Management Service Developer Guide.

    \n     \n

    Use this parameter only when you intend to prevent the principal that is making the\n request from making a subsequent PutKeyPolicy\n request on the KMS key.

    " } }, "Tags": { @@ -1431,7 +1431,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Decrypts ciphertext that was encrypted by a KMS key using any of the following\n operations:

    \n \n

    You can use this operation to decrypt ciphertext that was encrypted under a symmetric\n encryption KMS key or an asymmetric encryption KMS key. When the KMS key is asymmetric, you\n must specify the KMS key and the encryption algorithm that was used to encrypt the ciphertext.\n For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    The Decrypt operation also decrypts ciphertext that was encrypted outside of\n KMS by the public key in an KMS asymmetric KMS key. However, it cannot decrypt symmetric\n ciphertext produced by other libraries, such as the Amazon Web Services Encryption SDK or Amazon S3 client-side encryption.\n These libraries return a ciphertext format that is incompatible with KMS.

    \n

    If the ciphertext was encrypted under a symmetric encryption KMS key, the\n KeyId parameter is optional. KMS can get this information from metadata that\n it adds to the symmetric ciphertext blob. This feature adds durability to your implementation\n by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even\n if they've lost track of the key ID. However, specifying the KMS key is always recommended as\n a best practice. When you use the KeyId parameter to specify a KMS key, KMS\n only uses the KMS key you specify. If the ciphertext was encrypted under a different KMS key,\n the Decrypt operation fails. This practice ensures that you use the KMS key that\n you intend.

    \n

    Whenever possible, use key policies to give users permission to call the\n Decrypt operation on a particular KMS key, instead of using &IAM; policies.\n Otherwise, you might create an &IAM; policy that gives the user Decrypt\n permission on all KMS keys. This user could decrypt ciphertext that was encrypted by KMS keys\n in other accounts if the key policy for the cross-account KMS key permits it. If you must use\n an IAM policy for Decrypt permissions, limit the user to particular KMS keys or\n particular trusted accounts. For details, see Best practices for IAM\n policies in the Key Management Service Developer Guide.

    \n

    \n Decrypt also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call Decrypt for a Nitro enclave, use\n the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient parameter to provide the\n attestation document for the enclave. Instead of the plaintext data, the response includes the\n plaintext data encrypted with the public key from the attestation document\n (CiphertextForRecipient).For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide..

    \n

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

    \n

    \n Cross-account use: Yes. If you use the KeyId\n parameter to identify a KMS key in a different Amazon Web Services account, specify the key ARN or the alias\n ARN of the KMS key.

    \n

    \n Required permissions: kms:Decrypt (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Decrypts ciphertext that was encrypted by a KMS key using any of the following\n operations:

    \n \n

    You can use this operation to decrypt ciphertext that was encrypted under a symmetric\n encryption KMS key or an asymmetric encryption KMS key. When the KMS key is asymmetric, you\n must specify the KMS key and the encryption algorithm that was used to encrypt the ciphertext.\n For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    The Decrypt operation also decrypts ciphertext that was encrypted outside of\n KMS by the public key in an KMS asymmetric KMS key. However, it cannot decrypt symmetric\n ciphertext produced by other libraries, such as the Amazon Web Services Encryption SDK or Amazon S3 client-side encryption.\n These libraries return a ciphertext format that is incompatible with KMS.

    \n

    If the ciphertext was encrypted under a symmetric encryption KMS key, the\n KeyId parameter is optional. KMS can get this information from metadata that\n it adds to the symmetric ciphertext blob. This feature adds durability to your implementation\n by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even\n if they've lost track of the key ID. However, specifying the KMS key is always recommended as\n a best practice. When you use the KeyId parameter to specify a KMS key, KMS\n only uses the KMS key you specify. If the ciphertext was encrypted under a different KMS key,\n the Decrypt operation fails. This practice ensures that you use the KMS key that\n you intend.

    \n

    Whenever possible, use key policies to give users permission to call the\n Decrypt operation on a particular KMS key, instead of using &IAM; policies.\n Otherwise, you might create an &IAM; policy that gives the user Decrypt\n permission on all KMS keys. This user could decrypt ciphertext that was encrypted by KMS keys\n in other accounts if the key policy for the cross-account KMS key permits it. If you must use\n an IAM policy for Decrypt permissions, limit the user to particular KMS keys or\n particular trusted accounts. For details, see Best practices for IAM\n policies in the Key Management Service Developer Guide.

    \n

    \n Decrypt also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call Decrypt for a Nitro enclave, use\n the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient parameter to provide the\n attestation document for the enclave. Instead of the plaintext data, the response includes the\n plaintext data encrypted with the public key from the attestation document\n (CiphertextForRecipient). For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Cross-account use: Yes. If you use the KeyId\n parameter to identify a KMS key in a different Amazon Web Services account, specify the key ARN or the alias\n ARN of the KMS key.

    \n

    \n Required permissions: kms:Decrypt (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To decrypt data with a symmetric encryption KMS key", @@ -1486,7 +1486,7 @@ "Recipient": { "target": "com.amazonaws.kms#RecipientInfo", "traits": { - "smithy.api#documentation": "

    A signed attestation document from\n an Amazon Web Services Nitro enclave and the encryption algorithm to use with the enclave's public key. The\n only valid encryption algorithm is RSAES_OAEP_SHA_256.

    \n

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To include this\n parameter, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK.

    \n

    When you use this parameter, instead of returning the plaintext data, KMS encrypts the\n plaintext data with the public key in the attestation document, and returns the resulting\n ciphertext in the CiphertextForRecipient field in the response. This ciphertext\n can be decrypted only with the private key in the enclave. The Plaintext field in\n the response is null or empty.

    \n

    For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    " + "smithy.api#documentation": "

    A signed attestation\n document from an Amazon Web Services Nitro enclave and the encryption algorithm to use with the\n enclave's public key. The only valid encryption algorithm is RSAES_OAEP_SHA_256.

    \n

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To include this\n parameter, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK.

    \n

    When you use this parameter, instead of returning the plaintext data, KMS encrypts the\n plaintext data with the public key in the attestation document, and returns the resulting\n ciphertext in the CiphertextForRecipient field in the response. This ciphertext\n can be decrypted only with the private key in the enclave. The Plaintext field in\n the response is null or empty.

    \n

    For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    " } }, "DryRun": { @@ -1555,7 +1555,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Deletes the specified alias.

    \n \n

    Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    Because an alias is not a property of a KMS key, you can delete and change the aliases of\n a KMS key without affecting the KMS key. Also, aliases do not appear in the response from the\n DescribeKey operation. To get the aliases of all KMS keys, use the ListAliases operation.

    \n

    Each KMS key can have multiple aliases. To change the alias of a KMS key, use DeleteAlias to delete the current alias and CreateAlias to\n create a new alias. To associate an existing alias with a different KMS key, call UpdateAlias.

    \n

    \n Cross-account use: No. You cannot perform this operation on an alias in a different Amazon Web Services account.

    \n

    \n Required permissions\n

    \n \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Deletes the specified alias.

    \n \n

    Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    Because an alias is not a property of a KMS key, you can delete and change the aliases of\n a KMS key without affecting the KMS key. Also, aliases do not appear in the response from the\n DescribeKey operation. To get the aliases of all KMS keys, use the ListAliases operation.

    \n

    Each KMS key can have multiple aliases. To change the alias of a KMS key, use DeleteAlias to delete the current alias and CreateAlias to\n create a new alias. To associate an existing alias with a different KMS key, call UpdateAlias.

    \n

    \n Cross-account use: No. You cannot perform this operation on an alias in a different Amazon Web Services account.

    \n

    \n Required permissions\n

    \n \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To delete an alias", @@ -1605,7 +1605,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Deletes a custom key store. This operation does not affect any backing elements of the\n custom key store. It does not delete the CloudHSM cluster that is associated with an CloudHSM key\n store, or affect any users or keys in the cluster. For an external key store, it does not\n affect the external key store proxy, external key manager, or any external keys.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    The custom key store that you delete cannot contain any KMS keys. Before deleting the key store,\n verify that you will never need to use any of the KMS keys in the key store for any\n cryptographic operations. Then, use ScheduleKeyDeletion to delete the KMS keys from the\n key store. After the required waiting period expires and all KMS keys are deleted from the\n custom key store, use DisconnectCustomKeyStore to disconnect the key store\n from KMS. Then, you can delete the custom key store.

    \n

    For keys in an CloudHSM key store, the ScheduleKeyDeletion operation makes a\n best effort to delete the key material from the associated cluster. However, you might need to\n manually delete the orphaned key\n material from the cluster and its backups. KMS never creates, manages, or deletes\n cryptographic keys in the external key manager associated with an external key store. You must\n manage them using your external key manager tools.

    \n

    Instead of deleting the custom key store, consider using the DisconnectCustomKeyStore operation to disconnect the custom key store from its\n backing key store. While the key store is disconnected, you cannot create or use the KMS keys\n in the key store. But, you do not need to delete KMS keys and you can reconnect a disconnected\n custom key store at any time.

    \n

    If the operation succeeds, it returns a JSON object with no\nproperties.

    \n

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

    \n

    \n Required permissions: kms:DeleteCustomKeyStore (IAM policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Deletes a custom key store. This operation does not affect any backing elements of the\n custom key store. It does not delete the CloudHSM cluster that is associated with an CloudHSM key\n store, or affect any users or keys in the cluster. For an external key store, it does not\n affect the external key store proxy, external key manager, or any external keys.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    The custom key store that you delete cannot contain any KMS keys. Before deleting the key store,\n verify that you will never need to use any of the KMS keys in the key store for any\n cryptographic operations. Then, use ScheduleKeyDeletion to delete the KMS keys from the\n key store. After the required waiting period expires and all KMS keys are deleted from the\n custom key store, use DisconnectCustomKeyStore to disconnect the key store\n from KMS. Then, you can delete the custom key store.

    \n

    For keys in an CloudHSM key store, the ScheduleKeyDeletion operation makes a\n best effort to delete the key material from the associated cluster. However, you might need to\n manually delete the orphaned key\n material from the cluster and its backups. KMS never creates, manages, or deletes\n cryptographic keys in the external key manager associated with an external key store. You must\n manage them using your external key manager tools.

    \n

    Instead of deleting the custom key store, consider using the DisconnectCustomKeyStore operation to disconnect the custom key store from its\n backing key store. While the key store is disconnected, you cannot create or use the KMS keys\n in the key store. But, you do not need to delete KMS keys and you can reconnect a disconnected\n custom key store at any time.

    \n

    If the operation succeeds, it returns a JSON object with no\nproperties.

    \n

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

    \n

    \n Required permissions: kms:DeleteCustomKeyStore (IAM policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To delete a custom key store from AWS KMS", @@ -1669,7 +1669,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Deletes key material that was previously imported. This operation makes the specified KMS\n key temporarily unusable. To restore the usability of the KMS key, reimport the same key\n material. For more information about importing key material into KMS, see Importing Key Material\n in the Key Management Service Developer Guide.

    \n

    When the specified KMS key is in the PendingDeletion state, this operation\n does not change the KMS key's state. Otherwise, it changes the KMS key's state to\n PendingImport.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:DeleteImportedKeyMaterial (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Deletes key material that was previously imported. This operation makes the specified KMS\n key temporarily unusable. To restore the usability of the KMS key, reimport the same key\n material. For more information about importing key material into KMS, see Importing Key Material\n in the Key Management Service Developer Guide.

    \n

    When the specified KMS key is in the PendingDeletion state, this operation\n does not change the KMS key's state. Otherwise, it changes the KMS key's state to\n PendingImport.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:DeleteImportedKeyMaterial (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To delete imported key material", @@ -1733,7 +1733,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Gets information about custom key stores in the account and Region.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    By default, this operation returns information about all custom key stores in the account\n and Region. To get only information about a particular custom key store, use either the\n CustomKeyStoreName or CustomKeyStoreId parameter (but not\n both).

    \n

    To determine whether the custom key store is connected to its CloudHSM cluster or external\n key store proxy, use the ConnectionState element in the response. If an attempt\n to connect the custom key store failed, the ConnectionState value is\n FAILED and the ConnectionErrorCode element in the response\n indicates the cause of the failure. For help interpreting the\n ConnectionErrorCode, see CustomKeyStoresListEntry.

    \n

    Custom key stores have a DISCONNECTED connection state if the key store has\n never been connected or you used the DisconnectCustomKeyStore operation to\n disconnect it. Otherwise, the connection state is CONNECTED. If your custom key store\n connection state is CONNECTED but you are having trouble using it, verify that\n the backing store is active and available. For an CloudHSM key store, verify that the associated\n CloudHSM cluster is active and contains the minimum number of HSMs required for the operation, if\n any. For an external key store, verify that the external key store proxy and its associated\n external key manager are reachable and enabled.

    \n

    For help repairing your CloudHSM key store, see the Troubleshooting CloudHSM key stores. For help\n repairing your external key store, see the Troubleshooting external key stores.\n Both topics are in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:DescribeCustomKeyStores (IAM policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Gets information about custom key stores in the account and Region.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    By default, this operation returns information about all custom key stores in the account\n and Region. To get only information about a particular custom key store, use either the\n CustomKeyStoreName or CustomKeyStoreId parameter (but not\n both).

    \n

    To determine whether the custom key store is connected to its CloudHSM cluster or external\n key store proxy, use the ConnectionState element in the response. If an attempt\n to connect the custom key store failed, the ConnectionState value is\n FAILED and the ConnectionErrorCode element in the response\n indicates the cause of the failure. For help interpreting the\n ConnectionErrorCode, see CustomKeyStoresListEntry.

    \n

    Custom key stores have a DISCONNECTED connection state if the key store has\n never been connected or you used the DisconnectCustomKeyStore operation to\n disconnect it. Otherwise, the connection state is CONNECTED. If your custom key store\n connection state is CONNECTED but you are having trouble using it, verify that\n the backing store is active and available. For an CloudHSM key store, verify that the associated\n CloudHSM cluster is active and contains the minimum number of HSMs required for the operation, if\n any. For an external key store, verify that the external key store proxy and its associated\n external key manager are reachable and enabled.

    \n

    For help repairing your CloudHSM key store, see the Troubleshooting CloudHSM key stores. For help\n repairing your external key store, see the Troubleshooting external key stores.\n Both topics are in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:DescribeCustomKeyStores (IAM policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To get detailed information about custom key stores in the account and Region", @@ -1833,7 +1833,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Provides detailed information about a KMS key. You can run DescribeKey on a\n customer managed\n key or an Amazon Web Services managed key.

    \n

    This detailed information includes the key ARN, creation date (and deletion date, if\n applicable), the key state, and the origin and expiration date (if any) of the key material.\n It includes fields, like KeySpec, that help you distinguish different types of\n KMS keys. It also displays the key usage (encryption, signing, or generating and verifying\n MACs) and the algorithms that the KMS key supports.

    \n

    For multi-Region keys,\n DescribeKey displays the primary key and all related replica keys. For KMS keys\n in CloudHSM key stores, it includes\n information about the key store, such as the key store ID and the CloudHSM cluster ID. For KMS\n keys in external key stores, it\n includes the custom key store ID and the ID of the external key.

    \n

    \n DescribeKey does not return the following information:

    \n \n

    In general, DescribeKey is a non-mutating operation. It returns data about\n KMS keys, but doesn't change them. However, Amazon Web Services services use DescribeKey to\n create Amazon Web Services\n managed keys from a predefined Amazon Web Services alias with no key\n ID.

    \n

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

    \n

    \n Required permissions: kms:DescribeKey (key policy)

    \n

    \n Related operations:\n

    \n " + "smithy.api#documentation": "

    Provides detailed information about a KMS key. You can run DescribeKey on a\n customer managed\n key or an Amazon Web Services managed key.

    \n

    This detailed information includes the key ARN, creation date (and deletion date, if\n applicable), the key state, and the origin and expiration date (if any) of the key material.\n It includes fields, like KeySpec, that help you distinguish different types of\n KMS keys. It also displays the key usage (encryption, signing, or generating and verifying\n MACs) and the algorithms that the KMS key supports.

    \n

    For multi-Region keys, DescribeKey displays the primary key and all\n related replica keys. For KMS keys in CloudHSM key stores, it includes information\n about the key store, such as the key store ID and the CloudHSM cluster ID. For KMS keys in external key stores,\n it includes the custom key store ID and the ID of the external key.

    \n

    \n DescribeKey does not return the following information:

    \n \n

    In general, DescribeKey is a non-mutating operation. It returns data about\n KMS keys, but doesn't change them. However, Amazon Web Services services use DescribeKey to\n create Amazon Web Services\n managed keys from a predefined Amazon Web Services alias with no key\n ID.

    \n

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

    \n

    \n Required permissions: kms:DescribeKey (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    " } }, "com.amazonaws.kms#DescribeKeyRequest": { @@ -1906,7 +1906,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Sets the state of a KMS key to disabled. This change temporarily prevents use of the KMS\n key for cryptographic operations.

    \n

    For more information about how key state affects the use of a KMS key, see\n Key states of KMS keys in the \n Key Management Service Developer Guide\n .

    \n

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

    \n

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

    \n

    \n Required permissions: kms:DisableKey (key policy)

    \n

    \n Related operations: EnableKey\n

    ", + "smithy.api#documentation": "

    Sets the state of a KMS key to disabled. This change temporarily prevents use of the KMS\n key for cryptographic operations.

    \n

    For more information about how key state affects the use of a KMS key, see\n Key states of KMS keys in the \n Key Management Service Developer Guide\n .

    \n

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

    \n

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

    \n

    \n Required permissions: kms:DisableKey (key policy)

    \n

    \n Related operations: EnableKey\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To disable a KMS key", @@ -1965,7 +1965,7 @@ } ], "traits": { - "smithy.api#documentation": "

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

    \n

    Automatic key rotation is supported only on symmetric encryption KMS keys.\n 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.

    \n

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

    \n \n

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

    \n     \n

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

    \n

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

    \n

    \n Required permissions: kms:DisableKeyRotation (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

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

    \n

    Automatic key rotation is supported only on symmetric encryption KMS keys.\n 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.

    \n

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

    \n \n

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

    \n     \n

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

    \n

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

    \n

    \n Required permissions: kms:DisableKeyRotation (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To disable automatic rotation of key material", @@ -2029,7 +2029,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Disconnects the custom key store from its backing key store. This operation disconnects an\n CloudHSM key store from its associated CloudHSM cluster or disconnects an external key store from\n the external key store proxy that communicates with your external key manager.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    While a custom key store is disconnected, you can manage the custom key store and its KMS\n keys, but you cannot create or use its KMS keys. You can reconnect the custom key store at any\n time.

    \n \n

    While a custom key store is disconnected, all attempts to create KMS keys in the custom key store or to use existing KMS keys in cryptographic operations will\n fail. This action can prevent users from storing and accessing sensitive data.

    \n     \n

    When you disconnect a custom key store, its ConnectionState changes to\n Disconnected. To find the connection state of a custom key store, use the DescribeCustomKeyStores operation. To reconnect a custom key store, use the\n ConnectCustomKeyStore operation.

    \n

    If the operation succeeds, it returns a JSON object with no\nproperties.

    \n

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

    \n

    \n Required permissions: kms:DisconnectCustomKeyStore (IAM policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Disconnects the custom key store from its backing key store. This operation disconnects an\n CloudHSM key store from its associated CloudHSM cluster or disconnects an external key store from\n the external key store proxy that communicates with your external key manager.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n

    While a custom key store is disconnected, you can manage the custom key store and its KMS\n keys, but you cannot create or use its KMS keys. You can reconnect the custom key store at any\n time.

    \n \n

    While a custom key store is disconnected, all attempts to create KMS keys in the custom key store or to use existing KMS keys in cryptographic operations will\n fail. This action can prevent users from storing and accessing sensitive data.

    \n     \n

    When you disconnect a custom key store, its ConnectionState changes to\n Disconnected. To find the connection state of a custom key store, use the DescribeCustomKeyStores operation. To reconnect a custom key store, use the\n ConnectCustomKeyStore operation.

    \n

    If the operation succeeds, it returns a JSON object with no\nproperties.

    \n

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

    \n

    \n Required permissions: kms:DisconnectCustomKeyStore (IAM policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To disconnect a custom key store from its CloudHSM cluster", @@ -2076,7 +2076,7 @@ "code": "DryRunOperation", "httpResponseCode": 412 }, - "smithy.api#documentation": "

    \n The request was rejected because the DryRun parameter was specified.\n

    ", + "smithy.api#documentation": "

    The request was rejected because the DryRun parameter was specified.

    ", "smithy.api#error": "client", "smithy.api#httpError": 412 } @@ -2110,7 +2110,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Sets the key state of a KMS key to enabled. This allows you to use the KMS key for\n cryptographic operations.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:EnableKey (key policy)

    \n

    \n Related operations: DisableKey\n

    ", + "smithy.api#documentation": "

    Sets the key state of a KMS key to enabled. This allows you to use the KMS key for\n cryptographic operations.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:EnableKey (key policy)

    \n

    \n Related operations: DisableKey\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To enable a KMS key", @@ -2169,7 +2169,7 @@ } ], "traits": { - "smithy.api#documentation": "

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

    \n

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

    \n

    Automatic key rotation is supported only on symmetric encryption KMS keys.\n 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.

    \n

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

    \n \n

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

    \n

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

    \n

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

    \n     \n

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

    \n

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

    \n

    \n Required permissions: kms:EnableKeyRotation (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

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

    \n

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

    \n

    Automatic key rotation is supported only on symmetric encryption KMS keys.\n 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.

    \n

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

    \n \n

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

    \n

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

    \n

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

    \n     \n

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

    \n

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

    \n

    \n Required permissions: kms:EnableKeyRotation (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To enable automatic rotation of key material", @@ -2234,7 +2234,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Encrypts plaintext of up to 4,096 bytes using a KMS key. You can use a symmetric or\n asymmetric KMS key with a KeyUsage of ENCRYPT_DECRYPT.

    \n

    You can use this operation to encrypt small amounts of arbitrary data, such as a personal\n identifier or database password, or other sensitive information. You don't need to use the\n Encrypt operation to encrypt a data key. The GenerateDataKey\n and GenerateDataKeyPair operations return a plaintext data key and an\n encrypted copy of that data key.

    \n

    If you use a symmetric encryption KMS key, you can use an encryption context to add\n additional security to your encryption operation. If you specify an\n EncryptionContext when encrypting data, you must specify the same encryption\n context (a case-sensitive exact match) when decrypting the data. Otherwise, the request to\n decrypt fails with an InvalidCiphertextException. For more information, see\n Encryption\n Context in the Key Management Service Developer Guide.

    \n

    If you specify an asymmetric KMS key, you must also specify the encryption algorithm. The\n algorithm must be compatible with the KMS key spec.

    \n \n

    When you use an asymmetric KMS key to encrypt or reencrypt data, be sure to record the KMS key and encryption algorithm that you choose. You will be required to provide the same KMS key and encryption algorithm when you decrypt the data. If the KMS key and algorithm do not match the values used to encrypt the data, the decrypt operation fails.

    \n

    You are not required to supply the key ID and encryption algorithm when you decrypt with symmetric encryption KMS keys because KMS stores this information in the ciphertext blob. KMS cannot store metadata in ciphertext generated with asymmetric keys. The standard format for asymmetric key ciphertext does not include configurable fields.

    \n     \n

    The maximum size of the data that you can encrypt varies with the type of KMS key and the\n encryption algorithm that you choose.

    \n \n

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

    \n

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

    \n

    \n Required permissions: kms:Encrypt (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Encrypts plaintext of up to 4,096 bytes using a KMS key. You can use a symmetric or\n asymmetric KMS key with a KeyUsage of ENCRYPT_DECRYPT.

    \n

    You can use this operation to encrypt small amounts of arbitrary data, such as a personal\n identifier or database password, or other sensitive information. You don't need to use the\n Encrypt operation to encrypt a data key. The GenerateDataKey\n and GenerateDataKeyPair operations return a plaintext data key and an\n encrypted copy of that data key.

    \n

    If you use a symmetric encryption KMS key, you can use an encryption context to add\n additional security to your encryption operation. If you specify an\n EncryptionContext when encrypting data, you must specify the same encryption\n context (a case-sensitive exact match) when decrypting the data. Otherwise, the request to\n decrypt fails with an InvalidCiphertextException. For more information, see\n Encryption\n Context in the Key Management Service Developer Guide.

    \n

    If you specify an asymmetric KMS key, you must also specify the encryption algorithm. The\n algorithm must be compatible with the KMS key spec.

    \n \n

    When you use an asymmetric KMS key to encrypt or reencrypt data, be sure to record the KMS key and encryption algorithm that you choose. You will be required to provide the same KMS key and encryption algorithm when you decrypt the data. If the KMS key and algorithm do not match the values used to encrypt the data, the decrypt operation fails.

    \n

    You are not required to supply the key ID and encryption algorithm when you decrypt with symmetric encryption KMS keys because KMS stores this information in the ciphertext blob. KMS cannot store metadata in ciphertext generated with asymmetric keys. The standard format for asymmetric key ciphertext does not include configurable fields.

    \n     \n

    The maximum size of the data that you can encrypt varies with the type of KMS key and the\n encryption algorithm that you choose.

    \n \n

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

    \n

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

    \n

    \n Required permissions: kms:Encrypt (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To encrypt data with a symmetric encryption KMS key", @@ -2449,7 +2449,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns a unique symmetric data key for use outside of KMS. This operation returns a\n plaintext copy of the data key and a copy that is encrypted under a symmetric encryption KMS\n key that you specify. The bytes in the plaintext key are random; they are not related to the\n caller or the KMS key. You can use the plaintext key to encrypt your data outside of KMS and\n store the encrypted data key with the encrypted data.

    \n

    To generate a data key, specify the symmetric encryption KMS key that will be used to\n encrypt the data key. You cannot use an asymmetric KMS key to encrypt data keys. To get the\n type of your KMS key, use the DescribeKey operation.

    \n

    You must also specify the length of the data key. Use either the KeySpec or\n NumberOfBytes parameters (but not both). For 128-bit and 256-bit data keys, use\n the KeySpec parameter.

    \n

    To generate a 128-bit SM4 data key (China Regions only), specify a KeySpec\n value of AES_128 or a NumberOfBytes value of 16. The\n symmetric encryption key used in China Regions to encrypt your data key is an SM4 encryption\n key.

    \n

    To get only an encrypted copy of the data key, use GenerateDataKeyWithoutPlaintext. To generate an asymmetric data key pair, use\n the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext operation. To get a cryptographically secure\n random byte string, use GenerateRandom.

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

    \n GenerateDataKey also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call GenerateDataKey for an Amazon Web Services Nitro\n enclave, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient parameter\n to provide the attestation document for the enclave. GenerateDataKey returns a\n copy of the data key encrypted under the specified KMS key, as usual. But instead of a\n plaintext copy of the data key, the response includes a copy of the data key encrypted under\n the public key from the attestation document (CiphertextForRecipient).\n For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide..

    \n

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

    \n

    \n How to use your data key\n

    \n

    We recommend that you use the following pattern to encrypt data locally in your\n application. You can write your own code or use a client-side encryption library, such as the\n Amazon Web Services Encryption SDK, the\n Amazon DynamoDB Encryption Client,\n or Amazon S3\n client-side encryption to do these tasks for you.

    \n

    To encrypt data outside of KMS:

    \n
      \n
    1. \n

      Use the GenerateDataKey operation to get a data key.

      \n
      2. \n
    2. \n

      Use the plaintext data key (in the Plaintext field of the response) to\n encrypt your data outside of KMS. Then erase the plaintext data key from memory.

      \n
      3. \n
    3. \n

      Store the encrypted data key (in the CiphertextBlob field of the\n response) with the encrypted data.

      \n
      4. \n
    \n

    To decrypt data outside of KMS:

    \n
      \n
    1. \n

      Use the Decrypt operation to decrypt the encrypted data key. The\n operation returns a plaintext copy of the data key.

      \n
      2. \n
    2. \n

      Use the plaintext data key to decrypt data outside of KMS, then erase the plaintext\n data key from memory.

      \n
      3. \n
    \n

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

    \n

    \n Required permissions: kms:GenerateDataKey (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Returns a unique symmetric data key for use outside of KMS. This operation returns a\n plaintext copy of the data key and a copy that is encrypted under a symmetric encryption KMS\n key that you specify. The bytes in the plaintext key are random; they are not related to the\n caller or the KMS key. You can use the plaintext key to encrypt your data outside of KMS and\n store the encrypted data key with the encrypted data.

    \n

    To generate a data key, specify the symmetric encryption KMS key that will be used to\n encrypt the data key. You cannot use an asymmetric KMS key to encrypt data keys. To get the\n type of your KMS key, use the DescribeKey operation.

    \n

    You must also specify the length of the data key. Use either the KeySpec or\n NumberOfBytes parameters (but not both). For 128-bit and 256-bit data keys, use\n the KeySpec parameter.

    \n

    To generate a 128-bit SM4 data key (China Regions only), specify a KeySpec\n value of AES_128 or a NumberOfBytes value of 16. The\n symmetric encryption key used in China Regions to encrypt your data key is an SM4 encryption\n key.

    \n

    To get only an encrypted copy of the data key, use GenerateDataKeyWithoutPlaintext. To generate an asymmetric data key pair, use\n the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext operation. To get a cryptographically secure\n random byte string, use GenerateRandom.

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

    \n GenerateDataKey also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call GenerateDataKey for an Amazon Web Services Nitro\n enclave, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient parameter\n to provide the attestation document for the enclave. GenerateDataKey returns a\n copy of the data key encrypted under the specified KMS key, as usual. But instead of a\n plaintext copy of the data key, the response includes a copy of the data key encrypted under\n the public key from the attestation document (CiphertextForRecipient).\n For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide..

    \n

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

    \n

    \n How to use your data key\n

    \n

    We recommend that you use the following pattern to encrypt data locally in your\n application. You can write your own code or use a client-side encryption library, such as the\n Amazon Web Services Encryption SDK, the\n Amazon DynamoDB Encryption Client,\n or Amazon S3\n client-side encryption to do these tasks for you.

    \n

    To encrypt data outside of KMS:

    \n
      \n
    1. \n

      Use the GenerateDataKey operation to get a data key.

      \n
      2. \n
    2. \n

      Use the plaintext data key (in the Plaintext field of the response) to\n encrypt your data outside of KMS. Then erase the plaintext data key from memory.

      \n
      3. \n
    3. \n

      Store the encrypted data key (in the CiphertextBlob field of the\n response) with the encrypted data.

      \n
      4. \n
    \n

    To decrypt data outside of KMS:

    \n
      \n
    1. \n

      Use the Decrypt operation to decrypt the encrypted data key. The\n operation returns a plaintext copy of the data key.

      \n
      2. \n
    2. \n

      Use the plaintext data key to decrypt data outside of KMS, then erase the plaintext\n data key from memory.

      \n
      3. \n
    \n

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

    \n

    \n Required permissions: kms:GenerateDataKey (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To generate a data key", @@ -2508,7 +2508,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns a unique asymmetric data key pair for use outside of KMS. This operation returns\n a plaintext public key, a plaintext private key, and a copy of the private key that is\n encrypted under the symmetric encryption KMS key you specify. You can use the data key pair to\n perform asymmetric cryptography and implement digital signatures outside of KMS. The bytes\n in the keys are random; they not related to the caller or to the KMS key that is used to\n encrypt the private key.

    \n

    You can use the public key that GenerateDataKeyPair returns to encrypt data\n or verify a signature outside of KMS. Then, store the encrypted private key with the data.\n When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.

    \n

    To generate a data key pair, you must specify a symmetric encryption KMS key to encrypt\n the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a\n custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.

    \n

    Use the KeyPairSpec parameter to choose an RSA or Elliptic Curve (ECC) data\n key pair. In China Regions, you can also choose an SM2 data key pair. KMS recommends that\n you use ECC key pairs for signing, and use RSA and SM2 key pairs for either encryption or\n signing, but not both. However, KMS cannot enforce any restrictions on the use of data key\n pairs outside of KMS.

    \n

    If you are using the data key pair to encrypt data, or for any operation where you don't\n immediately need a private key, consider using the GenerateDataKeyPairWithoutPlaintext operation.\n GenerateDataKeyPairWithoutPlaintext returns a plaintext public key and an\n encrypted private key, but omits the plaintext private key that you need only to decrypt\n ciphertext or sign a message. Later, when you need to decrypt the data or sign a message, use\n the Decrypt operation to decrypt the encrypted private key in the data key\n pair.

    \n

    \n GenerateDataKeyPair returns a unique data key pair for each request. The\n bytes in the keys are random; they are not related to the caller or the KMS key that is used\n to encrypt the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as\n specified in RFC 5280. The private\n key is a DER-encoded PKCS8 PrivateKeyInfo, as specified in RFC 5958.

    \n

    \n GenerateDataKeyPair also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call GenerateDataKeyPair for an Amazon Web Services\n Nitro enclave, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient\n parameter to provide the attestation document for the enclave.\n GenerateDataKeyPair returns the public data key and a copy of the private data\n key encrypted under the specified KMS key, as usual. But instead of a plaintext copy of the\n private data key (PrivateKeyPlaintext), the response includes a copy of the\n private data key encrypted under the public key from the attestation document\n (CiphertextForRecipient). For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide..

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateDataKeyPair (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Returns a unique asymmetric data key pair for use outside of KMS. This operation returns\n a plaintext public key, a plaintext private key, and a copy of the private key that is\n encrypted under the symmetric encryption KMS key you specify. You can use the data key pair to\n perform asymmetric cryptography and implement digital signatures outside of KMS. The bytes\n in the keys are random; they are not related to the caller or to the KMS key that is used to\n encrypt the private key.

    \n

    You can use the public key that GenerateDataKeyPair returns to encrypt data\n or verify a signature outside of KMS. Then, store the encrypted private key with the data.\n When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.

    \n

    To generate a data key pair, you must specify a symmetric encryption KMS key to encrypt\n the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a\n custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.

    \n

    Use the KeyPairSpec parameter to choose an RSA or Elliptic Curve (ECC) data\n key pair. In China Regions, you can also choose an SM2 data key pair. KMS recommends that\n you use ECC key pairs for signing, and use RSA and SM2 key pairs for either encryption or\n signing, but not both. However, KMS cannot enforce any restrictions on the use of data key\n pairs outside of KMS.

    \n

    If you are using the data key pair to encrypt data, or for any operation where you don't\n immediately need a private key, consider using the GenerateDataKeyPairWithoutPlaintext operation.\n GenerateDataKeyPairWithoutPlaintext returns a plaintext public key and an\n encrypted private key, but omits the plaintext private key that you need only to decrypt\n ciphertext or sign a message. Later, when you need to decrypt the data or sign a message, use\n the Decrypt operation to decrypt the encrypted private key in the data key\n pair.

    \n

    \n GenerateDataKeyPair returns a unique data key pair for each request. The\n bytes in the keys are random; they are not related to the caller or the KMS key that is used\n to encrypt the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as\n specified in RFC 5280. The private\n key is a DER-encoded PKCS8 PrivateKeyInfo, as specified in RFC 5958.

    \n

    \n GenerateDataKeyPair also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call GenerateDataKeyPair for an Amazon Web Services\n Nitro enclave, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient\n parameter to provide the attestation document for the enclave.\n GenerateDataKeyPair returns the public data key and a copy of the private data\n key encrypted under the specified KMS key, as usual. But instead of a plaintext copy of the\n private data key (PrivateKeyPlaintext), the response includes a copy of the\n private data key encrypted under the public key from the attestation document\n (CiphertextForRecipient). For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide..

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateDataKeyPair (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To generate an RSA key pair for encryption and decryption", @@ -2659,7 +2659,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns a unique asymmetric data key pair for use outside of KMS. This operation returns\n a plaintext public key and a copy of the private key that is encrypted under the symmetric\n encryption KMS key you specify. Unlike GenerateDataKeyPair, this operation\n does not return a plaintext private key. The bytes in the keys are random; they are not\n related to the caller or to the KMS key that is used to encrypt the private key.

    \n

    You can use the public key that GenerateDataKeyPairWithoutPlaintext returns\n to encrypt data or verify a signature outside of KMS. Then, store the encrypted private key\n with the data. When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.

    \n

    To generate a data key pair, you must specify a symmetric encryption KMS key to encrypt\n the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a\n custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.

    \n

    Use the KeyPairSpec parameter to choose an RSA or Elliptic Curve (ECC) data\n key pair. In China Regions, you can also choose an SM2 data key pair. KMS recommends that\n you use ECC key pairs for signing, and use RSA and SM2 key pairs for either encryption or\n signing, but not both. However, KMS cannot enforce any restrictions on the use of data key\n pairs outside of KMS.

    \n

    \n GenerateDataKeyPairWithoutPlaintext returns a unique data key pair for each\n request. The bytes in the key are not related to the caller or KMS key that is used to encrypt\n the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in\n RFC 5280.

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateDataKeyPairWithoutPlaintext (key\n policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Returns a unique asymmetric data key pair for use outside of KMS. This operation returns\n a plaintext public key and a copy of the private key that is encrypted under the symmetric\n encryption KMS key you specify. Unlike GenerateDataKeyPair, this operation\n does not return a plaintext private key. The bytes in the keys are random; they are not\n related to the caller or to the KMS key that is used to encrypt the private key.

    \n

    You can use the public key that GenerateDataKeyPairWithoutPlaintext returns\n to encrypt data or verify a signature outside of KMS. Then, store the encrypted private key\n with the data. When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.

    \n

    To generate a data key pair, you must specify a symmetric encryption KMS key to encrypt\n the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a\n custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.

    \n

    Use the KeyPairSpec parameter to choose an RSA or Elliptic Curve (ECC) data\n key pair. In China Regions, you can also choose an SM2 data key pair. KMS recommends that\n you use ECC key pairs for signing, and use RSA and SM2 key pairs for either encryption or\n signing, but not both. However, KMS cannot enforce any restrictions on the use of data key\n pairs outside of KMS.

    \n

    \n GenerateDataKeyPairWithoutPlaintext returns a unique data key pair for each\n request. The bytes in the key are not related to the caller or KMS key that is used to encrypt\n the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in\n RFC 5280.

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateDataKeyPairWithoutPlaintext (key\n policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To generate an asymmetric data key pair without a plaintext key", @@ -2871,7 +2871,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns a unique symmetric data key for use outside of KMS. This operation returns a\n data key that is encrypted under a symmetric encryption KMS key that you specify. The bytes in\n the key are random; they are not related to the caller or to the KMS key.

    \n

    \n GenerateDataKeyWithoutPlaintext is identical to the GenerateDataKey operation except that it does not return a plaintext copy of the\n data key.

    \n

    This operation is useful for systems that need to encrypt data at some point, but not\n immediately. When you need to encrypt the data, you call the Decrypt\n operation on the encrypted copy of the key.

    \n

    It's also useful in distributed systems with different levels of trust. For example, you\n might store encrypted data in containers. One component of your system creates new containers\n and stores an encrypted data key with each container. Then, a different component puts the\n data into the containers. That component first decrypts the data key, uses the plaintext data\n key to encrypt data, puts the encrypted data into the container, and then destroys the\n plaintext data key. In this system, the component that creates the containers never sees the\n plaintext data key.

    \n

    To request an asymmetric data key pair, use the GenerateDataKeyPair or\n GenerateDataKeyPairWithoutPlaintext operations.

    \n

    To generate a data key, you must specify the symmetric encryption KMS key that is used to\n encrypt the data key. You cannot use an asymmetric KMS key or a key in a custom key store to\n generate a data key. To get the type of your KMS key, use the DescribeKey\n operation.

    \n

    You must also specify the length of the data key. Use either the KeySpec or\n NumberOfBytes parameters (but not both). For 128-bit and 256-bit data keys, use\n the KeySpec parameter.

    \n

    To generate an SM4 data key (China Regions only), specify a KeySpec value of\n AES_128 or NumberOfBytes value of 16. The symmetric\n encryption key used in China Regions to encrypt your data key is an SM4 encryption key.

    \n

    If the operation succeeds, you will find the encrypted copy of the data key in the\n CiphertextBlob field.

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateDataKeyWithoutPlaintext (key\n policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Returns a unique symmetric data key for use outside of KMS. This operation returns a\n data key that is encrypted under a symmetric encryption KMS key that you specify. The bytes in\n the key are random; they are not related to the caller or to the KMS key.

    \n

    \n GenerateDataKeyWithoutPlaintext is identical to the GenerateDataKey operation except that it does not return a plaintext copy of the\n data key.

    \n

    This operation is useful for systems that need to encrypt data at some point, but not\n immediately. When you need to encrypt the data, you call the Decrypt\n operation on the encrypted copy of the key.

    \n

    It's also useful in distributed systems with different levels of trust. For example, you\n might store encrypted data in containers. One component of your system creates new containers\n and stores an encrypted data key with each container. Then, a different component puts the\n data into the containers. That component first decrypts the data key, uses the plaintext data\n key to encrypt data, puts the encrypted data into the container, and then destroys the\n plaintext data key. In this system, the component that creates the containers never sees the\n plaintext data key.

    \n

    To request an asymmetric data key pair, use the GenerateDataKeyPair or\n GenerateDataKeyPairWithoutPlaintext operations.

    \n

    To generate a data key, you must specify the symmetric encryption KMS key that is used to\n encrypt the data key. You cannot use an asymmetric KMS key or a key in a custom key store to\n generate a data key. To get the type of your KMS key, use the DescribeKey\n operation.

    \n

    You must also specify the length of the data key. Use either the KeySpec or\n NumberOfBytes parameters (but not both). For 128-bit and 256-bit data keys, use\n the KeySpec parameter.

    \n

    To generate an SM4 data key (China Regions only), specify a KeySpec value of\n AES_128 or NumberOfBytes value of 16. The symmetric\n encryption key used in China Regions to encrypt your data key is an SM4 encryption key.

    \n

    If the operation succeeds, you will find the encrypted copy of the data key in the\n CiphertextBlob field.

    \n

    You can use an optional encryption context to add additional security to the encryption\n operation. If you specify an EncryptionContext, you must specify the same\n encryption context (a case-sensitive exact match) when decrypting the encrypted data key.\n Otherwise, the request to decrypt fails with an InvalidCiphertextException. For more information, see Encryption Context in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateDataKeyWithoutPlaintext (key\n policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To generate an encrypted data key", @@ -2988,7 +2988,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Generates a hash-based message authentication code (HMAC) for a message using an HMAC KMS\n key and a MAC algorithm that the key supports. HMAC KMS keys and the HMAC algorithms that\n KMS uses conform to industry standards defined in RFC 2104.

    \n

    You can use value that GenerateMac returns in the VerifyMac operation to\n demonstrate that the original message has not changed. Also, because a secret key is used to\n create the hash, you can verify that the party that generated the hash has the required secret\n key. You can also use the raw result to implement HMAC-based algorithms such as key derivation\n functions. This operation is part of KMS support for HMAC KMS keys. For\n details, see HMAC keys in\n KMS in the \n Key Management Service Developer Guide\n .

    \n \n

    Best practices recommend that you limit the time during which any signing mechanism,\n including an HMAC, is effective. This deters an attack where the actor uses a signed message\n to establish validity repeatedly or long after the message is superseded. HMAC tags do not\n include a timestamp, but you can include a timestamp in the token or message to help you\n detect when its time to refresh the HMAC.

    \n     \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateMac (key policy)

    \n

    \n Related operations: VerifyMac\n

    ", + "smithy.api#documentation": "

    Generates a hash-based message authentication code (HMAC) for a message using an HMAC KMS\n key and a MAC algorithm that the key supports. HMAC KMS keys and the HMAC algorithms that\n KMS uses conform to industry standards defined in RFC 2104.

    \n

    You can use value that GenerateMac returns in the VerifyMac operation to\n demonstrate that the original message has not changed. Also, because a secret key is used to\n create the hash, you can verify that the party that generated the hash has the required secret\n key. You can also use the raw result to implement HMAC-based algorithms such as key derivation\n functions. This operation is part of KMS support for HMAC KMS keys. For\n details, see HMAC keys in\n KMS in the \n Key Management Service Developer Guide\n .

    \n \n

    Best practices recommend that you limit the time during which any signing mechanism,\n including an HMAC, is effective. This deters an attack where the actor uses a signed message\n to establish validity repeatedly or long after the message is superseded. HMAC tags do not\n include a timestamp, but you can include a timestamp in the token or message to help you\n detect when its time to refresh the HMAC.

    \n     \n

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

    \n

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

    \n

    \n Required permissions: kms:GenerateMac (key policy)

    \n

    \n Related operations: VerifyMac\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To generate an HMAC for a message", @@ -3100,7 +3100,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns a random byte string that is cryptographically secure.

    \n

    You must use the NumberOfBytes parameter to specify the length of the random\n byte string. There is no default value for string length.

    \n

    By default, the random byte string is generated in KMS. To generate the byte string in\n the CloudHSM cluster associated with an CloudHSM key store, use the CustomKeyStoreId\n parameter.

    \n

    \n GenerateRandom also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call GenerateRandom for a Nitro\n enclave, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient parameter\n to provide the attestation document for the enclave. Instead of plaintext bytes, the response\n includes the plaintext bytes encrypted under the public key from the attestation document\n (CiphertextForRecipient).For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    \n

    For more information about entropy and random number generation, see\n Key Management Service Cryptographic Details.

    \n

    \n Cross-account use: Not applicable.\n GenerateRandom does not use any account-specific resources, such as KMS\n keys.

    \n

    \n Required permissions: kms:GenerateRandom (IAM policy)

    ", + "smithy.api#documentation": "

    Returns a random byte string that is cryptographically secure.

    \n

    You must use the NumberOfBytes parameter to specify the length of the random\n byte string. There is no default value for string length.

    \n

    By default, the random byte string is generated in KMS. To generate the byte string in\n the CloudHSM cluster associated with an CloudHSM key store, use the CustomKeyStoreId\n parameter.

    \n

    \n GenerateRandom also supports Amazon Web Services Nitro Enclaves, which provide an\n isolated compute environment in Amazon EC2. To call GenerateRandom for a Nitro\n enclave, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK. Use the Recipient parameter\n to provide the attestation document for the enclave. Instead of plaintext bytes, the response\n includes the plaintext bytes encrypted under the public key from the attestation document\n (CiphertextForRecipient).For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    \n

    For more information about entropy and random number generation, see\n Key Management Service Cryptographic Details.

    \n

    \n Cross-account use: Not applicable.\n GenerateRandom does not use any account-specific resources, such as KMS\n keys.

    \n

    \n Required permissions: kms:GenerateRandom (IAM policy)

    \n

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

    ", "smithy.api#examples": [ { "title": "To generate random data", @@ -3187,7 +3187,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Gets a key policy attached to the specified KMS key.

    \n

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

    \n

    \n Required permissions: kms:GetKeyPolicy (key policy)

    \n

    \n Related operations: PutKeyPolicy\n

    ", + "smithy.api#documentation": "

    Gets a key policy attached to the specified KMS key.

    \n

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

    \n

    \n Required permissions: kms:GetKeyPolicy (key policy)

    \n

    \n Related operations: PutKeyPolicy\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To retrieve a key policy", @@ -3268,7 +3268,7 @@ } ], "traits": { - "smithy.api#documentation": "

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

    \n

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

    \n

    Automatic key rotation is supported only on symmetric encryption KMS keys.\n 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..

    \n

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

    \n \n

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

    \n     \n

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

    \n \n

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

    \n

    \n Required permissions: kms:GetKeyRotationStatus (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

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

    \n

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

    \n

    Automatic key rotation is supported only on symmetric encryption KMS keys.\n 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..

    \n

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

    \n \n

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

    \n     \n

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

    \n \n

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

    \n

    \n Required permissions: kms:GetKeyRotationStatus (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To retrieve the rotation status for a KMS key", @@ -3342,7 +3342,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns the public key and an import token you need to import or reimport key material for\n a KMS key.

    \n

    By default, KMS keys are created with key material that KMS generates. This operation\n supports Importing key\n material, an advanced feature that lets you generate and import the cryptographic\n key material for a KMS key. For more information about importing key material into KMS, see\n Importing key\n material in the Key Management Service Developer Guide.

    \n

    Before calling GetParametersForImport, use the CreateKey\n operation with an Origin value of EXTERNAL to create a KMS key with\n no key material. You can import key material for a symmetric encryption KMS key, HMAC KMS key,\n asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material\n into a multi-Region key of\n any supported type. However, you can't import key material into a KMS key in a custom key store. You can also use\n GetParametersForImport to get a public key and import token to reimport the original key\n material into a KMS key whose key material expired or was deleted.

    \n

    \n GetParametersForImport returns the items that you need to import your key\n material.

    \n \n

    The public key and its import token are permanently linked and must be used together. Each\n public key and import token set is valid for 24 hours. The expiration date and time appear in\n the ParametersValidTo field in the GetParametersForImport response.\n You cannot use an expired public key or import token in an ImportKeyMaterial\n request. If your key and token expire, send another GetParametersForImport\n request.

    \n

    \n GetParametersForImport requires the following information:

    \n \n

    You can use the same or a different public key spec and wrapping algorithm each time you\n import or reimport the same key material.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GetParametersForImport (key policy)

    \n

    \n Related operations:\n

    \n " + "smithy.api#documentation": "

    Returns the public key and an import token you need to import or reimport key material for\n a KMS key.

    \n

    By default, KMS keys are created with key material that KMS generates. This operation\n supports Importing key\n material, an advanced feature that lets you generate and import the cryptographic\n key material for a KMS key. For more information about importing key material into KMS, see\n Importing key\n material in the Key Management Service Developer Guide.

    \n

    Before calling GetParametersForImport, use the CreateKey\n operation with an Origin value of EXTERNAL to create a KMS key with\n no key material. You can import key material for a symmetric encryption KMS key, HMAC KMS key,\n asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material\n into a multi-Region key of\n any supported type. However, you can't import key material into a KMS key in a custom key\n store. You can also use GetParametersForImport to get a public key and\n import token to reimport\n the original key material into a KMS key whose key material expired or was\n deleted.

    \n

    \n GetParametersForImport returns the items that you need to import your key\n material.

    \n \n

    The public key and its import token are permanently linked and must be used together. Each\n public key and import token set is valid for 24 hours. The expiration date and time appear in\n the ParametersValidTo field in the GetParametersForImport response.\n You cannot use an expired public key or import token in an ImportKeyMaterial\n request. If your key and token expire, send another GetParametersForImport\n request.

    \n

    \n GetParametersForImport requires the following information:

    \n \n

    You can use the same or a different public key spec and wrapping algorithm each time you\n import or reimport the same key material.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GetParametersForImport (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    " } }, "com.amazonaws.kms#GetParametersForImportRequest": { @@ -3358,7 +3358,7 @@ "WrappingAlgorithm": { "target": "com.amazonaws.kms#AlgorithmSpec", "traits": { - "smithy.api#documentation": "

    The algorithm you will use with the RSA public key (PublicKey) in the\n response to protect your key material during import. For more information, see Select a wrapping algorithm in the Key Management Service Developer Guide.

    \n

    For RSA_AES wrapping algorithms, you encrypt your key material with an AES key that you\n generate, then encrypt your AES key with the RSA public key from KMS. For RSAES wrapping\n algorithms, you encrypt your key material directly with the RSA public key from KMS.

    \n

    The wrapping algorithms that you can use depend on the type of key material that you are\n importing. To import an RSA private key, you must use an RSA_AES wrapping algorithm.

    \n ", + "smithy.api#documentation": "

    The algorithm you will use with the RSA public key (PublicKey) in the\n response to protect your key material during import. For more information, see Select a wrapping algorithm in the Key Management Service Developer Guide.

    \n

    For RSA_AES wrapping algorithms, you encrypt your key material with an AES key that you\n generate, then encrypt your AES key with the RSA public key from KMS. For RSAES wrapping\n algorithms, you encrypt your key material directly with the RSA public key from KMS.

    \n

    The wrapping algorithms that you can use depend on the type of key material that you are\n importing. To import an RSA private key, you must use an RSA_AES wrapping algorithm.

    \n ", "smithy.api#required": {} } }, @@ -3447,7 +3447,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns the public key of an asymmetric KMS key. Unlike the private key of a asymmetric\n KMS key, which never leaves KMS unencrypted, callers with kms:GetPublicKey\n permission can download the public key of an asymmetric KMS key. You can share the public key\n to allow others to encrypt messages and verify signatures outside of KMS.\n For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    You do not need to download the public key. Instead, you can use the public key within\n KMS by calling the Encrypt, ReEncrypt, or Verify operations with the identifier of an asymmetric KMS key. When you use the\n public key within KMS, you benefit from the authentication, authorization, and logging that\n are part of every KMS operation. You also reduce of risk of encrypting data that cannot be\n decrypted. These features are not effective outside of KMS.

    \n

    To help you use the public key safely outside of KMS, GetPublicKey returns\n important information about the public key in the response, including:

    \n \n

    Although KMS cannot enforce these restrictions on external operations, it is crucial\n that you use this information to prevent the public key from being used improperly. For\n example, you can prevent a public signing key from being used encrypt data, or prevent a\n public key from being used with an encryption algorithm that is not supported by KMS. You\n can also avoid errors, such as using the wrong signing algorithm in a verification\n operation.

    \n

    To verify a signature outside of KMS with an SM2 public key (China Regions only), you\n must specify the distinguishing ID. By default, KMS uses 1234567812345678 as\n the distinguishing ID. For more information, see Offline\n verification with SM2 key pairs.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GetPublicKey (key policy)

    \n

    \n Related operations: CreateKey\n

    ", + "smithy.api#documentation": "

    Returns the public key of an asymmetric KMS key. Unlike the private key of a asymmetric\n KMS key, which never leaves KMS unencrypted, callers with kms:GetPublicKey\n permission can download the public key of an asymmetric KMS key. You can share the public key\n to allow others to encrypt messages and verify signatures outside of KMS.\n For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    You do not need to download the public key. Instead, you can use the public key within\n KMS by calling the Encrypt, ReEncrypt, or Verify operations with the identifier of an asymmetric KMS key. When you use the\n public key within KMS, you benefit from the authentication, authorization, and logging that\n are part of every KMS operation. You also reduce of risk of encrypting data that cannot be\n decrypted. These features are not effective outside of KMS.

    \n

    To help you use the public key safely outside of KMS, GetPublicKey returns\n important information about the public key in the response, including:

    \n \n

    Although KMS cannot enforce these restrictions on external operations, it is crucial\n that you use this information to prevent the public key from being used improperly. For\n example, you can prevent a public signing key from being used encrypt data, or prevent a\n public key from being used with an encryption algorithm that is not supported by KMS. You\n can also avoid errors, such as using the wrong signing algorithm in a verification\n operation.

    \n

    To verify a signature outside of KMS with an SM2 public key (China Regions only), you\n must specify the distinguishing ID. By default, KMS uses 1234567812345678 as\n the distinguishing ID. For more information, see Offline\n verification with SM2 key pairs.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:GetPublicKey (key policy)

    \n

    \n Related operations: CreateKey\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To download the public key of an asymmetric KMS key", @@ -3816,7 +3816,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Imports or reimports key material into an existing KMS key that was created without key\n material. ImportKeyMaterial also sets the expiration model and expiration date of\n the imported key material.

    \n

    By default, KMS keys are created with key material that KMS generates. This operation\n supports Importing key\n material, an advanced feature that lets you generate and import the cryptographic\n key material for a KMS key. For more information about importing key material into KMS, see\n Importing key\n material in the Key Management Service Developer Guide.

    \n

    After you successfully import key material into a KMS key, you can reimport\n the same key material into that KMS key, but you cannot import different key\n material. You might reimport key material to replace key material that expired or key material\n that you deleted. You might also reimport key material to change the expiration model or\n expiration date of the key material. Before reimporting key material, if necessary, call DeleteImportedKeyMaterial to delete the current imported key material.

    \n

    Each time you import key material into KMS, you can determine whether\n (ExpirationModel) and when (ValidTo) the key material expires. To\n change the expiration of your key material, you must import it again, either by calling\n ImportKeyMaterial or using the import features of the KMS console.

    \n

    Before calling ImportKeyMaterial:

    \n \n

    Then, in an ImportKeyMaterial request, you submit your encrypted key\n material and import token. When calling this operation, you must specify the following\n values:

    \n \n

    When this operation is successful, the key state of the KMS key changes from\n PendingImport to Enabled, and you can use the KMS key in\n cryptographic operations.

    \n

    If this operation fails, use the exception to help determine the problem. If the error is\n related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key\n and repeat the import procedure. For help, see How To Import Key\n Material in the Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:ImportKeyMaterial (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Imports or reimports key material into an existing KMS key that was created without key\n material. ImportKeyMaterial also sets the expiration model and expiration date of\n the imported key material.

    \n

    By default, KMS keys are created with key material that KMS generates. This operation\n supports Importing key\n material, an advanced feature that lets you generate and import the cryptographic\n key material for a KMS key. For more information about importing key material into KMS, see\n Importing key\n material in the Key Management Service Developer Guide.

    \n

    After you successfully import key material into a KMS key, you can reimport\n the same key material into that KMS key, but you cannot import different key\n material. You might reimport key material to replace key material that expired or key material\n that you deleted. You might also reimport key material to change the expiration model or\n expiration date of the key material. Before reimporting key material, if necessary, call DeleteImportedKeyMaterial to delete the current imported key material.

    \n

    Each time you import key material into KMS, you can determine whether\n (ExpirationModel) and when (ValidTo) the key material expires. To\n change the expiration of your key material, you must import it again, either by calling\n ImportKeyMaterial or using the import features of the KMS console.

    \n

    Before calling ImportKeyMaterial:

    \n \n

    Then, in an ImportKeyMaterial request, you submit your encrypted key\n material and import token. When calling this operation, you must specify the following\n values:

    \n \n

    When this operation is successful, the key state of the KMS key changes from\n PendingImport to Enabled, and you can use the KMS key in\n cryptographic operations.

    \n

    If this operation fails, use the exception to help determine the problem. If the error is\n related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key\n and repeat the import procedure. For help, see How To Import Key\n Material in the Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:ImportKeyMaterial (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To import key material into a KMS key", @@ -4592,7 +4592,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Gets a list of aliases in the caller's Amazon Web Services account and region. For more information\n about aliases, see CreateAlias.

    \n

    By default, the ListAliases operation returns all aliases in the account and\n region. To get only the aliases associated with a particular KMS key, use the\n KeyId parameter.

    \n

    The ListAliases response can include aliases that you created and associated\n with your customer managed keys, and aliases that Amazon Web Services created and associated with Amazon Web Services\n managed keys in your account. You can recognize Amazon Web Services aliases because their names have the\n format aws/, such as aws/dynamodb.

    \n

    The response might also include aliases that have no TargetKeyId field. These\n are predefined aliases that Amazon Web Services has created but has not yet associated with a KMS key.\n Aliases that Amazon Web Services creates in your account, including predefined aliases, do not count against\n your KMS aliases\n quota.

    \n

    \n Cross-account use: No. ListAliases does not\n return aliases in other Amazon Web Services accounts.

    \n

    \n Required permissions: kms:ListAliases (IAM policy)

    \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Gets a list of aliases in the caller's Amazon Web Services account and region. For more information\n about aliases, see CreateAlias.

    \n

    By default, the ListAliases operation returns all aliases in the account and\n region. To get only the aliases associated with a particular KMS key, use the\n KeyId parameter.

    \n

    The ListAliases response can include aliases that you created and associated\n with your customer managed keys, and aliases that Amazon Web Services created and associated with Amazon Web Services\n managed keys in your account. You can recognize Amazon Web Services aliases because their names have the\n format aws/, such as aws/dynamodb.

    \n

    The response might also include aliases that have no TargetKeyId field. These\n are predefined aliases that Amazon Web Services has created but has not yet associated with a KMS key.\n Aliases that Amazon Web Services creates in your account, including predefined aliases, do not count against\n your KMS aliases\n quota.

    \n

    \n Cross-account use: No. ListAliases does not\n return aliases in other Amazon Web Services accounts.

    \n

    \n Required permissions: kms:ListAliases (IAM policy)

    \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To list aliases", @@ -4737,7 +4737,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Gets a list of all grants for the specified KMS key.

    \n

    You must specify the KMS key in all requests. You can filter the grant list by grant ID or\n grantee principal.

    \n

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

    \n \n

    The GranteePrincipal field in the ListGrants response usually contains the\n user or role designated as the grantee principal in the grant. However, when the grantee\n principal in the grant is an Amazon Web Services service, the GranteePrincipal field contains\n the service\n principal, which might represent several different grantee principals.

    \n     \n

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

    \n

    \n Required permissions: kms:ListGrants (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Gets a list of all grants for the specified KMS key.

    \n

    You must specify the KMS key in all requests. You can filter the grant list by grant ID or\n grantee principal.

    \n

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

    \n \n

    The GranteePrincipal field in the ListGrants response usually contains the\n user or role designated as the grantee principal in the grant. However, when the grantee\n principal in the grant is an Amazon Web Services service, the GranteePrincipal field contains\n the service\n principal, which might represent several different grantee principals.

    \n     \n

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

    \n

    \n Required permissions: kms:ListGrants (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#paginated": { "inputToken": "Marker", "outputToken": "NextMarker", @@ -4835,7 +4835,7 @@ } ], "traits": { - "smithy.api#documentation": "

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

    \n

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

    \n

    \n Required permissions: kms:ListKeyPolicies (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

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

    \n

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

    \n

    \n Required permissions: kms:ListKeyPolicies (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To list key policies for a KMS key", @@ -4931,7 +4931,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Gets a list of all KMS keys in the caller's Amazon Web Services account and Region.

    \n

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

    \n

    \n Required permissions: kms:ListKeys (IAM policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Gets a list of all KMS keys in the caller's Amazon Web Services account and Region.

    \n

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

    \n

    \n Required permissions: kms:ListKeys (IAM policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To list KMS keys", @@ -5049,7 +5049,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns all tags on the specified KMS key.

    \n

    For general information about tags, including the format and syntax, see Tagging Amazon Web Services resources in\n the Amazon Web Services General Reference. For information about using\n tags in KMS, see Tagging\n keys.

    \n

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

    \n

    \n Required permissions: kms:ListResourceTags (key policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Returns all tags on the specified KMS key.

    \n

    For general information about tags, including the format and syntax, see Tagging Amazon Web Services resources in\n the Amazon Web Services General Reference. For information about using\n tags in KMS, see Tagging\n keys.

    \n

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

    \n

    \n Required permissions: kms:ListResourceTags (key policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To list tags for a KMS key", @@ -5164,7 +5164,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Returns information about all grants in the Amazon Web Services account and Region that have the\n specified retiring principal.

    \n

    You can specify any principal in your Amazon Web Services account. The grants that are returned include\n grants for KMS keys in your Amazon Web Services account and other Amazon Web Services accounts. You might use this\n operation to determine which grants you may retire. To retire a grant, use the RetireGrant operation.

    \n

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

    \n

    \n Cross-account use: You must specify a principal in your\n Amazon Web Services account. However, this operation can return grants in any Amazon Web Services account. You do not need\n kms:ListRetirableGrants permission (or any other additional permission) in any\n Amazon Web Services account other than your own.

    \n

    \n Required permissions: kms:ListRetirableGrants (IAM policy) in your\n Amazon Web Services account.

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Returns information about all grants in the Amazon Web Services account and Region that have the\n specified retiring principal.

    \n

    You can specify any principal in your Amazon Web Services account. The grants that are returned include\n grants for KMS keys in your Amazon Web Services account and other Amazon Web Services accounts. You might use this\n operation to determine which grants you may retire. To retire a grant, use the RetireGrant operation.

    \n

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

    \n

    \n Cross-account use: You must specify a principal in your\n Amazon Web Services account. This operation returns a list of grants where the retiring principal specified\n in the ListRetirableGrants request is the same retiring principal on the grant.\n This can include grants on KMS keys owned by other Amazon Web Services accounts, but you do not need\n kms:ListRetirableGrants permission (or any other additional permission) in any\n Amazon Web Services account other than your own.

    \n

    \n Required permissions: kms:ListRetirableGrants (IAM policy) in your\n Amazon Web Services account.

    \n \n

    KMS authorizes ListRetirableGrants requests by evaluating the caller\n account's kms:ListRetirableGrants permissions. The authorized resource in\n ListRetirableGrants calls is the retiring principal specified in the request.\n KMS does not evaluate the caller's permissions to verify their access to any KMS keys or\n grants that might be returned by the ListRetirableGrants call.

    \n     \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#paginated": { "inputToken": "Marker", "outputToken": "NextMarker", @@ -5505,7 +5505,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Attaches a key policy to the specified KMS key.

    \n

    For more information about key policies, see Key Policies in the Key Management Service Developer Guide.\n For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the \n Identity and Access Management User Guide\n . For examples of adding a key policy in multiple programming languages,\n see Setting a key policy in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:PutKeyPolicy (key policy)

    \n

    \n Related operations: GetKeyPolicy\n

    ", + "smithy.api#documentation": "

    Attaches a key policy to the specified KMS key.

    \n

    For more information about key policies, see Key Policies in the Key Management Service Developer Guide.\n For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the \n Identity and Access Management User Guide\n . For examples of adding a key policy in multiple programming languages,\n see Setting a key policy in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Required permissions: kms:PutKeyPolicy (key policy)

    \n

    \n Related operations: GetKeyPolicy\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To attach a key policy to a KMS key", @@ -5547,7 +5547,7 @@ "target": "com.amazonaws.kms#BooleanType", "traits": { "smithy.api#default": false, - "smithy.api#documentation": "

    Skips (\"bypasses\") the key policy lockout safety check. The default value is false.

    \n \n

    Setting this value to true increases the risk that the KMS key becomes unmanageable. Do\n not set this value to true indiscriminately.

    \n

    For more information, see Default key policy in the Key Management Service Developer Guide.

    \n     \n

    Use this parameter only when you intend to prevent the principal that is making the\n request from making a subsequent PutKeyPolicy request on the KMS key.

    " + "smithy.api#documentation": "

    Skips (\"bypasses\") the key policy lockout safety check. The default value is false.

    \n \n

    Setting this value to true increases the risk that the KMS key becomes unmanageable. Do\n not set this value to true indiscriminately.

    \n

    For more information, see Default key policy in the Key Management Service Developer Guide.

    \n     \n

    Use this parameter only when you intend to prevent the principal that is making the\n request from making a subsequent PutKeyPolicy\n request on the KMS key.

    " } } }, @@ -5599,7 +5599,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Decrypts ciphertext and then reencrypts it entirely within KMS. You can use this\n operation to change the KMS key under which data is encrypted, such as when you manually\n rotate a KMS key or change the KMS key that protects a ciphertext. You can also use\n it to reencrypt ciphertext under the same KMS key, such as to change the encryption\n context of a ciphertext.

    \n

    The ReEncrypt operation can decrypt ciphertext that was encrypted by using a\n KMS key in an KMS operation, such as Encrypt or GenerateDataKey. It can also decrypt ciphertext that was encrypted by using the\n public key of an asymmetric KMS key\n outside of KMS. However, it cannot decrypt ciphertext produced by other libraries, such as\n the Amazon Web Services Encryption SDK or\n Amazon S3\n client-side encryption. These libraries return a ciphertext format that is\n incompatible with KMS.

    \n

    When you use the ReEncrypt operation, you need to provide information for the\n decrypt operation and the subsequent encrypt operation.

    \n \n

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

    \n

    \n Cross-account use: Yes. The source KMS key and\n destination KMS key can be in different Amazon Web Services accounts. Either or both KMS keys can be in a\n different account than the caller. To specify a KMS key in a different account, you must use\n its key ARN or alias ARN.

    \n

    \n Required permissions:

    \n \n

    To permit reencryption from or to a KMS key, include the \"kms:ReEncrypt*\"\n permission in your key policy. This permission is\n automatically included in the key policy when you use the console to create a KMS key. But you\n must include it manually when you create a KMS key programmatically or when you use the PutKeyPolicy operation to set a key policy.

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Decrypts ciphertext and then reencrypts it entirely within KMS. You can use this\n operation to change the KMS key under which data is encrypted, such as when you manually\n rotate a KMS key or change the KMS key that protects a ciphertext. You can also use\n it to reencrypt ciphertext under the same KMS key, such as to change the encryption\n context of a ciphertext.

    \n

    The ReEncrypt operation can decrypt ciphertext that was encrypted by using a\n KMS key in an KMS operation, such as Encrypt or GenerateDataKey. It can also decrypt ciphertext that was encrypted by using the\n public key of an asymmetric KMS key\n outside of KMS. However, it cannot decrypt ciphertext produced by other libraries, such as\n the Amazon Web Services Encryption SDK or\n Amazon S3\n client-side encryption. These libraries return a ciphertext format that is\n incompatible with KMS.

    \n

    When you use the ReEncrypt operation, you need to provide information for the\n decrypt operation and the subsequent encrypt operation.

    \n \n

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

    \n

    \n Cross-account use: Yes. The source KMS key and\n destination KMS key can be in different Amazon Web Services accounts. Either or both KMS keys can be in a\n different account than the caller. To specify a KMS key in a different account, you must use\n its key ARN or alias ARN.

    \n

    \n Required permissions:

    \n \n

    To permit reencryption from or to a KMS key, include the \"kms:ReEncrypt*\"\n permission in your key policy. This permission is\n automatically included in the key policy when you use the console to create a KMS key. But you\n must include it manually when you create a KMS key programmatically or when you use the PutKeyPolicy operation to set a key policy.

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To reencrypt data", @@ -5790,7 +5790,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Replicates a multi-Region key into the specified Region. This operation creates a\n multi-Region replica key based on a multi-Region primary key in a different Region of the same\n Amazon Web Services partition. You can create multiple replicas of a primary key, but each must be in a\n different Region. To create a multi-Region primary key, use the CreateKey\n operation.

    \n

    This operation supports multi-Region keys, an KMS feature that lets you create multiple\n interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key\n material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt\n it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    A replica key is a fully-functional KMS key that can be used\n independently of its primary and peer replica keys. A primary key and its replica keys share\n properties that make them interoperable. They have the same key ID and key material. They also\n have the same key\n spec, key\n usage, key\n material origin, and automatic key rotation status. KMS automatically synchronizes these shared\n properties among related multi-Region keys. All other properties of a replica key can differ,\n including its key\n policy, tags, aliases, and Key states of KMS keys. KMS pricing and quotas for KMS keys apply to each\n primary key and replica key.

    \n

    When this operation completes, the new replica key has a transient key state of\n Creating. This key state changes to Enabled (or\n PendingImport) after a few seconds when the process of creating the new replica\n key is complete. While the key state is Creating, you can manage key, but you\n cannot yet use it in cryptographic operations. If you are creating and using the replica key\n programmatically, retry on KMSInvalidStateException or call\n DescribeKey to check its KeyState value before using it. For\n details about the Creating key state, see Key states of KMS keys in the\n Key Management Service Developer Guide.

    \n

    You cannot create more than one replica of a primary key in any Region. If the Region\n already includes a replica of the key you're trying to replicate, ReplicateKey\n returns an AlreadyExistsException error. If the key state of the existing replica\n is PendingDeletion, you can cancel the scheduled key deletion (CancelKeyDeletion) or wait for the key to be deleted. The new replica key you\n create will have the same shared\n properties as the original replica key.

    \n

    The CloudTrail log of a ReplicateKey operation records a\n ReplicateKey operation in the primary key's Region and a CreateKey operation in the replica key's Region.

    \n

    If you replicate a multi-Region primary key with imported key material, the replica key is\n created with no key material. You must import the same key material that you imported into the\n primary key. For details, see Importing key material into multi-Region keys in the Key Management Service Developer Guide.

    \n

    To convert a replica key to a primary key, use the UpdatePrimaryRegion\n operation.

    \n \n

    \n ReplicateKey uses different default values for the KeyPolicy\n and Tags parameters than those used in the KMS console. For details, see the\n parameter descriptions.

    \n     \n

    \n Cross-account use: No. You cannot use this operation to\n create a replica key in a different Amazon Web Services account.

    \n

    \n Required permissions:

    \n \n

    \n Related operations\n

    \n ", + "smithy.api#documentation": "

    Replicates a multi-Region key into the specified Region. This operation creates a\n multi-Region replica key based on a multi-Region primary key in a different Region of the same\n Amazon Web Services partition. You can create multiple replicas of a primary key, but each must be in a\n different Region. To create a multi-Region primary key, use the CreateKey\n operation.

    \n

    This operation supports multi-Region keys, an KMS feature that lets you create multiple\n interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key\n material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt\n it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    A replica key is a fully-functional KMS key that can be used\n independently of its primary and peer replica keys. A primary key and its replica keys share\n properties that make them interoperable. They have the same key ID and key material. They also\n have the same key\n spec, key\n usage, key\n material origin, and automatic key rotation status. KMS automatically synchronizes these shared\n properties among related multi-Region keys. All other properties of a replica key can differ,\n including its key\n policy, tags, aliases, and Key states of KMS keys. KMS pricing and quotas for KMS keys apply to each\n primary key and replica key.

    \n

    When this operation completes, the new replica key has a transient key state of\n Creating. This key state changes to Enabled (or\n PendingImport) after a few seconds when the process of creating the new replica\n key is complete. While the key state is Creating, you can manage key, but you\n cannot yet use it in cryptographic operations. If you are creating and using the replica key\n programmatically, retry on KMSInvalidStateException or call\n DescribeKey to check its KeyState value before using it. For\n details about the Creating key state, see Key states of KMS keys in the\n Key Management Service Developer Guide.

    \n

    You cannot create more than one replica of a primary key in any Region. If the Region\n already includes a replica of the key you're trying to replicate, ReplicateKey\n returns an AlreadyExistsException error. If the key state of the existing replica\n is PendingDeletion, you can cancel the scheduled key deletion (CancelKeyDeletion) or wait for the key to be deleted. The new replica key you\n create will have the same shared\n properties as the original replica key.

    \n

    The CloudTrail log of a ReplicateKey operation records a\n ReplicateKey operation in the primary key's Region and a CreateKey operation in the replica key's Region.

    \n

    If you replicate a multi-Region primary key with imported key material, the replica key is\n created with no key material. You must import the same key material that you imported into the\n primary key. For details, see Importing key material into multi-Region keys in the Key Management Service Developer Guide.

    \n

    To convert a replica key to a primary key, use the UpdatePrimaryRegion\n operation.

    \n \n

    \n ReplicateKey uses different default values for the KeyPolicy\n and Tags parameters than those used in the KMS console. For details, see the\n parameter descriptions.

    \n     \n

    \n Cross-account use: No. You cannot use this operation to\n create a replica key in a different Amazon Web Services account.

    \n

    \n Required permissions:

    \n \n

    \n Related operations\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To replicate a multi-Region key in a different AWS Region", @@ -5817,7 +5817,7 @@ }, "AWSAccountId": "111122223333", "Arn": "arn:aws:kms:us-west-2:111122223333:key/mrk-1234abcd12ab34cd56ef1234567890ab", - "CreationDate": 1607472987.918, + "CreationDate": 1.607472987918e9, "Description": "", "Enabled": true, "KeyId": "mrk-1234abcd12ab34cd56ef1234567890ab", @@ -5862,7 +5862,7 @@ "target": "com.amazonaws.kms#BooleanType", "traits": { "smithy.api#default": false, - "smithy.api#documentation": "

    Skips (\"bypasses\") the key policy lockout safety check. The default value is false.

    \n \n

    Setting this value to true increases the risk that the KMS key becomes unmanageable. Do\n not set this value to true indiscriminately.

    \n

    For more information, see Default key policy in the Key Management Service Developer Guide.

    \n     \n

    Use this parameter only when you intend to prevent the principal that is making the\n request from making a subsequent PutKeyPolicy request on the KMS key.

    " + "smithy.api#documentation": "

    Skips (\"bypasses\") the key policy lockout safety check. The default value is false.

    \n \n

    Setting this value to true increases the risk that the KMS key becomes unmanageable. Do\n not set this value to true indiscriminately.

    \n

    For more information, see Default key policy in the Key Management Service Developer Guide.

    \n     \n

    Use this parameter only when you intend to prevent the principal that is making the\n request from making a subsequent PutKeyPolicy\n request on the KMS key.

    " } }, "Description": { @@ -5943,7 +5943,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Deletes a grant. Typically, you retire a grant when you no longer need its permissions. To\n identify the grant to retire, use a grant token, or both the grant ID and a\n key identifier (key ID or key ARN) of the KMS key. The CreateGrant operation\n returns both values.

    \n

    This operation can be called by the retiring principal for a grant,\n by the grantee principal if the grant allows the RetireGrant\n operation, and by the Amazon Web Services account in which the grant is created. It can also be called by\n principals to whom permission for retiring a grant is delegated. For details, see Retiring and revoking\n grants in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Cross-account use: Yes. You can retire a grant on a KMS\n key in a different Amazon Web Services account.

    \n

    \n Required permissions::Permission to retire a grant is\n determined primarily by the grant. For details, see Retiring and revoking grants in\n the Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Deletes a grant. Typically, you retire a grant when you no longer need its permissions. To\n identify the grant to retire, use a grant token, or both the grant ID and a\n key identifier (key ID or key ARN) of the KMS key. The CreateGrant operation\n returns both values.

    \n

    This operation can be called by the retiring principal for a grant,\n by the grantee principal if the grant allows the RetireGrant\n operation, and by the Amazon Web Services account in which the grant is created. It can also be called by\n principals to whom permission for retiring a grant is delegated. For details, see Retiring and revoking\n grants in the Key Management Service Developer Guide.

    \n

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

    \n

    \n Cross-account use: Yes. You can retire a grant on a KMS\n key in a different Amazon Web Services account.

    \n

    \n Required permissions: Permission to retire a grant is\n determined primarily by the grant. For details, see Retiring and revoking grants in\n the Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To retire a grant", @@ -6020,7 +6020,7 @@ } ], "traits": { - "smithy.api#documentation": "

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

    \n

    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\n the \n Key Management Service Developer Guide\n .

    \n

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

    \n

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

    \n

    \n Required permissions: kms:RevokeGrant (key policy).

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

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

    \n

    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\n the \n Key Management Service Developer Guide\n .

    \n

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

    \n

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

    \n

    \n Required permissions: kms:RevokeGrant (key policy).

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To revoke a grant", @@ -6087,7 +6087,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Schedules the deletion of a KMS key. By default, KMS applies a waiting period of 30\n days, but you can specify a waiting period of 7-30 days. When this operation is successful,\n the key state of the KMS key changes to PendingDeletion and the key can't be used\n in any cryptographic operations. It remains in this state for the duration of the waiting\n period. Before the waiting period ends, you can use CancelKeyDeletion to\n cancel the deletion of the KMS key. After the waiting period ends, KMS deletes the KMS key,\n its key material, and all KMS data associated with it, including all aliases that refer to\n it.

    \n \n

    Deleting a KMS key is a destructive and potentially dangerous operation. When a KMS key\n is deleted, all data that was encrypted under the KMS key is unrecoverable. (The only\n exception is a multi-Region replica\n key, or an asymmetric or HMAC KMS\n key with imported key material.) To prevent the use of a KMS key without deleting\n it, use DisableKey.

    \n     \n

    You can schedule the deletion of a multi-Region primary key and its replica keys at any\n time. However, KMS will not delete a multi-Region primary key with existing replica keys. If\n you schedule the deletion of a primary key with replicas, its key state changes to\n PendingReplicaDeletion and it cannot be replicated or used in cryptographic\n operations. This status can continue indefinitely. When the last of its replicas keys is\n deleted (not just scheduled), the key state of the primary key changes to\n PendingDeletion and its waiting period (PendingWindowInDays)\n begins. For details, see Deleting multi-Region keys in the\n Key Management Service Developer Guide.

    \n

    When KMS deletes\n a KMS key from an CloudHSM key store, it makes a best effort to delete the associated\n key material from the associated CloudHSM cluster. However, you might need to manually delete\n the orphaned key material from the cluster and its backups. Deleting a KMS key from an\n external key store has no effect on the associated external key. However, for both\n types of custom key stores, deleting a KMS key is destructive and irreversible. You cannot\n decrypt ciphertext encrypted under the KMS key by using only its associated external key or\n CloudHSM key. Also, you cannot recreate a KMS key in an external key store by creating a new KMS\n key with the same key material.

    \n

    For more information about scheduling a KMS key for deletion, see Deleting KMS keys in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:ScheduleKeyDeletion (key\n policy)

    \n

    \n Related operations\n

    \n " + "smithy.api#documentation": "

    Schedules the deletion of a KMS key. By default, KMS applies a waiting period of 30\n days, but you can specify a waiting period of 7-30 days. When this operation is successful,\n the key state of the KMS key changes to PendingDeletion and the key can't be used\n in any cryptographic operations. It remains in this state for the duration of the waiting\n period. Before the waiting period ends, you can use CancelKeyDeletion to\n cancel the deletion of the KMS key. After the waiting period ends, KMS deletes the KMS key,\n its key material, and all KMS data associated with it, including all aliases that refer to\n it.

    \n \n

    Deleting a KMS key is a destructive and potentially dangerous operation. When a KMS key\n is deleted, all data that was encrypted under the KMS key is unrecoverable. (The only\n exception is a multi-Region replica key, or an asymmetric or HMAC KMS\n key with imported key material.) To prevent the use of a KMS key without deleting\n it, use DisableKey.

    \n     \n

    You can schedule the deletion of a multi-Region primary key and its replica keys at any\n time. However, KMS will not delete a multi-Region primary key with existing replica keys. If\n you schedule the deletion of a primary key with replicas, its key state changes to\n PendingReplicaDeletion and it cannot be replicated or used in cryptographic\n operations. This status can continue indefinitely. When the last of its replicas keys is\n deleted (not just scheduled), the key state of the primary key changes to\n PendingDeletion and its waiting period (PendingWindowInDays)\n begins. For details, see Deleting multi-Region keys in the\n Key Management Service Developer Guide.

    \n

    When KMS deletes\n a KMS key from an CloudHSM key store, it makes a best effort to delete the associated\n key material from the associated CloudHSM cluster. However, you might need to manually delete\n the orphaned key material from the cluster and its backups. Deleting a KMS key from an\n external key store has no effect on the associated external key. However, for both\n types of custom key stores, deleting a KMS key is destructive and irreversible. You cannot\n decrypt ciphertext encrypted under the KMS key by using only its associated external key or\n CloudHSM key. Also, you cannot recreate a KMS key in an external key store by creating a new KMS\n key with the same key material.

    \n

    For more information about scheduling a KMS key for deletion, see Deleting KMS keys in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:ScheduleKeyDeletion (key\n policy)

    \n

    \n Related operations\n

    \n \n

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

    " } }, "com.amazonaws.kms#ScheduleKeyDeletionRequest": { @@ -6181,7 +6181,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Creates a digital\n signature for a message or message digest by using the private key in an asymmetric\n signing KMS key. To verify the signature, use the Verify operation, or use\n the public key in the same asymmetric KMS key outside of KMS. For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    Digital signatures are generated and verified by using asymmetric key pair, such as an RSA\n or ECC pair that is represented by an asymmetric KMS key. The key owner (or an authorized\n user) uses their private key to sign a message. Anyone with the public key can verify that the\n message was signed with that particular private key and that the message hasn't changed since\n it was signed.

    \n

    To use the Sign operation, provide the following information:

    \n \n \n

    When signing a message, be sure to record the KMS key and the signing algorithm. This\n information is required to verify the signature.

    \n     \n \n

    Best practices recommend that you limit the time during which any signature is\n effective. This deters an attack where the actor uses a signed message to establish validity\n repeatedly or long after the message is superseded. Signatures do not include a timestamp,\n but you can include a timestamp in the signed message to help you detect when its time to\n refresh the signature.

    \n     \n

    To verify the signature that this operation generates, use the Verify\n operation. Or use the GetPublicKey operation to download the public key and\n then use the public key to verify the signature outside of KMS.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:Sign (key policy)

    \n

    \n Related operations: Verify\n

    ", + "smithy.api#documentation": "

    Creates a digital\n signature for a message or message digest by using the private key in an asymmetric\n signing KMS key. To verify the signature, use the Verify operation, or use\n the public key in the same asymmetric KMS key outside of KMS. For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    Digital signatures are generated and verified by using asymmetric key pair, such as an RSA\n or ECC pair that is represented by an asymmetric KMS key. The key owner (or an authorized\n user) uses their private key to sign a message. Anyone with the public key can verify that the\n message was signed with that particular private key and that the message hasn't changed since\n it was signed.

    \n

    To use the Sign operation, provide the following information:

    \n \n \n

    When signing a message, be sure to record the KMS key and the signing algorithm. This\n information is required to verify the signature.

    \n     \n \n

    Best practices recommend that you limit the time during which any signature is\n effective. This deters an attack where the actor uses a signed message to establish validity\n repeatedly or long after the message is superseded. Signatures do not include a timestamp,\n but you can include a timestamp in the signed message to help you detect when its time to\n refresh the signature.

    \n     \n

    To verify the signature that this operation generates, use the Verify\n operation. Or use the GetPublicKey operation to download the public key and\n then use the public key to verify the signature outside of KMS.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:Sign (key policy)

    \n

    \n Related operations: Verify\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To digitally sign a message with an asymmetric KMS key.", @@ -6434,7 +6434,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Adds or edits tags on a customer managed key.

    \n \n

    Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    Each tag consists of a tag key and a tag value, both of which are case-sensitive strings.\n The tag value can be an empty (null) string. To add a tag, specify a new tag key and a tag\n value. To edit a tag, specify an existing tag key and a new tag value.

    \n

    You can use this operation to tag a customer managed key, but you cannot\n tag an Amazon Web Services\n managed key, an Amazon Web Services owned key, a custom key\n store, or an alias.

    \n

    You can also add tags to a KMS key while creating it (CreateKey) or\n replicating it (ReplicateKey).

    \n

    For information about using tags in KMS, see Tagging keys. For general information about\n tags, including the format and syntax, see Tagging Amazon Web Services resources in the Amazon\n Web Services General Reference.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:TagResource (key policy)

    \n

    \n Related operations\n

    \n ", + "smithy.api#documentation": "

    Adds or edits tags on a customer managed key.

    \n \n

    Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    Each tag consists of a tag key and a tag value, both of which are case-sensitive strings.\n The tag value can be an empty (null) string. To add a tag, specify a new tag key and a tag\n value. To edit a tag, specify an existing tag key and a new tag value.

    \n

    You can use this operation to tag a customer managed key, but you cannot\n tag an Amazon Web Services\n managed key, an Amazon Web Services owned key, a custom key\n store, or an alias.

    \n

    You can also add tags to a KMS key while creating it (CreateKey) or\n replicating it (ReplicateKey).

    \n

    For information about using tags in KMS, see Tagging keys. For general information about\n tags, including the format and syntax, see Tagging Amazon Web Services resources in the Amazon\n Web Services General Reference.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:TagResource (key policy)

    \n

    \n Related operations\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To tag a KMS key", @@ -7948,7 +7948,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Deletes tags from a customer managed key. To delete a tag,\n specify the tag key and the KMS key.

    \n \n

    Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    When it succeeds, the UntagResource operation doesn't return any output.\n Also, if the specified tag key isn't found on the KMS key, it doesn't throw an exception or\n return a response. To confirm that the operation worked, use the ListResourceTags operation.

    \n

    For information about using tags in KMS, see Tagging keys. For general information about\n tags, including the format and syntax, see Tagging Amazon Web Services resources in the Amazon\n Web Services General Reference.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:UntagResource (key policy)

    \n

    \n Related operations\n

    \n ", + "smithy.api#documentation": "

    Deletes tags from a customer managed key. To delete a tag,\n specify the tag key and the KMS key.

    \n \n

    Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    When it succeeds, the UntagResource operation doesn't return any output.\n Also, if the specified tag key isn't found on the KMS key, it doesn't throw an exception or\n return a response. To confirm that the operation worked, use the ListResourceTags operation.

    \n

    For information about using tags in KMS, see Tagging keys. For general information about\n tags, including the format and syntax, see Tagging Amazon Web Services resources in the Amazon\n Web Services General Reference.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:UntagResource (key policy)

    \n

    \n Related operations\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To remove tags from a KMS key", @@ -8009,7 +8009,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Associates an existing KMS alias with a different KMS key. Each alias is associated with\n only one KMS key at a time, although a KMS key can have multiple aliases. The alias and the\n KMS key must be in the same Amazon Web Services account and Region.

    \n \n

    Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    The current and new KMS key must be the same type (both symmetric or both asymmetric or\n both HMAC), and they must have the same key usage. This restriction prevents errors in code\n that uses aliases. If you must assign an alias to a different type of KMS key, use DeleteAlias to delete the old alias and CreateAlias to create\n a new alias.

    \n

    You cannot use UpdateAlias to change an alias name. To change an alias name,\n use DeleteAlias to delete the old alias and CreateAlias to\n create a new alias.

    \n

    Because an alias is not a property of a KMS key, you can create, update, and delete the\n aliases of a KMS key without affecting the KMS key. Also, aliases do not appear in the\n response from the DescribeKey operation. To get the aliases of all KMS keys\n in the account, use the ListAliases operation.

    \n

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

    \n

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

    \n

    \n Required permissions\n

    \n \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Associates an existing KMS alias with a different KMS key. Each alias is associated with\n only one KMS key at a time, although a KMS key can have multiple aliases. The alias and the\n KMS key must be in the same Amazon Web Services account and Region.

    \n \n

    Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see ABAC for KMS in the Key Management Service Developer Guide.

    \n     \n

    The current and new KMS key must be the same type (both symmetric or both asymmetric or\n both HMAC), and they must have the same key usage. This restriction prevents errors in code\n that uses aliases. If you must assign an alias to a different type of KMS key, use DeleteAlias to delete the old alias and CreateAlias to create\n a new alias.

    \n

    You cannot use UpdateAlias to change an alias name. To change an alias name,\n use DeleteAlias to delete the old alias and CreateAlias to\n create a new alias.

    \n

    Because an alias is not a property of a KMS key, you can create, update, and delete the\n aliases of a KMS key without affecting the KMS key. Also, aliases do not appear in the\n response from the DescribeKey operation. To get the aliases of all KMS keys\n in the account, use the ListAliases operation.

    \n

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

    \n

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

    \n

    \n Required permissions\n

    \n \n

    For details, see Controlling access to aliases in the\n Key Management Service Developer Guide.

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To update an alias", @@ -8106,7 +8106,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Changes the properties of a custom key store. You can use this operation to change the\n properties of an CloudHSM key store or an external key store.

    \n

    Use the required CustomKeyStoreId parameter to identify the custom key store.\n Use the remaining optional parameters to change its properties. This operation does not return\n any property values. To verify the updated property values, use the DescribeCustomKeyStores operation.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n \n

    When updating the properties of an external key store, verify that the updated settings\n connect your key store, via the external key store proxy, to the same external key manager\n as the previous settings, or to a backup or snapshot of the external key manager with the\n same cryptographic keys. If the updated connection settings fail, you can fix them and\n retry, although an extended delay might disrupt Amazon Web Services services. However, if KMS\n permanently loses its access to cryptographic keys, ciphertext encrypted under those keys is\n unrecoverable.

    \n     \n \n

    For external key stores:

    \n

    Some external key managers provide a simpler method for updating an external key store.\n For details, see your external key manager documentation.

    \n

    When updating an external key store in the KMS console, you can upload a JSON-based\n proxy configuration file with the desired values. You cannot upload the proxy configuration\n file to the UpdateCustomKeyStore operation. However, you can use the file to\n help you determine the correct values for the UpdateCustomKeyStore\n parameters.

    \n     \n

    For an CloudHSM key store, you can use this operation to change the custom key store friendly\n name (NewCustomKeyStoreName), to tell KMS about a change to the\n kmsuser crypto user password (KeyStorePassword), or to associate\n the custom key store with a different, but related, CloudHSM cluster\n (CloudHsmClusterId). To update any property of an CloudHSM key store, the\n ConnectionState of the CloudHSM key store must be DISCONNECTED.

    \n

    For an external key store, you can use this operation to change the custom key store\n friendly name (NewCustomKeyStoreName), or to tell KMS about a change to the\n external key store proxy authentication credentials\n (XksProxyAuthenticationCredential), connection method\n (XksProxyConnectivity), external proxy endpoint\n (XksProxyUriEndpoint) and path (XksProxyUriPath). For external key\n stores with an XksProxyConnectivity of VPC_ENDPOINT_SERVICE, you can\n also update the Amazon VPC endpoint service name (XksProxyVpcEndpointServiceName). To\n update most properties of an external key store, the ConnectionState of the\n external key store must be DISCONNECTED. However, you can update the\n CustomKeyStoreName, XksProxyAuthenticationCredential, and\n XksProxyUriPath of an external key store when it is in the CONNECTED or\n DISCONNECTED state.

    \n

    If your update requires a DISCONNECTED state, before using\n UpdateCustomKeyStore, use the DisconnectCustomKeyStore\n operation to disconnect the custom key store. After the UpdateCustomKeyStore\n operation completes, use the ConnectCustomKeyStore to reconnect the custom\n key store. To find the ConnectionState of the custom key store, use the DescribeCustomKeyStores operation.

    \n

    \n

    \n

    Before updating the custom key store, verify that the new values allow KMS to connect\n the custom key store to its backing key store. For example, before you change the\n XksProxyUriPath value, verify that the external key store proxy is reachable at\n the new path.

    \n

    If the operation succeeds, it returns a JSON object with no\nproperties.

    \n

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

    \n

    \n Required permissions: kms:UpdateCustomKeyStore (IAM policy)

    \n

    \n Related operations:\n

    \n ", + "smithy.api#documentation": "

    Changes the properties of a custom key store. You can use this operation to change the\n properties of an CloudHSM key store or an external key store.

    \n

    Use the required CustomKeyStoreId parameter to identify the custom key store.\n Use the remaining optional parameters to change its properties. This operation does not return\n any property values. To verify the updated property values, use the DescribeCustomKeyStores operation.

    \n

    This operation is part of the custom key stores feature in KMS, which\ncombines the convenience and extensive integration of KMS with the isolation and control of a\nkey store that you own and manage.

    \n \n

    When updating the properties of an external key store, verify that the updated settings\n connect your key store, via the external key store proxy, to the same external key manager\n as the previous settings, or to a backup or snapshot of the external key manager with the\n same cryptographic keys. If the updated connection settings fail, you can fix them and\n retry, although an extended delay might disrupt Amazon Web Services services. However, if KMS\n permanently loses its access to cryptographic keys, ciphertext encrypted under those keys is\n unrecoverable.

    \n     \n \n

    For external key stores:

    \n

    Some external key managers provide a simpler method for updating an external key store.\n For details, see your external key manager documentation.

    \n

    When updating an external key store in the KMS console, you can upload a JSON-based\n proxy configuration file with the desired values. You cannot upload the proxy configuration\n file to the UpdateCustomKeyStore operation. However, you can use the file to\n help you determine the correct values for the UpdateCustomKeyStore\n parameters.

    \n     \n

    For an CloudHSM key store, you can use this operation to change the custom key store friendly\n name (NewCustomKeyStoreName), to tell KMS about a change to the\n kmsuser crypto user password (KeyStorePassword), or to associate\n the custom key store with a different, but related, CloudHSM cluster\n (CloudHsmClusterId). To update any property of an CloudHSM key store, the\n ConnectionState of the CloudHSM key store must be DISCONNECTED.

    \n

    For an external key store, you can use this operation to change the custom key store\n friendly name (NewCustomKeyStoreName), or to tell KMS about a change to the\n external key store proxy authentication credentials\n (XksProxyAuthenticationCredential), connection method\n (XksProxyConnectivity), external proxy endpoint\n (XksProxyUriEndpoint) and path (XksProxyUriPath). For external key\n stores with an XksProxyConnectivity of VPC_ENDPOINT_SERVICE, you can\n also update the Amazon VPC endpoint service name (XksProxyVpcEndpointServiceName). To\n update most properties of an external key store, the ConnectionState of the\n external key store must be DISCONNECTED. However, you can update the\n CustomKeyStoreName, XksProxyAuthenticationCredential, and\n XksProxyUriPath of an external key store when it is in the CONNECTED or\n DISCONNECTED state.

    \n

    If your update requires a DISCONNECTED state, before using\n UpdateCustomKeyStore, use the DisconnectCustomKeyStore\n operation to disconnect the custom key store. After the UpdateCustomKeyStore\n operation completes, use the ConnectCustomKeyStore to reconnect the custom\n key store. To find the ConnectionState of the custom key store, use the DescribeCustomKeyStores operation.

    \n

    \n

    \n

    Before updating the custom key store, verify that the new values allow KMS to connect\n the custom key store to its backing key store. For example, before you change the\n XksProxyUriPath value, verify that the external key store proxy is reachable at\n the new path.

    \n

    If the operation succeeds, it returns a JSON object with no\nproperties.

    \n

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

    \n

    \n Required permissions: kms:UpdateCustomKeyStore (IAM policy)

    \n

    \n Related operations:\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To edit the friendly name of a custom key store", @@ -8216,7 +8216,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Updates the description of a KMS key. To see the description of a KMS key, use DescribeKey.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:UpdateKeyDescription (key policy)

    \n

    \n Related operations\n

    \n ", + "smithy.api#documentation": "

    Updates the description of a KMS key. To see the description of a KMS key, use DescribeKey.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:UpdateKeyDescription (key policy)

    \n

    \n Related operations\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To update the description of a KMS key", @@ -8280,7 +8280,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Changes the primary key of a multi-Region key.

    \n

    This operation changes the replica key in the specified Region to a primary key and\n changes the former primary key to a replica key. For example, suppose you have a primary key\n in us-east-1 and a replica key in eu-west-2. If you run\n UpdatePrimaryRegion with a PrimaryRegion value of\n eu-west-2, the primary key is now the key in eu-west-2, and the\n key in us-east-1 becomes a replica key. For details, see Updating the primary Region in the Key Management Service Developer Guide.

    \n

    This operation supports multi-Region keys, an KMS feature that lets you create multiple\n interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key\n material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt\n it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    The primary key of a multi-Region key is the source for properties\n that are always shared by primary and replica keys, including the key material, key ID, key spec, key usage, key material\n origin, and automatic\n key rotation. It's the only key that can be replicated. You cannot delete the primary\n key until all replica keys are deleted.

    \n

    The key ID and primary Region that you specify uniquely identify the replica key that will\n become the primary key. The primary Region must already have a replica key. This operation\n does not create a KMS key in the specified Region. To find the replica keys, use the DescribeKey operation on the primary key or any replica key. To create a replica\n key, use the ReplicateKey operation.

    \n

    You can run this operation while using the affected multi-Region keys in cryptographic\n operations. This operation should not delay, interrupt, or cause failures in cryptographic\n operations.

    \n

    Even after this operation completes, the process of updating the primary Region might\n still be in progress for a few more seconds. Operations such as DescribeKey might\n display both the old and new primary keys as replicas. The old and new primary keys have a\n transient key state of Updating. The original key state is restored when the\n update is complete. While the key state is Updating, you can use the keys in\n cryptographic operations, but you cannot replicate the new primary key or perform certain\n management operations, such as enabling or disabling these keys. For details about the\n Updating key state, see Key states of KMS keys in the Key Management Service Developer Guide.

    \n

    This operation does not return any output. To verify that primary key is changed, use the\n DescribeKey operation.

    \n

    \n Cross-account use: No. You cannot use this operation in a\n different Amazon Web Services account.

    \n

    \n Required permissions:

    \n \n

    \n Related operations\n

    \n ", + "smithy.api#documentation": "

    Changes the primary key of a multi-Region key.

    \n

    This operation changes the replica key in the specified Region to a primary key and\n changes the former primary key to a replica key. For example, suppose you have a primary key\n in us-east-1 and a replica key in eu-west-2. If you run\n UpdatePrimaryRegion with a PrimaryRegion value of\n eu-west-2, the primary key is now the key in eu-west-2, and the\n key in us-east-1 becomes a replica key. For details, see Updating the primary Region in the Key Management Service Developer Guide.

    \n

    This operation supports multi-Region keys, an KMS feature that lets you create multiple\n interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key\n material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt\n it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Multi-Region keys in KMS in the Key Management Service Developer Guide.

    \n

    The primary key of a multi-Region key is the source for properties\n that are always shared by primary and replica keys, including the key material, key ID, key spec, key usage, key material\n origin, and automatic\n key rotation. It's the only key that can be replicated. You cannot delete the primary\n key until all replica keys are deleted.

    \n

    The key ID and primary Region that you specify uniquely identify the replica key that will\n become the primary key. The primary Region must already have a replica key. This operation\n does not create a KMS key in the specified Region. To find the replica keys, use the DescribeKey operation on the primary key or any replica key. To create a replica\n key, use the ReplicateKey operation.

    \n

    You can run this operation while using the affected multi-Region keys in cryptographic\n operations. This operation should not delay, interrupt, or cause failures in cryptographic\n operations.

    \n

    Even after this operation completes, the process of updating the primary Region might\n still be in progress for a few more seconds. Operations such as DescribeKey might\n display both the old and new primary keys as replicas. The old and new primary keys have a\n transient key state of Updating. The original key state is restored when the\n update is complete. While the key state is Updating, you can use the keys in\n cryptographic operations, but you cannot replicate the new primary key or perform certain\n management operations, such as enabling or disabling these keys. For details about the\n Updating key state, see Key states of KMS keys in the Key Management Service Developer Guide.

    \n

    This operation does not return any output. To verify that primary key is changed, use the\n DescribeKey operation.

    \n

    \n Cross-account use: No. You cannot use this operation in a\n different Amazon Web Services account.

    \n

    \n Required permissions:

    \n \n

    \n Related operations\n

    \n \n

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

    ", "smithy.api#examples": [ { "title": "To update the primary Region of a multi-Region KMS key", @@ -8356,7 +8356,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Verifies a digital signature that was generated by the Sign operation.

    \n

    \n

    Verification confirms that an authorized user signed the message with the specified KMS\n key and signing algorithm, and the message hasn't changed since it was signed. If the\n signature is verified, the value of the SignatureValid field in the response is\n True. If the signature verification fails, the Verify operation\n fails with an KMSInvalidSignatureException exception.

    \n

    A digital signature is generated by using the private key in an asymmetric KMS key. The\n signature is verified by using the public key in the same asymmetric KMS key.\n For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    To use the Verify operation, specify the same asymmetric KMS key, message,\n and signing algorithm that were used to produce the signature. The message type does not need\n to be the same as the one used for signing, but it must indicate whether the value of the\n Message parameter should be hashed as part of the verification process.

    \n

    You can also verify the digital signature by using the public key of the KMS key outside\n of KMS. Use the GetPublicKey operation to download the public key in the\n asymmetric KMS key and then use the public key to verify the signature outside of KMS. The\n advantage of using the Verify operation is that it is performed within KMS. As\n a result, it's easy to call, the operation is performed within the FIPS boundary, it is logged\n in CloudTrail, and you can use key policy and IAM policy to determine who is authorized to use\n the KMS key to verify signatures.

    \n

    To verify a signature outside of KMS with an SM2 public key (China Regions only), you\n must specify the distinguishing ID. By default, KMS uses 1234567812345678 as\n the distinguishing ID. For more information, see Offline\n verification with SM2 key pairs.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:Verify (key policy)

    \n

    \n Related operations: Sign\n

    ", + "smithy.api#documentation": "

    Verifies a digital signature that was generated by the Sign operation.

    \n

    \n

    Verification confirms that an authorized user signed the message with the specified KMS\n key and signing algorithm, and the message hasn't changed since it was signed. If the\n signature is verified, the value of the SignatureValid field in the response is\n True. If the signature verification fails, the Verify operation\n fails with an KMSInvalidSignatureException exception.

    \n

    A digital signature is generated by using the private key in an asymmetric KMS key. The\n signature is verified by using the public key in the same asymmetric KMS key.\n For information about asymmetric KMS keys, see Asymmetric KMS keys in the Key Management Service Developer Guide.

    \n

    To use the Verify operation, specify the same asymmetric KMS key, message,\n and signing algorithm that were used to produce the signature. The message type does not need\n to be the same as the one used for signing, but it must indicate whether the value of the\n Message parameter should be hashed as part of the verification process.

    \n

    You can also verify the digital signature by using the public key of the KMS key outside\n of KMS. Use the GetPublicKey operation to download the public key in the\n asymmetric KMS key and then use the public key to verify the signature outside of KMS. The\n advantage of using the Verify operation is that it is performed within KMS. As\n a result, it's easy to call, the operation is performed within the FIPS boundary, it is logged\n in CloudTrail, and you can use key policy and IAM policy to determine who is authorized to use\n the KMS key to verify signatures.

    \n

    To verify a signature outside of KMS with an SM2 public key (China Regions only), you\n must specify the distinguishing ID. By default, KMS uses 1234567812345678 as\n the distinguishing ID. For more information, see Offline\n verification with SM2 key pairs.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:Verify (key policy)

    \n

    \n Related operations: Sign\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To use an asymmetric KMS key to verify a digital signature", @@ -8415,7 +8415,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Verifies the hash-based message authentication code (HMAC) for a specified message, HMAC\n KMS key, and MAC algorithm. To verify the HMAC, VerifyMac computes an HMAC using\n the message, HMAC KMS key, and MAC algorithm that you specify, and compares the computed HMAC\n to the HMAC that you specify. If the HMACs are identical, the verification succeeds;\n otherwise, it fails. Verification indicates that the message hasn't changed since the HMAC was\n calculated, and the specified key was used to generate and verify the HMAC.

    \n

    HMAC KMS keys and the HMAC algorithms that KMS uses conform to industry standards\n defined in RFC 2104.

    \n

    This operation is part of KMS support for HMAC KMS keys. For details, see\n HMAC keys in KMS in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:VerifyMac (key policy)

    \n

    \n Related operations: GenerateMac\n

    ", + "smithy.api#documentation": "

    Verifies the hash-based message authentication code (HMAC) for a specified message, HMAC\n KMS key, and MAC algorithm. To verify the HMAC, VerifyMac computes an HMAC using\n the message, HMAC KMS key, and MAC algorithm that you specify, and compares the computed HMAC\n to the HMAC that you specify. If the HMACs are identical, the verification succeeds;\n otherwise, it fails. Verification indicates that the message hasn't changed since the HMAC was\n calculated, and the specified key was used to generate and verify the HMAC.

    \n

    HMAC KMS keys and the HMAC algorithms that KMS uses conform to industry standards\n defined in RFC 2104.

    \n

    This operation is part of KMS support for HMAC KMS keys. For details, see\n HMAC keys in KMS in the\n Key Management Service Developer Guide.

    \n

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

    \n

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

    \n

    \n Required permissions: kms:VerifyMac (key policy)

    \n

    \n Related operations: GenerateMac\n

    \n

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

    ", "smithy.api#examples": [ { "title": "To verify an HMAC", @@ -8939,7 +8939,7 @@ "code": "XksProxyVpcEndpointServiceInvalidConfigurationException", "httpResponseCode": 400 }, - "smithy.api#documentation": "

    The request was rejected because the Amazon VPC endpoint service configuration does not fulfill\n the requirements for an external key store proxy. For details, see the exception message and\n review the\n requirements for Amazon VPC endpoint service connectivity for an external key\n store.

    ", + "smithy.api#documentation": "

    The request was rejected because the Amazon VPC endpoint service configuration does not fulfill\n the requirements for an external key store proxy. For details, see the exception message and\n review the requirements for Amazon VPC endpoint service connectivity for an external key\n store.

    ", "smithy.api#error": "client", "smithy.api#httpError": 400 }