@aws-sdk/client-kms 3.32.0 → 3.36.0

package/{dist/types → dist-types}/commands/SignCommand.d.ts

@@ -1,27 +1,28 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { SignRequest, SignResponse } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface SignCommandInput extends SignRequest {
 }
 export interface SignCommandOutput extends SignResponse, __MetadataBearer {
 }
 /**
  * <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
@@ -43,7 +44,7 @@ export interface SignCommandOutput extends SignResponse, __MetadataBearer {
  *       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>
  *

package/{dist/types → dist-types}/commands/TagResourceCommand.d.ts

@@ -1,7 +1,7 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { TagResourceRequest } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface TagResourceCommandInput extends TagResourceRequest {
 }
 export interface TagResourceCommandOutput extends __MetadataBearer {
@@ -15,16 +15,18 @@ export interface TagResourceCommandOutput extends __MetadataBearer {
  *       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>

package/{dist/types → dist-types}/commands/UntagResourceCommand.d.ts

@@ -1,7 +1,7 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { UntagResourceRequest } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface UntagResourceCommandInput extends UntagResourceRequest {
 }
 export interface UntagResourceCommandOutput extends __MetadataBearer {
@@ -13,8 +13,8 @@ export interface UntagResourceCommandOutput extends __MetadataBearer {
  *             <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
@@ -22,7 +22,7 @@ export interface UntagResourceCommandOutput extends __MetadataBearer {
  *          <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>

package/{dist/types → dist-types}/commands/UpdateAliasCommand.d.ts

@@ -1,15 +1,15 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { UpdateAliasRequest } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface UpdateAliasCommandInput extends UpdateAliasRequest {
 }
 export interface UpdateAliasCommandOutput extends __MetadataBearer {
 }
 /**
- * <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>
@@ -21,12 +21,12 @@ export interface UpdateAliasCommandOutput extends __MetadataBearer {
  *       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>
@@ -34,18 +34,22 @@ export interface UpdateAliasCommandOutput extends __MetadataBearer {
  *          <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>

package/{dist/types → dist-types}/commands/UpdateCustomKeyStoreCommand.d.ts

@@ -1,7 +1,7 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { UpdateCustomKeyStoreRequest, UpdateCustomKeyStoreResponse } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface UpdateCustomKeyStoreCommandInput extends UpdateCustomKeyStoreRequest {
 }
 export interface UpdateCustomKeyStoreCommandOutput extends UpdateCustomKeyStoreResponse, __MetadataBearer {
@@ -15,29 +15,29 @@ export interface UpdateCustomKeyStoreCommandOutput extends UpdateCustomKeyStoreR
  *       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
@@ -45,9 +45,9 @@ export interface UpdateCustomKeyStoreCommandOutput extends UpdateCustomKeyStoreR
  *          <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>

package/{dist/types → dist-types}/commands/UpdateKeyDescriptionCommand.d.ts

@@ -1,18 +1,18 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { UpdateKeyDescriptionRequest } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface UpdateKeyDescriptionCommandInput extends UpdateKeyDescriptionRequest {
 }
 export interface UpdateKeyDescriptionCommandOutput extends __MetadataBearer {
 }
 /**
- * <p>Updates the description of a KMS key. To see the description of a KMS key,
- *       use <a>DescribeKey</a>. </p>
+ * <p>Updates the description of a KMS key. To see the description of a KMS key, use <a>DescribeKey</a>. </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:UpdateKeyDescription</a> (key policy)</p>

package/{dist/types → dist-types}/commands/UpdatePrimaryRegionCommand.d.ts

@@ -1,7 +1,7 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { UpdatePrimaryRegionRequest } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface UpdatePrimaryRegionCommandInput extends UpdatePrimaryRegionRequest {
 }
 export interface UpdatePrimaryRegionCommandOutput extends __MetadataBearer {
@@ -22,7 +22,7 @@ export interface UpdatePrimaryRegionCommandOutput extends __MetadataBearer {
  *       that are always shared by primary and replica keys, including the key material, <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-id">key ID</a>, <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-spec">key spec</a>, <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-usage">key usage</a>, <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-origin">key material
  *       origin</a>, and <a href="https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html">automatic
  *         key rotation</a>. It's the only key that can be replicated. You cannot <a href="https://docs.aws.amazon.com/kms/latest/APIReference/API_ScheduleKeyDeletion.html">delete the primary
- *           key</a> until all replica keys are deleted.</p>
+ *         key</a> until all replica keys are deleted.</p>
  *          <p>The key ID and primary Region that you specify uniquely identify the replica key that will
  *       become the primary key. The primary Region must already have a replica key. This operation
  *       does not create a KMS key in the specified Region. To find the replica keys, use the <a>DescribeKey</a> operation on the primary key or any replica key. To create a replica

package/{dist/types → dist-types}/commands/VerifyCommand.d.ts

@@ -1,7 +1,7 @@
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { KMSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../KMSClient";
 import { VerifyRequest, VerifyResponse } from "../models/models_0";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer } from "@aws-sdk/types";
 export interface VerifyCommandInput extends VerifyRequest {
 }
 export interface VerifyCommandOutput extends VerifyResponse, __MetadataBearer {
@@ -9,9 +9,9 @@ export interface VerifyCommandOutput extends VerifyResponse, __MetadataBearer {
 /**
  * <p>Verifies a digital signature that was generated by the <a>Sign</a> operation. </p>
  *          <p></p>
- *          <p>Verification confirms that an authorized user signed the message with the specified KMS key
- *       and signing algorithm, and the message hasn't changed since it was signed. If the signature is
- *       verified, the value of the <code>SignatureValid</code> field in the response is
+ *          <p>Verification confirms that an authorized user signed the message with the specified KMS
+ *       key and signing algorithm, and the message hasn't changed since it was signed. If the
+ *       signature is verified, the value of the <code>SignatureValid</code> field in the response is
  *         <code>True</code>. If the signature verification fails, the <code>Verify</code> operation
  *       fails with an <code>KMSInvalidSignatureException</code> exception.</p>
  *          <p>A digital signature is generated by using the private key in an asymmetric KMS key. The
@@ -20,8 +20,8 @@ export interface VerifyCommandOutput extends VerifyResponse, __MetadataBearer {
  *          <p>To verify a digital signature, you can use the <code>Verify</code> operation. Specify the
  *       same asymmetric KMS key, message, and signing algorithm that were used to produce the
  *       signature.</p>
- *          <p>You can also verify the digital signature by using the public key of the KMS key outside of
- *       KMS. Use the <a>GetPublicKey</a> operation to download the public key in the
+ *          <p>You can also verify the digital signature by using the public key of the KMS key outside
+ *       of KMS. Use the <a>GetPublicKey</a> operation to download the public key in the
  *       asymmetric KMS key and then use the public key to verify the signature outside of KMS. The
  *       advantage of using the <code>Verify</code> operation is that it is performed within KMS. As
  *       a result, it's easy to call, the operation is performed within the FIPS boundary, it is logged