@aws-sdk/client-kms 3.35.0 → 3.36.0

package/dist-types/KMS.d.ts

@@ -82,10 +82,11 @@ import { KMSClient } from "./KMSClient";
  *          <p>
  *             <b>Logging API Requests</b>
  *          </p>
- *          <p>KMS supports CloudTrail, a service that logs Amazon Web Services API calls and related events for your Amazon Web Services account and delivers them to an Amazon S3 bucket that you specify. By using the information
- *       collected by CloudTrail, you can determine what requests were made to KMS, who made the request,
- *       when it was made, and so on. To learn more about CloudTrail, including how to turn it on and find
- *       your log files, see the <a href="https://docs.aws.amazon.com/awscloudtrail/latest/userguide/">CloudTrail User Guide</a>.</p>
+ *          <p>KMS supports CloudTrail, a service that logs Amazon Web Services API calls and related events for your
+ *       Amazon Web Services account and delivers them to an Amazon S3 bucket that you specify. By using the
+ *       information collected by CloudTrail, you can determine what requests were made to KMS, who made
+ *       the request, when it was made, and so on. To learn more about CloudTrail, including how to turn it
+ *       on and find your log files, see the <a href="https://docs.aws.amazon.com/awscloudtrail/latest/userguide/">CloudTrail User Guide</a>.</p>
  *          <p>
  *             <b>Additional Resources</b>
  *          </p>
@@ -93,9 +94,9 @@ import { KMSClient } from "./KMSClient";
  *          <ul>
  *             <li>
  *                <p>
- *                   <a href="https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html">Amazon Web Services Security
- *             Credentials</a> - This topic provides general information about the types of
- *           credentials used to access Amazon Web Services.</p>
+ *                   <a href="https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html">Amazon Web Services
+ *             Security Credentials</a> - This topic provides general information about the types
+ *           of credentials used to access Amazon Web Services.</p>
  *             </li>
  *             <li>
  *                <p>
