@aws-sdk/client-kms 3.32.0 → 3.36.0

package/{dist/cjs → dist-cjs}/commands/ReEncryptCommand.js

@@ -1,45 +1,51 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ReEncryptCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Decrypts ciphertext and then reencrypts it entirely within KMS. You can use this
- *       operation to change the KMS key under which data is encrypted, such as when
- *       you <a href="https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-manually">manually rotate</a> a KMS key or change the KMS key that protects a ciphertext. You can also
- *       use it to reencrypt ciphertext under the same KMS key, such as to change the <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context">encryption
+ *       operation to change the KMS key under which data is encrypted, such as when you <a href="https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-manually">manually
+ *         rotate</a> a KMS key or change the KMS key that protects a ciphertext. You can also use
+ *       it to reencrypt ciphertext under the same KMS key, such as to change the <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context">encryption
  *         context</a> of a ciphertext.</p>
  *          <p>The <code>ReEncrypt</code> operation can decrypt ciphertext that was encrypted by using an
  *       KMS KMS key in an KMS operation, such as <a>Encrypt</a> or <a>GenerateDataKey</a>. It can also decrypt ciphertext that was encrypted by using the
- *       public key of an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks">asymmetric KMS key</a> outside of KMS. However, it cannot decrypt ciphertext
- *       produced by other libraries, such as the <a href="https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/">Amazon Web Services Encryption SDK</a> or <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html">Amazon S3 client-side encryption</a>.
- *       These libraries return a ciphertext format that is incompatible with KMS.</p>
+ *       public key of an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks">asymmetric KMS key</a>
+ *       outside of KMS. However, it cannot decrypt ciphertext produced by other libraries, such as
+ *       the <a href="https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/">Amazon Web Services Encryption SDK</a> or
+ *         <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html">Amazon S3
+ *         client-side encryption</a>. These libraries return a ciphertext format that is
+ *       incompatible with KMS.</p>
  *          <p>When you use the <code>ReEncrypt</code> operation, you need to provide information for the
  *       decrypt operation and the subsequent encrypt operation.</p>
  *          <ul>
  *             <li>
  *                <p>If your ciphertext was encrypted under an asymmetric KMS key, you must use the
- *             <code>SourceKeyId</code> parameter to identify the KMS key that encrypted the ciphertext.
- *           You must also supply the encryption algorithm that was used. This information is required
- *           to decrypt the data.</p>
+ *             <code>SourceKeyId</code> parameter to identify the KMS key that encrypted the
+ *           ciphertext. You must also supply the encryption algorithm that was used. This information
+ *           is required to decrypt the data.</p>
  *             </li>
  *             <li>
- *                <p>If your ciphertext was encrypted under a symmetric KMS key, the <code>SourceKeyId</code>
- *           parameter is optional. KMS can get this information from metadata that it adds to the
- *           symmetric ciphertext blob. This feature adds durability to your implementation by ensuring
- *           that authorized users can decrypt ciphertext decades after it was encrypted, even if
- *           they've lost track of the key ID. However, specifying the source KMS key is always recommended
- *           as a best practice. When you use the <code>SourceKeyId</code> parameter to specify a KMS key,
- *           KMS uses only the KMS key you specify. If the ciphertext was encrypted under a different KMS key, the <code>ReEncrypt</code> operation fails. This practice ensures that you use the KMS key that you intend.</p>
+ *                <p>If your ciphertext was encrypted under a symmetric KMS key, the
+ *             <code>SourceKeyId</code> parameter is optional. KMS can get this information from
+ *           metadata that it adds to the symmetric ciphertext blob. This feature adds durability to
+ *           your implementation by ensuring that authorized users can decrypt ciphertext decades after
+ *           it was encrypted, even if they've lost track of the key ID. However, specifying the source
+ *           KMS key is always recommended as a best practice. When you use the
+ *             <code>SourceKeyId</code> parameter to specify a KMS key, KMS uses only the KMS key you
+ *           specify. If the ciphertext was encrypted under a different KMS key, the
+ *             <code>ReEncrypt</code> operation fails. This practice ensures that you use the KMS key
+ *           that you intend.</p>
  *             </li>
  *             <li>
  *                <p>To reencrypt the data, you must use the <code>DestinationKeyId</code> parameter
  *           specify the KMS key that re-encrypts the data after it is decrypted. You can select a
