@aws-sdk/client-kms 3.35.0 → 3.36.0

package/CHANGELOG.md

@@ -3,6 +3,20 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [3.36.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.35.0...v3.36.0) (2021-10-08)
+
+
+### Features
+
+* **clients:** update clients as of 10/07/2021 ([#2879](https://github.com/aws/aws-sdk-js-v3/issues/2879)) ([1f4441e](https://github.com/aws/aws-sdk-js-v3/commit/1f4441e46b63ae6ff01067780b26d49916c267a0))
+* publish files in dist-* only ([#2873](https://github.com/aws/aws-sdk-js-v3/issues/2873)) ([53b4243](https://github.com/aws/aws-sdk-js-v3/commit/53b4243b066f25ff2412d5f0dea1036054b2df32))
+* **codegen:** ts-ignore packageInfo imports in codegen ([#2875](https://github.com/aws/aws-sdk-js-v3/issues/2875)) ([99d9267](https://github.com/aws/aws-sdk-js-v3/commit/99d926762193e83a354edec6e9de2b0543449704))
+* **tsconfig:** remove sourceMap ([#2867](https://github.com/aws/aws-sdk-js-v3/issues/2867)) ([d25f526](https://github.com/aws/aws-sdk-js-v3/commit/d25f526627a02a2ca28675fecce66c76b6c97966))
+
+
+
+
+
 # [3.35.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.34.0...v3.35.0) (2021-10-04)
 
 

package/README.md

@@ -41,10 +41,11 @@ security credentials that you can use to sign requests.</p>
 <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>
@@ -52,9 +53,9 @@ your log files, see the <a href="https://docs.aws.amazon.com/awscloudtrail/lates
 <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>

package/dist-cjs/KMS.js

@@ -84,10 +84,11 @@ const KMSClient_1 = require("./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>
@@ -95,9 +96,9 @@ const KMSClient_1 = require("./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>
@@ -816,4 +817,3 @@ class KMS extends KMSClient_1.KMSClient {
     }
 }
 exports.KMS = KMS;
-//# sourceMappingURL=KMS.js.map

package/dist-cjs/KMSClient.js

@@ -44,10 +44,11 @@ const runtimeConfig_1 = require("./runtimeConfig");
  *          <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>
@@ -55,9 +56,9 @@ const runtimeConfig_1 = require("./runtimeConfig");
  *          <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>
@@ -129,4 +130,3 @@ class KMSClient extends smithy_client_1.Client {
     }
 }
 exports.KMSClient = KMSClient;
-//# sourceMappingURL=KMSClient.js.map

package/dist-cjs/commands/CancelKeyDeletionCommand.js

@@ -6,13 +6,15 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
- * <p>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>
@@ -69,4 +71,3 @@ class CancelKeyDeletionCommand extends smithy_client_1.Command {
     }
 }
 exports.CancelKeyDeletionCommand = CancelKeyDeletionCommand;
-//# sourceMappingURL=CancelKeyDeletionCommand.js.map

package/dist-cjs/commands/ConnectCustomKeyStoreCommand.js

@@ -7,9 +7,9 @@ const models_0_1 = require("../models/models_0");
 const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <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">
@@ -119,4 +119,3 @@ class ConnectCustomKeyStoreCommand extends smithy_client_1.Command {
     }
 }
 exports.ConnectCustomKeyStoreCommand = ConnectCustomKeyStoreCommand;
-//# sourceMappingURL=ConnectCustomKeyStoreCommand.js.map

package/dist-cjs/commands/CreateAliasCommand.js

@@ -11,11 +11,12 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *             <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>
@@ -32,14 +33,17 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *          <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>
@@ -111,4 +115,3 @@ class CreateAliasCommand extends smithy_client_1.Command {
     }
 }
 exports.CreateAliasCommand = CreateAliasCommand;
-//# sourceMappingURL=CreateAliasCommand.js.map

package/dist-cjs/commands/CreateCustomKeyStoreCommand.js

@@ -107,4 +107,3 @@ class CreateCustomKeyStoreCommand extends smithy_client_1.Command {
     }
 }
 exports.CreateCustomKeyStoreCommand = CreateCustomKeyStoreCommand;
-//# sourceMappingURL=CreateCustomKeyStoreCommand.js.map

package/dist-cjs/commands/CreateGrantCommand.js

@@ -7,7 +7,9 @@ const models_0_1 = require("../models/models_0");
 const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <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
@@ -16,28 +18,29 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *             </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>
@@ -117,4 +120,3 @@ class CreateGrantCommand extends smithy_client_1.Command {
     }
 }
 exports.CreateGrantCommand = CreateGrantCommand;
-//# sourceMappingURL=CreateGrantCommand.js.map

package/dist-cjs/commands/CreateKeyCommand.js

@@ -6,20 +6,21 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
- * <p>Creates a 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>
@@ -27,9 +28,9 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *                   <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>
@@ -60,8 +61,8 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *             <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
@@ -102,13 +103,14 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *             </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>
@@ -180,4 +182,3 @@ class CreateKeyCommand extends smithy_client_1.Command {
     }
 }
 exports.CreateKeyCommand = CreateKeyCommand;
-//# sourceMappingURL=CreateKeyCommand.js.map

package/dist-cjs/commands/DecryptCommand.js

@@ -6,8 +6,8 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
- * <p>Decrypts ciphertext 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>
@@ -36,33 +36,36 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *             </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>
@@ -143,4 +146,3 @@ class DecryptCommand extends smithy_client_1.Command {
     }
 }
 exports.DecryptCommand = DecryptCommand;
-//# sourceMappingURL=DecryptCommand.js.map

package/dist-cjs/commands/DeleteAliasCommand.js

@@ -6,14 +6,15 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
- * <p>Deletes the specified 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>
@@ -22,14 +23,17 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *          <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>
@@ -101,4 +105,3 @@ class DeleteAliasCommand extends smithy_client_1.Command {
     }
 }
 exports.DeleteAliasCommand = DeleteAliasCommand;
-//# sourceMappingURL=DeleteAliasCommand.js.map

package/dist-cjs/commands/DeleteCustomKeyStoreCommand.js

@@ -8,16 +8,15 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
  * <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>
@@ -26,9 +25,9 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *          <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>
@@ -113,4 +112,3 @@ class DeleteCustomKeyStoreCommand extends smithy_client_1.Command {
     }
 }
 exports.DeleteCustomKeyStoreCommand = DeleteCustomKeyStoreCommand;
-//# sourceMappingURL=DeleteCustomKeyStoreCommand.js.map

package/dist-cjs/commands/DeleteImportedKeyMaterialCommand.js

@@ -6,12 +6,11 @@ const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
 /**
- * <p>Deletes 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>
@@ -88,4 +87,3 @@ class DeleteImportedKeyMaterialCommand extends smithy_client_1.Command {
     }
 }
 exports.DeleteImportedKeyMaterialCommand = DeleteImportedKeyMaterialCommand;
-//# sourceMappingURL=DeleteImportedKeyMaterialCommand.js.map

package/dist-cjs/commands/DescribeCustomKeyStoresCommand.js

@@ -10,10 +10,10 @@ const Aws_json1_1_1 = require("../protocols/Aws_json1_1");
  *          <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
@@ -111,4 +111,3 @@ class DescribeCustomKeyStoresCommand extends smithy_client_1.Command {
     }
 }
 exports.DescribeCustomKeyStoresCommand = DescribeCustomKeyStoresCommand;
-//# sourceMappingURL=DescribeCustomKeyStoresCommand.js.map