@@ -141,13 +142,15 @@ import { KMSClient } from "./KMSClient";
  */
 export declare class KMS extends KMSClient {
     /**
-     * <p>Cancels the deletion of a KMS key. When this operation succeeds, the key
-     *       state of the KMS key is <code>Disabled</code>. To enable the KMS key, use <a>EnableKey</a>. </p>
-     *          <p>For more information about scheduling and canceling deletion of a KMS key, 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>Cancels the deletion of a KMS key. When this operation succeeds, the key state of the KMS
+     *       key is <code>Disabled</code>. To enable the KMS key, use <a>EnableKey</a>. </p>
+     *          <p>For more information about scheduling and canceling deletion of a KMS key, 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>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:CancelKeyDeletion</a> (key policy)</p>
      *          <p>
@@ -159,9 +162,9 @@ export declare class KMS extends KMSClient {
     cancelKeyDeletion(args: CancelKeyDeletionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CancelKeyDeletionCommandOutput) => void): void;
     /**
      * <p>Connects or reconnects a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">custom key store</a> to its associated CloudHSM cluster.</p>
-     *          <p>The custom key store must be connected before you can create KMS keys
-     *       in the key store or use the KMS keys it contains. You can disconnect and reconnect a custom key
-     *       store at any time.</p>
+     *          <p>The custom key store must be connected before you can create KMS keys in the key store or
+     *       use the KMS keys it contains. You can disconnect and reconnect a custom key store at any
+     *       time.</p>
      *          <p>To connect a custom key store, its associated CloudHSM cluster must have at least one active
      *       HSM. To get the number of active HSMs in a cluster, use the <a href="https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_DescribeClusters.html">DescribeClusters</a> operation. To add HSMs
      *       to the cluster, use the <a href="https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html">CreateHsm</a> operation. Also, the <a href="https://docs.aws.amazon.com/kms/latest/developerguide/key-store-concepts.html#concept-kmsuser">
@@ -230,11 +233,12 @@ export declare class KMS extends KMSClient {
      *             <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>
      *          <p>You can use an alias to identify a KMS key in the KMS console, in the <a>DescribeKey</a> operation and in <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</a>, such as <a>Encrypt</a> and
-     *         <a>GenerateDataKey</a>. You can also change the KMS key that's associated with the
-     *       alias (<a>UpdateAlias</a>) or delete the alias (<a>DeleteAlias</a>) at
-     *       any time. These operations don't affect the underlying KMS key. </p>
+     *         <a>GenerateDataKey</a>. You can also change the KMS key that's associated with
+     *       the alias (<a>UpdateAlias</a>) or delete the alias (<a>DeleteAlias</a>)
+     *       at any time. These operations don't affect the underlying KMS key. </p>
      *          <p>You can associate the alias with any customer managed key in the same Amazon Web Services Region. Each
-     *       alias is associated with only one KMS key at a time, but a KMS key can have multiple aliases. A valid KMS key is required. You can't create an alias without a KMS key.</p>
+     *       alias is associated with only one KMS key at a time, but a KMS key can have multiple aliases.
+     *       A valid KMS key is required. You can't create an alias without a KMS key.</p>
      *          <p>The alias must be unique in the account and Region, but you can have aliases with the same
      *       name in different Regions. For detailed information about aliases, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html">Using aliases</a> in the
      *       <i>Key Management Service Developer Guide</i>.</p>
@@ -251,14 +255,17 @@ export declare class KMS extends KMSClient {
      *          <ul>
      *             <li>
      *                <p>
-     *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:CreateAlias</a> on the alias (IAM policy).</p>
+     *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:CreateAlias</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:CreateAlias</a> on the KMS key (key policy).</p>
+     *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:CreateAlias</a> on
+     *           the 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>
@@ -340,7 +347,9 @@ export declare class KMS extends KMSClient {
     createCustomKeyStore(args: CreateCustomKeyStoreCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateCustomKeyStoreCommandOutput) => void): void;
     /**
      * <p>Adds a grant to a KMS key. </p>
-     *          <p>A <i>grant</i> is a policy instrument that allows Amazon Web Services principals to use KMS keys in cryptographic operations. It also can allow them to view a KMS key (<a>DescribeKey</a>) and create and manage grants. When authorizing access to a KMS key, grants are considered along with key policies and IAM policies. Grants are often used for
+     *          <p>A <i>grant</i> is a policy instrument that allows Amazon Web Services principals to use
+     *       KMS keys in cryptographic operations. It also can allow them to view a KMS key (<a>DescribeKey</a>) and create and manage grants. When authorizing access to a KMS key,
+     *       grants are considered along with key policies and IAM policies. Grants are often used for
      *       temporary permissions because you can create one, use its permissions, and delete it without
      *       changing your key policies or IAM policies. </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
@@ -349,28 +358,29 @@ export declare class KMS extends KMSClient {
      *             </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>The <code>CreateGrant</code> operation returns a <code>GrantToken</code> and a
-     *       <code>GrantId</code>.</p>
+     *         <code>GrantId</code>.</p>
      *          <ul>
      *             <li>
-     *                <p>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 <i>eventual consistency</i>. Once the grant has achieved eventual consistency, the grantee principal
-     *         can use the permissions in the grant without identifying the grant. </p>
+     *                <p>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 <i>eventual consistency</i>. Once the grant has achieved eventual consistency, the grantee
+     *           principal can use the permissions in the grant without identifying the grant. </p>
      *                <p>However, to use the permissions in the grant immediately, use the
-     *           <code>GrantToken</code> that <code>CreateGrant</code> returns. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token">Using a grant
-     *             token</a> in the <i>
+     *             <code>GrantToken</code> that <code>CreateGrant</code> returns. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token">Using a
+     *             grant token</a> in the <i>
      *                      <i>Key Management Service Developer Guide</i>
      *                   </i>.</p>
      *             </li>
      *             <li>
-     *                <p>The <code>CreateGrant</code> operation also returns a <code>GrantId</code>. You can use the
-     *         <code>GrantId</code> and a key identifier to identify the grant in the <a>RetireGrant</a> and <a>RevokeGrant</a> operations. To find the grant
-     *         ID, use the <a>ListGrants</a> or <a>ListRetirableGrants</a>
-     *         operations.</p>
+     *                <p>The <code>CreateGrant</code> operation also returns a <code>GrantId</code>. You can
+     *           use the <code>GrantId</code> and a key identifier to identify the grant in the <a>RetireGrant</a> and <a>RevokeGrant</a> operations. To find the grant
+     *           ID, use the <a>ListGrants</a> or <a>ListRetirableGrants</a>
+     *           operations.</p>
      *             </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. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key
+     *             <b>Cross-account use</b>: Yes.
+     *       To perform this operation on a KMS key in a different Amazon Web Services account, specify the key
      *   ARN in the value of the <code>KeyId</code> parameter. </p>
      *          <p>
      *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:CreateGrant</a> (key policy)</p>
@@ -404,20 +414,21 @@ export declare class KMS extends KMSClient {
     createGrant(args: CreateGrantCommandInput, cb: (err: any, data?: CreateGrantCommandOutput) => void): void;
     createGrant(args: CreateGrantCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateGrantCommandOutput) => void): void;
     /**
-     * <p>Creates a unique customer managed <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms-keys">KMS key</a> in your Amazon Web Services account and Region.</p>
+     * <p>Creates a unique customer managed <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms-keys">KMS key</a> in your Amazon Web Services account and
+     *       Region.</p>
      *          <note>
      *             <p>KMS is replacing the term <i>customer master key (CMK)</i> with <i>KMS key</i> and <i>KMS key</i>. The concept has not changed. To prevent breaking changes, KMS is keeping some variations of this term.</p>
      *          </note>
      *
-     *          <p>You can use the <code>CreateKey</code> operation to create symmetric or asymmetric KMS keys.</p>
+     *          <p>You can use the <code>CreateKey</code> operation to create symmetric or asymmetric KMS
+     *       keys.</p>
      *          <ul>
      *             <li>
      *                <p>
-     *                   <b>Symmetric KMS keys</b> contain a 256-bit symmetric key that
-     *           never leaves KMS unencrypted. To use the KMS key, you must call KMS. You can use a
-     *           symmetric KMS key to encrypt and decrypt small amounts of data, but they are typically used to
-     *           generate <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#data-keys">data
-     *             keys</a> and <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#data-key-pairs">data keys pairs</a>. For details,
+     *                   <b>Symmetric KMS keys</b> contain a 256-bit symmetric key
+     *           that never leaves KMS unencrypted. To use the KMS key, you must call KMS. You can use
+     *           a symmetric KMS key to encrypt and decrypt small amounts of data, but they are typically
+     *           used to generate <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#data-keys">data keys</a> and <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#data-key-pairs">data keys pairs</a>. For details,
      *           see <a>GenerateDataKey</a> and <a>GenerateDataKeyPair</a>.</p>
      *             </li>
      *             <li>
@@ -425,9 +436,9 @@ export declare class KMS extends KMSClient {
      *                   <b>Asymmetric KMS keys</b> can contain an RSA key pair or an
      *           Elliptic Curve (ECC) key pair. The private key in an asymmetric KMS key never leaves KMS
      *           unencrypted. However, you can use the <a>GetPublicKey</a> operation to download
-     *           the public key so it can be used outside of KMS. KMS keys with RSA key pairs can be used to
-     *           encrypt or decrypt data or sign and verify messages (but not both). KMS keys with ECC key
-     *           pairs can be used only to sign and verify messages.</p>
+     *           the public key so it can be used outside of KMS. KMS keys with RSA key pairs can be used
+     *           to encrypt or decrypt data or sign and verify messages (but not both). KMS keys with ECC
+     *           key pairs can be used only to sign and verify messages.</p>
      *             </li>
      *          </ul>
      *          <p>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>
@@ -458,8 +469,8 @@ export declare class KMS extends KMSClient {
      *             <dd>
      *                <p>To create a multi-Region <i>primary key</i> in the local Amazon Web Services Region,
      *             use the <code>MultiRegion</code> parameter with a value of <code>True</code>. To create
-     *             a multi-Region <i>replica key</i>, that is, a KMS key with the same key ID and
-     *             key material as a primary key, but in a different Amazon Web Services Region, use the <a>ReplicateKey</a> operation. To change a replica key to a primary key, and its
+     *             a multi-Region <i>replica key</i>, that is, a KMS key with the same key ID
+     *             and key material as a primary key, but in a different Amazon Web Services Region, use the <a>ReplicateKey</a> operation. To change a replica key to a primary key, and its
      *             primary key to a replica key, use the <a>UpdatePrimaryRegion</a>
      *             operation.</p>
      *                <p>This operation supports <i>multi-Region keys</i>, an KMS feature that lets you create multiple
@@ -500,13 +511,14 @@ export declare class KMS extends KMSClient {
      *             </dd>
      *          </dl>
      *          <p>
-     *             <b>Cross-account use</b>:  No. You cannot use this operation to
+     *             <b>Cross-account use</b>: No. You cannot use this operation to
      *       create 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:CreateKey</a> (IAM policy). To use the
      *         <code>Tags</code> parameter, <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:TagResource</a> (IAM policy). For examples and information about related
-     *       permissions, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policy-example-create-key">Allow a user to create KMS keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
+     *       permissions, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policy-example-create-key">Allow a user to create
+     *         KMS keys</a> in the <i>Key Management Service Developer Guide</i>.</p>
      *          <p>
      *             <b>Related operations:</b>
      *          </p>
@@ -532,8 +544,8 @@ export declare class KMS extends KMSClient {
     createKey(args: CreateKeyCommandInput, cb: (err: any, data?: CreateKeyCommandOutput) => void): void;
     createKey(args: CreateKeyCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateKeyCommandOutput) => void): void;
     /**
-     * <p>Decrypts ciphertext that was encrypted by a KMS key using any of
-     *       the following operations:</p>
+     * <p>Decrypts ciphertext that was encrypted by a KMS key using any of the following
+     *       operations:</p>
      *          <ul>
      *             <li>
      *                <p>
@@ -562,33 +574,36 @@ export declare class KMS extends KMSClient {
      *             </li>
      *          </ul>
      *          <p>You can use this operation to decrypt ciphertext that was encrypted under a symmetric or
-     *       asymmetric KMS key. When the KMS key is asymmetric, you must specify the KMS key and the encryption
-     *       algorithm that was used to encrypt the ciphertext. 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>
+     *       asymmetric KMS key. When the KMS key is asymmetric, you must specify the KMS key and the
+     *       encryption algorithm that was used to encrypt the ciphertext. 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>The Decrypt operation also decrypts ciphertext that was encrypted outside of KMS by the
-     *       public key in an KMS asymmetric KMS key. 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>If the ciphertext was encrypted under a symmetric KMS key, the <code>KeyId</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 KMS key is always recommended as a best practice.
-     *       When you use the <code>KeyId</code> parameter to specify a KMS key, KMS only uses the KMS key you
-     *       specify. If the ciphertext was encrypted under a different KMS key, the <code>Decrypt</code>
-     *       operation fails. This practice ensures that you use the KMS key that you intend.</p>
+     *       public key in an KMS asymmetric KMS key. 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>If the ciphertext was encrypted under a symmetric KMS key, the <code>KeyId</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 KMS key is always recommended as a best
+     *       practice. When you use the <code>KeyId</code> parameter to specify a KMS key, KMS only uses
+     *       the KMS key you specify. If the ciphertext was encrypted under a different KMS key, the
+     *         <code>Decrypt</code> operation fails. This practice ensures that you use the KMS key that
+     *       you intend.</p>
      *          <p>Whenever possible, use key policies to give users permission to call the
      *         <code>Decrypt</code> operation on a particular KMS key, instead of using IAM policies.
      *       Otherwise, you might create an IAM user policy that gives the user <code>Decrypt</code>
-     *       permission on all KMS keys. This user could decrypt ciphertext that was encrypted by KMS keys in other
-     *       accounts if the key policy for the cross-account KMS key permits it. If you must use an IAM policy
-     *       for <code>Decrypt</code> permissions, limit the user to particular KMS keys or particular trusted
-     *       accounts. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policies-best-practices">Best practices for IAM policies</a> in the <i>Key Management Service Developer Guide</i>.</p>
+     *       permission on all KMS keys. This user could decrypt ciphertext that was encrypted by KMS keys
+     *       in other accounts if the key policy for the cross-account KMS key permits it. If you must use
+     *       an IAM policy for <code>Decrypt</code> permissions, limit the user to particular KMS keys or
+     *       particular trusted accounts. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policies-best-practices">Best practices for IAM
+     *         policies</a> in the <i>Key Management Service Developer Guide</i>.</p>
      *          <p>Applications in Amazon Web Services Nitro Enclaves can call this operation by using the <a href="https://github.com/aws/aws-nitro-enclaves-sdk-c">Amazon Web Services Nitro Enclaves Development Kit</a>. For information about the supporting parameters, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/services-nitro-enclaves.html">How Amazon Web Services Nitro Enclaves use KMS</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>: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify
+     *             <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>
      *
      *          <p>
@@ -623,14 +638,15 @@ export declare class KMS extends KMSClient {
     decrypt(args: DecryptCommandInput, cb: (err: any, data?: DecryptCommandOutput) => void): void;
     decrypt(args: DecryptCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DecryptCommandOutput) => void): void;
     /**
-     * <p>Deletes the specified alias.  </p>
+     * <p>Deletes the specified alias. </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>
-     *          <p>Because an alias is not a property of a KMS key, you can delete and change 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, use the <a>ListAliases</a> operation. </p>
+     *          <p>Because an alias is not a property of a KMS key, you can delete and change 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, use the <a>ListAliases</a> operation. </p>
      *          <p>Each KMS key can have multiple aliases. To change the alias of a KMS key, use <a>DeleteAlias</a> to delete the current alias and <a>CreateAlias</a> to
-     *       create a new alias. To associate an existing alias with a different KMS key,
-     *       call <a>UpdateAlias</a>.</p>
+     *       create a new alias. To associate an existing alias with a different KMS key, call <a>UpdateAlias</a>.</p>
      *          <p>
      *             <b>Cross-account use</b>: No. You cannot perform this operation on an alias in a different Amazon Web Services account.</p>
      *          <p>
@@ -639,14 +655,17 @@ export declare class KMS extends KMSClient {
      *          <ul>
      *             <li>
      *                <p>
-     *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:DeleteAlias</a> on the alias (IAM policy).</p>
+     *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:DeleteAlias</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:DeleteAlias</a> on the KMS key (key policy).</p>
+     *                   <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:DeleteAlias</a> on
+     *           the 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>
@@ -674,16 +693,15 @@ export declare class KMS extends KMSClient {
     /**
      * <p>Deletes a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">custom key store</a>. This operation does not delete the CloudHSM cluster that is
      *       associated with the custom key store, or affect any users or keys in the cluster.</p>
-     *          <p>The custom key store that you delete cannot contain any KMS <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys">KMS keys</a>. Before
-     *       deleting the key store, verify that you will never need to use any of the KMS keys in the key
-     *       store for any <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</a>. Then, use <a>ScheduleKeyDeletion</a> to delete the
-     *       KMS keys from the key store. When the scheduled waiting period
-     *       expires, the <code>ScheduleKeyDeletion</code> operation deletes the KMS keys. Then it makes a best
-     *       effort to delete the key material from the associated 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
+     *          <p>The custom key store that you delete cannot contain any KMS <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys">KMS keys</a>. Before deleting the key store,
+     *       verify that you will never need to use any of the KMS keys in the key store for any
+     *       <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</a>. Then, use <a>ScheduleKeyDeletion</a> to delete the KMS keys from the
+     *       key store. When the scheduled waiting period expires, the <code>ScheduleKeyDeletion</code>
+     *       operation deletes the KMS keys. Then it makes a best effort to delete the key material from
+     *       the associated 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>After all KMS keys are deleted from KMS, use <a>DisconnectCustomKeyStore</a> to
-     *       disconnect the key store from KMS. Then, you can delete the custom key store.</p>
+     *          <p>After all KMS keys are deleted from KMS, use <a>DisconnectCustomKeyStore</a>
+     *       to disconnect the key store from KMS. Then, you can delete the custom key store.</p>
      *          <p>Instead of deleting the custom key store, consider using <a>DisconnectCustomKeyStore</a> to disconnect it from KMS. While the key store is
      *       disconnected, you cannot create or use the KMS keys in the key store. But, you do not need to
      *       delete KMS keys and you can reconnect a disconnected custom key store at any time.</p>
@@ -692,9 +710,9 @@ export declare class KMS extends KMSClient {
      *          <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:DeleteCustomKeyStore</a> (IAM policy)</p>
@@ -733,12 +751,11 @@ export declare class KMS extends KMSClient {
     deleteCustomKeyStore(args: DeleteCustomKeyStoreCommandInput, cb: (err: any, data?: DeleteCustomKeyStoreCommandOutput) => void): void;
     deleteCustomKeyStore(args: DeleteCustomKeyStoreCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteCustomKeyStoreCommandOutput) => void): void;
     /**
-     * <p>Deletes key material that you previously imported. This operation makes the specified
-     *       KMS key unusable. For more information about importing key material into
-     *       KMS, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">Importing Key
-     *         Material</a> in the <i>Key Management Service Developer Guide</i>. </p>
-     *          <p>When the specified KMS key is in the <code>PendingDeletion</code> state, this operation does
-     *       not change the KMS key's state. Otherwise, it changes the KMS key's state to
+     * <p>Deletes key material that you previously imported. This operation makes the specified KMS
+     *       key unusable. For more information about importing key material into KMS, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">Importing Key Material</a>
+     *       in the <i>Key Management Service Developer Guide</i>. </p>
+     *          <p>When the specified KMS key is in the <code>PendingDeletion</code> state, this operation
+     *       does not change the KMS key's state. Otherwise, it changes the KMS key's state to
      *         <code>PendingImport</code>.</p>
      *          <p>After you delete key material, you can use <a>ImportKeyMaterial</a> to reimport
      *       the same key material into the KMS key.</p>
@@ -773,10 +790,10 @@ export declare class KMS extends KMSClient {
      *          <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>By default, this operation returns information about all custom key stores in the account and
-     *       Region. To get only information about a particular custom key store, use either the
-     *         <code>CustomKeyStoreName</code> or <code>CustomKeyStoreId</code> parameter (but not
-     *       both).</p>
+     *          <p>By default, this operation returns information about all custom key
+     *       stores in the account and Region. To get only information about a particular custom key store,
+     *       use either the <code>CustomKeyStoreName</code> or <code>CustomKeyStoreId</code> parameter (but
+     *       not both).</p>
      *          <p>To determine whether the custom key store is connected to its CloudHSM cluster, use the
      *         <code>ConnectionState</code> element in the response. If an attempt to connect the custom
      *       key store failed, the <code>ConnectionState</code> value is <code>FAILED</code> and the
@@ -828,16 +845,17 @@ export declare class KMS extends KMSClient {
     describeCustomKeyStores(args: DescribeCustomKeyStoresCommandInput, cb: (err: any, data?: DescribeCustomKeyStoresCommandOutput) => void): void;
     describeCustomKeyStores(args: DescribeCustomKeyStoresCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeCustomKeyStoresCommandOutput) => void): void;
     /**
-     * <p>Provides detailed information about a KMS key. You can run
-     *         <code>DescribeKey</code> on a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a> or an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed key</a>.</p>
+     * <p>Provides detailed information about a KMS key. You can run <code>DescribeKey</code> on a
+     *         <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed
+     *         key</a> or an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed key</a>.</p>
      *          <p>This detailed information includes the key ARN, creation date (and deletion date, if
      *       applicable), the key state, and the origin and expiration date (if any) of the key material.
      *       It includes fields, like <code>KeySpec</code>, that help you distinguish symmetric from
      *       asymmetric KMS keys. It also provides information that is particularly important to asymmetric
      *       keys, such as the key usage (encryption or signing) and the encryption algorithms or signing
-     *       algorithms that the KMS key supports. For KMS keys in custom key stores, it includes information about
-     *       the custom key store, such as the key store ID and the CloudHSM cluster ID. For multi-Region
-     *       keys, it displays the primary key and all related replica keys. </p>
+     *       algorithms that the KMS key supports. For KMS keys in custom key stores, it includes
+     *       information about the custom key store, such as the key store ID and the CloudHSM cluster ID. For
+     *       multi-Region keys, it displays the primary key and all related replica keys. </p>
      *          <p>
      *             <code>DescribeKey</code> does not return the following information:</p>
      *          <ul>
@@ -846,8 +864,8 @@ export declare class KMS extends KMSClient {
      *             </li>
      *             <li>
      *                <p>Whether automatic key rotation is enabled on the KMS key. To get this information, use
-     *             <a>GetKeyRotationStatus</a>. Also, some key states prevent a KMS key from being
-     *           automatically rotated. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-how-it-works">How Automatic Key Rotation
+     *             <a>GetKeyRotationStatus</a>. Also, some key states prevent a KMS key from
+     *           being automatically rotated. For details, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-how-it-works">How Automatic Key Rotation
      *             Works</a> in <i>Key Management Service Developer Guide</i>.</p>
      *             </li>
      *             <li>
@@ -857,9 +875,10 @@ export declare class KMS extends KMSClient {
      *                <p>Key policies and grants on the KMS key. To get this information, use <a>GetKeyPolicy</a> and <a>ListGrants</a>.</p>
      *             </li>
      *          </ul>
-     *          <p>If you call the <code>DescribeKey</code> operation on a <i>predefined Amazon Web Services alias</i>, that is, an Amazon Web Services alias with no key ID, KMS creates an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed key</a>.
-     *       Then, it associates the alias with the new KMS key, and returns the <code>KeyId</code> and
-     *         <code>Arn</code> of the new KMS key in the response.</p>
+     *          <p>If you call the <code>DescribeKey</code> operation on a <i>predefined Amazon Web Services
+     *         alias</i>, that is, an Amazon Web Services alias with no key ID, KMS creates an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed
+     *         key</a>. Then, it associates the alias with the new KMS key, and returns the
+     *         <code>KeyId</code> and <code>Arn</code> of the new KMS key in the response.</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>
@@ -911,14 +930,15 @@ export declare class KMS extends KMSClient {
     describeKey(args: DescribeKeyCommandInput, cb: (err: any, data?: DescribeKeyCommandOutput) => void): void;
     describeKey(args: DescribeKeyCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeKeyCommandOutput) => void): void;
     /**
-     * <p>Sets the state of a KMS key to disabled. This change temporarily
-     *       prevents use of the KMS key for <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</a>. </p>
-     *          <p>For more information about how key state affects the use of a KMS key, 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>
+     * <p>Sets the state of a KMS key to disabled. This change temporarily prevents use of the KMS
+     *       key for <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</a>. </p>
+     *          <p>For more information about how key state affects the use of a KMS key, 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>
      *                <i>Key Management Service Developer Guide</i>
      *             </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>
+     *         <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>
@@ -937,7 +957,8 @@ export declare class KMS extends KMSClient {
      *          <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:DisableKeyRotation</a> (key policy)</p>
@@ -962,8 +983,9 @@ export declare class KMS extends KMSClient {
     disableKeyRotation(args: DisableKeyRotationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DisableKeyRotationCommandOutput) => void): void;
     /**
      * <p>Disconnects the <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">custom key store</a> from its associated CloudHSM cluster. While a custom key
-     *       store is disconnected, you can manage the custom key store and its KMS keys, but you cannot create or use KMS keys in the custom key store. You can reconnect the
-     *       custom key store at any time.</p>
+     *       store is disconnected, you can manage the custom key store and its KMS keys, but you cannot
+     *       create or use KMS keys in the custom key store. You can reconnect the custom key store at any
+     *       time.</p>
      *          <note>
      *             <p>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 <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</a> will
      *         fail. This action can prevent users from storing and accessing sensitive data.</p>
@@ -977,8 +999,9 @@ export declare class KMS extends KMSClient {
      * 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>
+     *         <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:DisconnectCustomKeyStore</a> (IAM policy)</p>
@@ -1017,11 +1040,13 @@ export declare class KMS extends KMSClient {
     disconnectCustomKeyStore(args: DisconnectCustomKeyStoreCommandInput, cb: (err: any, data?: DisconnectCustomKeyStoreCommandOutput) => void): void;
     disconnectCustomKeyStore(args: DisconnectCustomKeyStoreCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DisconnectCustomKeyStoreCommandOutput) => void): void;
     /**
-     * <p>Sets the key state of a KMS key to enabled. This allows you to use the KMS key for <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</a>. </p>
+     * <p>Sets the key state of a KMS key to enabled. This allows you to use the KMS key for
+     *       <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations">cryptographic operations</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:EnableKey</a> (key policy)</p>
@@ -1039,7 +1064,8 @@ export declare class KMS extends KMSClient {
      *          <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:EnableKeyRotation</a> (key policy)</p>
@@ -1063,19 +1089,20 @@ export declare class KMS extends KMSClient {
     enableKeyRotation(args: EnableKeyRotationCommandInput, cb: (err: any, data?: EnableKeyRotationCommandOutput) => void): void;
     enableKeyRotation(args: EnableKeyRotationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: EnableKeyRotationCommandOutput) => void): void;
     /**
-     * <p>Encrypts plaintext into ciphertext by using a KMS key. The
-     *         <code>Encrypt</code> operation has two primary use cases:</p>
+     * <p>Encrypts plaintext into ciphertext by using a KMS key. The <code>Encrypt</code> operation
+     *       has two primary use cases:</p>
      *          <ul>
      *             <li>
      *                <p>You can encrypt small amounts of arbitrary data, such as a personal identifier or
      *           database password, or other sensitive information. </p>
      *             </li>
      *             <li>
-     *                <p>You can use the <code>Encrypt</code> operation to move encrypted data from one Amazon Web Services Region to another. For example, in Region A, generate a data key and use the plaintext key to encrypt
-     *           your data. Then, in Region A, use the <code>Encrypt</code> operation to encrypt the
-     *           plaintext data key under a KMS key in Region B. Now, you can move the encrypted data and the
-     *           encrypted data key to Region B. When necessary, you can decrypt the encrypted data key and
-     *           the encrypted data entirely within in Region B.</p>
+     *                <p>You can use the <code>Encrypt</code> operation to move encrypted data from one Amazon Web Services
+     *           Region to another. For example, in Region A, generate a data key and use the plaintext key
+     *           to encrypt your data. Then, in Region A, use the <code>Encrypt</code> operation to encrypt
+     *           the plaintext data key under a KMS key in Region B. Now, you can move the encrypted data
+     *           and the encrypted data key to Region B. When necessary, you can decrypt the encrypted data
+     *           key and the encrypted data entirely within in Region B.</p>
      *             </li>
      *          </ul>
      *
@@ -1086,10 +1113,10 @@ export declare class KMS extends KMSClient {
      *       encryption operation. The KMS key must have a <code>KeyUsage</code> value of
      *         <code>ENCRYPT_DECRYPT.</code> To find the <code>KeyUsage</code> of a KMS key, use the <a>DescribeKey</a> operation. </p>
      *
-     *          <p>If you use a symmetric KMS key, you can use an encryption context to add additional security
-     *       to your encryption operation. If you specify an <code>EncryptionContext</code> when encrypting
-     *       data, you must specify the same encryption context (a case-sensitive exact match) when
-     *       decrypting the data. Otherwise, the request to decrypt fails with an
+     *          <p>If you use a symmetric KMS key, you can use an encryption context to add additional
+     *       security to your encryption operation. If you specify an <code>EncryptionContext</code> when
+     *       encrypting data, you must specify the same encryption context (a case-sensitive exact match)
+     *       when decrypting the data. Otherwise, the request to decrypt fails with an
      *         <code>InvalidCiphertextException</code>. For more information, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context">Encryption
      *         Context</a> in the <i>Key Management Service Developer Guide</i>.</p>
      *          <p>If you specify an asymmetric KMS key, you must also specify the encryption algorithm. The
@@ -1161,7 +1188,8 @@ export declare class KMS extends KMSClient {
      *          <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. To perform this operation with a KMS key in a different Amazon Web Services account, specify
+     *             <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>
      *
      *          <p>
@@ -1192,19 +1220,19 @@ export declare class KMS extends KMSClient {
     encrypt(args: EncryptCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: EncryptCommandOutput) => void): void;
     /**
      * <p>Generates a unique symmetric data key for client-side encryption. This operation returns a
-     *       plaintext copy of the data key and a copy that is encrypted under a KMS key
-     *       that you specify. You can use the plaintext key to encrypt your data outside of KMS and
-     *       store the encrypted data key with the encrypted data.</p>
+     *       plaintext copy of the data key and a copy that is encrypted under a KMS key that you specify.
+     *       You can use the plaintext key to encrypt your data outside of KMS and store the encrypted
+     *       data key with the encrypted data.</p>
      *
      *          <p>
      *             <code>GenerateDataKey</code> returns a unique data key for each request. The bytes in the
      *       plaintext key are not related to the caller or the KMS key.</p>
      *
-     *          <p>To generate a data key, specify the symmetric KMS key that will be used to encrypt the data
-     *       key. You cannot use an asymmetric KMS key to generate data keys. To get the type of your KMS key, use
-     *       the <a>DescribeKey</a> operation. You must also specify the length of the data key.
-     *       Use either the <code>KeySpec</code> or <code>NumberOfBytes</code> parameters (but not both).
-     *       For 128-bit and 256-bit data keys, use the <code>KeySpec</code> parameter. </p>
+     *          <p>To generate a data key, specify the symmetric KMS key that will be used to encrypt the
+     *       data key. You cannot use an asymmetric KMS key to generate data keys. To get the type of your
+     *       KMS key, use the <a>DescribeKey</a> operation. You must also specify the length of
+     *       the data key. Use either the <code>KeySpec</code> or <code>NumberOfBytes</code> parameters
+     *       (but not both). For 128-bit and 256-bit data keys, use the <code>KeySpec</code> parameter. </p>
      *
      *          <p>To get only an encrypted copy of the data key, use <a>GenerateDataKeyWithoutPlaintext</a>. To generate an asymmetric data key pair, use
      *       the <a>GenerateDataKeyPair</a> or <a>GenerateDataKeyPairWithoutPlaintext</a> operation. To get a cryptographically secure
@@ -1219,11 +1247,14 @@ export declare class KMS extends KMSClient {
      *          <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>How to use your data key</b>
+     *             <b>How to use your data
+     *         key</b>
      *          </p>
-     *          <p>We recommend that you use the following pattern to encrypt data locally in your application.
-     *       You can write your own code or use a client-side encryption library, such as the <a href="https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/">Amazon Web Services Encryption SDK</a>, the <a href="https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/">Amazon DynamoDB Encryption Client</a>, or
-     *         <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html">Amazon S3
+     *          <p>We recommend that you use the following pattern to encrypt data locally in your
+     *       application. You can write your own code or use a client-side encryption library, such as the
+     *         <a href="https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/">Amazon Web Services Encryption SDK</a>, the
+     *         <a href="https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/">Amazon DynamoDB Encryption Client</a>,
+     *       or <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html">Amazon S3
      *         client-side encryption</a> to do these tasks for you.</p>
      *          <p>To encrypt data outside of KMS:</p>
      *          <ol>
@@ -1293,20 +1324,21 @@ export declare class KMS extends KMSClient {
     /**
      * <p>Generates a unique asymmetric data key pair. The <code>GenerateDataKeyPair</code>
      *       operation returns a plaintext public key, a plaintext private key, and a copy of the private
-     *       key that is encrypted under the symmetric KMS key you specify. You can use the data key pair to
-     *       perform asymmetric cryptography and implement digital signatures outside of KMS.</p>
+     *       key that is encrypted under the symmetric KMS key you specify. You can use the data key pair
+     *       to perform asymmetric cryptography and implement digital signatures outside of KMS.</p>
      *
      *          <p>You can use the public key that <code>GenerateDataKeyPair</code> returns to encrypt data
      *       or verify a signature outside of KMS. Then, store the encrypted private key with the data.
      *       When you are ready to decrypt data or sign a message, you can use the <a>Decrypt</a> operation to decrypt the encrypted private key.</p>
      *
-     *          <p>To generate a data key pair, you must specify a symmetric KMS key to
-     *       encrypt the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a
-     *       custom key store. To get the type and origin of your KMS key, use the <a>DescribeKey</a> operation. </p>
+     *          <p>To generate a data key pair, you must specify a symmetric KMS key to encrypt the private
+     *       key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a custom key
+     *       store. To get the type and origin of your KMS key, use the <a>DescribeKey</a>
+     *       operation. </p>
      *          <p>Use the <code>KeyPairSpec</code> parameter to choose an RSA or Elliptic Curve (ECC) data
-     *       key pair. KMS recommends that your use ECC key pairs for signing, and use RSA key pairs
-     *       for either encryption or signing, but not both. However, KMS cannot enforce any restrictions
-     *       on the use of data key pairs outside of KMS.</p>
+     *       key pair. KMS recommends that your use ECC key pairs for signing, and use RSA key pairs for
+     *       either encryption or signing, but not both. However, KMS cannot enforce any restrictions on
+     *       the use of data key pairs outside of KMS.</p>
      *
      *          <p>If you are using the data key pair to encrypt data, or for any operation where you don't
      *       immediately need a private key, consider using the <a>GenerateDataKeyPairWithoutPlaintext</a> operation.
@@ -1318,10 +1350,10 @@ export declare class KMS extends KMSClient {
      *
      *          <p>
      *             <code>GenerateDataKeyPair</code> returns a unique data key pair for each request. The
-     *       bytes in the keys are not related to the caller or the KMS key that is used to encrypt the private
-     *       key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in <a href="https://tools.ietf.org/html/rfc5280">RFC 5280</a>. The
-     *       private key is a DER-encoded PKCS8 PrivateKeyInfo, as specified in <a href="https://tools.ietf.org/html/rfc5958">RFC
-     *         5958</a>.</p>
+     *       bytes in the keys are not related to the caller or the KMS key that is used to encrypt the
+     *       private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in
+     *         <a href="https://tools.ietf.org/html/rfc5280">RFC 5280</a>. The private key is a
+     *       DER-encoded PKCS8 PrivateKeyInfo, as specified in <a href="https://tools.ietf.org/html/rfc5958">RFC 5958</a>.</p>
      *
      *          <p>You can use the optional encryption context to add additional security to the encryption
      *       operation. If you specify an <code>EncryptionContext</code>, you must specify the same
@@ -1331,7 +1363,8 @@ export declare class KMS extends KMSClient {
      *          <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. To perform this operation with a KMS key in a different Amazon Web Services account, specify
+     *             <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>
      *
      *          <p>
@@ -1373,23 +1406,24 @@ export declare class KMS extends KMSClient {
     /**
      * <p>Generates a unique asymmetric data key pair. The
      *         <code>GenerateDataKeyPairWithoutPlaintext</code> operation returns a plaintext public key
-     *       and a copy of the private key that is encrypted under the symmetric KMS key you specify. Unlike
-     *         <a>GenerateDataKeyPair</a>, this operation does not return a plaintext private
-     *       key. </p>
+     *       and a copy of the private key that is encrypted under the symmetric KMS key you specify.
+     *       Unlike <a>GenerateDataKeyPair</a>, this operation does not return a plaintext
+     *       private key. </p>
      *          <p>You can use the public key that <code>GenerateDataKeyPairWithoutPlaintext</code> returns
      *       to encrypt data or verify a signature outside of KMS. Then, store the encrypted private key
      *       with the data. When you are ready to decrypt data or sign a message, you can use the <a>Decrypt</a> operation to decrypt the encrypted private key.</p>
-     *          <p>To generate a data key pair, you must specify a symmetric KMS key to
-     *       encrypt the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a
-     *       custom key store. To get the type and origin of your KMS key, use the <a>DescribeKey</a> operation. </p>
+     *          <p>To generate a data key pair, you must specify a symmetric KMS key to encrypt the private
+     *       key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a custom key
+     *       store. To get the type and origin of your KMS key, use the <a>DescribeKey</a>
+     *       operation. </p>
      *          <p>Use the <code>KeyPairSpec</code> parameter to choose an RSA or Elliptic Curve (ECC) data
-     *       key pair. KMS recommends that your use ECC key pairs for signing, and use RSA key pairs
-     *       for either encryption or signing, but not both. However, KMS cannot enforce any restrictions
-     *       on the use of data key pairs outside of KMS.</p>
+     *       key pair. KMS recommends that your use ECC key pairs for signing, and use RSA key pairs for
+     *       either encryption or signing, but not both. However, KMS cannot enforce any restrictions on
+     *       the use of data key pairs outside of KMS.</p>
      *          <p>
      *             <code>GenerateDataKeyPairWithoutPlaintext</code> returns a unique data key pair for each
-     *       request. The bytes in the key are not related to the caller or KMS key that is used to encrypt the
-     *       private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in
+     *       request. The bytes in the key are not related to the caller or KMS key that is used to encrypt
+     *       the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in
      *         <a href="https://tools.ietf.org/html/rfc5280">RFC 5280</a>.</p>
      *
      *          <p>You can use the optional encryption context to add additional security to the encryption
@@ -1400,11 +1434,13 @@ export declare class KMS extends KMSClient {
      *          <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. To perform this operation with a KMS key in a different Amazon Web Services account, specify
+     *             <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>
      *
      *          <p>
-     *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:GenerateDataKeyPairWithoutPlaintext</a> (key policy)</p>
+     *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:GenerateDataKeyPairWithoutPlaintext</a> (key
+     *       policy)</p>
      *          <p>
      *             <b>Related operations:</b>
      *          </p>
@@ -1441,8 +1477,8 @@ export declare class KMS extends KMSClient {
     generateDataKeyPairWithoutPlaintext(args: GenerateDataKeyPairWithoutPlaintextCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GenerateDataKeyPairWithoutPlaintextCommandOutput) => void): void;
     /**
      * <p>Generates a unique symmetric data key. This operation returns a data key that is encrypted
-     *       under a KMS key that you specify. To request an asymmetric data key pair,
-     *       use the <a>GenerateDataKeyPair</a> or <a>GenerateDataKeyPairWithoutPlaintext</a> operations.</p>
+     *       under a KMS key that you specify. To request an asymmetric data key pair, use the <a>GenerateDataKeyPair</a> or <a>GenerateDataKeyPairWithoutPlaintext</a>
+     *       operations.</p>
      *          <p>
      *             <code>GenerateDataKeyWithoutPlaintext</code> is identical to the <a>GenerateDataKey</a> operation except that returns only the encrypted copy of the
      *       data key. This operation is useful for systems that need to encrypt data at some point, but
@@ -1457,12 +1493,12 @@ export declare class KMS extends KMSClient {
      *       plaintext data key.</p>
      *          <p>
      *             <code>GenerateDataKeyWithoutPlaintext</code> returns a unique data key for each request.
-     *       The bytes in the keys are not related to the caller or KMS key that is used to encrypt the private
-     *       key.</p>
+     *       The bytes in the keys are not related to the caller or KMS key that is used to encrypt the
+     *       private key.</p>
      *
-     *          <p>To generate a data key, you must specify the symmetric KMS key that is
-     *       used to encrypt the data key. You cannot use an asymmetric KMS key to generate a data key. To get
-     *       the type of your KMS key, use the <a>DescribeKey</a> operation.</p>
+     *          <p>To generate a data key, you must specify the symmetric KMS key that is used to encrypt the
+     *       data key. You cannot use an asymmetric KMS key to generate a data key. To get the type of your
+     *       KMS key, use the <a>DescribeKey</a> operation.</p>
      *
      *          <p>If the operation succeeds, you will find the encrypted copy of the data key in the
      *         <code>CiphertextBlob</code> field.</p>
@@ -1475,11 +1511,13 @@ export declare class KMS extends KMSClient {
      *          <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. To perform this operation with a KMS key in a different Amazon Web Services account, specify
+     *             <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>
      *
      *          <p>
-     *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:GenerateDataKeyWithoutPlaintext</a> (key policy)</p>
+     *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:GenerateDataKeyWithoutPlaintext</a> (key
+     *       policy)</p>
      *          <p>
      *             <b>Related operations:</b>
      *          </p>
@@ -1520,7 +1558,8 @@ export declare class KMS extends KMSClient {
      *       the CloudHSM cluster that is associated with a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">custom key store</a>, specify the custom key store
      *       ID.</p>
      *          <p>Applications in Amazon Web Services Nitro Enclaves can call this operation by using the <a href="https://github.com/aws/aws-nitro-enclaves-sdk-c">Amazon Web Services Nitro Enclaves Development Kit</a>. For information about the supporting parameters, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/services-nitro-enclaves.html">How Amazon Web Services Nitro Enclaves use KMS</a> in the <i>Key Management Service Developer Guide</i>.</p>
-     *          <p>For more information about entropy and random number generation, see <a href="https://docs.aws.amazon.com/kms/latest/cryptographic-details/">Key Management Service Cryptographic Details</a>.</p>
+     *          <p>For more information about entropy and random number generation, see
+     *       <a href="https://docs.aws.amazon.com/kms/latest/cryptographic-details/">Key Management Service Cryptographic Details</a>.</p>
      *
      *          <p>
      *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:GenerateRandom</a> (IAM policy)</p>
@@ -1545,7 +1584,8 @@ export declare class KMS extends KMSClient {
     /**
      * <p>Gets a Boolean value that indicates whether <a href="https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html">automatic rotation of the key material</a> is
      *       enabled for the specified KMS key.</p>
-     *          <p>You cannot enable automatic rotation of <a href="https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks">asymmetric KMS keys</a>, KMS keys with <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">imported key material</a>, or KMS keys in a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">custom key store</a>. To enable or disable automatic rotation of a set of related <a href="https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html#mrk-replica-key">multi-Region keys</a>, set the property on the primary key. The key rotation status for these KMS keys is always <code>false</code>.</p>
+     *          <p>You cannot enable automatic rotation of <a href="https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks">asymmetric KMS keys</a>, KMS keys with <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">imported key material</a>, or KMS keys in a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html">custom key store</a>. To enable or disable automatic rotation of a set of related <a href="https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html#mrk-replica-key">multi-Region keys</a>, set the property on the primary key. The key rotation status for these KMS keys is always
+     *       <code>false</code>.</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>
      *          <ul>
@@ -1585,16 +1625,15 @@ export declare class KMS extends KMSClient {
     getKeyRotationStatus(args: GetKeyRotationStatusCommandInput, cb: (err: any, data?: GetKeyRotationStatusCommandOutput) => void): void;
     getKeyRotationStatus(args: GetKeyRotationStatusCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetKeyRotationStatusCommandOutput) => void): void;
     /**
-     * <p>Returns the items you need to import key material into a symmetric, customer managed
-     *       KMS key. For more information about importing key material into KMS, see
-     *         <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">Importing Key
-     *         Material</a> in the <i>Key Management Service Developer Guide</i>.</p>
+     * <p>Returns the items you need to import key material into a symmetric, customer managed KMS
+     *       key. For more information about importing key material into KMS, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">Importing Key Material</a>
+     *       in the <i>Key Management Service Developer Guide</i>.</p>
      *          <p>This operation returns a public key and an import token. Use the public key to encrypt the
      *       symmetric key material. Store the import token to send with a subsequent <a>ImportKeyMaterial</a> request.</p>
-     *          <p>You must specify the key ID of the symmetric KMS key into which you will import key material.
-     *       This KMS key's <code>Origin</code> must be <code>EXTERNAL</code>. You must also specify the
-     *       wrapping algorithm and type of wrapping key (public key) that you will use to encrypt the key
-     *       material. You cannot perform this operation on an asymmetric KMS key or on any KMS key in a different Amazon Web Services account.</p>
+     *          <p>You must specify the key ID of the symmetric KMS key into which you will import key
+     *       material. This KMS key's <code>Origin</code> must be <code>EXTERNAL</code>. You must also
+     *       specify the wrapping algorithm and type of wrapping key (public key) that you will use to
+     *       encrypt the key material. You cannot perform this operation on an asymmetric KMS key or on any KMS key in a different Amazon Web Services account.</p>
      *          <p>To import key material, you must use the public key and import token from the same
      *       response. These items are valid for 24 hours. The expiration date and time appear in the
      *         <code>GetParametersForImport</code> response. You cannot use an expired token in an <a>ImportKeyMaterial</a> request. If your key and token expire, send another
@@ -1626,10 +1665,11 @@ export declare class KMS extends KMSClient {
     getParametersForImport(args: GetParametersForImportCommandInput, cb: (err: any, data?: GetParametersForImportCommandOutput) => void): void;
     getParametersForImport(args: GetParametersForImportCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetParametersForImportCommandOutput) => void): void;
     /**
-     * <p>Returns the public key of an asymmetric KMS key. Unlike the private key of a asymmetric KMS key,
-     *       which never leaves KMS unencrypted, callers with <code>kms:GetPublicKey</code> permission
-     *       can download the public key of an asymmetric KMS key. You can share the public key to allow others
-     *       to encrypt messages and verify signatures 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>Returns the public key of an asymmetric KMS key. Unlike the private key of a asymmetric
+     *       KMS key, which never leaves KMS unencrypted, callers with <code>kms:GetPublicKey</code>
+     *       permission can download the public key of an asymmetric KMS key. You can share the public key
+     *       to allow others to encrypt messages and verify signatures 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>You do not need to download the public key. Instead, you can use the public key within
      *       KMS by calling the <a>Encrypt</a>, <a>ReEncrypt</a>, or <a>Verify</a> operations with the identifier of an asymmetric KMS key. When you use the
      *       public key within KMS, you benefit from the authentication, authorization, and logging that
@@ -1663,7 +1703,8 @@ export declare class KMS extends KMSClient {
      *          <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. To perform this operation with a KMS key in a different Amazon Web Services account, specify
+     *             <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>
      *
      *          <p>
@@ -1676,12 +1717,12 @@ export declare class KMS extends KMSClient {
     getPublicKey(args: GetPublicKeyCommandInput, cb: (err: any, data?: GetPublicKeyCommandOutput) => void): void;
     getPublicKey(args: GetPublicKeyCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetPublicKeyCommandOutput) => void): void;
     /**
-     * <p>Imports key material into an existing symmetric KMS KMS key that was
-     *       created without key material. After you successfully import key material into a KMS key, you can
-     *         <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html#reimport-key-material">reimport the same key material</a> into that KMS key, but you cannot import different key
+     * <p>Imports key material into an existing symmetric KMS KMS key that was created without key
+     *       material. After you successfully import key material into a KMS key, you can <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html#reimport-key-material">reimport
+     *         the same key material</a> into that KMS key, but you cannot import different key
      *       material. </p>
-     *          <p>You cannot perform this operation on an asymmetric KMS key or on any KMS key in a different Amazon Web Services account. For more information about creating KMS keys with no key material and
-     *       then importing key material, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">Importing Key Material</a> in the
+     *          <p>You cannot perform this operation on an asymmetric KMS key or on any KMS key in a different Amazon Web Services account. For more information about creating KMS keys with no key material
+     *       and then importing key material, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html">Importing Key Material</a> in the
      *       <i>Key Management Service Developer Guide</i>.</p>
      *          <p>Before using this operation, call <a>GetParametersForImport</a>. Its response
      *       includes a public key and an import token. Use the public key to encrypt the key material.
@@ -1690,8 +1731,8 @@ export declare class KMS extends KMSClient {
      *          <p>When calling this operation, you must specify the following values:</p>
      *          <ul>
      *             <li>
-     *                <p>The key ID or key ARN of a KMS key with no key material. Its <code>Origin</code> must be
-     *             <code>EXTERNAL</code>.</p>
+     *                <p>The key ID or key ARN of a KMS key with no key material. Its <code>Origin</code> must
+     *           be <code>EXTERNAL</code>.</p>
      *                <p>To create a KMS key with no key material, call <a>CreateKey</a> and set the
      *           value of its <code>Origin</code> parameter to <code>EXTERNAL</code>. To get the
      *             <code>Origin</code> of a KMS key, call <a>DescribeKey</a>.)</p>
@@ -1706,17 +1747,17 @@ export declare class KMS extends KMSClient {
      *             </li>
      *             <li>
      *                <p>Whether the key material expires and if so, when. If you set an expiration date, KMS
-     *           deletes the key material from the KMS key on the specified date, and the KMS key becomes unusable.
-     *           To use the KMS key again, you must reimport the same key material. The only way to change an
-     *           expiration date is by reimporting the same key material and specifying a new expiration
-     *           date. </p>
+     *           deletes the key material from the KMS key on the specified date, and the KMS key becomes
+     *           unusable. To use the KMS key again, you must reimport the same key material. The only way
+     *           to change an expiration date is by reimporting the same key material and specifying a new
+     *           expiration date. </p>
      *             </li>
      *          </ul>
      *          <p>When this operation is successful, the key state of the KMS key changes from
      *         <code>PendingImport</code> to <code>Enabled</code>, and you can use the KMS key.</p>
      *          <p>If this operation fails, use the exception to help determine the problem. If the error is
-     *       related to the key material, the import token, or wrapping key, use <a>GetParametersForImport</a> to get a new public key and import token for the KMS key and
-     *       repeat the import procedure. For help, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html#importing-keys-overview">How To Import Key
+     *       related to the key material, the import token, or wrapping key, use <a>GetParametersForImport</a> to get a new public key and import token for the KMS key
+     *       and repeat the import procedure. For help, see <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html#importing-keys-overview">How To Import Key
      *         Material</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>
@@ -1745,26 +1786,29 @@ export declare class KMS extends KMSClient {
     importKeyMaterial(args: ImportKeyMaterialCommandInput, cb: (err: any, data?: ImportKeyMaterialCommandOutput) => void): void;
     importKeyMaterial(args: ImportKeyMaterialCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ImportKeyMaterialCommandOutput) => void): void;
     /**
-     * <p>Gets a list of aliases in the caller's Amazon Web Services account and region. For more information about
-     *       aliases, see <a>CreateAlias</a>.</p>
+     * <p>Gets a list of aliases in the caller's Amazon Web Services account and region. For more information
+     *       about aliases, see <a>CreateAlias</a>.</p>
      *          <p>By default, the <code>ListAliases</code> operation returns all aliases in the account and
-     *       region. To get only the aliases associated with a particular KMS key, use
-     *       the <code>KeyId</code> parameter.</p>
+     *       region. To get only the aliases associated with a particular KMS key, use the
+     *         <code>KeyId</code> parameter.</p>
      *          <p>The <code>ListAliases</code> response can include aliases that you created and associated
-     *       with your customer managed keys, and aliases that Amazon Web Services created and associated with Amazon Web Services managed keys in your account. You can recognize Amazon Web Services aliases because their names have the format
-     *         <code>aws/<service-name></code>, such as <code>aws/dynamodb</code>.</p>
+     *       with your customer managed keys, and aliases that Amazon Web Services created and associated with Amazon Web Services
+     *       managed keys in your account. You can recognize Amazon Web Services aliases because their names have the
+     *       format <code>aws/<service-name></code>, such as <code>aws/dynamodb</code>.</p>
      *          <p>The response might also include aliases that have no <code>TargetKeyId</code> field. These
-     *       are predefined aliases that Amazon Web Services has created but has not yet associated with a KMS key. Aliases
-     *       that Amazon Web Services creates in your account, including predefined aliases, do not count against your
-     *         <a href="https://docs.aws.amazon.com/kms/latest/developerguide/limits.html#aliases-limit">KMS aliases
+     *       are predefined aliases that Amazon Web Services has created but has not yet associated with a KMS key.
+     *       Aliases that Amazon Web Services creates in your account, including predefined aliases, do not count against
+     *       your <a href="https://docs.aws.amazon.com/kms/latest/developerguide/limits.html#aliases-limit">KMS aliases
      *         quota</a>.</p>
      *          <p>
      *             <b>Cross-account use</b>: No. <code>ListAliases</code> does not
      *       return aliases in other Amazon Web Services accounts.</p>
      *
+     *
      *          <p>
      *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:ListAliases</a> (IAM policy)</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>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>
@@ -1791,8 +1835,8 @@ export declare class KMS extends KMSClient {
     listAliases(args: ListAliasesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListAliasesCommandOutput) => void): void;
     /**
      * <p>Gets a list of all grants for the specified KMS key. </p>
-     *          <p>You must specify the KMS key in all requests. You can filter the grant list by grant ID
-     *       or grantee principal.</p>
+     *          <p>You must specify the KMS key in all requests. You can filter the grant list by grant ID or
+     *       grantee principal.</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>
      *                <i>Key Management Service Developer Guide</i>
@@ -1841,9 +1885,9 @@ export declare class KMS extends KMSClient {
     listGrants(args: ListGrantsCommandInput, cb: (err: any, data?: ListGrantsCommandOutput) => void): void;
     listGrants(args: ListGrantsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListGrantsCommandOutput) => void): void;
     /**
-     * <p>Gets the names of the key policies that are attached to a KMS key. This
-     *       operation is designed to get policy names that you can use in a <a>GetKeyPolicy</a>
-     *       operation. However, the only valid policy name is <code>default</code>. </p>
+     * <p>Gets the names of the key policies that are attached to a KMS key. This operation is
+     *       designed to get policy names that you can use in a <a>GetKeyPolicy</a> operation.
+     *       However, the only valid policy name is <code>default</code>. </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>
      *
@@ -1869,8 +1913,7 @@ export declare class KMS extends KMSClient {
     listKeyPolicies(args: ListKeyPoliciesCommandInput, cb: (err: any, data?: ListKeyPoliciesCommandOutput) => void): void;
     listKeyPolicies(args: ListKeyPoliciesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListKeyPoliciesCommandOutput) => void): void;
     /**
-     * <p>Gets a list of all KMS keys in the caller's Amazon Web Services account and
-     *       Region.</p>
+     * <p>Gets a list of all KMS keys in the caller's Amazon Web Services account and Region.</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>
      *
@@ -1946,11 +1989,11 @@ export declare class KMS extends KMSClient {
     listResourceTags(args: ListResourceTagsCommandInput, cb: (err: any, data?: ListResourceTagsCommandOutput) => void): void;
     listResourceTags(args: ListResourceTagsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListResourceTagsCommandOutput) => void): void;
     /**
-     * <p>Returns information about all grants in the Amazon Web Services account and Region that have the specified
-     *       retiring principal. </p>
+     * <p>Returns information about all grants in the Amazon Web Services account and Region that have the
+     *       specified retiring principal. </p>
      *          <p>You can specify any principal in your Amazon Web Services account. The grants that are returned include
-     *       grants for KMS keys in your Amazon Web Services account and other Amazon Web Services accounts. You might use this operation to
-     *       determine which grants you may retire. To retire a grant, use the <a>RetireGrant</a> operation.</p>
+     *       grants for KMS keys in your Amazon Web Services account and other Amazon Web Services accounts. You might use this
+     *       operation to determine which grants you may retire. To retire a grant, use the <a>RetireGrant</a> operation.</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>
      *                <i>Key Management Service Developer Guide</i>
@@ -1959,11 +2002,12 @@ export declare class KMS extends KMSClient {
      *          <p>
      *             <b>Cross-account use</b>: 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
-     *       <code>kms:ListRetirableGrants</code> permission (or any other additional permission) in any
+     *         <code>kms:ListRetirableGrants</code> permission (or any other additional permission) in any
      *       Amazon Web Services account other than your own.</p>
      *
      *          <p>
-     *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:ListRetirableGrants</a> (IAM policy) in your Amazon Web Services account.</p>
+     *             <b>Required permissions</b>: <a href="https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html">kms:ListRetirableGrants</a> (IAM policy) in your
+     *       Amazon Web Services account.</p>
      *          <p>
      *             <b>Related operations:</b>
      *          </p>
@@ -2014,39 +2058,45 @@ export declare class KMS extends KMSClient {
     putKeyPolicy(args: PutKeyPolicyCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: PutKeyPolicyCommandOutput) => void): void;
     /**
      * <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>
@@ -2054,26 +2104,26 @@ export declare class KMS extends KMSClient {
      *                </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>
@@ -2142,7 +2192,7 @@ export declare class KMS extends KMSClient {
      *       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>
@@ -2150,8 +2200,8 @@ export declare class KMS extends KMSClient {
      *       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>
@@ -2162,8 +2212,8 @@ export declare class KMS extends KMSClient {
      *          <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>
@@ -2196,12 +2246,13 @@ export declare class KMS extends KMSClient {
     /**
      * <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>
@@ -2209,11 +2260,12 @@ export declare class KMS extends KMSClient {
      *             </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>
@@ -2245,8 +2297,7 @@ export declare class KMS extends KMSClient {
     retireGrant(args: RetireGrantCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: RetireGrantCommandOutput) => void): void;
     /**
      * <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>
@@ -2294,22 +2345,24 @@ export declare class KMS extends KMSClient {
     revokeGrant(args: RevokeGrantCommandInput, cb: (err: any, data?: RevokeGrantCommandOutput) => void): void;
     revokeGrant(args: RevokeGrantCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: RevokeGrantCommandOutput) => void): void;
     /**
-     * <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
@@ -2318,18 +2371,20 @@ export declare class KMS extends KMSClient {
      *       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>
@@ -2351,20 +2406,21 @@ export declare class KMS extends KMSClient {
     scheduleKeyDeletion(args: ScheduleKeyDeletionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ScheduleKeyDeletionCommandOutput) => void): void;
     /**
      * <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
@@ -2386,7 +2442,7 @@ export declare class KMS extends KMSClient {
      *       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>
      *
@@ -2408,16 +2464,18 @@ export declare class KMS extends KMSClient {
      *       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>
@@ -2457,8 +2515,8 @@ export declare class KMS extends KMSClient {
      *             <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
@@ -2466,7 +2524,7 @@ export declare class KMS extends KMSClient {
      *          <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>
@@ -2500,9 +2558,9 @@ export declare class KMS extends KMSClient {
     untagResource(args: UntagResourceCommandInput, cb: (err: any, data?: UntagResourceCommandOutput) => void): void;
     untagResource(args: UntagResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UntagResourceCommandOutput) => void): void;
     /**
-     * <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>
@@ -2514,12 +2572,12 @@ export declare class KMS extends KMSClient {
      *       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>
@@ -2527,18 +2585,22 @@ export declare class KMS extends KMSClient {
      *          <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>
@@ -2572,29 +2634,29 @@ export declare class KMS extends KMSClient {
      *       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
@@ -2602,9 +2664,9 @@ export declare class KMS extends KMSClient {
      *          <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>
@@ -2642,12 +2704,12 @@ export declare class KMS extends KMSClient {
     updateCustomKeyStore(args: UpdateCustomKeyStoreCommandInput, cb: (err: any, data?: UpdateCustomKeyStoreCommandOutput) => void): void;
     updateCustomKeyStore(args: UpdateCustomKeyStoreCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateCustomKeyStoreCommandOutput) => void): void;
     /**
-     * <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>
@@ -2686,7 +2748,7 @@ export declare class KMS extends KMSClient {
      *       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
@@ -2744,9 +2806,9 @@ export declare class KMS extends KMSClient {
     /**
      * <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
@@ -2755,8 +2817,8 @@ export declare class KMS extends KMSClient {
      *          <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