- *           symmetric or asymmetric KMS key. If the destination KMS key is an asymmetric KMS key, you must also
- *           provide the encryption algorithm. The algorithm that you choose must be compatible with
- *           the KMS key.</p>
+ *           symmetric or asymmetric KMS key. If the destination KMS key is an asymmetric KMS key, you
+ *           must also provide the encryption algorithm. The algorithm that you choose must be
+ *           compatible with the KMS key.</p>
  *
  *                <important>
  *                   <p>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.</p>
@@ -47,26 +53,26 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *                </important>
  *             </li>
  *          </ul>
- *
- *
- *
  *          <p>The KMS key that you use for this operation must be in a compatible key state. For
  * details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html">Key state: Effect on your KMS key</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          <p>
- *             <b>Cross-account use</b>: Yes. The source KMS key and destination KMS key can be in different Amazon Web Services accounts. Either or both KMS keys can be in a different account than
- *       the caller. To specify a KMS key in a different account, you must use its key ARN or alias
- *       ARN.</p>
+ *             <b>Cross-account use</b>: Yes.
+ *       The source KMS key and destination KMS key can be in different Amazon Web Services accounts. Either or both
+ *       KMS keys can be in a different account than the caller. To specify a KMS key in a different
+ *       account, you must use its key ARN or alias ARN.</p>
  *
  *          <p>
  *             <b>Required permissions</b>:</p>
  *          <ul>
  *             <li>
  *                <p>
- *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:ReEncryptFrom</a> permission on the source KMS key (key policy)</p>
+ *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:ReEncryptFrom</a>
+ *           permission on the source KMS key (key policy)</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:ReEncryptTo</a> permission on the destination KMS key (key policy)</p>
+ *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:ReEncryptTo</a>
+ *           permission on the destination KMS key (key policy)</p>
  *             </li>
  *          </ul>
  *          <p>To permit reencryption from or to a KMS key, include the <code>"kms:ReEncrypt*"</code>
@@ -150,4 +156,3 @@ class ReEncryptCommand extends smithy_client_1.Command {
     }
 }
 exports.ReEncryptCommand = ReEncryptCommand;
-//# sourceMappingURL=ReEncryptCommand.js.map

package/{dist/cjs → dist-cjs}/commands/ReplicateKeyCommand.js

@@ -1,10 +1,10 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ReplicateKeyCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Replicates a multi-Region key into the specified Region. This operation creates a
  *       multi-Region replica key based on a multi-Region primary key in a different Region of the same
@@ -37,7 +37,7 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *       details about the <code>Creating</code> key state, see <a href="kms/latest/developerguide/key-state.html">Key state: Effect on your KMS key</a> in the
  *       <i>Key Management Service Developer Guide</i>.</p>
  *          <p>The CloudTrail log of a <code>ReplicateKey</code> operation records a
- *       <code>ReplicateKey</code> operation in the primary key's Region and a <a>CreateKey</a> operation in the replica key's Region.</p>
+ *         <code>ReplicateKey</code> operation in the primary key's Region and a <a>CreateKey</a> operation in the replica key's Region.</p>
  *          <p>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 <a href="kms/latest/developerguide/multi-region-keys-import.html">Importing key material into multi-Region keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
@@ -45,8 +45,8 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *       operation.</p>
  *          <note>
  *             <p>
- *                <code>ReplicateKey</code> uses different default values for the <code>KeyPolicy</code> and
- *           <code>Tags</code> parameters than those used in the KMS console. For details, see the
+ *                <code>ReplicateKey</code> uses different default values for the <code>KeyPolicy</code>
+ *         and <code>Tags</code> parameters than those used in the KMS console. For details, see the
  *         parameter descriptions.</p>
  *          </note>
  *          <p>
@@ -57,8 +57,8 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *          <ul>
  *             <li>
  *                <p>
