@aws-sdk/client-s3 3.844.0 → 3.846.0

package/dist-types/commands/PutBucketEncryptionCommand.d.ts

@@ -27,8 +27,7 @@ declare const PutBucketEncryptionCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>This operation configures default encryption and Amazon S3 Bucket Keys for an existing
- *          bucket.</p>
+ * <p>This operation configures default encryption and Amazon S3 Bucket Keys for an existing bucket.</p>
  *          <note>
  *             <p>
  *                <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i>
@@ -37,8 +36,8 @@ declare const PutBucketEncryptionCommand_base: {
  *     <i>Amazon S3 User Guide</i>. For more information about endpoints in Local Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.html">Concepts for directory buckets in Local Zones</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
- *          <p>By default, all buckets have a default encryption configuration that uses server-side
- *          encryption with Amazon S3 managed keys (SSE-S3).</p>
+ *          <p>By default, all buckets have a default encryption configuration that uses server-side encryption
+ *       with Amazon S3 managed keys (SSE-S3).</p>
  *          <note>
  *             <ul>
  *                <li>
@@ -47,35 +46,32 @@ declare const PutBucketEncryptionCommand_base: {
  *                   </p>
  *                   <ul>
  *                      <li>
- *                         <p>You can optionally configure default encryption for a bucket by using
- *                         server-side encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer
- *                         server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). If you specify
- *                         default encryption by using SSE-KMS, you can also configure <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3
- *                            Bucket Keys</a>. For information about the bucket default encryption
- *                         feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3 Bucket Default
- *                            Encryption</a> in the <i>Amazon S3 User Guide</i>. </p>
+ *                         <p>You can optionally configure default encryption for a bucket by using server-side
+ *                 encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer server-side encryption with
+ *                 Amazon Web Services KMS keys (DSSE-KMS). If you specify default encryption by using SSE-KMS, you can also
+ *                 configure <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket
+ *                   Keys</a>. For information about the bucket default encryption feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3 Bucket Default
+ *                   Encryption</a> in the <i>Amazon S3 User Guide</i>. </p>
  *                      </li>
  *                      <li>
- *                         <p>If you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket
- *                            encryption</a> to SSE-KMS, you should verify that your KMS key ID
- *                         is correct. Amazon S3 doesn't validate the KMS key ID provided in
- *                         PutBucketEncryption requests.</p>
+ *                         <p>If you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket encryption</a> to
+ *                 SSE-KMS, you should verify that your KMS key ID is correct. Amazon S3 doesn't validate the
+ *                 KMS key ID provided in PutBucketEncryption requests.</p>
  *                      </li>
  *                   </ul>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets </b> - You can
- *                   optionally configure default encryption for a bucket by using server-side
- *                   encryption with Key Management Service (KMS) keys (SSE-KMS).</p>
+ *                      <b>Directory buckets </b> - You can optionally configure
+ *             default encryption for a bucket by using server-side encryption with Key Management Service (KMS) keys
+ *             (SSE-KMS).</p>
  *                   <ul>
  *                      <li>
- *                         <p>We recommend that the bucket's default encryption uses the desired
- *                         encryption configuration and you don't override the bucket default
- *                         encryption in your <code>CreateSession</code> requests or <code>PUT</code>
- *                         object requests. Then, new objects are automatically encrypted with the
- *                         desired encryption settings.
- *                         For more information about the encryption overriding behaviors in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-specifying-kms-encryption.html">Specifying server-side encryption with KMS for new object uploads</a>.</p>
+ *                         <p>We recommend that the bucket's default encryption uses the desired encryption
+ *                 configuration and you don't override the bucket default encryption in your
+ *                   <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects
+ *                 are automatically encrypted with the desired encryption settings.
+ *                 For more information about the encryption overriding behaviors in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-specifying-kms-encryption.html">Specifying server-side encryption with KMS for new object uploads</a>.</p>
  *                      </li>
  *                      <li>
  *                         <p>Your SSE-KMS configuration can only support 1 <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a> per directory bucket's lifetime.
@@ -91,21 +87,21 @@ declare const PutBucketEncryptionCommand_base: {
  *                         <p>When you specify an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">KMS customer managed key</a> for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.</p>
  *                      </li>
  *                      <li>
- *                         <p>For directory buckets, if you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket encryption</a> to SSE-KMS, Amazon S3 validates the
- *                         KMS key ID provided in PutBucketEncryption requests.</p>
+ *                         <p>For directory buckets, if you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket
+ *                   encryption</a> to SSE-KMS, Amazon S3 validates the KMS key ID provided in
+ *                 PutBucketEncryption requests.</p>
  *                      </li>
  *                   </ul>
  *                </li>
  *             </ul>
  *          </note>
  *          <important>
- *             <p>If you're specifying a customer managed KMS key, we recommend using a fully
- *             qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the
- *             key within the requester’s account. This behavior can result in data that's encrypted
- *             with a KMS key that belongs to the requester, and not the bucket owner.</p>
- *             <p>Also, this action requires Amazon Web Services Signature Version 4. For more information, see
- *                <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html"> Authenticating
- *                Requests (Amazon Web Services Signature Version 4)</a>. </p>
+ *             <p>If you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key
+ *         ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester’s account.
+ *         This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and
+ *         not the bucket owner.</p>
+ *             <p>Also, this action requires Amazon Web Services Signature Version 4. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html"> Authenticating
+ *           Requests (Amazon Web Services Signature Version 4)</a>. </p>
  *          </important>
  *          <dl>
  *             <dt>Permissions</dt>
@@ -114,24 +110,20 @@ declare const PutBucketEncryptionCommand_base: {
  *                   <li>
  *                      <p>
  *                         <b>General purpose bucket permissions</b> - The
- *                            <code>s3:PutEncryptionConfiguration</code> permission is required in a
- *                         policy. The bucket owner has this permission by default. The bucket owner
- *                         can grant this permission to others. For more information about permissions,
- *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions Related to Bucket Operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access
- *                            Permissions to Your Amazon S3 Resources</a> in the
- *                            <i>Amazon S3 User Guide</i>.</p>
+ *                   <code>s3:PutEncryptionConfiguration</code> permission is required in a policy. The bucket
+ *                 owner has this permission by default. The bucket owner can grant this permission to others.
+ *                 For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions Related to Bucket Operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access Permissions to Your
+ *                   Amazon S3 Resources</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> -
- *                         To grant access to this API operation, you must have the
- *                            <code>s3express:PutEncryptionConfiguration</code> permission in
- *                         an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- *                         For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
- *                      <p>To set a directory bucket default encryption with SSE-KMS, you must also
- *                         have the <code>kms:GenerateDataKey</code> and the <code>kms:Decrypt</code>
- *                         permissions in IAM identity-based policies and KMS key policies for the
- *                         target KMS key.</p>
+ *                         <b>Directory bucket permissions</b> - To grant access to
+ *                 this API operation, you must have the <code>s3express:PutEncryptionConfiguration</code>
+ *                 permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ *                 For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>To set a directory bucket default encryption with SSE-KMS, you must also have the
+ *                   <code>kms:GenerateDataKey</code> and the <code>kms:Decrypt</code> permissions in IAM
+ *                 identity-based policies and KMS key policies for the target KMS key.</p>
  *                   </li>
  *                </ul>
  *             </dd>

package/dist-types/commands/PutBucketIntelligentTieringConfigurationCommand.d.ts

@@ -30,8 +30,8 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to
- *          1,000 S3 Intelligent-Tiering configurations per bucket.</p>
+ *          <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to 1,000
+ *       S3 Intelligent-Tiering configurations per bucket.</p>
  *          <p>The S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.</p>
  *          <p>The S3 Intelligent-Tiering storage class is  the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.</p>
  *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html#sc-dynamic-data-access">Storage class for automatically optimizing frequently and infrequently accessed objects</a>.</p>
@@ -54,13 +54,12 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
  *             </li>
  *          </ul>
  *          <note>
- *             <p>You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically
- *             move objects stored in the S3 Intelligent-Tiering storage class to the Archive Access
- *             or Deep Archive Access tier.</p>
+ *             <p>You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically move objects
+ *         stored in the S3 Intelligent-Tiering storage class to the Archive Access or Deep Archive Access
+ *         tier.</p>
  *          </note>
  *          <p>
- *             <code>PutBucketIntelligentTieringConfiguration</code> has the following special
- *          errors:</p>
+ *             <code>PutBucketIntelligentTieringConfiguration</code> has the following special errors:</p>
  *          <dl>
  *             <dt>HTTP 400 Bad Request Error</dt>
  *             <dd>
@@ -74,15 +73,15 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
  *                <p>
  *                   <i>Code:</i> TooManyConfigurations</p>
  *                <p>
- *                   <i>Cause:</i> You are attempting to create a new configuration
- *                   but have already reached the 1,000-configuration limit. </p>
+ *                   <i>Cause:</i> You are attempting to create a new configuration but have already
+ *             reached the 1,000-configuration limit. </p>
  *             </dd>
  *             <dt>HTTP 403 Forbidden Error</dt>
  *             <dd>
  *                <p>
- *                   <i>Cause:</i> You are not the owner of the specified bucket, or
- *                   you do not have the <code>s3:PutIntelligentTieringConfiguration</code> bucket
- *                   permission to set the configuration on the bucket. </p>
+ *                   <i>Cause:</i> You are not the owner of the specified bucket, or you do not have
+ *             the <code>s3:PutIntelligentTieringConfiguration</code> bucket permission to set the configuration
+ *             on the bucket. </p>
  *             </dd>
  *          </dl>
  * @example

package/dist-types/commands/PutBucketInventoryConfigurationCommand.d.ts

@@ -30,43 +30,40 @@ declare const PutBucketInventoryConfigurationCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>This implementation of the <code>PUT</code> action adds an inventory configuration
- *          (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory
- *          configurations per bucket. </p>
- *          <p>Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly
- *          basis, and the results are published to a flat file. The bucket that is inventoried is
- *          called the <i>source</i> bucket, and the bucket where the inventory flat file
- *          is stored is called the <i>destination</i> bucket. The
- *             <i>destination</i> bucket must be in the same Amazon Web Services Region as the
- *             <i>source</i> bucket. </p>
- *          <p>When you configure an inventory for a <i>source</i> bucket, you specify
- *          the <i>destination</i> bucket where you want the inventory to be stored, and
- *          whether to generate the inventory daily or weekly. You can also configure what object
- *          metadata to include and whether to inventory all object versions or only current versions.
- *          For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html">Amazon S3 Inventory</a> in the
- *          Amazon S3 User Guide.</p>
+ *          <p>This implementation of the <code>PUT</code> action adds an S3 Inventory configuration (identified by
+ *       the inventory ID) to the bucket. You can have up to 1,000 inventory configurations per bucket. </p>
+ *          <p>Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly basis, and
+ *       the results are published to a flat file. The bucket that is inventoried is called the
+ *         <i>source</i> bucket, and the bucket where the inventory flat file is stored is called
+ *       the <i>destination</i> bucket. The <i>destination</i> bucket must be in the
+ *       same Amazon Web Services Region as the <i>source</i> bucket. </p>
+ *          <p>When you configure an inventory for a <i>source</i> bucket, you specify the
+ *         <i>destination</i> bucket where you want the inventory to be stored, and whether to
+ *       generate the inventory daily or weekly. You can also configure what object metadata to include and
+ *       whether to inventory all object versions or only current versions. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html">Amazon S3 Inventory</a> in the
+ *       Amazon S3 User Guide.</p>
  *          <important>
- *             <p>You must create a bucket policy on the <i>destination</i> bucket to
- *             grant permissions to Amazon S3 to write objects to the bucket in the defined location. For an
- *             example policy, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html#example-bucket-policies-use-case-9"> Granting Permissions for Amazon S3 Inventory and Storage Class Analysis</a>.</p>
+ *             <p>You must create a bucket policy on the <i>destination</i> bucket to grant
+ *         permissions to Amazon S3 to write objects to the bucket in the defined location. For an example policy, see
+ *           <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html#example-bucket-policies-use-case-9"> Granting
+ *           Permissions for Amazon S3 Inventory and Storage Class Analysis</a>.</p>
  *          </important>
  *          <dl>
  *             <dt>Permissions</dt>
  *             <dd>
  *                <p>To use this operation, you must have permission to perform the
- *                      <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this
- *                   permission by default and can grant this permission to others. </p>
- *                <p>The <code>s3:PutInventoryConfiguration</code> permission allows a user to
- *                   create an <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html">S3 Inventory</a>
- *                   report that includes all object metadata fields available and to specify the
- *                   destination bucket to store the inventory. A user with read access to objects in
- *                   the destination bucket can also access all object metadata fields that are
- *                   available in the inventory report. </p>
+ *               <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this permission by
+ *             default and can grant this permission to others. </p>
+ *                <p>The <code>s3:PutInventoryConfiguration</code> permission allows a user to create an <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html">S3 Inventory</a>
+ *             report that includes all object metadata fields available and to specify the destination bucket to
+ *             store the inventory. A user with read access to objects in the destination bucket can also access
+ *             all object metadata fields that are available in the inventory report. </p>
  *                <p>To restrict access to an inventory report, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html#example-bucket-policies-use-case-10">Restricting access to an Amazon S3 Inventory report</a> in the
- *                      <i>Amazon S3 User Guide</i>. For more information about the metadata
- *                   fields available in S3 Inventory, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html#storage-inventory-contents">Amazon S3 Inventory lists</a> in the <i>Amazon S3 User Guide</i>. For
- *                   more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions related to bucket subresource operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Identity and access management in Amazon S3</a> in the
- *                      <i>Amazon S3 User Guide</i>.</p>
+ *               <i>Amazon S3 User Guide</i>. For more information about the metadata fields available
+ *             in S3 Inventory, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html#storage-inventory-contents">Amazon S3 Inventory
+ *               lists</a> in the <i>Amazon S3 User Guide</i>. For more information about
+ *             permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions related to bucket subresource operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Identity and access management in
+ *               Amazon S3</a> in the <i>Amazon S3 User Guide</i>.</p>
  *             </dd>
  *          </dl>
  *          <p>
@@ -84,19 +81,18 @@ declare const PutBucketInventoryConfigurationCommand_base: {
  *                <p>
  *                   <i>Code:</i> TooManyConfigurations</p>
  *                <p>
- *                   <i>Cause:</i> You are attempting to create a new configuration
- *                   but have already reached the 1,000-configuration limit. </p>
+ *                   <i>Cause:</i> You are attempting to create a new configuration but have already
+ *             reached the 1,000-configuration limit. </p>
  *             </dd>
  *             <dt>HTTP 403 Forbidden Error</dt>
  *             <dd>
  *                <p>
- *                   <i>Cause:</i> You are not the owner of the specified bucket, or
- *                   you do not have the <code>s3:PutInventoryConfiguration</code> bucket permission to
- *                   set the configuration on the bucket. </p>
+ *                   <i>Cause:</i> You are not the owner of the specified bucket, or you do not have
+ *             the <code>s3:PutInventoryConfiguration</code> bucket permission to set the configuration on the
+ *             bucket. </p>
  *             </dd>
  *          </dl>
- *          <p>The following operations are related to
- *          <code>PutBucketInventoryConfiguration</code>:</p>
+ *          <p>The following operations are related to <code>PutBucketInventoryConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>

package/dist-types/commands/PutBucketLifecycleConfigurationCommand.d.ts

@@ -28,73 +28,69 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
 };
 /**
  * <p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle
- *          configuration. Keep in mind that this will overwrite an existing lifecycle configuration,
- *          so if you want to retain any configuration details, they must be included in the new
- *          lifecycle configuration. For information about lifecycle configuration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html">Managing
- *             your storage lifecycle</a>.</p>
+ *       configuration. Keep in mind that this will overwrite an existing lifecycle configuration, so if you want
+ *       to retain any configuration details, they must be included in the new lifecycle configuration. For
+ *       information about lifecycle configuration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html">Managing your storage
+ *       lifecycle</a>.</p>
  *          <note>
- *             <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, object size, or any combination of these. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility.
- *             For the related API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>.</p>
+ *             <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name
+ *         prefix, one or more object tags, object size, or any combination of these. Accordingly, this section
+ *         describes the latest API. The previous version of the API supported filtering based only on an object
+ *         key name prefix, which is supported for backward compatibility. For the related API description, see
+ *           <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>.</p>
  *          </note>
  *          <dl>
  *             <dt>Rules</dt>
  *             <dt>Permissions</dt>
  *             <dt>HTTP Host header syntax</dt>
  *             <dd>
- *                <p>You specify the lifecycle configuration in your request body. The lifecycle
- *                   configuration is specified as XML consisting of one or more rules. An Amazon S3
- *                   Lifecycle configuration can have up to 1,000 rules. This limit is not
- *                   adjustable.</p>
- *                <p>Bucket lifecycle configuration supports specifying a lifecycle rule using an
- *                   object key name prefix, one or more object tags, object size, or any combination
- *                   of these. Accordingly, this section describes the latest API. The previous version
- *                   of the API supported filtering based only on an object key name prefix, which is
- *                   supported for backward compatibility for general purpose buckets. For the related
- *                   API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>. </p>
+ *                <p>You specify the lifecycle configuration in your request body. The lifecycle configuration is
+ *             specified as XML consisting of one or more rules. An Amazon S3 Lifecycle configuration can have up to
+ *             1,000 rules. This limit is not adjustable.</p>
+ *                <p>Bucket lifecycle configuration supports specifying a lifecycle rule using an object key name
+ *             prefix, one or more object tags, object size, or any combination of these. Accordingly, this
+ *             section describes the latest API. The previous version of the API supported filtering based only
+ *             on an object key name prefix, which is supported for backward compatibility for general purpose
+ *             buckets. For the related API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>. </p>
  *                <note>
- *                   <p>Lifecyle configurations for directory buckets only support expiring objects and
- *                      cancelling multipart uploads. Expiring of versioned objects,transitions and tag
- *                      filters are not supported.</p>
+ *                   <p>Lifecyle configurations for directory buckets only support expiring objects and cancelling
+ *               multipart uploads. Expiring of versioned objects,transitions and tag filters are not
+ *               supported.</p>
  *                </note>
  *                <p>A lifecycle rule consists of the following:</p>
  *                <ul>
  *                   <li>
- *                      <p>A filter identifying a subset of objects to which the rule applies. The
- *                         filter can be based on a key name prefix, object tags, object size, or any
- *                         combination of these.</p>
+ *                      <p>A filter identifying a subset of objects to which the rule applies. The filter can be
+ *                 based on a key name prefix, object tags, object size, or any combination of these.</p>
  *                   </li>
  *                   <li>
  *                      <p>A status indicating whether the rule is in effect.</p>
  *                   </li>
  *                   <li>
- *                      <p>One or more lifecycle transition and expiration actions that you want
- *                         Amazon S3 to perform on the objects identified by the filter. If the state of
- *                         your bucket is versioning-enabled or versioning-suspended, you can have many
- *                         versions of the same object (one current version and zero or more noncurrent
- *                         versions). Amazon S3 provides predefined actions that you can specify for current
- *                         and noncurrent object versions.</p>
+ *                      <p>One or more lifecycle transition and expiration actions that you want Amazon S3 to perform on
+ *                 the objects identified by the filter. If the state of your bucket is versioning-enabled or
+ *                 versioning-suspended, you can have many versions of the same object (one current version and
+ *                 zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for
+ *                 current and noncurrent object versions.</p>
  *                   </li>
  *                </ul>
- *                <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html">Object Lifecycle
- *                      Management</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html">Lifecycle Configuration
- *                      Elements</a>.</p>
+ *                <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html">Object Lifecycle Management</a> and
+ *               <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html">Lifecycle
+ *               Configuration Elements</a>.</p>
  *             </dd>
  *             <dd>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - By
- *                         default, all Amazon S3 resources are private, including buckets, objects, and
- *                         related subresources (for example, lifecycle configuration and website
- *                         configuration). Only the resource owner (that is, the Amazon Web Services account that
- *                         created it) can access the resource. The resource owner can optionally grant
- *                         access permissions to others by writing an access policy. For this
- *                         operation, a user must have the <code>s3:PutLifecycleConfiguration</code>
- *                         permission.</p>
- *                      <p>You can also explicitly deny permissions. An explicit deny also
- *                         supersedes any other permissions. If you want to block users or accounts
- *                         from removing or deleting objects from your bucket, you must deny them
- *                         permissions for the following actions:</p>
+ *                         <b>General purpose bucket permissions</b> - By default, all Amazon S3
+ *                 resources are private, including buckets, objects, and related subresources (for example,
+ *                 lifecycle configuration and website configuration). Only the resource owner (that is, the
+ *                 Amazon Web Services account that created it) can access the resource. The resource owner can optionally
+ *                 grant access permissions to others by writing an access policy. For this operation, a user
+ *                 must have the <code>s3:PutLifecycleConfiguration</code> permission.</p>
+ *                      <p>You can also explicitly deny permissions. An explicit deny also supersedes any other
+ *                 permissions. If you want to block users or accounts from removing or deleting objects from
+ *                 your bucket, you must deny them permissions for the following actions:</p>
  *                      <ul>
  *                         <li>
  *                            <p>
@@ -110,8 +106,8 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
  *                            <p>
  *                               <code>s3:PutLifecycleConfiguration</code>
  *                            </p>
- *                            <p>For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing
- *                                  Access Permissions to Your Amazon S3 Resources</a>.</p>
+ *                            <p>For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access Permissions to
+ *                       Your Amazon S3 Resources</a>.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -119,16 +115,13 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> -
- *                         You must have the <code>s3express:PutLifecycleConfiguration</code>
- *                         permission in an IAM identity-based policy to use this operation.
- *                         Cross-account access to this API operation isn't supported. The resource
- *                         owner can optionally grant access permissions to others by creating a role
- *                         or user for them as long as they are within the same account as the owner
- *                         and resource.</p>
- *                      <p>For more information about directory bucket policies and permissions, see
- *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Authorizing Regional endpoint APIs with IAM</a> in the
- *                            <i>Amazon S3 User Guide</i>.</p>
+ *                         <b>Directory bucket permissions</b> - You must have the
+ *                   <code>s3express:PutLifecycleConfiguration</code> permission in an IAM identity-based policy
+ *                 to use this operation. Cross-account access to this API operation isn't supported. The
+ *                 resource owner can optionally grant access permissions to others by creating a role or user
+ *                 for them as long as they are within the same account as the owner and resource.</p>
+ *                      <p>For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Authorizing Regional endpoint APIs with IAM</a> in the <i>Amazon S3 User
+ *                   Guide</i>.</p>
  *                      <note>
  *                         <p>
  *                            <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i>
@@ -142,11 +135,9 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
  *             </dd>
  *             <dd>
  *                <p>
- *                   <b>Directory buckets </b> - The HTTP Host
- *                   header syntax is
- *                      <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
- *                <p>The following operations are related to
- *                      <code>PutBucketLifecycleConfiguration</code>:</p>
+ *                   <b>Directory buckets </b> - The HTTP Host header syntax is
+ *                 <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
+ *                <p>The following operations are related to <code>PutBucketLifecycleConfiguration</code>:</p>
  *                <ul>
  *                   <li>
  *                      <p>

package/dist-types/commands/PutBucketLoggingCommand.d.ts

@@ -38,36 +38,32 @@ declare const PutBucketLoggingCommand_base: {
  *          <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Set the logging parameters for a bucket and to specify permissions for who can view and
- *          modify the logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as
- *          the source bucket. To set the logging status of a bucket, you must be the bucket
- *          owner.</p>
- *          <p>The bucket owner is automatically granted FULL_CONTROL to all logs. You use the
- *             <code>Grantee</code> request element to grant access to other people. The
- *             <code>Permissions</code> request element specifies the kind of access the grantee has to
- *          the logs.</p>
+ *          <p>Set the logging parameters for a bucket and to specify permissions for who can view and modify the
+ *       logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as the source bucket. To set
+ *       the logging status of a bucket, you must be the bucket owner.</p>
+ *          <p>The bucket owner is automatically granted FULL_CONTROL to all logs. You use the <code>Grantee</code>
+ *       request element to grant access to other people. The <code>Permissions</code> request element specifies
+ *       the kind of access the grantee has to the logs.</p>
  *          <important>
- *             <p>If the target bucket for log delivery uses the bucket owner enforced setting for S3
- *             Object Ownership, you can't use the <code>Grantee</code> request element to grant access
- *             to others. Permissions can only be granted using policies. For more information, see
- *                <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html#grant-log-delivery-permissions-general">Permissions for server access log delivery</a> in the
- *                <i>Amazon S3 User Guide</i>.</p>
+ *             <p>If the target bucket for log delivery uses the bucket owner enforced setting for S3 Object
+ *         Ownership, you can't use the <code>Grantee</code> request element to grant access to others.
+ *         Permissions can only be granted using policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html#grant-log-delivery-permissions-general">Permissions for server access log delivery</a> in the
+ *         <i>Amazon S3 User Guide</i>.</p>
  *          </important>
  *          <dl>
  *             <dt>Grantee Values</dt>
  *             <dd>
- *                <p>You can specify the person (grantee) to whom you're assigning access rights (by
- *                  using request elements) in the following ways. For examples of how to specify these
- *                  grantee values in JSON format, see the Amazon Web Services CLI example in  <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html">
- *                    Enabling Amazon S3 server access logging</a> in the
- *                  <i>Amazon S3 User Guide</i>.</p>
+ *                <p>You can specify the person (grantee) to whom you're assigning access rights (by using request
+ *             elements) in the following ways. For examples of how to specify these grantee values in JSON
+ *             format, see the Amazon Web Services CLI example in <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html"> Enabling Amazon S3 server
+ *               access logging</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                <ul>
  *                   <li>
  *                      <p>By the person's ID:</p>
  *                      <p>
  *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                            xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
- *                            </Grantee></code>
+ *                   xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
+ *                   </Grantee></code>
  *                      </p>
  *                      <p>
  *                         <code>DisplayName</code> is optional and ignored in the request.</p>
@@ -76,33 +72,30 @@ declare const PutBucketLoggingCommand_base: {
  *                      <p>By Email address:</p>
  *                      <p>
  *                         <code> <Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                            xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress></Grantee></code>
+ *                   xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress></Grantee></code>
  *                      </p>
- *                      <p>The grantee is resolved to the <code>CanonicalUser</code> and, in a
- *                         response to a <code>GETObjectAcl</code> request, appears as the
- *                         CanonicalUser.</p>
+ *                      <p>The grantee is resolved to the <code>CanonicalUser</code> and, in a response to a
+ *                   <code>GETObjectAcl</code> request, appears as the CanonicalUser.</p>
  *                   </li>
  *                   <li>
  *                      <p>By URI:</p>
  *                      <p>
  *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                            xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>
+ *                   xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>
  *                      </p>
  *                   </li>
  *                </ul>
  *             </dd>
  *          </dl>
- *          <p>To enable logging, you use <code>LoggingEnabled</code> and its children request
- *          elements. To disable logging, you use an empty <code>BucketLoggingStatus</code> request
- *          element:</p>
+ *          <p>To enable logging, you use <code>LoggingEnabled</code> and its children request elements. To disable
+ *       logging, you use an empty <code>BucketLoggingStatus</code> request element:</p>
  *          <p>
- *             <code><BucketLoggingStatus xmlns="http://doc.s3.amazonaws.com/2006-03-01"
- *             /></code>
+ *             <code><BucketLoggingStatus xmlns="http://doc.s3.amazonaws.com/2006-03-01" /></code>
  *          </p>
  *          <p>For more information about server access logging, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerLogs.html">Server Access Logging</a> in the
- *             <i>Amazon S3 User Guide</i>. </p>
- *          <p>For more information about creating a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html">CreateBucket</a>. For more
- *          information about returning the logging status of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLogging.html">GetBucketLogging</a>.</p>
+ *         <i>Amazon S3 User Guide</i>. </p>
+ *          <p>For more information about creating a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html">CreateBucket</a>. For more information about
+ *       returning the logging status of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLogging.html">GetBucketLogging</a>.</p>
  *          <p>The following operations are related to <code>PutBucketLogging</code>:</p>
  *          <ul>
  *             <li>