@aws-sdk/client-s3 3.844.0 → 3.846.0

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

@@ -30,19 +30,17 @@ declare const PutBucketMetricsConfigurationCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Sets a metrics configuration (specified by the metrics configuration ID) for the bucket.
- *          You can have up to 1,000 metrics configurations per bucket. If you're updating an existing
- *          metrics configuration, note that this is a full replacement of the existing metrics
- *          configuration. If you don't include the elements you want to keep, they are erased.</p>
+ *          <p>Sets a metrics configuration (specified by the metrics configuration ID) for the bucket. You can
+ *       have up to 1,000 metrics configurations per bucket. If you're updating an existing metrics
+ *       configuration, note that this is a full replacement of the existing metrics configuration. If you don't
+ *       include the elements you want to keep, they are erased.</p>
  *          <p>To use this operation, you must have permissions to perform the
- *             <code>s3:PutMetricsConfiguration</code> action. 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 Subresource 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>.</p>
- *          <p>For information about CloudWatch request metrics for Amazon S3, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html">Monitoring
- *             Metrics with Amazon CloudWatch</a>.</p>
- *          <p>The following operations are related to
- *          <code>PutBucketMetricsConfiguration</code>:</p>
+ *         <code>s3:PutMetricsConfiguration</code> action. 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 Subresource 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>.</p>
+ *          <p>For information about CloudWatch request metrics for Amazon S3, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html">Monitoring Metrics with Amazon
+ *       CloudWatch</a>.</p>
+ *          <p>The following operations are related to <code>PutBucketMetricsConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -68,8 +66,8 @@ declare const PutBucketMetricsConfigurationCommand_base: {
  *                </p>
  *                <ul>
  *                   <li>
- *                      <p>Description: You are attempting to create a new configuration but have
- *                      already reached the 1,000-configuration limit.</p>
+ *                      <p>Description: You are attempting to create a new configuration but have already reached the
+ *               1,000-configuration limit.</p>
  *                   </li>
  *                   <li>
  *                      <p>HTTP Status Code: HTTP 400 Bad Request</p>

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

@@ -31,50 +31,44 @@ declare const PutBucketNotificationConfigurationCommand_base: {
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Enables notifications of specified events for a bucket. For more information about event
- *          notifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Event
- *          Notifications</a>.</p>
- *          <p>Using this API, you can replace an existing notification configuration. The
- *          configuration is an XML file that defines the event types that you want Amazon S3 to publish and
- *          the destination where you want Amazon S3 to publish an event notification when it detects an
- *          event of the specified type.</p>
+ *       notifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Event Notifications</a>.</p>
+ *          <p>Using this API, you can replace an existing notification configuration. The configuration is an XML
+ *       file that defines the event types that you want Amazon S3 to publish and the destination where you want Amazon S3
+ *       to publish an event notification when it detects an event of the specified type.</p>
  *          <p>By default, your bucket has no event notifications configured. That is, the notification
- *          configuration will be an empty <code>NotificationConfiguration</code>.</p>
+ *       configuration will be an empty <code>NotificationConfiguration</code>.</p>
  *          <p>
  *             <code><NotificationConfiguration></code>
  *          </p>
  *          <p>
  *             <code></NotificationConfiguration></code>
  *          </p>
- *          <p>This action replaces the existing notification configuration with the configuration you
- *          include in the request body.</p>
- *          <p>After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification
- *          Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and
- *          that the bucket owner has permission to publish to it by sending a test notification. In
- *          the case of Lambda destinations, Amazon S3 verifies that the Lambda function permissions
- *          grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information,
- *          see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Notifications for Amazon S3 Events</a>.</p>
- *          <p>You can disable notifications by adding the empty NotificationConfiguration
- *          element.</p>
- *          <p>For more information about the number of event notification configurations that you can
- *          create per bucket, see <a href="https://docs.aws.amazon.com/general/latest/gr/s3.html#limits_s3">Amazon S3 service quotas</a> in <i>Amazon Web Services
- *             General Reference</i>.</p>
- *          <p>By default, only the bucket owner can configure notifications on a bucket. However,
- *          bucket owners can use a bucket policy to grant permission to other users to set this
- *          configuration with the required <code>s3:PutBucketNotification</code> permission.</p>
+ *          <p>This action replaces the existing notification configuration with the configuration you include in
+ *       the request body.</p>
+ *          <p>After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification Service
+ *       (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and that the bucket owner
+ *       has permission to publish to it by sending a test notification. In the case of Lambda destinations,
+ *       Amazon S3 verifies that the Lambda function permissions grant Amazon S3 permission to invoke the function from the
+ *       Amazon S3 bucket. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Notifications for Amazon S3
+ *       Events</a>.</p>
+ *          <p>You can disable notifications by adding the empty NotificationConfiguration element.</p>
+ *          <p>For more information about the number of event notification configurations that you can create per
+ *       bucket, see <a href="https://docs.aws.amazon.com/general/latest/gr/s3.html#limits_s3">Amazon S3 service
+ *         quotas</a> in <i>Amazon Web Services General Reference</i>.</p>
+ *          <p>By default, only the bucket owner can configure notifications on a bucket. However, bucket owners
+ *       can use a bucket policy to grant permission to other users to set this configuration with the required
+ *         <code>s3:PutBucketNotification</code> permission.</p>
  *          <note>
- *             <p>The PUT notification is an atomic operation. For example, suppose your notification
- *             configuration includes SNS topic, SQS queue, and Lambda function configurations. When
- *             you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS
- *             topic. If the message fails, the entire PUT action will fail, and Amazon S3 will not add the
- *             configuration to your bucket.</p>
+ *             <p>The PUT notification is an atomic operation. For example, suppose your notification configuration
+ *         includes SNS topic, SQS queue, and Lambda function configurations. When you send a PUT request with
+ *         this configuration, Amazon S3 sends test messages to your SNS topic. If the message fails, the entire PUT
+ *         action will fail, and Amazon S3 will not add the configuration to your bucket.</p>
  *          </note>
- *          <p>If the configuration in the request body includes only one
- *             <code>TopicConfiguration</code> specifying only the
- *             <code>s3:ReducedRedundancyLostObject</code> event type, the response will also include
- *          the <code>x-amz-sns-test-message-id</code> header containing the message ID of the test
- *          notification sent to the topic.</p>
- *          <p>The following action is related to
- *          <code>PutBucketNotificationConfiguration</code>:</p>
+ *          <p>If the configuration in the request body includes only one <code>TopicConfiguration</code>
+ *       specifying only the <code>s3:ReducedRedundancyLostObject</code> event type, the response will also
+ *       include the <code>x-amz-sns-test-message-id</code> header containing the message ID of the test
+ *       notification sent to the topic.</p>
+ *          <p>The following action is related to <code>PutBucketNotificationConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>

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

@@ -30,12 +30,10 @@ declare const PutBucketOwnershipControlsCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Creates or modifies <code>OwnershipControls</code> for an Amazon S3 bucket. To use this
- *          operation, you must have the <code>s3:PutBucketOwnershipControls</code> permission. For
- *          more information about Amazon S3 permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-with-s3-actions.html">Specifying permissions in a
- *             policy</a>. </p>
- *          <p>For information about Amazon S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/about-object-ownership.html">Using object
- *             ownership</a>. </p>
+ *          <p>Creates or modifies <code>OwnershipControls</code> for an Amazon S3 bucket. To use this operation, you
+ *       must have the <code>s3:PutBucketOwnershipControls</code> permission. For more information about Amazon S3
+ *       permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-with-s3-actions.html">Specifying permissions in a policy</a>. </p>
+ *          <p>For information about Amazon S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/about-object-ownership.html">Using object ownership</a>. </p>
  *          <p>The following operations are related to <code>PutBucketOwnershipControls</code>:</p>
  *          <ul>
  *             <li>

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

@@ -39,51 +39,46 @@ declare const PutBucketPolicyCommand_base: {
  *          <dl>
  *             <dt>Permissions</dt>
  *             <dd>
- *                <p>If you are using an identity other than the root user of the Amazon Web Services account that
- *                   owns the bucket, the calling identity must both have the
- *                      <code>PutBucketPolicy</code> permissions on the specified bucket and belong to
- *                   the bucket owner's account in order to use this operation.</p>
- *                <p>If you don't have <code>PutBucketPolicy</code> permissions, Amazon S3 returns a
- *                      <code>403 Access Denied</code> error. If you have the correct permissions, but
- *                   you're not using an identity that belongs to the bucket owner's account, Amazon S3
- *                   returns a <code>405 Method Not Allowed</code> error.</p>
+ *                <p>If you are using an identity other than the root user of the Amazon Web Services account that owns the
+ *             bucket, the calling identity must both have the <code>PutBucketPolicy</code> permissions on the
+ *             specified bucket and belong to the bucket owner's account in order to use this operation.</p>
+ *                <p>If you don't have <code>PutBucketPolicy</code> permissions, Amazon S3 returns a <code>403 Access
+ *               Denied</code> error. If you have the correct permissions, but you're not using an identity that
+ *             belongs to the bucket owner's account, Amazon S3 returns a <code>405 Method Not Allowed</code>
+ *             error.</p>
  *                <important>
- *                   <p>To ensure that bucket owners don't inadvertently lock themselves out of
- *                      their own buckets, the root principal in a bucket owner's Amazon Web Services account can
- *                      perform the <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and
- *                         <code>DeleteBucketPolicy</code> API actions, even if their bucket policy
- *                      explicitly denies the root principal's access. Bucket owner root principals can
- *                      only be blocked from performing these API actions by VPC endpoint policies and
- *                      Amazon Web Services Organizations policies.</p>
+ *                   <p>To ensure that bucket owners don't inadvertently lock themselves out of their own buckets,
+ *               the root principal in a bucket owner's Amazon Web Services account can perform the
+ *                 <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and
+ *                 <code>DeleteBucketPolicy</code> API actions, even if their bucket policy explicitly denies the
+ *               root principal's access. Bucket owner root principals can only be blocked from performing these
+ *               API actions by VPC endpoint policies and Amazon Web Services Organizations policies.</p>
  *                </important>
  *                <ul>
  *                   <li>
  *                      <p>
  *                         <b>General purpose bucket permissions</b> - The
- *                            <code>s3:PutBucketPolicy</code> permission is required in a policy. For
- *                         more information about general purpose buckets bucket policies, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html">Using Bucket Policies and User Policies</a> in the
- *                            <i>Amazon S3 User Guide</i>.</p>
+ *                   <code>s3:PutBucketPolicy</code> permission is required in a policy. For more information
+ *                 about general purpose buckets bucket policies, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html">Using Bucket Policies and User
+ *                   Policies</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:PutBucketPolicy</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>
+ *                         <b>Directory bucket permissions</b> - To grant access to
+ *                 this API operation, you must have the <code>s3express:PutBucketPolicy</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>
  *                   </li>
  *                </ul>
  *             </dd>
  *             <dt>Example bucket policies</dt>
  *             <dd>
  *                <p>
- *                   <b>General purpose buckets example bucket policies</b>
- *                   - See <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html">Bucket policy
- *                      examples</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                   <b>General purpose buckets example bucket policies</b> - See <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html">Bucket policy
+ *               examples</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                <p>
- *                   <b>Directory bucket example bucket policies</b>
- *                   - See <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html">Example bucket policies for S3 Express One Zone</a> in the
- *                      <i>Amazon S3 User Guide</i>.</p>
+ *                   <b>Directory bucket example bucket policies</b> - See <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html">Example
+ *               bucket policies for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
  *             </dd>
  *             <dt>HTTP Host header syntax</dt>
  *             <dd>

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

@@ -30,60 +30,53 @@ declare const PutBucketReplicationCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p> Creates a replication configuration or replaces an existing one. For more information,
- *          see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html">Replication</a> in the <i>Amazon S3 User Guide</i>. </p>
- *          <p>Specify the replication configuration in the request body. In the replication
- *          configuration, you provide the name of the destination bucket or buckets where you want
- *          Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your
- *          behalf, and other relevant information. You can invoke this request for a specific Amazon Web Services
- *          Region by using the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-requestedregion">
+ *          <p> Creates a replication configuration or replaces an existing one. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html">Replication</a> in the
+ *         <i>Amazon S3 User Guide</i>. </p>
+ *          <p>Specify the replication configuration in the request body. In the replication configuration, you
+ *       provide the name of the destination bucket or buckets where you want Amazon S3 to replicate objects, the
+ *       IAM role that Amazon S3 can assume to replicate objects on your behalf, and other relevant information. You
+ *       can invoke this request for a specific Amazon Web Services Region by using the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-requestedregion">
  *                <code>aws:RequestedRegion</code>
  *             </a> condition key.</p>
- *          <p>A replication configuration must include at least one rule, and can contain a maximum of
- *          1,000. Each rule identifies a subset of objects to replicate by filtering the objects in
- *          the source bucket. To choose additional subsets of objects to replicate, add a rule for
- *          each subset.</p>
- *          <p>To specify a subset of the objects in the source bucket to apply a replication rule to,
- *          add the Filter element as a child of the Rule element. You can filter objects based on an
- *          object key prefix, one or more object tags, or both. When you add the Filter element in the
- *          configuration, you must also add the following elements:
- *             <code>DeleteMarkerReplication</code>, <code>Status</code>, and
- *          <code>Priority</code>.</p>
+ *          <p>A replication configuration must include at least one rule, and can contain a maximum of 1,000. Each
+ *       rule identifies a subset of objects to replicate by filtering the objects in the source bucket. To
+ *       choose additional subsets of objects to replicate, add a rule for each subset.</p>
+ *          <p>To specify a subset of the objects in the source bucket to apply a replication rule to, add the
+ *       Filter element as a child of the Rule element. You can filter objects based on an object key prefix, one
+ *       or more object tags, or both. When you add the Filter element in the configuration, you must also add
+ *       the following elements: <code>DeleteMarkerReplication</code>, <code>Status</code>, and
+ *         <code>Priority</code>.</p>
  *          <note>
- *             <p>If you are using an earlier version of the replication configuration, Amazon S3 handles
- *             replication of delete markers differently. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-add-config.html#replication-backward-compat-considerations">Backward Compatibility</a>.</p>
+ *             <p>If you are using an earlier version of the replication configuration, Amazon S3 handles replication of
+ *         delete markers differently. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-add-config.html#replication-backward-compat-considerations">Backward Compatibility</a>.</p>
  *          </note>
  *          <p>For information about enabling versioning on a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html">Using Versioning</a>.</p>
  *          <dl>
  *             <dt>Handling Replication of Encrypted Objects</dt>
  *             <dd>
- *                <p>By default, Amazon S3 doesn't replicate objects that are stored at rest using
- *                   server-side encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects,
- *                   add the following: <code>SourceSelectionCriteria</code>,
- *                      <code>SseKmsEncryptedObjects</code>, <code>Status</code>,
- *                      <code>EncryptionConfiguration</code>, and <code>ReplicaKmsKeyID</code>. For
- *                   information about replication configuration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-config-for-kms-objects.html">Replicating
- *                      Objects Created with SSE Using KMS keys</a>.</p>
+ *                <p>By default, Amazon S3 doesn't replicate objects that are stored at rest using server-side
+ *             encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects, add the following:
+ *               <code>SourceSelectionCriteria</code>, <code>SseKmsEncryptedObjects</code>, <code>Status</code>,
+ *               <code>EncryptionConfiguration</code>, and <code>ReplicaKmsKeyID</code>. For information about
+ *             replication configuration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-config-for-kms-objects.html">Replicating Objects Created
+ *               with SSE Using KMS keys</a>.</p>
  *                <p>For information on <code>PutBucketReplication</code> errors, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ReplicationErrorCodeList">List of
- *                      replication-related error codes</a>
+ *               replication-related error codes</a>
  *                </p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
  *                <p>To create a <code>PutBucketReplication</code> request, you must have
- *                      <code>s3:PutReplicationConfiguration</code> permissions for the bucket.
+ *               <code>s3:PutReplicationConfiguration</code> permissions for the bucket.
  *
- *                </p>
- *                <p>By default, a resource owner, in this case the Amazon Web Services account that created the
- *                   bucket, can perform this operation. The resource owner can also grant others
- *                   permissions to perform the operation. For more information about permissions, see
- *                      <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html">Specifying Permissions in
- *                      a Policy</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>.</p>
+ *           </p>
+ *                <p>By default, a resource owner, in this case the Amazon Web Services account that created the bucket, can
+ *             perform this operation. The resource owner can also grant others permissions to perform the
+ *             operation. For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html">Specifying Permissions in a Policy</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>.</p>
  *                <note>
- *                   <p>To perform this operation, the user or role performing the action must have
- *                      the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_passrole.html">iam:PassRole</a>
- *                      permission.</p>
+ *                   <p>To perform this operation, the user or role performing the action must have the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_passrole.html">iam:PassRole</a> permission.</p>
  *                </note>
  *             </dd>
  *          </dl>

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

@@ -30,11 +30,10 @@ declare const PutBucketRequestPaymentCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Sets the request payment configuration for a bucket. By default, the bucket owner pays
- *          for downloads from the bucket. This configuration parameter enables the bucket owner (only)
- *          to specify that the person requesting the download will be charged for the download. For
- *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html">Requester Pays
- *          Buckets</a>.</p>
+ *          <p>Sets the request payment configuration for a bucket. By default, the bucket owner pays for downloads
+ *       from the bucket. This configuration parameter enables the bucket owner (only) to specify that the person
+ *       requesting the download will be charged for the download. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html">Requester Pays
+ *         Buckets</a>.</p>
  *          <p>The following operations are related to <code>PutBucketRequestPayment</code>:</p>
  *          <ul>
  *             <li>

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

@@ -31,48 +31,42 @@ declare const PutBucketTaggingCommand_base: {
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the tags for a bucket.</p>
- *          <p>Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this,
- *          sign up to get your Amazon Web Services account bill with tag key values included. Then, to see the cost
- *          of combined resources, organize your billing information according to resources with the
- *          same tag key values. For example, you can tag several resources with a specific application
- *          name, and then organize your billing information to see the total cost of that application
- *          across several services. For more information, see <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html">Cost Allocation and
- *             Tagging</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/CostAllocTagging.html">Using Cost Allocation in Amazon S3
- *             Bucket Tags</a>.</p>
+ *          <p>Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this, sign up to get
+ *       your Amazon Web Services account bill with tag key values included. Then, to see the cost of combined resources,
+ *       organize your billing information according to resources with the same tag key values. For example, you
+ *       can tag several resources with a specific application name, and then organize your billing information
+ *       to see the total cost of that application across several services. For more information, see <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html">Cost Allocation and
+ *         Tagging</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/CostAllocTagging.html">Using Cost Allocation in Amazon S3 Bucket Tags</a>.</p>
  *          <note>
- *             <p> When this operation sets the tags for a bucket, it will overwrite any current tags
- *             the bucket already has. You cannot use this operation to add tags to an existing list of
- *             tags.</p>
+ *             <p> When this operation sets the tags for a bucket, it will overwrite any current tags the bucket
+ *         already has. You cannot use this operation to add tags to an existing list of tags.</p>
  *          </note>
- *          <p>To use this operation, you must have permissions to perform the
- *             <code>s3:PutBucketTagging</code> action. The bucket owner has this permission by default
- *          and 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 Subresource 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>.</p>
+ *          <p>To use this operation, you must have permissions to perform the <code>s3:PutBucketTagging</code>
+ *       action. The bucket owner has this permission by default and 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 Subresource 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>.</p>
  *          <p>
- *             <code>PutBucketTagging</code> has the following special errors. For more Amazon S3 errors
- *          see, <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html">Error
- *             Responses</a>.</p>
+ *             <code>PutBucketTagging</code> has the following special errors. For more Amazon S3 errors see, <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html">Error Responses</a>.</p>
  *          <ul>
  *             <li>
  *                <p>
- *                   <code>InvalidTag</code> - The tag provided was not a valid tag. This error
- *                can occur if the tag did not pass input validation. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/CostAllocTagging.html">Using
- *                   Cost Allocation in Amazon S3 Bucket Tags</a>.</p>
+ *                   <code>InvalidTag</code> - The tag provided was not a valid tag. This error can occur if
+ *           the tag did not pass input validation. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/CostAllocTagging.html">Using Cost Allocation in Amazon S3 Bucket
+ *             Tags</a>.</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <code>MalformedXML</code> - The XML provided does not match the
- *                schema.</p>
+ *                   <code>MalformedXML</code> - The XML provided does not match the schema.</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <code>OperationAborted</code> - A conflicting conditional action is
- *                currently in progress against this resource. Please try again.</p>
+ *                   <code>OperationAborted</code> - A conflicting conditional action is currently in progress
+ *           against this resource. Please try again.</p>
  *             </li>
  *             <li>
  *                <p>
- *                   <code>InternalError</code> - The service was unable to apply the provided
- *                tag to the bucket.</p>
+ *                   <code>InternalError</code> - The service was unable to apply the provided tag to the
+ *           bucket.</p>
  *             </li>
  *          </ul>
  *          <p>The following operations are related to <code>PutBucketTagging</code>:</p>

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

@@ -31,35 +31,32 @@ declare const PutBucketVersioningCommand_base: {
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <note>
- *             <p>When you enable versioning on a bucket for the first time, it might take a short
- *             amount of time for the change to be fully propagated. While this change is propagating,
- *             you might encounter intermittent <code>HTTP 404 NoSuchKey</code> errors for requests to
- *             objects created or updated after enabling versioning. We recommend that you wait for 15
- *             minutes after enabling versioning before issuing write operations (<code>PUT</code> or
- *             <code>DELETE</code>) on objects in the bucket. </p>
+ *             <p>When you enable versioning on a bucket for the first time, it might take a short amount of time
+ *         for the change to be fully propagated. While this change is propagating, you might encounter
+ *         intermittent <code>HTTP 404 NoSuchKey</code> errors for requests to objects created or updated after
+ *         enabling versioning. We recommend that you wait for 15 minutes after enabling versioning before
+ *         issuing write operations (<code>PUT</code> or <code>DELETE</code>) on objects in the bucket. </p>
  *          </note>
  *          <p>Sets the versioning state of an existing bucket.</p>
  *          <p>You can set the versioning state with one of the following values:</p>
  *          <p>
- *             <b>Enabled</b>—Enables versioning for the objects in the
- *          bucket. All objects added to the bucket receive a unique version ID.</p>
+ *             <b>Enabled</b>—Enables versioning for the objects in the bucket. All
+ *       objects added to the bucket receive a unique version ID.</p>
  *          <p>
- *             <b>Suspended</b>—Disables versioning for the objects in the
- *          bucket. All objects added to the bucket receive the version ID null.</p>
- *          <p>If the versioning state has never been set on a bucket, it has no versioning state; a
- *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a> request does not return a versioning state value.</p>
- *          <p>In order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner
- *          and want to enable MFA Delete in the bucket versioning configuration, you must include the
- *             <code>x-amz-mfa request</code> header and the <code>Status</code> and the
- *             <code>MfaDelete</code> request elements in a request to set the versioning state of the
- *          bucket.</p>
+ *             <b>Suspended</b>—Disables versioning for the objects in the bucket. All
+ *       objects added to the bucket receive the version ID null.</p>
+ *          <p>If the versioning state has never been set on a bucket, it has no versioning state; a <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a> request does not return a versioning state value.</p>
+ *          <p>In order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner and want to
+ *       enable MFA Delete in the bucket versioning configuration, you must include the <code>x-amz-mfa
+ *         request</code> header and the <code>Status</code> and the <code>MfaDelete</code> request elements in a
+ *       request to set the versioning state of the bucket.</p>
  *          <important>
- *             <p>If you have an object expiration lifecycle configuration in your non-versioned bucket
- *             and you want to maintain the same permanent delete behavior when you enable versioning,
- *             you must add a noncurrent expiration policy. The noncurrent expiration lifecycle
- *             configuration will manage the deletes of the noncurrent object versions in the
- *             version-enabled bucket. (A version-enabled bucket maintains one current and zero or more
- *             noncurrent object versions.) For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html#lifecycle-and-other-bucket-config">Lifecycle and Versioning</a>.</p>
+ *             <p>If you have an object expiration lifecycle configuration in your non-versioned bucket and you want
+ *         to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent
+ *         expiration policy. The noncurrent expiration lifecycle configuration will manage the deletes of the
+ *         noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one
+ *         current and zero or more noncurrent object versions.) For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html#lifecycle-and-other-bucket-config">Lifecycle and
+ *           Versioning</a>.</p>
  *          </important>
  *          <p>The following operations are related to <code>PutBucketVersioning</code>:</p>
  *          <ul>

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

@@ -30,17 +30,18 @@ declare const PutBucketWebsiteCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Sets the configuration of the website that is specified in the <code>website</code>
- *          subresource. To configure a bucket as a website, you can add this subresource on the bucket
- *          with website configuration information such as the file name of the index document and any
- *          redirect rules. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html">Hosting Websites on Amazon S3</a>.</p>
- *          <p>This PUT action requires the <code>S3:PutBucketWebsite</code> permission. By default,
- *          only the bucket owner can configure the website attached to a bucket; however, bucket
- *          owners can allow other users to set the website configuration by writing a bucket policy
- *          that grants them the <code>S3:PutBucketWebsite</code> permission.</p>
- *          <p>To redirect all website requests sent to the bucket's website endpoint, you add a
- *          website configuration with the following elements. Because all requests are sent to another
- *          website, you don't need to provide index document name for the bucket.</p>
+ *          <p>Sets the configuration of the website that is specified in the <code>website</code> subresource. To
+ *       configure a bucket as a website, you can add this subresource on the bucket with website configuration
+ *       information such as the file name of the index document and any redirect rules. For more information,
+ *       see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html">Hosting Websites on
+ *         Amazon S3</a>.</p>
+ *          <p>This PUT action requires the <code>S3:PutBucketWebsite</code> permission. By default, only the
+ *       bucket owner can configure the website attached to a bucket; however, bucket owners can allow other
+ *       users to set the website configuration by writing a bucket policy that grants them the
+ *         <code>S3:PutBucketWebsite</code> permission.</p>
+ *          <p>To redirect all website requests sent to the bucket's website endpoint, you add a website
+ *       configuration with the following elements. Because all requests are sent to another website, you don't
+ *       need to provide index document name for the bucket.</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -63,10 +64,10 @@ declare const PutBucketWebsiteCommand_base: {
  *                </p>
  *             </li>
  *          </ul>
- *          <p>If you want granular control over redirects, you can use the following elements to add
- *          routing rules that describe conditions for redirecting requests and information about the
- *          redirect destination. In this case, the website configuration must provide an index
- *          document for the bucket, because some requests might not be redirected. </p>
+ *          <p>If you want granular control over redirects, you can use the following elements to add routing rules
+ *       that describe conditions for redirecting requests and information about the redirect destination. In
+ *       this case, the website configuration must provide an index document for the bucket, because some
+ *       requests might not be redirected. </p>
  *          <ul>
  *             <li>
  *                <p>
@@ -149,9 +150,9 @@ declare const PutBucketWebsiteCommand_base: {
  *                </p>
  *             </li>
  *          </ul>
- *          <p>Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more
- *          than 50 routing rules, you can use object redirect. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html">Configuring an
- *             Object Redirect</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more than 50
+ *       routing rules, you can use object redirect. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html">Configuring an Object Redirect</a> in the
+ *         <i>Amazon S3 User Guide</i>.</p>
  *          <p>The maximum request length is limited to 128 KB.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.