- *                   <code>kms:ReplicateKey</code> on the primary key (in the primary key's Region). Include this
- *           permission in the primary key's key policy.</p>
+ *                   <code>kms:ReplicateKey</code> on the primary key (in the primary key's Region).
+ *           Include this permission in the primary key's key policy.</p>
  *             </li>
  *             <li>
  *                <p>
@@ -135,4 +135,3 @@ class ReplicateKeyCommand extends smithy_client_1.Command {
     }
 }
 exports.ReplicateKeyCommand = ReplicateKeyCommand;
-//# sourceMappingURL=ReplicateKeyCommand.js.map

package/{dist/cjs → dist-cjs}/commands/RetireGrantCommand.js

@@ -1,19 +1,20 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.RetireGrantCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Deletes a grant. Typically, you retire a grant when you no longer need its permissions. To
  *       identify the grant to retire, use a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token">grant token</a>, or both the grant ID and a
- *       key identifier (key ID or key ARN) of the KMS key. The <a>CreateGrant</a> operation returns both values.</p>
+ *       key identifier (key ID or key ARN) of the KMS key. The <a>CreateGrant</a> operation
+ *       returns both values.</p>
  *          <p>This operation can be called by the <i>retiring principal</i> for a grant,
  *       by the <i>grantee principal</i> if the grant allows the <code>RetireGrant</code>
  *       operation, and by the Amazon Web Services account (root user) in which the grant is created. It can also be
  *       called by principals to whom permission for retiring a grant is delegated. For details, see
- *       <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete">Retiring and
+ *         <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete">Retiring and
  *         revoking grants</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          <p>For detailed information about grants, including grant terminology, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grants.html">Using grants</a> in the
  *         <i>
@@ -21,11 +22,12 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *             </i>. For examples of working with grants in several
  *       programming languages, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html">Programming grants</a>. </p>
  *          <p>
- *             <b>Cross-account use</b>: Yes. You can retire a grant on a KMS key
- *       in a different Amazon Web Services account.</p>
+ *             <b>Cross-account use</b>: Yes. You can retire a grant on a KMS
+ *       key in a different Amazon Web Services account.</p>
  *          <p>
  *             <b>Required permissions:</b>:Permission to retire a grant is
- *       determined primarily by the grant. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete">Retiring and revoking grants</a> in the <i>Key Management Service Developer Guide</i>.</p>
+ *       determined primarily by the grant. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete">Retiring and revoking grants</a> in
+ *       the <i>Key Management Service Developer Guide</i>.</p>
  *          <p>
  *             <b>Related operations:</b>
  *          </p>
@@ -102,4 +104,3 @@ class RetireGrantCommand extends smithy_client_1.Command {
     }
 }
 exports.RetireGrantCommand = RetireGrantCommand;
-//# sourceMappingURL=RetireGrantCommand.js.map

package/{dist/cjs → dist-cjs}/commands/RevokeGrantCommand.js

@@ -1,14 +1,13 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.RevokeGrantCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Deletes the specified grant. You revoke a grant to terminate the permissions that the
- *       grant allows. For more
- *       information, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/managing-grants.html#grant-delete">Retiring and revoking grants</a> in
+ *       grant allows. For more information, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/managing-grants.html#grant-delete">Retiring and revoking grants</a> in
  *       the <i>
  *                <i>Key Management Service Developer Guide</i>
  *             </i>.</p>
@@ -102,4 +101,3 @@ class RevokeGrantCommand extends smithy_client_1.Command {
     }
 }
 exports.RevokeGrantCommand = RevokeGrantCommand;
-//# sourceMappingURL=RevokeGrantCommand.js.map

package/{dist/cjs → dist-cjs}/commands/ScheduleKeyDeletionCommand.js

@@ -1,27 +1,29 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ScheduleKeyDeletionCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
- * <p>Schedules the deletion of a KMS key. By default, KMS applies a waiting
- *       period of 30 days, but you can specify a waiting period of 7-30 days. When this operation is
- *       successful, the key state of the KMS key changes to <code>PendingDeletion</code> and the key can't
- *       be used in any cryptographic operations. It remains in this state for the duration of the
- *       waiting period. Before the waiting period ends, you can use <a>CancelKeyDeletion</a> to cancel the deletion of the KMS key. After the waiting period ends, KMS deletes the KMS key,
+ * <p>Schedules the deletion of a KMS key. By default, KMS applies a waiting period of 30
+ *       days, but you can specify a waiting period of 7-30 days. When this operation is successful,
+ *       the key state of the KMS key changes to <code>PendingDeletion</code> and the key can't be used
+ *       in any cryptographic operations. It remains in this state for the duration of the waiting
+ *       period. Before the waiting period ends, you can use <a>CancelKeyDeletion</a> to
+ *       cancel the deletion of the KMS key. After the waiting period ends, KMS deletes the KMS key,
  *       its key material, and all KMS data associated with it, including all aliases that refer to
  *       it.</p>
  *          <important>
- *             <p>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.) To prevent the use of a KMS key without deleting it, use <a>DisableKey</a>. </p>
+ *             <p>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.) To prevent the use of a KMS key without deleting
+ *         it, use <a>DisableKey</a>. </p>
  *          </important>
  *          <p>If you schedule deletion of a KMS key from a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">custom key store</a>, when the waiting period
- *       expires, <code>ScheduleKeyDeletion</code> deletes the KMS key from KMS. Then KMS makes a best
- *       effort to delete the key material from the associated CloudHSM cluster. However, you might need
- *       to manually <a href="https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-orphaned-key">delete the orphaned key
+ *       expires, <code>ScheduleKeyDeletion</code> deletes the KMS key from KMS. Then KMS makes a
+ *       best effort to delete the key material from the associated CloudHSM cluster. However, you might
+ *       need to manually <a href="https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-orphaned-key">delete the orphaned key
  *         material</a> from the cluster and its backups.</p>
  *          <p>You can schedule the deletion of a multi-Region primary key and its replica keys at any
  *       time. However, KMS will not delete a multi-Region primary key with existing replica keys. If
@@ -30,18 +32,20 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *       operations. This status can continue indefinitely. When the last of its replicas keys is
  *       deleted (not just scheduled), the key state of the primary key changes to
  *         <code>PendingDeletion</code> and its waiting period (<code>PendingWindowInDays</code>)
- *       begins. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-delete.html">Deleting multi-Region keys</a> in the <i>Key Management Service Developer Guide</i>. </p>
+ *       begins. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-delete.html">Deleting multi-Region keys</a> in the
+ *       <i>Key Management Service Developer Guide</i>. </p>
  *          <p>For more information about scheduling a KMS key for deletion, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html">Deleting KMS keys</a> in the
  *       <i>Key Management Service Developer Guide</i>.</p>
  *          <p>The KMS key that you use for this operation must be in a compatible key state. For
  * details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html">Key state: Effect on your KMS key</a> in the <i>Key Management Service Developer Guide</i>.</p>
- *
  *          <p>
- *             <b>Cross-account use</b>: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.</p>
+ *             <b>Cross-account
+ *         use</b>: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.</p>
  *
  *
  *          <p>
- *             <b>Required permissions</b>: kms:ScheduleKeyDeletion (key policy)</p>
+ *             <b>Required permissions</b>: kms:ScheduleKeyDeletion (key
+ *       policy)</p>
  *          <p>
  *             <b>Related operations</b>
  *          </p>
@@ -108,4 +112,3 @@ class ScheduleKeyDeletionCommand extends smithy_client_1.Command {
     }
 }
 exports.ScheduleKeyDeletionCommand = ScheduleKeyDeletionCommand;
-//# sourceMappingURL=ScheduleKeyDeletionCommand.js.map

package/{dist/cjs → dist-cjs}/commands/SignCommand.js

@@ -1,26 +1,27 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.SignCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Creates a <a href="https://en.wikipedia.org/wiki/Digital_signature">digital
- *         signature</a> for a message or message digest by using the private key in an asymmetric KMS key. To verify the signature, use the <a>Verify</a> operation, or use the public
- *       key in the same asymmetric KMS key outside of KMS. For information about symmetric and asymmetric KMS keys, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html">Using Symmetric and Asymmetric KMS keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
+ *         signature</a> for a message or message digest by using the private key in an asymmetric
+ *       KMS key. To verify the signature, use the <a>Verify</a> operation, or use the
+ *       public key in the same asymmetric KMS key outside of KMS. For information about symmetric and asymmetric KMS keys, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html">Using Symmetric and Asymmetric KMS keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          <p>Digital signatures are generated and verified by using asymmetric key pair, such as an RSA
- *       or ECC pair that is represented by an asymmetric KMS key. The key owner (or
- *       an authorized user) uses their private key to sign a message. Anyone with the public key can
- *       verify that the message was signed with that particular private key and that the message
- *       hasn't changed since it was signed. </p>
+ *       or ECC pair that is represented by an asymmetric KMS key. The key owner (or an authorized
+ *       user) uses their private key to sign a message. Anyone with the public key can verify that the
+ *       message was signed with that particular private key and that the message hasn't changed since
+ *       it was signed. </p>
  *          <p>To use the <code>Sign</code> operation, provide the following information:</p>
  *          <ul>
  *             <li>
  *                <p>Use the <code>KeyId</code> parameter to identify an asymmetric KMS key with a
  *             <code>KeyUsage</code> value of <code>SIGN_VERIFY</code>. To get the
- *             <code>KeyUsage</code> value of a KMS key, use the <a>DescribeKey</a> operation.
- *           The caller must have <code>kms:Sign</code> permission on the KMS key.</p>
+ *             <code>KeyUsage</code> value of a KMS key, use the <a>DescribeKey</a>
+ *           operation. The caller must have <code>kms:Sign</code> permission on the KMS key.</p>
  *             </li>
  *             <li>
  *                <p>Use the <code>Message</code> parameter to specify the message or message digest to
@@ -42,7 +43,7 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *       then use the public key to verify the signature outside of KMS. </p>
  *          <p>The KMS key that you use for this operation must be in a compatible key state. For
  * details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html">Key state: Effect on your KMS key</a> in the <i>Key Management Service Developer Guide</i>.</p>
- *          <p>
+ *         <p>
  *             <b>Cross-account use</b>: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify
  *   the key ARN or alias ARN in the value of the <code>KeyId</code> parameter.</p>
  *
@@ -102,4 +103,3 @@ class SignCommand extends smithy_client_1.Command {
     }
 }
 exports.SignCommand = SignCommand;
-//# sourceMappingURL=SignCommand.js.map

package/{dist/cjs → dist-cjs}/commands/TagResourceCommand.js

@@ -1,10 +1,10 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.TagResourceCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Adds or edits tags on a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a>.</p>
  *          <note>
@@ -14,16 +14,18 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *       The tag value can be an empty (null) string. To add a tag, specify a new tag key and a tag
  *       value. To edit a tag, specify an existing tag key and a new tag value.</p>
  *          <p>You can use this operation to tag a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a>, but you cannot
- *       tag an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed key</a>, an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-cmk">Amazon Web Services owned key</a>, a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#keystore-concept">custom key store</a>, or
- *       an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#alias-concept">alias</a>.</p>
- *          <p>You can also add tags to a KMS key while creating it (<a>CreateKey</a>) or replicating it (<a>ReplicateKey</a>).</p>
+ *       tag an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services
+ *         managed key</a>, an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-cmk">Amazon Web Services owned key</a>, a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#keystore-concept">custom key
+ *         store</a>, or an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#alias-concept">alias</a>.</p>
+ *          <p>You can also add tags to a KMS key while creating it (<a>CreateKey</a>) or
+ *       replicating it (<a>ReplicateKey</a>).</p>
  *          <p>For information about using tags in KMS, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html">Tagging keys</a>. For general information about
  *       tags, including the format and syntax, see <a href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging Amazon Web Services resources</a> in the <i>Amazon
  *         Web Services General Reference</i>. </p>
  *          <p>The KMS key that you use for this operation must be in a compatible key state. For
  * details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html">Key state: Effect on your KMS key</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          <p>
- *             <b>Cross-account use</b>: No.  You cannot perform this operation on a KMS key in a different Amazon Web Services account. </p>
+ *             <b>Cross-account use</b>: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. </p>
  *
  *          <p>
  *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:TagResource</a> (key policy)</p>
@@ -103,4 +105,3 @@ class TagResourceCommand extends smithy_client_1.Command {
     }
 }
 exports.TagResourceCommand = TagResourceCommand;
-//# sourceMappingURL=TagResourceCommand.js.map

package/{dist/cjs → dist-cjs}/commands/UntagResourceCommand.js

@@ -1,10 +1,10 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.UntagResourceCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Deletes tags from a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a>. To delete a tag,
  *       specify the tag key and the KMS key.</p>
@@ -12,8 +12,8 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *             <p>Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/abac.html">Using ABAC in KMS</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          </note>
  *          <p>When it succeeds, the <code>UntagResource</code> operation doesn't return any output.
- *       Also, if the specified tag key isn't found on the KMS key, it doesn't throw an exception or return
- *       a response. To confirm that the operation worked, use the <a>ListResourceTags</a> operation.</p>
+ *       Also, if the specified tag key isn't found on the KMS key, it doesn't throw an exception or
+ *       return a response. To confirm that the operation worked, use the <a>ListResourceTags</a> operation.</p>
  *
  *          <p>For information about using tags in KMS, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html">Tagging keys</a>. For general information about
  *       tags, including the format and syntax, see <a href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging Amazon Web Services resources</a> in the <i>Amazon
@@ -21,7 +21,7 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *          <p>The KMS key that you use for this operation must be in a compatible key state. For
  * details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html">Key state: Effect on your KMS key</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          <p>
- *             <b>Cross-account use</b>: No.  You cannot perform this operation on a KMS key in a different Amazon Web Services account.</p>
+ *             <b>Cross-account use</b>: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.</p>
  *
  *          <p>
  *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UntagResource</a> (key policy)</p>
@@ -101,4 +101,3 @@ class UntagResourceCommand extends smithy_client_1.Command {
     }
 }
 exports.UntagResourceCommand = UntagResourceCommand;
-//# sourceMappingURL=UntagResourceCommand.js.map

package/{dist/cjs → dist-cjs}/commands/UpdateAliasCommand.js

@@ -1,14 +1,14 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.UpdateAliasCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
- * <p>Associates an existing KMS alias with a different KMS key. Each alias
- *       is associated with only one KMS key at a time, although a KMS key can have multiple aliases. The alias
- *       and the KMS key must be in the same Amazon Web Services account and Region.</p>
+ * <p>Associates an existing KMS alias with a different KMS key. Each alias is associated with
+ *       only one KMS key at a time, although a KMS key can have multiple aliases. The alias and the
+ *       KMS key must be in the same Amazon Web Services account and Region.</p>
  *          <note>
  *             <p>Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/abac.html">Using ABAC in KMS</a> in the <i>Key Management Service Developer Guide</i>.</p>
  *          </note>
@@ -20,12 +20,12 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *       use <a>DeleteAlias</a> to delete the old alias and <a>CreateAlias</a> to
  *       create a new alias.</p>
  *          <p>Because an alias is not a property of a KMS key, you can create, update, and delete the
- *       aliases of a KMS key without affecting the KMS key. Also, aliases do not appear in the response from
- *       the <a>DescribeKey</a> operation. To get the aliases of all KMS keys in the account,
- *       use the <a>ListAliases</a> operation. </p>
+ *       aliases of a KMS key without affecting the KMS key. Also, aliases do not appear in the
+ *       response from the <a>DescribeKey</a> operation. To get the aliases of all KMS keys
+ *       in the account, use the <a>ListAliases</a> operation. </p>
  *          <p>The KMS key that you use for this operation must be in a compatible key state. For
  * details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html">Key state: Effect on your KMS key</a> in the <i>Key Management Service Developer Guide</i>.</p>
- *          <p>
+ *         <p>
  *             <b>Cross-account use</b>: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. </p>
  *          <p>
  *             <b>Required permissions</b>
@@ -33,18 +33,22 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *          <ul>
  *             <li>
  *                <p>
- *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UpdateAlias</a> on the alias (IAM policy).</p>
+ *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UpdateAlias</a> on
+ *           the alias (IAM policy).</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UpdateAlias</a> on the current KMS key (key policy).</p>
+ *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UpdateAlias</a> on
+ *           the current KMS key (key policy).</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UpdateAlias</a> on the new KMS key (key policy).</p>
+ *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UpdateAlias</a> on
+ *           the new KMS key (key policy).</p>
  *             </li>
  *          </ul>
- *          <p>For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html#alias-access">Controlling access to aliases</a> in the <i>Key Management Service Developer Guide</i>.</p>
+ *          <p>For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html#alias-access">Controlling access to aliases</a> in the
+ *       <i>Key Management Service Developer Guide</i>.</p>
  *          <p>
  *             <b>Related operations:</b>
  *          </p>
@@ -116,4 +120,3 @@ class UpdateAliasCommand extends smithy_client_1.Command {
     }
 }
 exports.UpdateAliasCommand = UpdateAliasCommand;
-//# sourceMappingURL=UpdateAliasCommand.js.map

package/{dist/cjs → dist-cjs}/commands/UpdateCustomKeyStoreCommand.js

@@ -1,10 +1,10 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.UpdateCustomKeyStoreCommand = void 0;
-const models_0_1 = require("../models/models_0");
-const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
+const models_0_1 = require("../models/models_0");
+const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <p>Changes the properties of a custom key store. Use the <code>CustomKeyStoreId</code>
  *       parameter to identify the custom key store you want to edit. Use the remaining parameters to
@@ -14,29 +14,29 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *       the update completes, use <a>ConnectCustomKeyStore</a>. To find the connection
  *       state of a custom key store, use the <a>DescribeCustomKeyStores</a>
  *       operation.</p>
- *          <p>Use the parameters of <code>UpdateCustomKeyStore</code> to edit your keystore
- *       settings.</p>
+ *          <p>The <code>CustomKeyStoreId</code> parameter is required in all commands. Use the other
+ *       parameters of <code>UpdateCustomKeyStore</code> to edit your key store settings.</p>
  *          <ul>
  *             <li>
- *                <p>Use the <b>NewCustomKeyStoreName</b> parameter to change the
- *           friendly name of the custom key store to the value that you specify.</p>
+ *                <p>Use the <code>NewCustomKeyStoreName</code> parameter to change the friendly name of
+ *           the custom key store to the value that you specify.</p>
  *                <p> </p>
  *             </li>
  *             <li>
- *                <p>Use the <b>KeyStorePassword</b> parameter tell KMS the
- *           current password of the <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-store-concepts.html#concept-kmsuser">
- *                      <code>kmsuser</code> crypto
- *             user (CU)</a> in the associated CloudHSM cluster. You can use this parameter to <a href="https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-password">fix
- *             connection failures</a> that occur when KMS cannot log into the associated cluster
- *           because the <code>kmsuser</code> password has changed. This value does not change the
- *           password in the CloudHSM cluster.</p>
+ *                <p>Use the <code>KeyStorePassword</code> parameter tell KMS the current password of the
+ *             <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-store-concepts.html#concept-kmsuser">
+ *                      <code>kmsuser</code> crypto user (CU)</a> in the associated CloudHSM cluster. You
+ *           can use this parameter to <a href="https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-password">fix connection
+ *             failures</a> that occur when KMS cannot log into the associated cluster because
+ *           the <code>kmsuser</code> password has changed. This value does not change the password in
+ *           the CloudHSM cluster.</p>
  *                <p> </p>
  *             </li>
  *             <li>
- *                <p>Use the <b>CloudHsmClusterId</b> parameter to associate the
- *           custom key store with a different, but related, CloudHSM cluster. You can use this parameter
- *           to repair a custom key store if its CloudHSM cluster becomes corrupted or is deleted, or when
- *           you need to create or restore a cluster from a backup. </p>
+ *                <p>Use the <code>CloudHsmClusterId</code> parameter to associate the custom key store
+ *           with a different, but related, CloudHSM cluster. You can use this parameter to repair a
+ *           custom key store if its CloudHSM cluster becomes corrupted or is deleted, or when you need to
+ *           create or restore a cluster from a backup. </p>
  *             </li>
  *          </ul>
  *          <p>If the operation succeeds, it returns a JSON object with no
@@ -44,9 +44,9 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
  *          <p>This operation is part of the <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">Custom Key Store feature</a> feature in KMS, which
  * combines the convenience and extensive integration of KMS with the isolation and control of a
  * single-tenant key store.</p>
- *
  *          <p>
- *             <b>Cross-account use</b>: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account. </p>
+ *             <b>Cross-account
+ *         use</b>: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account. </p>
  *          <p>
  *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:UpdateCustomKeyStore</a> (IAM policy)</p>
  *          <p>
@@ -130,4 +130,3 @@ class UpdateCustomKeyStoreCommand extends smithy_client_1.Command {
     }
 }
 exports.UpdateCustomKeyStoreCommand = UpdateCustomKeyStoreCommand;
-//# sourceMappingURL=UpdateCustomKeyStoreCommand.js.map