From d5b27f31c7ec4928c89915b1cc97604041a2e658 Mon Sep 17 00:00:00 2001
From: awstools <awstools@amazon.com>
Date: Thu, 21 Nov 2024 19:24:39 +0000
Subject: [PATCH] feat(client-s3): Add support for conditional deletes for the
 S3 DeleteObject and DeleteObjects APIs. Add support for write offset bytes
 option used to append to objects with the S3 PutObject API.

---
 .../commands/AbortMultipartUploadCommand.ts   |   29 +-
 .../CompleteMultipartUploadCommand.ts         |   89 +-
 .../src/commands/CopyObjectCommand.ts         |  134 +-
 .../src/commands/CreateBucketCommand.ts       |  105 +-
 .../commands/CreateMultipartUploadCommand.ts  |  158 +-
 .../src/commands/CreateSessionCommand.ts      |   46 +-
 ...leteBucketAnalyticsConfigurationCommand.ts |    2 +-
 .../src/commands/DeleteBucketCommand.ts       |   13 +-
 .../src/commands/DeleteBucketCorsCommand.ts   |    2 +-
 .../commands/DeleteBucketEncryptionCommand.ts |   28 +-
 ...tIntelligentTieringConfigurationCommand.ts |    2 +-
 ...leteBucketInventoryConfigurationCommand.ts |    2 +-
 .../commands/DeleteBucketLifecycleCommand.ts  |   61 +-
 ...DeleteBucketMetricsConfigurationCommand.ts |    2 +-
 .../DeleteBucketOwnershipControlsCommand.ts   |    2 +-
 .../src/commands/DeleteBucketPolicyCommand.ts |   46 +-
 .../DeleteBucketReplicationCommand.ts         |    2 +-
 .../commands/DeleteBucketTaggingCommand.ts    |    2 +-
 .../commands/DeleteBucketWebsiteCommand.ts    |    2 +-
 .../src/commands/DeleteObjectCommand.ts       |    3 +
 .../commands/DeleteObjectTaggingCommand.ts    |    2 +-
 .../src/commands/DeleteObjectsCommand.ts      |   68 +-
 .../DeletePublicAccessBlockCommand.ts         |    2 +-
 ...GetBucketAccelerateConfigurationCommand.ts |    2 +-
 .../src/commands/GetBucketAclCommand.ts       |    2 +-
 .../GetBucketAnalyticsConfigurationCommand.ts |    2 +-
 .../src/commands/GetBucketCorsCommand.ts      |    2 +-
 .../commands/GetBucketEncryptionCommand.ts    |   28 +-
 ...tIntelligentTieringConfigurationCommand.ts |    2 +-
 .../GetBucketInventoryConfigurationCommand.ts |    2 +-
 .../GetBucketLifecycleConfigurationCommand.ts |   78 +-
 .../src/commands/GetBucketLocationCommand.ts  |    2 +-
 .../src/commands/GetBucketLoggingCommand.ts   |    2 +-
 .../GetBucketMetricsConfigurationCommand.ts   |    2 +-
 ...tBucketNotificationConfigurationCommand.ts |    2 +-
 .../GetBucketOwnershipControlsCommand.ts      |    2 +-
 .../src/commands/GetBucketPolicyCommand.ts    |   51 +-
 .../commands/GetBucketPolicyStatusCommand.ts  |    2 +-
 .../commands/GetBucketReplicationCommand.ts   |    2 +-
 .../GetBucketRequestPaymentCommand.ts         |    2 +-
 .../src/commands/GetBucketTaggingCommand.ts   |    2 +-
 .../commands/GetBucketVersioningCommand.ts    |    2 +-
 .../src/commands/GetBucketWebsiteCommand.ts   |    2 +-
 .../src/commands/GetObjectAclCommand.ts       |    2 +-
 .../commands/GetObjectAttributesCommand.ts    |  106 +-
 .../src/commands/GetObjectCommand.ts          |  139 +-
 .../src/commands/GetObjectLegalHoldCommand.ts |    2 +-
 .../GetObjectLockConfigurationCommand.ts      |    2 +-
 .../src/commands/GetObjectRetentionCommand.ts |    2 +-
 .../src/commands/GetObjectTaggingCommand.ts   |    2 +-
 .../src/commands/GetObjectTorrentCommand.ts   |    2 +-
 .../commands/GetPublicAccessBlockCommand.ts   |    2 +-
 .../src/commands/HeadBucketCommand.ts         |   48 +-
 .../src/commands/HeadObjectCommand.ts         |   98 +-
 ...istBucketAnalyticsConfigurationsCommand.ts |    2 +-
 ...IntelligentTieringConfigurationsCommand.ts |    2 +-
 ...istBucketInventoryConfigurationsCommand.ts |    2 +-
 .../ListBucketMetricsConfigurationsCommand.ts |    2 +-
 .../src/commands/ListBucketsCommand.ts        |   12 +-
 .../commands/ListDirectoryBucketsCommand.ts   |   14 +-
 .../commands/ListMultipartUploadsCommand.ts   |   83 +-
 .../src/commands/ListObjectVersionsCommand.ts |    2 +-
 .../src/commands/ListObjectsCommand.ts        |    2 +-
 .../src/commands/ListObjectsV2Command.ts      |   37 +-
 .../src/commands/ListPartsCommand.ts          |   39 +-
 ...PutBucketAccelerateConfigurationCommand.ts |    2 +-
 .../src/commands/PutBucketAclCommand.ts       |    2 +-
 .../PutBucketAnalyticsConfigurationCommand.ts |    2 +-
 .../src/commands/PutBucketCorsCommand.ts      |    2 +-
 .../commands/PutBucketEncryptionCommand.ts    |   79 +-
 ...tIntelligentTieringConfigurationCommand.ts |    2 +-
 .../PutBucketInventoryConfigurationCommand.ts |    2 +-
 .../PutBucketLifecycleConfigurationCommand.ts |  129 +-
 .../src/commands/PutBucketLoggingCommand.ts   |    2 +-
 .../PutBucketMetricsConfigurationCommand.ts   |    2 +-
 ...tBucketNotificationConfigurationCommand.ts |    2 +-
 .../PutBucketOwnershipControlsCommand.ts      |    2 +-
 .../src/commands/PutBucketPolicyCommand.ts    |   51 +-
 .../commands/PutBucketReplicationCommand.ts   |    7 +-
 .../PutBucketRequestPaymentCommand.ts         |    2 +-
 .../src/commands/PutBucketTaggingCommand.ts   |    2 +-
 .../commands/PutBucketVersioningCommand.ts    |    9 +-
 .../src/commands/PutBucketWebsiteCommand.ts   |    2 +-
 .../src/commands/PutObjectAclCommand.ts       |    2 +-
 .../src/commands/PutObjectCommand.ts          |  118 +-
 .../src/commands/PutObjectLegalHoldCommand.ts |    2 +-
 .../PutObjectLockConfigurationCommand.ts      |    6 +-
 .../src/commands/PutObjectRetentionCommand.ts |    2 +-
 .../src/commands/PutObjectTaggingCommand.ts   |    2 +-
 .../commands/PutPublicAccessBlockCommand.ts   |    2 +-
 .../src/commands/RestoreObjectCommand.ts      |    2 +-
 .../commands/SelectObjectContentCommand.ts    |    2 +-
 .../src/commands/UploadPartCommand.ts         |   93 +-
 .../src/commands/UploadPartCopyCommand.ts     |   92 +-
 .../commands/WriteGetObjectResponseCommand.ts |    2 +-
 clients/client-s3/src/models/models_0.ts      | 1577 ++++++++++-------
 clients/client-s3/src/models/models_1.ts      |  399 +++--
 .../client-s3/src/protocols/Aws_restXml.ts    |  100 +-
 codegen/sdk-codegen/aws-models/s3.json        |  704 +++++---
 99 files changed, 3069 insertions(+), 1932 deletions(-)

diff --git a/clients/client-s3/src/commands/AbortMultipartUploadCommand.ts b/clients/client-s3/src/commands/AbortMultipartUploadCommand.ts
index d912a79d6eb1..afdb0d44d58a 100644
--- a/clients/client-s3/src/commands/AbortMultipartUploadCommand.ts
+++ b/clients/client-s3/src/commands/AbortMultipartUploadCommand.ts
@@ -36,23 +36,24 @@ export interface AbortMultipartUploadCommandOutput extends AbortMultipartUploadO
  *          to abort a given multipart upload multiple times in order to completely free all storage
  *          consumed by all parts. </p>
  *          <p>To verify that all parts have been removed and prevent getting charged for the part
- *          storage, you should call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html">ListParts</a> API operation and ensure that
- *          the parts list is empty.</p>
+ *          storage, you should call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html">ListParts</a> API operation and ensure
+ *          that the parts list is empty.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> -
- *                   If multipart uploads in a directory bucket are in progress, you can't delete the bucket until all the in-progress multipart uploads are aborted or completed.
- *                   To delete these in-progress multipart uploads, use the
- *                <code>ListMultipartUploads</code> operation to list the in-progress multipart
- *                uploads in the bucket and use the <code>AbortMultipartUpload</code> operation to
- *                abort all the in-progress multipart uploads.
- *                </p>
+ *                      <b>Directory buckets</b> - If multipart
+ *                   uploads in a directory bucket are in progress, you can't delete the bucket until
+ *                   all the in-progress multipart uploads are aborted or completed. To delete these
+ *                   in-progress multipart uploads, use the <code>ListMultipartUploads</code> operation
+ *                   to list the in-progress multipart uploads in the bucket and use the
+ *                      <code>AbortMultipartUpload</code> operation to abort all the in-progress
+ *                   multipart uploads. </p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets</b> -
+ *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
@@ -64,9 +65,10 @@ export interface AbortMultipartUploadCommandOutput extends AbortMultipartUploadO
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - For information about permissions required to use the multipart upload, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload
- *                         and Permissions</a> in the <i>Amazon S3
- *                            User Guide</i>.</p>
+ *                         <b>General purpose bucket permissions</b> - For
+ *                         information about permissions required to use the multipart upload, see
+ *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
+ *                            Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -126,6 +128,7 @@ export interface AbortMultipartUploadCommandOutput extends AbortMultipartUploadO
  *   UploadId: "STRING_VALUE", // required
  *   RequestPayer: "requester",
  *   ExpectedBucketOwner: "STRING_VALUE",
+ *   IfMatchInitiatedTime: new Date("TIMESTAMP"),
  * };
  * const command = new AbortMultipartUploadCommand(input);
  * const response = await client.send(command);
diff --git a/clients/client-s3/src/commands/CompleteMultipartUploadCommand.ts b/clients/client-s3/src/commands/CompleteMultipartUploadCommand.ts
index de03417ea05d..abd0fe6b7aa8 100644
--- a/clients/client-s3/src/commands/CompleteMultipartUploadCommand.ts
+++ b/clients/client-s3/src/commands/CompleteMultipartUploadCommand.ts
@@ -37,41 +37,44 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
 /**
  * <p>Completes a multipart upload by assembling previously uploaded parts.</p>
  *          <p>You first initiate the multipart upload and then upload all parts using the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>
- *          operation or the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>
- *          operation. After successfully uploading all relevant parts of an upload, you call this
- *          <code>CompleteMultipartUpload</code> operation to complete the upload. Upon receiving this request, Amazon S3 concatenates all the parts
- *          in ascending order by part number to create a new object. In the CompleteMultipartUpload
- *          request, you must provide the parts list and ensure that the parts list is complete.
- *          The CompleteMultipartUpload API operation concatenates the parts that you provide in the list. For each part in the list,
- *          you must provide the <code>PartNumber</code> value and the <code>ETag</code> value that are returned after that part
- *          was uploaded.</p>
+ *          operation or the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> operation.
+ *          After successfully uploading all relevant parts of an upload, you call this
+ *             <code>CompleteMultipartUpload</code> operation to complete the upload. Upon receiving
+ *          this request, Amazon S3 concatenates all the parts in ascending order by part number to create a
+ *          new object. In the CompleteMultipartUpload request, you must provide the parts list and
+ *          ensure that the parts list is complete. The CompleteMultipartUpload API operation
+ *          concatenates the parts that you provide in the list. For each part in the list, you must
+ *          provide the <code>PartNumber</code> value and the <code>ETag</code> value that are returned
+ *          after that part was uploaded.</p>
  *          <p>The processing of a CompleteMultipartUpload request could take several minutes to
  *          finalize. After Amazon S3 begins processing the request, it sends an HTTP response header that
- *          specifies a <code>200 OK</code> response. While processing is in progress, Amazon S3 periodically sends white
- *          space characters to keep the connection from timing out. A request could fail after the
- *          initial <code>200 OK</code> response has been sent. This means that a <code>200 OK</code> response can
- *          contain either a success or an error. The error response might be embedded in the <code>200 OK</code> response.
- *          If you call this API operation directly, make sure to design
- *          your application to parse the contents of the response and handle it appropriately. If you
- *          use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the embedded error and apply
- *          error handling per your configuration settings (including automatically retrying the
- *          request as appropriate). If the condition persists, the SDKs throw an exception (or, for
- *          the SDKs that don't use exceptions, they return an error). </p>
+ *          specifies a <code>200 OK</code> response. While processing is in progress, Amazon S3
+ *          periodically sends white space characters to keep the connection from timing out. A request
+ *          could fail after the initial <code>200 OK</code> response has been sent. This means that a
+ *             <code>200 OK</code> response can contain either a success or an error. The error
+ *          response might be embedded in the <code>200 OK</code> response. If you call this API
+ *          operation directly, make sure to design your application to parse the contents of the
+ *          response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition.
+ *          The SDKs detect the embedded error and apply error handling per your configuration settings
+ *          (including automatically retrying the request as appropriate). If the condition persists,
+ *          the SDKs throw an exception (or, for the SDKs that don't use exceptions, they return an
+ *          error). </p>
  *          <p>Note that if <code>CompleteMultipartUpload</code> fails, applications should be prepared
- *          to retry any failed requests (including 500 error responses). For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html">Amazon S3 Error Best
- *          Practices</a>.</p>
+ *          to retry any failed requests (including 500 error responses). For more information, see
+ *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html">Amazon S3 Error
+ *             Best Practices</a>.</p>
  *          <important>
  *             <p>You can't use <code>Content-Type: application/x-www-form-urlencoded</code> for the
- *             CompleteMultipartUpload requests. Also, if you don't provide a
- *                <code>Content-Type</code> header, <code>CompleteMultipartUpload</code> can still return a <code>200
- *             OK</code> response.</p>
+ *             CompleteMultipartUpload requests. Also, if you don't provide a <code>Content-Type</code>
+ *             header, <code>CompleteMultipartUpload</code> can still return a <code>200 OK</code>
+ *             response.</p>
  *          </important>
  *          <p>For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading Objects Using Multipart
- *          Upload</a> in the <i>Amazon S3
- *             User Guide</i>.</p>
+ *             Upload</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 Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
@@ -86,10 +89,10 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
  *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
  *                            Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                      <p>If you provide an <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html">additional checksum
- *                         value</a> in your <code>MultipartUpload</code> requests and the
+ *                            value</a> in your <code>MultipartUpload</code> requests and the
  *                         object is encrypted with Key Management Service, you must have permission to use the
- *                         <code>kms:Decrypt</code> action for the
- *                         <code>CompleteMultipartUpload</code> request to succeed.</p>
+ *                            <code>kms:Decrypt</code> action for the
+ *                            <code>CompleteMultipartUpload</code> request to succeed.</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -99,9 +102,10 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
  * Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
  *                            <code>CreateSession</code>
  *                         </a>.</p>
- *                      <p>If the object is encrypted with
- *                         SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
+ *                      <p>If the object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -113,8 +117,9 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
  *                      </p>
  *                      <ul>
  *                         <li>
- *                            <p>Description: Your proposed upload is smaller than the minimum allowed object
- *                            size. Each part must be at least 5 MB in size, except the last part.</p>
+ *                            <p>Description: Your proposed upload is smaller than the minimum
+ *                               allowed object size. Each part must be at least 5 MB in size, except
+ *                               the last part.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 400 Bad Request</p>
@@ -126,9 +131,9 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
  *                      </p>
  *                      <ul>
  *                         <li>
- *                            <p>Description: One or more of the specified parts could not be found. The part
- *                            might not have been uploaded, or the specified ETag might not have
- *                            matched the uploaded part's ETag.</p>
+ *                            <p>Description: One or more of the specified parts could not be found.
+ *                               The part might not have been uploaded, or the specified ETag might not
+ *                               have matched the uploaded part's ETag.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 400 Bad Request</p>
@@ -140,8 +145,8 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
  *                      </p>
  *                      <ul>
  *                         <li>
- *                            <p>Description: The list of parts was not in ascending order. The parts list
- *                            must be specified in order by part number.</p>
+ *                            <p>Description: The list of parts was not in ascending order. The
+ *                               parts list must be specified in order by part number.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 400 Bad Request</p>
@@ -153,9 +158,9 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
  *                      </p>
  *                      <ul>
  *                         <li>
- *                            <p>Description: The specified multipart upload does not exist. The upload ID
- *                            might be invalid, or the multipart upload might have been aborted or
- *                            completed.</p>
+ *                            <p>Description: The specified multipart upload does not exist. The
+ *                               upload ID might be invalid, or the multipart upload might have been
+ *                               aborted or completed.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 404 Not Found</p>
diff --git a/clients/client-s3/src/commands/CopyObjectCommand.ts b/clients/client-s3/src/commands/CopyObjectCommand.ts
index 6bb02ca9bfa2..27e003c99b15 100644
--- a/clients/client-s3/src/commands/CopyObjectCommand.ts
+++ b/clients/client-s3/src/commands/CopyObjectCommand.ts
@@ -43,55 +43,63 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *             (UploadPartCopy) API. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjctsUsingRESTMPUapi.html">Copy Object Using the
  *                REST Multipart Upload API</a>.</p>
  *          </note>
- *          <p>You can copy individual objects between general purpose buckets, between directory buckets, and
- *          between general purpose buckets and directory buckets.</p>
+ *          <p>You can copy individual objects between general purpose buckets, between directory buckets,
+ *          and between general purpose buckets and directory buckets.</p>
  *          <note>
  *             <ul>
  *                <li>
- *                   <p>Amazon S3 supports copy operations using Multi-Region Access Points only as a destination when using the Multi-Region Access Point ARN. </p>
+ *                   <p>Amazon S3 supports copy operations using Multi-Region Access Points only as a
+ *                   destination when using the Multi-Region Access Point ARN. </p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets </b> -
+ *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
  *                <li>
- *                   <p>VPC endpoints don't support cross-Region requests (including copies). If you're using VPC endpoints, your source and destination buckets should be in the same Amazon Web Services Region as your VPC endpoint.</p>
+ *                   <p>VPC endpoints don't support cross-Region requests (including copies). If you're
+ *                   using VPC endpoints, your source and destination buckets should be in the same
+ *                   Amazon Web Services Region as your VPC endpoint.</p>
  *                </li>
  *             </ul>
  *          </note>
- *          <p>Both the
- *       Region that you want to copy the object from and the Region that you want to copy the
- *       object to must be enabled for your account. For more information about how to enable a Region for your account, see <a href="https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#manage-acct-regions-enable-standalone">Enable
- *          or disable a Region for standalone accounts</a> in the
- *          <i>Amazon Web Services Account Management Guide</i>.</p>
+ *          <p>Both the Region that you want to copy the object from and the Region that you want to
+ *          copy the object to must be enabled for your account. For more information about how to
+ *          enable a Region for your account, see <a href="https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#manage-acct-regions-enable-standalone">Enable or disable a Region for standalone accounts</a> in the <i>Amazon Web Services
+ *             Account Management Guide</i>.</p>
  *          <important>
  *             <p>Amazon S3 transfer acceleration does not support cross-Region copies. If you request a
  *             cross-Region copy using a transfer acceleration endpoint, you get a <code>400 Bad
  *                Request</code> error. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer
- *                   Acceleration</a>.</p>
+ *             Acceleration</a>.</p>
  *          </important>
  *          <dl>
  *             <dt>Authentication and authorization</dt>
  *             <dd>
- *                <p>All <code>CopyObject</code> requests must be authenticated and signed by using IAM credentials (access key ID and secret access key for the IAM identities). All headers with the <code>x-amz-</code> prefix, including
- *                         <code>x-amz-copy-source</code>, must be signed. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
+ *                <p>All <code>CopyObject</code> requests must be authenticated and signed by using
+ *                   IAM credentials (access key ID and secret access key for the IAM identities).
+ *                   All headers with the <code>x-amz-</code> prefix, including
+ *                      <code>x-amz-copy-source</code>, must be signed. For more information, see
+ *                      <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
  *                <p>
- *                   <b>Directory buckets</b> - You must use the IAM credentials to authenticate and authorize your access to the <code>CopyObject</code> API operation, instead of using the
- *                   temporary security credentials through the <code>CreateSession</code> API operation.</p>
- *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>
+ *                   <b>Directory buckets</b> - You must use the
+ *                   IAM credentials to authenticate and authorize your access to the
+ *                      <code>CopyObject</code> API operation, instead of using the temporary security
+ *                   credentials through the <code>CreateSession</code> API operation.</p>
+ *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your
+ *                   behalf.</p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
- *                <p>You must have
- *                   <i>read</i> access to the source object and <i>write</i>
- *                   access to the destination bucket.</p>
+ *                <p>You must have <i>read</i> access to the source object and
+ *                      <i>write</i> access to the destination bucket.</p>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> -
- *                         You must have permissions in an IAM policy based on the source and destination
+ *                         <b>General purpose bucket permissions</b> - You
+ *                         must have permissions in an IAM policy based on the source and destination
  *                         bucket types in a <code>CopyObject</code> operation.</p>
  *                      <ul>
  *                         <li>
@@ -113,30 +121,38 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *                   <li>
  *                      <p>
  *                         <b>Directory bucket permissions</b> -
- *                         You must have permissions in a bucket policy or an IAM identity-based policy based on the source and destination
- *                         bucket types in a <code>CopyObject</code> operation.</p>
+ *                         You must have permissions in a bucket policy or an IAM identity-based policy based on the
+ *                         source and destination bucket types in a <code>CopyObject</code>
+ *                         operation.</p>
  *                      <ul>
  *                         <li>
  *                            <p>If the source object that you want to copy is in a
  *                               directory bucket, you must have the <b>
  *                                  <code>s3express:CreateSession</code>
  *                               </b> permission in
- *                               the <code>Action</code> element of a policy to read the object. By default, the session is in the <code>ReadWrite</code> mode. If you want to restrict the access, you can explicitly set the <code>s3express:SessionMode</code> condition key to <code>ReadOnly</code> on the copy source bucket.</p>
+ *                               the <code>Action</code> element of a policy to read the object. By
+ *                               default, the session is in the <code>ReadWrite</code> mode. If you
+ *                               want to restrict the access, you can explicitly set the
+ *                                  <code>s3express:SessionMode</code> condition key to
+ *                                  <code>ReadOnly</code> on the copy source bucket.</p>
  *                         </li>
  *                         <li>
- *                            <p>If the copy destination is a directory bucket, you must have the <b>
+ *                            <p>If the copy destination is a directory bucket, you must have the
+ *                                  <b>
  *                                  <code>s3express:CreateSession</code>
  *                               </b> permission in the
- *                                  <code>Action</code> element of a policy to write the object
- *                               to the destination. The <code>s3express:SessionMode</code> condition
- *                               key can't be set to <code>ReadOnly</code> on the copy destination bucket. </p>
+ *                                  <code>Action</code> element of a policy to write the object to the
+ *                               destination. The <code>s3express:SessionMode</code> condition key
+ *                               can't be set to <code>ReadOnly</code> on the copy destination bucket.
+ *                            </p>
  *                         </li>
  *                      </ul>
- *                      <p>If the object is encrypted with
- *                         SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
- *                      <p>For example policies, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the
- *                            <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>If the object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
+ *                      <p>For example policies, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for
+ *                            S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -148,33 +164,36 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *                   to check if the copy succeeds. </p>
  *                <ul>
  *                   <li>
- *                      <p>If the copy is successful, you receive a response with information about the copied
- *                      object.</p>
+ *                      <p>If the copy is successful, you receive a response with information about
+ *                         the copied object.</p>
  *                   </li>
  *                   <li>
- *                      <p>A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3
- *                         is copying the files. A <code>200 OK</code> response can contain either a success or an error.</p>
+ *                      <p>A copy request might return an error when Amazon S3 receives the copy request
+ *                         or while Amazon S3 is copying the files. A <code>200 OK</code> response can
+ *                         contain either a success or an error.</p>
  *                      <ul>
  *                         <li>
  *                            <p>If the error occurs before the copy action starts, you receive a
- *                            standard Amazon S3 error.</p>
+ *                               standard Amazon S3 error.</p>
  *                         </li>
  *                         <li>
- *                            <p>If the error occurs during the copy operation, the error response is
- *                            embedded in the <code>200 OK</code> response. For example, in a cross-region copy, you
- *                            may encounter throttling and receive a <code>200 OK</code> response.
- *                            For more information, see <a href="https://repost.aws/knowledge-center/s3-resolve-200-internalerror">Resolve
- *                            the Error 200 response when copying objects to Amazon S3</a>.
- *                            The <code>200 OK</code> status code means the copy was accepted, but
- *                            it doesn't mean the copy is complete. Another example is
- *                            when you disconnect from Amazon S3 before the copy is complete, Amazon S3 might cancel the copy and you may receive a <code>200 OK</code> response.
- *                            You must stay connected to Amazon S3 until the entire response is successfully received and processed.</p>
- *                            <p>If you call this API operation directly, make
- *                               sure to design your application to parse the content of the response and handle it
- *                               appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the
- *                               embedded error and apply error handling per your configuration settings (including
- *                               automatically retrying the request as appropriate). If the condition persists, the SDKs
- *                               throw an exception (or, for the SDKs that don't use exceptions, they return an
+ *                            <p>If the error occurs during the copy operation, the error response
+ *                               is embedded in the <code>200 OK</code> response. For example, in a
+ *                               cross-region copy, you may encounter throttling and receive a
+ *                                  <code>200 OK</code> response. For more information, see <a href="https://repost.aws/knowledge-center/s3-resolve-200-internalerror">Resolve the Error 200 response when copying objects to
+ *                                  Amazon S3</a>. The <code>200 OK</code> status code means the copy
+ *                               was accepted, but it doesn't mean the copy is complete. Another
+ *                               example is when you disconnect from Amazon S3 before the copy is complete,
+ *                               Amazon S3 might cancel the copy and you may receive a <code>200 OK</code>
+ *                               response. You must stay connected to Amazon S3 until the entire response is
+ *                               successfully received and processed.</p>
+ *                            <p>If you call this API operation directly, make sure to design your
+ *                               application to parse the content of the response and handle it
+ *                               appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The
+ *                               SDKs detect the embedded error and apply error handling per your
+ *                               configuration settings (including automatically retrying the request
+ *                               as appropriate). If the condition persists, the SDKs throw an
+ *                               exception (or, for the SDKs that don't use exceptions, they return an
  *                               error).</p>
  *                         </li>
  *                      </ul>
@@ -183,10 +202,11 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *             </dd>
  *             <dt>Charge</dt>
  *             <dd>
- *                <p>The copy request charge is based on the storage class and Region that you specify for
- *                   the destination object. The request can also result in a data retrieval charge for the
- *                   source if the source storage class bills for data retrieval. If the copy source is in a different region, the data transfer is billed to the copy source account. For pricing information, see
- *                   <a href="http://aws.amazon.com/s3/pricing/">Amazon S3 pricing</a>.</p>
+ *                <p>The copy request charge is based on the storage class and Region that you
+ *                   specify for the destination object. The request can also result in a data
+ *                   retrieval charge for the source if the source storage class bills for data
+ *                   retrieval. If the copy source is in a different region, the data transfer is
+ *                   billed to the copy source account. For pricing information, see <a href="http://aws.amazon.com/s3/pricing/">Amazon S3 pricing</a>.</p>
  *             </dd>
  *             <dt>HTTP Host header syntax</dt>
  *             <dd>
diff --git a/clients/client-s3/src/commands/CreateBucketCommand.ts b/clients/client-s3/src/commands/CreateBucketCommand.ts
index cde15cc0081f..1870bb4d2a7c 100644
--- a/clients/client-s3/src/commands/CreateBucketCommand.ts
+++ b/clients/client-s3/src/commands/CreateBucketCommand.ts
@@ -35,9 +35,9 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *                   <code>CreateBucket</code>
  *                </a>.</p>
  *          </note>
- *          <p>Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a
- *          valid Amazon Web Services Access Key ID to authenticate requests. Anonymous requests are never allowed to
- *          create buckets. By creating the bucket, you become the bucket owner.</p>
+ *          <p>Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services
+ *          Access Key ID to authenticate requests. Anonymous requests are never allowed to create
+ *          buckets. By creating the bucket, you become the bucket owner.</p>
  *          <p>There are two types of buckets: general purpose buckets and directory buckets. For more
  *          information about these bucket types, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html">Creating, configuring, and
  *             working with Amazon S3 buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
@@ -45,12 +45,14 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>General purpose buckets</b> - If you send your <code>CreateBucket</code> request to the <code>s3.amazonaws.com</code> global endpoint,
- *                   the request goes to the <code>us-east-1</code> Region. So the signature
- *                   calculations in Signature Version 4 must use <code>us-east-1</code> as the Region, even
- *                   if the location constraint in the request specifies another Region where the bucket is
- *                   to be created. If you create a bucket in a Region other than US East (N. Virginia), your
- *                   application must be able to handle 307 redirect. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html">Virtual hosting of
+ *                      <b>General purpose buckets</b> - If you send your
+ *                      <code>CreateBucket</code> request to the <code>s3.amazonaws.com</code> global
+ *                   endpoint, the request goes to the <code>us-east-1</code> Region. So the signature
+ *                   calculations in Signature Version 4 must use <code>us-east-1</code> as the Region,
+ *                   even if the location constraint in the request specifies another Region where the
+ *                   bucket is to be created. If you create a bucket in a Region other than US East (N.
+ *                   Virginia), your application must be able to handle 307 redirect. For more
+ *                   information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html">Virtual hosting of
  *                      buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                </li>
  *                <li>
@@ -68,33 +70,40 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - In addition to the <code>s3:CreateBucket</code> permission, the following permissions are
- *                      required in a policy when your <code>CreateBucket</code> request includes specific
- *                      headers: </p>
+ *                         <b>General purpose bucket permissions</b> - In
+ *                         addition to the <code>s3:CreateBucket</code> permission, the following
+ *                         permissions are required in a policy when your <code>CreateBucket</code>
+ *                         request includes specific headers: </p>
  *                      <ul>
  *                         <li>
  *                            <p>
- *                               <b>Access control lists (ACLs)</b> - In your <code>CreateBucket</code> request, if you specify an access control list (ACL)
- *                               and set it to <code>public-read</code>, <code>public-read-write</code>,
- *                               <code>authenticated-read</code>, or if you explicitly specify any other custom ACLs, both <code>s3:CreateBucket</code> and
- *                               <code>s3:PutBucketAcl</code> permissions are required. In your <code>CreateBucket</code> request, if you set the ACL to <code>private</code>,
- *                               or if you don't specify any ACLs, only the <code>s3:CreateBucket</code> permission is required.
- *                            </p>
+ *                               <b>Access control lists (ACLs)</b>
+ *                               - In your <code>CreateBucket</code> request, if you specify an
+ *                               access control list (ACL) and set it to <code>public-read</code>,
+ *                                  <code>public-read-write</code>, <code>authenticated-read</code>, or
+ *                               if you explicitly specify any other custom ACLs, both
+ *                                  <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code>
+ *                               permissions are required. In your <code>CreateBucket</code> request,
+ *                               if you set the ACL to <code>private</code>, or if you don't specify
+ *                               any ACLs, only the <code>s3:CreateBucket</code> permission is
+ *                               required. </p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <b>Object Lock</b> - In your
- *                               <code>CreateBucket</code> request, if you set
- *                               <code>x-amz-bucket-object-lock-enabled</code> to true, the
- *                               <code>s3:PutBucketObjectLockConfiguration</code> and
- *                               <code>s3:PutBucketVersioning</code> permissions are required.</p>
+ *                                  <code>CreateBucket</code> request, if you set
+ *                                  <code>x-amz-bucket-object-lock-enabled</code> to true, the
+ *                                  <code>s3:PutBucketObjectLockConfiguration</code> and
+ *                                  <code>s3:PutBucketVersioning</code> permissions are
+ *                               required.</p>
  *                         </li>
  *                         <li>
  *                            <p>
- *                               <b>S3 Object Ownership</b> - If your
- *                               <code>CreateBucket</code> request includes the
- *                               <code>x-amz-object-ownership</code> header, then the
- *                               <code>s3:PutBucketOwnershipControls</code> permission is required.</p>
+ *                               <b>S3 Object Ownership</b> - If
+ *                               your <code>CreateBucket</code> request includes the
+ *                                  <code>x-amz-object-ownership</code> header, then the
+ *                                  <code>s3:PutBucketOwnershipControls</code> permission is
+ *                               required.</p>
  *                            <important>
  *                               <p> To set an ACL on a bucket as part of a
  *                                     <code>CreateBucket</code> request, you must explicitly set S3
@@ -105,10 +114,10 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *                                  Public Access on the bucket before using <code>PutBucketAcl</code>
  *                                  to set the ACL. If you try to create a bucket with a public ACL,
  *                                  the request will fail. </p>
- *                               <p> For the majority of modern use cases in S3, we recommend
- *                                  that you keep all Block Public Access settings enabled and keep
- *                                  ACLs disabled. If you would like to share data with users outside
- *                                  of your account, you can use bucket policies as needed. For more
+ *                               <p> For the majority of modern use cases in S3, we recommend that
+ *                                  you keep all Block Public Access settings enabled and keep ACLs
+ *                                  disabled. If you would like to share data with users outside of
+ *                                  your account, you can use bucket policies as needed. For more
  *                                  information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your
  *                                     bucket </a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking public access to your Amazon S3 storage </a> in
  *                                  the <i>Amazon S3 User Guide</i>. </p>
@@ -116,30 +125,36 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *                         </li>
  *                         <li>
  *                            <p>
- *                               <b>S3 Block Public Access</b> - If your
- *                               specific use case requires granting public access to your S3 resources, you
- *                               can disable Block Public Access. Specifically, you can create a new bucket with Block
- *                               Public Access enabled, then separately call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html">
+ *                               <b>S3 Block Public Access</b> - If
+ *                               your specific use case requires granting public access to your S3
+ *                               resources, you can disable Block Public Access. Specifically, you can
+ *                               create a new bucket with Block Public Access enabled, then separately
+ *                               call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html">
  *                                  <code>DeletePublicAccessBlock</code>
  *                               </a> API. To use this operation, you must have the
- *                               <code>s3:PutBucketPublicAccessBlock</code> permission. For more information about S3 Block Public
- *                               Access, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking
- *                                  public access to your Amazon S3 storage </a> in the
- *                               <i>Amazon S3 User Guide</i>. </p>
+ *                                  <code>s3:PutBucketPublicAccessBlock</code> permission. For more
+ *                               information about S3 Block Public Access, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html">Blocking public access to your Amazon S3 storage </a> in the
+ *                                  <i>Amazon S3 User Guide</i>. </p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> - You must have the <code>s3express:CreateBucket</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> -
+ *                         You must have the <code>s3express:CreateBucket</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>
  *                      <important>
- *                         <p>The permissions for ACLs, Object Lock, S3 Object Ownership, and S3 Block Public Access are not supported for directory buckets.
- *                         For directory buckets, all Block Public Access settings are enabled at the bucket level and S3
- *                         Object Ownership is set to Bucket owner enforced (ACLs disabled). These settings can't be modified.
- *                      </p>
+ *                         <p>The permissions for ACLs, Object Lock, S3 Object Ownership, and S3
+ *                            Block Public Access are not supported for directory buckets. For
+ *                            directory buckets, all Block Public Access settings are enabled at the
+ *                            bucket level and S3 Object Ownership is set to Bucket owner enforced
+ *                            (ACLs disabled). These settings can't be modified. </p>
  *                         <p>For more information about permissions for creating and working with
- *                            directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.
- *                            For more information about supported S3 features for directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html#s3-express-features">Features of S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                            directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the
+ *                               <i>Amazon S3 User Guide</i>. For more information about
+ *                            supported S3 features for directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html#s3-express-features">Features of S3 Express One Zone</a> in the
+ *                               <i>Amazon S3 User Guide</i>.</p>
  *                      </important>
  *                   </li>
  *                </ul>
diff --git a/clients/client-s3/src/commands/CreateMultipartUploadCommand.ts b/clients/client-s3/src/commands/CreateMultipartUploadCommand.ts
index 532740654d77..67a04bf5d17a 100644
--- a/clients/client-s3/src/commands/CreateMultipartUploadCommand.ts
+++ b/clients/client-s3/src/commands/CreateMultipartUploadCommand.ts
@@ -38,28 +38,31 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  * <p>This action initiates a multipart upload and returns an upload ID. This upload ID is
  *          used to associate all of the parts in the specific multipart upload. You specify this
  *          upload ID in each of your subsequent upload part requests (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>). You also include this
- *          upload ID in the final request to either complete or abort the multipart upload
- *          request. For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          upload ID in the final request to either complete or abort the multipart upload request.
+ *          For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
  *          <note>
  *             <p>After you initiate a multipart upload and upload one or more parts, to stop being
  *             charged for storing the uploaded parts, you must either complete or abort the multipart
  *             upload. Amazon S3 frees up the space used to store the parts and stops charging you for
  *             storing them only after you either complete or abort a multipart upload. </p>
  *          </note>
- *          <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the created multipart
- *          upload must be completed within the number of days specified in the bucket lifecycle
- *          configuration. Otherwise, the incomplete multipart upload becomes eligible for an abort
- *          action and Amazon S3 aborts the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle
- *             Configuration</a>.</p>
+ *          <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the
+ *          created multipart upload must be completed within the number of days specified in the
+ *          bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible
+ *          for an abort action and Amazon S3 aborts the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle
+ *          Configuration</a>.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets </b> - S3 Lifecycle is not supported by directory buckets.</p>
+ *                      <b>Directory buckets </b> -
+ *                   S3 Lifecycle is not supported by directory buckets.</p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets </b> -
+ *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
@@ -68,10 +71,13 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *          <dl>
  *             <dt>Request signing</dt>
  *             <dd>
- *                <p>For request signing, multipart upload is just a series of regular requests. You initiate
- *                a multipart upload, send one or more requests to upload parts, and then complete the
- *                multipart upload process. You sign each request individually. There is nothing special
- *                about signing multipart upload requests. For more information about signing, 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> in the <i>Amazon S3 User Guide</i>.</p>
+ *                <p>For request signing, multipart upload is just a series of regular requests. You
+ *                   initiate a multipart upload, send one or more requests to upload parts, and then
+ *                   complete the multipart upload process. You sign each request individually. There
+ *                   is nothing special about signing multipart upload requests. For more information
+ *                   about signing, 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> in the
+ *                      <i>Amazon S3 User Guide</i>.</p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
@@ -109,29 +115,36 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose buckets</b> - Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it
- *                         writes it to disks in its data centers and decrypts it when you access it. Amazon S3
- *                         automatically encrypts all new objects that are uploaded to an S3 bucket. When doing a
- *                         multipart upload, if you don't specify encryption information in your request, the
- *                         encryption setting of the uploaded parts is set to the default encryption configuration of
- *                         the destination bucket. By default, all buckets have a base level of encryption
- *                         configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the
- *                         destination bucket has a default encryption configuration that uses server-side encryption
- *                         with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided encryption key (SSE-C),
- *                         Amazon S3 uses the corresponding KMS key, or a customer-provided key to encrypt the uploaded
- *                         parts. When you perform a CreateMultipartUpload operation, if you want to use a different
- *                         type of encryption setting for the uploaded parts, you can request that Amazon S3 encrypts the
- *                         object with a different encryption key (such as an Amazon S3 managed key, a KMS key, or a customer-provided key). When the encryption
- *                         setting in your request is different from the default encryption configuration of the
- *                         destination bucket, the encryption setting in your request takes precedence. If you choose
- *                         to provide your own encryption key, the request headers you provide in <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>
- *                         and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> requests must match the headers you used in the <code>CreateMultipartUpload</code> request.</p>
+ *                         <b>General purpose buckets</b> - Server-side
+ *                         encryption is for data encryption at rest. Amazon S3 encrypts your data as it
+ *                         writes it to disks in its data centers and decrypts it when you access it.
+ *                         Amazon S3 automatically encrypts all new objects that are uploaded to an S3
+ *                         bucket. When doing a multipart upload, if you don't specify encryption
+ *                         information in your request, the encryption setting of the uploaded parts is
+ *                         set to the default encryption configuration of the destination bucket. By
+ *                         default, all buckets have a base level of encryption configuration that uses
+ *                         server-side encryption with Amazon S3 managed keys (SSE-S3). If the destination
+ *                         bucket has a default encryption configuration that uses server-side
+ *                         encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided
+ *                         encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a
+ *                         customer-provided key to encrypt the uploaded parts. When you perform a
+ *                         CreateMultipartUpload operation, if you want to use a different type of
+ *                         encryption setting for the uploaded parts, you can request that Amazon S3
+ *                         encrypts the object with a different encryption key (such as an Amazon S3 managed
+ *                         key, a KMS key, or a customer-provided key). When the encryption setting
+ *                         in your request is different from the default encryption configuration of
+ *                         the destination bucket, the encryption setting in your request takes
+ *                         precedence. If you choose to provide your own encryption key, the request
+ *                         headers you provide in <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a> and
+ *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>
+ *                         requests must match the headers you used in the
+ *                            <code>CreateMultipartUpload</code> request.</p>
  *                      <ul>
  *                         <li>
  *                            <p>Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key
- *                               (<code>aws/s3</code>) and KMS customer managed keys stored in Key Management Service (KMS) –
- *                               If you want Amazon Web Services to manage the keys used to encrypt data, specify the
- *                               following headers in the request.</p>
+ *                                  (<code>aws/s3</code>) and KMS customer managed keys stored in Key Management Service
+ *                               (KMS) – If you want Amazon Web Services to manage the keys used to encrypt data,
+ *                               specify the following headers in the request.</p>
  *                            <ul>
  *                               <li>
  *                                  <p>
@@ -152,44 +165,53 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                            <note>
  *                               <ul>
  *                                  <li>
- *                                     <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but
- *                                     don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>,
- *                                     Amazon S3 uses the Amazon Web Services managed key (<code>aws/s3</code> key) in KMS to
- *                                     protect the data.</p>
+ *                                     <p>If you specify
+ *                                           <code>x-amz-server-side-encryption:aws:kms</code>, but
+ *                                        don't provide
+ *                                           <code>x-amz-server-side-encryption-aws-kms-key-id</code>,
+ *                                        Amazon S3 uses the Amazon Web Services managed key (<code>aws/s3</code> key) in
+ *                                        KMS to protect the data.</p>
  *                                  </li>
  *                                  <li>
- *                                     <p>To perform a multipart upload with encryption by using an Amazon Web Services KMS key, the requester
- *                                     must have permission to the <code>kms:Decrypt</code> and <code>kms:GenerateDataKey*</code>
- *                                     actions on the key. These permissions are required because Amazon S3 must decrypt and read data
- *                                     from the encrypted file parts before it completes the multipart upload. For more
- *                                     information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions">Multipart upload API
- *                                        and permissions</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting data using
- *                                           server-side encryption with Amazon Web Services KMS</a> in the
- *                                     <i>Amazon S3 User Guide</i>.</p>
+ *                                     <p>To perform a multipart upload with encryption by using an
+ *                                        Amazon Web Services KMS key, the requester must have permission to the
+ *                                           <code>kms:Decrypt</code> and
+ *                                           <code>kms:GenerateDataKey*</code> actions on the key.
+ *                                        These permissions are required because Amazon S3 must decrypt and
+ *                                        read data from the encrypted file parts before it completes
+ *                                        the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions">Multipart upload API and permissions</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting data using server-side encryption with Amazon Web Services
+ *                                           KMS</a> in the
+ *                                        <i>Amazon S3 User Guide</i>.</p>
  *                                  </li>
  *                                  <li>
- *                                     <p>If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account as the KMS key,
- *                                     then you must have these permissions on the key policy. If your IAM user or role is in a different account from the key, then you must have the permissions on both the key
- *                                     policy and your IAM user or role.</p>
+ *                                     <p>If your Identity and Access Management (IAM) user or role is in the same
+ *                                        Amazon Web Services account as the KMS key, then you must have these
+ *                                        permissions on the key policy. If your IAM user or role is
+ *                                        in a different account from the key, then you must have the
+ *                                        permissions on both the key policy and your IAM user or
+ *                                        role.</p>
  *                                  </li>
  *                                  <li>
- *                                     <p>All <code>GET</code> and <code>PUT</code> requests for an object
- *                                        protected by KMS fail if you don't make them by using Secure Sockets
- *                                        Layer (SSL), Transport Layer Security (TLS), or Signature Version
- *                                        4. For information about configuring any of the officially supported Amazon Web Services
- *                                        SDKs and Amazon Web Services CLI, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version">Specifying the Signature Version in Request Authentication</a>
- *                                        in the <i>Amazon S3 User Guide</i>.</p>
+ *                                     <p>All <code>GET</code> and <code>PUT</code> requests for an
+ *                                        object protected by KMS fail if you don't make them by
+ *                                        using Secure Sockets Layer (SSL), Transport Layer Security
+ *                                        (TLS), or Signature Version 4. For information about
+ *                                        configuring any of the officially supported Amazon Web Services SDKs and
+ *                                        Amazon Web Services CLI, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version">Specifying the Signature Version in
+ *                                           Request Authentication</a> in the
+ *                                           <i>Amazon S3 User Guide</i>.</p>
  *                                  </li>
  *                               </ul>
  *                            </note>
  *                            <p>For more information about server-side encryption with KMS keys
- *                               (SSE-KMS), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting Data
- *                                  Using Server-Side Encryption with KMS keys</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                               (SSE-KMS), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting
+ *                                  Data Using Server-Side Encryption with KMS keys</a> in the
+ *                                  <i>Amazon S3 User Guide</i>.</p>
  *                         </li>
  *                         <li>
- *                            <p>Use customer-provided encryption keys (SSE-C) – If you want to manage
- *                               your own encryption keys, provide all the following headers in the
- *                               request.</p>
+ *                            <p>Use customer-provided encryption keys (SSE-C) – If you want to
+ *                               manage your own encryption keys, provide all the following headers in
+ *                               the request.</p>
  *                            <ul>
  *                               <li>
  *                                  <p>
@@ -207,16 +229,17 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                                  </p>
  *                               </li>
  *                            </ul>
- *                            <p>For more information about server-side encryption with customer-provided
- *                               encryption keys (SSE-C), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html">
- *                                  Protecting data using server-side encryption with customer-provided
- *                                  encryption keys (SSE-C)</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                            <p>For more information about server-side encryption with
+ *                               customer-provided encryption keys (SSE-C), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html"> Protecting data using server-side encryption with
+ *                                  customer-provided encryption keys (SSE-C)</a> in the
+ *                                  <i>Amazon S3 User Guide</i>.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+ *                         <b>Directory buckets</b> -
+ *                         For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). 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, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>
@@ -234,8 +257,11 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  * </p>
  *                      </note>
  *                      <note>
- *                         <p>For directory buckets, when you perform a <code>CreateMultipartUpload</code> operation and an <code>UploadPartCopy</code> operation,
- *                         the request headers you provide in the <code>CreateMultipartUpload</code> request must match the default encryption configuration of the destination bucket. </p>
+ *                         <p>For directory buckets, when you perform a
+ *                               <code>CreateMultipartUpload</code> operation and an
+ *                               <code>UploadPartCopy</code> operation, the request headers you provide
+ *                            in the <code>CreateMultipartUpload</code> request must match the default
+ *                            encryption configuration of the destination bucket. </p>
  *                      </note>
  *                   </li>
  *                </ul>
diff --git a/clients/client-s3/src/commands/CreateSessionCommand.ts b/clients/client-s3/src/commands/CreateSessionCommand.ts
index 2fb49a2373ed..5a108098fa50 100644
--- a/clients/client-s3/src/commands/CreateSessionCommand.ts
+++ b/clients/client-s3/src/commands/CreateSessionCommand.ts
@@ -34,10 +34,10 @@ export interface CreateSessionCommandInput extends CreateSessionRequest {}
 export interface CreateSessionCommandOutput extends CreateSessionOutput, __MetadataBearer {}
 
 /**
- * <p>Creates a session that establishes temporary security credentials to support fast authentication and authorization for the Zonal endpoint API operations on directory buckets.
- *          For more information about Zonal endpoint API operations that include the Availability Zone in the request endpoint, see
- *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-APIs.html">S3 Express One Zone  APIs</a> in the <i>Amazon S3 User Guide</i>.
- *       </p>
+ * <p>Creates a session that establishes temporary security credentials to support fast
+ *          authentication and authorization for the Zonal endpoint API operations on directory buckets. For more
+ *          information about Zonal endpoint API operations that include the Availability Zone in the request endpoint, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-APIs.html">S3 Express One Zone
+ *             APIs</a> in the <i>Amazon S3 User Guide</i>. </p>
  *          <p>To make Zonal endpoint API requests on a directory bucket, use the <code>CreateSession</code>
  *          API operation. Specifically, you grant <code>s3express:CreateSession</code> permission to a
  *          bucket in a bucket policy or an IAM identity-based policy. Then, you use IAM credentials to make the
@@ -67,30 +67,44 @@ export interface CreateSessionCommandOutput extends CreateSessionOutput, __Metad
  *                <li>
  *                   <p>
  *                      <b>
- *                         <code>CopyObject</code> API operation</b> - Unlike other Zonal endpoint API operations, the <code>CopyObject</code> API operation doesn't use the temporary security credentials returned from the <code>CreateSession</code> API operation for authentication and authorization. For information about authentication and authorization of the <code>CopyObject</code> API operation on directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a>.</p>
+ *                         <code>CopyObject</code> API operation</b> -
+ *                   Unlike other Zonal endpoint API operations, the <code>CopyObject</code> API operation doesn't use
+ *                   the temporary security credentials returned from the <code>CreateSession</code>
+ *                   API operation for authentication and authorization. For information about
+ *                   authentication and authorization of the <code>CopyObject</code> API operation on
+ *                   directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a>.</p>
  *                </li>
  *                <li>
  *                   <p>
  *                      <b>
- *                         <code>HeadBucket</code> API operation</b> - Unlike other Zonal endpoint API operations, the <code>HeadBucket</code> API operation doesn't use the temporary security credentials returned from the <code>CreateSession</code> API operation for authentication and authorization. For information about authentication and authorization of the <code>HeadBucket</code> API operation on directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html">HeadBucket</a>.</p>
+ *                         <code>HeadBucket</code> API operation</b> -
+ *                   Unlike other Zonal endpoint API operations, the <code>HeadBucket</code> API operation doesn't use
+ *                   the temporary security credentials returned from the <code>CreateSession</code>
+ *                   API operation for authentication and authorization. For information about
+ *                   authentication and authorization of the <code>HeadBucket</code> API operation on
+ *                   directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html">HeadBucket</a>.</p>
  *                </li>
  *             </ul>
  *          </note>
  *          <dl>
  *             <dt>Permissions</dt>
  *             <dd>
- *                <p>To obtain temporary security credentials, you must create a bucket policy or an IAM identity-based policy that
- *                   grants <code>s3express:CreateSession</code> permission to the bucket. In a
- *                   policy, you can have the <code>s3express:SessionMode</code> condition key to
- *                   control who can create a <code>ReadWrite</code> or <code>ReadOnly</code> session.
- *                   For more information about <code>ReadWrite</code> or <code>ReadOnly</code>
- *                   sessions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html#API_CreateSession_RequestParameters">
+ *                <p>To obtain temporary security credentials, you must create
+ *                   a bucket policy or an IAM identity-based policy that grants <code>s3express:CreateSession</code>
+ *                   permission to the bucket. In a policy, you can have the
+ *                      <code>s3express:SessionMode</code> condition key to control who can create a
+ *                      <code>ReadWrite</code> or <code>ReadOnly</code> session. For more information
+ *                   about <code>ReadWrite</code> or <code>ReadOnly</code> sessions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html#API_CreateSession_RequestParameters">
  *                      <code>x-amz-create-session-mode</code>
  *                   </a>. For example policies, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the
- *                      <i>Amazon S3 User Guide</i>. </p>
- *                <p>To grant cross-account access to Zonal endpoint API operations, the bucket policy should also grant both accounts the <code>s3express:CreateSession</code> permission.</p>
- *                <p>If you want to encrypt objects 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>
+ *                      <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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for
+ *                      S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>. </p>
+ *                <p>To grant cross-account access to Zonal endpoint API operations, the bucket policy should also
+ *                   grant both accounts the <code>s3express:CreateSession</code> permission.</p>
+ *                <p>If you want to encrypt objects 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>
  *             </dd>
  *             <dt>Encryption</dt>
  *             <dd>
diff --git a/clients/client-s3/src/commands/DeleteBucketAnalyticsConfigurationCommand.ts b/clients/client-s3/src/commands/DeleteBucketAnalyticsConfigurationCommand.ts
index eea2fa649562..3fbd6a5da7d1 100644
--- a/clients/client-s3/src/commands/DeleteBucketAnalyticsConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketAnalyticsConfigurationCommand.ts
@@ -32,7 +32,7 @@ export interface DeleteBucketAnalyticsConfigurationCommandOutput extends __Metad
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Deletes an analytics configuration for the bucket (specified by the analytics
  *          configuration ID).</p>
diff --git a/clients/client-s3/src/commands/DeleteBucketCommand.ts b/clients/client-s3/src/commands/DeleteBucketCommand.ts
index df5bcbbbd495..db7e6e62bba5 100644
--- a/clients/client-s3/src/commands/DeleteBucketCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketCommand.ts
@@ -34,7 +34,9 @@ export interface DeleteBucketCommandOutput extends __MetadataBearer {}
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - If multipart uploads in a directory bucket are in progress, you can't delete the bucket until all the in-progress multipart uploads are aborted or completed.</p>
+ *                      <b>Directory buckets</b> - If multipart
+ *                   uploads in a directory bucket are in progress, you can't delete the bucket until
+ *                   all the in-progress multipart uploads are aborted or completed.</p>
  *                </li>
  *                <li>
  *                   <p>
@@ -51,11 +53,16 @@ export interface DeleteBucketCommandOutput extends __MetadataBearer {}
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - You must have the <code>s3:DeleteBucket</code> permission on the specified bucket in a policy.</p>
+ *                         <b>General purpose bucket permissions</b> - You
+ *                         must have the <code>s3:DeleteBucket</code> permission on the specified
+ *                         bucket in a policy.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> - You must have the <code>s3express:DeleteBucket</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> -
+ *                         You must have the <code>s3express:DeleteBucket</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>
diff --git a/clients/client-s3/src/commands/DeleteBucketCorsCommand.ts b/clients/client-s3/src/commands/DeleteBucketCorsCommand.ts
index 4da1e5a6ffab..2962cb69b85a 100644
--- a/clients/client-s3/src/commands/DeleteBucketCorsCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketCorsCommand.ts
@@ -29,7 +29,7 @@ export interface DeleteBucketCorsCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Deletes the <code>cors</code> configuration information set for the bucket.</p>
  *          <p>To use this operation, you must have permission to perform the
diff --git a/clients/client-s3/src/commands/DeleteBucketEncryptionCommand.ts b/clients/client-s3/src/commands/DeleteBucketEncryptionCommand.ts
index e18a4fb3379f..717433843785 100644
--- a/clients/client-s3/src/commands/DeleteBucketEncryptionCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketEncryptionCommand.ts
@@ -34,13 +34,16 @@ export interface DeleteBucketEncryptionCommandOutput extends __MetadataBearer {}
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>General purpose buckets</b> - 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>
+ *                      <b>General purpose buckets</b> - 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>
- *                      <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption configuration in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html">Setting default server-side encryption behavior
- *                   for directory buckets</a>.</p>
+ *                      <b>Directory buckets</b> -
+ *                   For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption
+ *                   configuration in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html">Setting
+ *                      default server-side encryption behavior for directory buckets</a>.</p>
  *                </li>
  *             </ul>
  *          </note>
@@ -50,15 +53,20 @@ export interface DeleteBucketEncryptionCommandOutput extends __MetadataBearer {}
  *                <ul>
  *                   <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>.</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>.</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>
+ *                         <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>
  *                   </li>
  *                </ul>
  *             </dd>
diff --git a/clients/client-s3/src/commands/DeleteBucketIntelligentTieringConfigurationCommand.ts b/clients/client-s3/src/commands/DeleteBucketIntelligentTieringConfigurationCommand.ts
index f1ff91ea3532..94356714e15c 100644
--- a/clients/client-s3/src/commands/DeleteBucketIntelligentTieringConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketIntelligentTieringConfigurationCommand.ts
@@ -33,7 +33,7 @@ export interface DeleteBucketIntelligentTieringConfigurationCommandOutput extend
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Deletes the S3 Intelligent-Tiering configuration from the specified 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>
diff --git a/clients/client-s3/src/commands/DeleteBucketInventoryConfigurationCommand.ts b/clients/client-s3/src/commands/DeleteBucketInventoryConfigurationCommand.ts
index 7acee47f6f5f..8e42e8263338 100644
--- a/clients/client-s3/src/commands/DeleteBucketInventoryConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketInventoryConfigurationCommand.ts
@@ -32,7 +32,7 @@ export interface DeleteBucketInventoryConfigurationCommandOutput extends __Metad
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Deletes an inventory configuration (identified by the inventory ID) from the
  *          bucket.</p>
diff --git a/clients/client-s3/src/commands/DeleteBucketLifecycleCommand.ts b/clients/client-s3/src/commands/DeleteBucketLifecycleCommand.ts
index 4f8fe764b867..7cd655401a3b 100644
--- a/clients/client-s3/src/commands/DeleteBucketLifecycleCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketLifecycleCommand.ts
@@ -28,18 +28,61 @@ export interface DeleteBucketLifecycleCommandInput extends DeleteBucketLifecycle
 export interface DeleteBucketLifecycleCommandOutput extends __MetadataBearer {}
 
 /**
- * <note>
- *             <p>This operation is not supported by directory buckets.</p>
- *          </note>
- *          <p>Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the
+ * <p>Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the
  *          lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your
  *          objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of
  *          rules contained in the deleted lifecycle configuration.</p>
- *          <p>To use this operation, you must have permission to perform the
- *             <code>s3:PutLifecycleConfiguration</code> action. By default, the bucket owner has this
- *          permission and the bucket owner can grant this permission to others.</p>
- *          <p>There is usually some time lag before lifecycle configuration deletion is fully
- *          propagated to all the Amazon S3 systems.</p>
+ *          <dl>
+ *             <dt>Permissions</dt>
+ *             <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>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>
+ *                <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>
+ *                      <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>
+ *                            </code>. Virtual-hosted-style requests aren't supported.
+ * For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
+ *     <i>Amazon S3 User Guide</i>.</p>
+ *                      </note>
+ *                   </li>
+ *                </ul>
+ *             </dd>
+ *          </dl>
+ *          <dl>
+ *             <dt>HTTP Host header syntax</dt>
+ *             <dd>
+ *                <p>
+ *                   <b>Directory buckets </b> - The HTTP Host
+ *                   header syntax is
+ *                      <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
+ *             </dd>
+ *          </dl>
  *          <p>For more information about the object expiration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#intro-lifecycle-rules-actions">Elements to Describe Lifecycle Actions</a>.</p>
  *          <p>Related actions include:</p>
  *          <ul>
diff --git a/clients/client-s3/src/commands/DeleteBucketMetricsConfigurationCommand.ts b/clients/client-s3/src/commands/DeleteBucketMetricsConfigurationCommand.ts
index 0a7bcd8de43a..5dfb35d4bb84 100644
--- a/clients/client-s3/src/commands/DeleteBucketMetricsConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketMetricsConfigurationCommand.ts
@@ -32,7 +32,7 @@ export interface DeleteBucketMetricsConfigurationCommandOutput extends __Metadat
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the
  *          metrics configuration ID) from the bucket. Note that this doesn't include the daily storage
diff --git a/clients/client-s3/src/commands/DeleteBucketOwnershipControlsCommand.ts b/clients/client-s3/src/commands/DeleteBucketOwnershipControlsCommand.ts
index 172a1876498d..c9ff659610cf 100644
--- a/clients/client-s3/src/commands/DeleteBucketOwnershipControlsCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketOwnershipControlsCommand.ts
@@ -32,7 +32,7 @@ export interface DeleteBucketOwnershipControlsCommandOutput extends __MetadataBe
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Removes <code>OwnershipControls</code> for an Amazon S3 bucket. To use this operation, you
  *          must have the <code>s3:PutBucketOwnershipControls</code> permission. For more information
diff --git a/clients/client-s3/src/commands/DeleteBucketPolicyCommand.ts b/clients/client-s3/src/commands/DeleteBucketPolicyCommand.ts
index ae2202246b13..9d5b582d37bc 100644
--- a/clients/client-s3/src/commands/DeleteBucketPolicyCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketPolicyCommand.ts
@@ -28,8 +28,7 @@ export interface DeleteBucketPolicyCommandInput extends DeleteBucketPolicyReques
 export interface DeleteBucketPolicyCommandOutput extends __MetadataBearer {}
 
 /**
- * <p>Deletes the
- *          policy of a specified bucket.</p>
+ * <p>Deletes the policy of a specified 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>
@@ -40,33 +39,38 @@ export interface DeleteBucketPolicyCommandOutput extends __MetadataBearer {}
  *          <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>DeleteBucketPolicy</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>DeleteBucketPolicy</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>DeleteBucketPolicy</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>DeleteBucketPolicy</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:DeleteBucketPolicy</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>
+ *                         <b>General purpose bucket permissions</b> - The
+ *                            <code>s3:DeleteBucketPolicy</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:DeleteBucketPolicy</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:DeleteBucketPolicy</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>
diff --git a/clients/client-s3/src/commands/DeleteBucketReplicationCommand.ts b/clients/client-s3/src/commands/DeleteBucketReplicationCommand.ts
index 13420a73213f..d6bb7c31cd3d 100644
--- a/clients/client-s3/src/commands/DeleteBucketReplicationCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketReplicationCommand.ts
@@ -29,7 +29,7 @@ export interface DeleteBucketReplicationCommandOutput extends __MetadataBearer {
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p> Deletes the replication configuration from the bucket.</p>
  *          <p>To use this operation, you must have permissions to perform the
diff --git a/clients/client-s3/src/commands/DeleteBucketTaggingCommand.ts b/clients/client-s3/src/commands/DeleteBucketTaggingCommand.ts
index 6370e78d36ea..fb3d0475232c 100644
--- a/clients/client-s3/src/commands/DeleteBucketTaggingCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketTaggingCommand.ts
@@ -29,7 +29,7 @@ export interface DeleteBucketTaggingCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Deletes the tags from the bucket.</p>
  *          <p>To use this operation, you must have permission to perform the
diff --git a/clients/client-s3/src/commands/DeleteBucketWebsiteCommand.ts b/clients/client-s3/src/commands/DeleteBucketWebsiteCommand.ts
index 88df9c8d20b8..2c675338d71a 100644
--- a/clients/client-s3/src/commands/DeleteBucketWebsiteCommand.ts
+++ b/clients/client-s3/src/commands/DeleteBucketWebsiteCommand.ts
@@ -29,7 +29,7 @@ export interface DeleteBucketWebsiteCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>This action removes the website configuration for a bucket. Amazon S3 returns a <code>200
  *             OK</code> response upon successfully deleting a website configuration on the specified
diff --git a/clients/client-s3/src/commands/DeleteObjectCommand.ts b/clients/client-s3/src/commands/DeleteObjectCommand.ts
index 6f938a15d5d5..2e0d30ea5ce4 100644
--- a/clients/client-s3/src/commands/DeleteObjectCommand.ts
+++ b/clients/client-s3/src/commands/DeleteObjectCommand.ts
@@ -133,6 +133,9 @@ export interface DeleteObjectCommandOutput extends DeleteObjectOutput, __Metadat
  *   RequestPayer: "requester",
  *   BypassGovernanceRetention: true || false,
  *   ExpectedBucketOwner: "STRING_VALUE",
+ *   IfMatch: "STRING_VALUE",
+ *   IfMatchLastModifiedTime: new Date("TIMESTAMP"),
+ *   IfMatchSize: Number("long"),
  * };
  * const command = new DeleteObjectCommand(input);
  * const response = await client.send(command);
diff --git a/clients/client-s3/src/commands/DeleteObjectTaggingCommand.ts b/clients/client-s3/src/commands/DeleteObjectTaggingCommand.ts
index e14facf9d3a9..f1c0711b8df7 100644
--- a/clients/client-s3/src/commands/DeleteObjectTaggingCommand.ts
+++ b/clients/client-s3/src/commands/DeleteObjectTaggingCommand.ts
@@ -30,7 +30,7 @@ export interface DeleteObjectTaggingCommandOutput extends DeleteObjectTaggingOut
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Removes the entire tag set from the specified object. For more information about
  *          managing object tags, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html"> Object Tagging</a>.</p>
diff --git a/clients/client-s3/src/commands/DeleteObjectsCommand.ts b/clients/client-s3/src/commands/DeleteObjectsCommand.ts
index 09378b0aaa82..55eaf27d5339 100644
--- a/clients/client-s3/src/commands/DeleteObjectsCommand.ts
+++ b/clients/client-s3/src/commands/DeleteObjectsCommand.ts
@@ -31,44 +31,46 @@ export interface DeleteObjectsCommandOutput extends DeleteObjectsOutput, __Metad
 
 /**
  * <p>This operation enables you to delete multiple objects from a bucket using a single HTTP
- *          request. If you know the object keys that you want to delete, then this operation provides a
- *          suitable alternative to sending individual delete requests, reducing per-request
+ *          request. If you know the object keys that you want to delete, then this operation provides
+ *          a suitable alternative to sending individual delete requests, reducing per-request
  *          overhead.</p>
- *          <p>The request can contain a list of up to 1000 keys that you want to delete. In the XML, you
- *          provide the object key names, and optionally, version IDs if you want to delete a specific
- *          version of the object from a versioning-enabled bucket. For each key, Amazon S3 performs a
- *          delete operation and returns the result of that delete, success or failure, in the response.
- *          Note that if the object specified in the request is not found, Amazon S3 returns the result as
- *          deleted.</p>
+ *          <p>The request can contain a list of up to 1000 keys that you want to delete. In the XML,
+ *          you provide the object key names, and optionally, version IDs if you want to delete a
+ *          specific version of the object from a versioning-enabled bucket. For each key, Amazon S3
+ *          performs a delete operation and returns the result of that delete, success or failure, in
+ *          the response. Note that if the object specified in the request is not found, Amazon S3 returns
+ *          the result as deleted.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets.</p>
+ *                      <b>Directory buckets</b> -
+ *                   S3 Versioning isn't enabled and supported for directory buckets.</p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets</b> -
+ *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
  *             </ul>
  *          </note>
  *          <p>The operation supports two modes for the response: verbose and quiet. By default, the
- *          operation uses verbose mode in which the response includes the result of deletion of each key
- *          in your request. In quiet mode the response includes only keys where the delete operation
- *          encountered an error. For a successful deletion in a quiet mode, the operation does not return any information
- *          about the delete in the response body.</p>
+ *          operation uses verbose mode in which the response includes the result of deletion of each
+ *          key in your request. In quiet mode the response includes only keys where the delete
+ *          operation encountered an error. For a successful deletion in a quiet mode, the operation
+ *          does not return any information about the delete in the response body.</p>
  *          <p>When performing this action on an MFA Delete enabled bucket, that attempts to delete any
  *          versioned objects, you must include an MFA token. If you do not provide one, the entire
  *          request will fail, even if there are non-versioned objects you are trying to delete. If you
  *          provide an invalid token, whether there are versioned keys in the request or not, the
  *          entire Multi-Object Delete request will fail. For information about MFA Delete, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete">MFA
- *             Delete</a> in the <i>Amazon S3
- *                User Guide</i>.</p>
+ *             Delete</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> - MFA delete is not supported by directory buckets.</p>
+ *                <b>Directory buckets</b> -
+ *             MFA delete is not supported by directory buckets.</p>
  *          </note>
  *          <dl>
  *             <dt>Permissions</dt>
@@ -76,20 +78,25 @@ export interface DeleteObjectsCommandOutput extends DeleteObjectsOutput, __Metad
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - The following permissions are required in your policies when your
- *                         <code>DeleteObjects</code> request includes specific headers.</p>
+ *                         <b>General purpose bucket permissions</b> - The
+ *                         following permissions are required in your policies when your
+ *                            <code>DeleteObjects</code> request includes specific headers.</p>
  *                      <ul>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:DeleteObject</code>
- *                               </b> - To delete an object from a bucket, you must always specify the <code>s3:DeleteObject</code> permission.</p>
+ *                               </b>
+ *                               - To delete an object from a bucket, you must always specify
+ *                               the <code>s3:DeleteObject</code> permission.</p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:DeleteObjectVersion</code>
- *                               </b> - To delete a specific version of an object from a versioning-enabled bucket, you must specify the <code>s3:DeleteObjectVersion</code> permission.</p>
+ *                               </b> - To delete a specific version of an object from a
+ *                               versioning-enabled bucket, you must specify the
+ *                                  <code>s3:DeleteObjectVersion</code> permission.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -109,15 +116,19 @@ export interface DeleteObjectsCommandOutput extends DeleteObjectsOutput, __Metad
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - The Content-MD5 request header is required for all Multi-Object Delete requests. Amazon S3
- *                      uses the header value to ensure that your request body has not been altered in
- *                      transit.</p>
+ *                         <b>General purpose bucket</b> - The Content-MD5
+ *                         request header is required for all Multi-Object Delete requests. Amazon S3 uses
+ *                         the header value to ensure that your request body has not been altered in
+ *                         transit.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket</b> - The Content-MD5 request header or a additional checksum request header
- *                      (including <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or
- *                      <code>x-amz-checksum-sha256</code>) is required for all Multi-Object Delete requests.</p>
+ *                         <b>Directory bucket</b> - The
+ *                         Content-MD5 request header or a additional checksum request header
+ *                         (including <code>x-amz-checksum-crc32</code>,
+ *                            <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or
+ *                            <code>x-amz-checksum-sha256</code>) is required for all Multi-Object
+ *                         Delete requests.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -169,6 +180,9 @@ export interface DeleteObjectsCommandOutput extends DeleteObjectsOutput, __Metad
  *       { // ObjectIdentifier
  *         Key: "STRING_VALUE", // required
  *         VersionId: "STRING_VALUE",
+ *         ETag: "STRING_VALUE",
+ *         LastModifiedTime: new Date("TIMESTAMP"),
+ *         Size: Number("long"),
  *       },
  *     ],
  *     Quiet: true || false,
diff --git a/clients/client-s3/src/commands/DeletePublicAccessBlockCommand.ts b/clients/client-s3/src/commands/DeletePublicAccessBlockCommand.ts
index 86533d29675d..9365facaf94e 100644
--- a/clients/client-s3/src/commands/DeletePublicAccessBlockCommand.ts
+++ b/clients/client-s3/src/commands/DeletePublicAccessBlockCommand.ts
@@ -29,7 +29,7 @@ export interface DeletePublicAccessBlockCommandOutput extends __MetadataBearer {
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Removes the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use this
  *          operation, you must have the <code>s3:PutBucketPublicAccessBlock</code> permission. For
diff --git a/clients/client-s3/src/commands/GetBucketAccelerateConfigurationCommand.ts b/clients/client-s3/src/commands/GetBucketAccelerateConfigurationCommand.ts
index 0b5cb6061163..6cd0cbf59f8a 100644
--- a/clients/client-s3/src/commands/GetBucketAccelerateConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketAccelerateConfigurationCommand.ts
@@ -35,7 +35,7 @@ export interface GetBucketAccelerateConfigurationCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>This implementation of the GET action uses the <code>accelerate</code> subresource to
  *          return the Transfer Acceleration state of a bucket, which is either <code>Enabled</code> or
diff --git a/clients/client-s3/src/commands/GetBucketAclCommand.ts b/clients/client-s3/src/commands/GetBucketAclCommand.ts
index 44669d5f3978..bbf9fc234064 100644
--- a/clients/client-s3/src/commands/GetBucketAclCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketAclCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketAclCommandOutput extends GetBucketAclOutput, __Metadat
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>This implementation of the <code>GET</code> action uses the <code>acl</code> subresource
  *          to return the access control list (ACL) of a bucket. To use <code>GET</code> to return the
diff --git a/clients/client-s3/src/commands/GetBucketAnalyticsConfigurationCommand.ts b/clients/client-s3/src/commands/GetBucketAnalyticsConfigurationCommand.ts
index 20e3d4c1a0c8..7f9058bd531d 100644
--- a/clients/client-s3/src/commands/GetBucketAnalyticsConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketAnalyticsConfigurationCommand.ts
@@ -35,7 +35,7 @@ export interface GetBucketAnalyticsConfigurationCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>This implementation of the GET action returns an analytics configuration (identified by
  *          the analytics configuration ID) from the bucket.</p>
diff --git a/clients/client-s3/src/commands/GetBucketCorsCommand.ts b/clients/client-s3/src/commands/GetBucketCorsCommand.ts
index 1b6833dcb836..260230abfba4 100644
--- a/clients/client-s3/src/commands/GetBucketCorsCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketCorsCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketCorsCommandOutput extends GetBucketCorsOutput, __Metad
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the Cross-Origin Resource Sharing (CORS) configuration information set for the
  *          bucket.</p>
diff --git a/clients/client-s3/src/commands/GetBucketEncryptionCommand.ts b/clients/client-s3/src/commands/GetBucketEncryptionCommand.ts
index 50390c28f41d..672997f93743 100644
--- a/clients/client-s3/src/commands/GetBucketEncryptionCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketEncryptionCommand.ts
@@ -40,13 +40,16 @@ export interface GetBucketEncryptionCommandOutput extends GetBucketEncryptionOut
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>General purpose buckets</b> - 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>
+ *                      <b>General purpose buckets</b> - 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>
- *                      <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption configuration in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html">Setting default server-side encryption behavior
- *                for directory buckets</a>.</p>
+ *                      <b>Directory buckets</b> -
+ *                   For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption
+ *                   configuration in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html">Setting
+ *                      default server-side encryption behavior for directory buckets</a>.</p>
  *                </li>
  *             </ul>
  *          </note>
@@ -56,15 +59,20 @@ export interface GetBucketEncryptionCommandOutput extends GetBucketEncryptionOut
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - The <code>s3:GetEncryptionConfiguration</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>.</p>
+ *                         <b>General purpose bucket permissions</b> - The
+ *                            <code>s3:GetEncryptionConfiguration</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>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> - To grant access to this API operation, you must have the <code>s3express:GetEncryptionConfiguration</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:GetEncryptionConfiguration</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>
diff --git a/clients/client-s3/src/commands/GetBucketIntelligentTieringConfigurationCommand.ts b/clients/client-s3/src/commands/GetBucketIntelligentTieringConfigurationCommand.ts
index 188a7210dc02..4369b3df6065 100644
--- a/clients/client-s3/src/commands/GetBucketIntelligentTieringConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketIntelligentTieringConfigurationCommand.ts
@@ -39,7 +39,7 @@ export interface GetBucketIntelligentTieringConfigurationCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Gets the S3 Intelligent-Tiering configuration from the specified 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>
diff --git a/clients/client-s3/src/commands/GetBucketInventoryConfigurationCommand.ts b/clients/client-s3/src/commands/GetBucketInventoryConfigurationCommand.ts
index c87ed307a9d7..38767f30bc06 100644
--- a/clients/client-s3/src/commands/GetBucketInventoryConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketInventoryConfigurationCommand.ts
@@ -39,7 +39,7 @@ export interface GetBucketInventoryConfigurationCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns an inventory configuration (identified by the inventory configuration ID) from
  *          the bucket.</p>
diff --git a/clients/client-s3/src/commands/GetBucketLifecycleConfigurationCommand.ts b/clients/client-s3/src/commands/GetBucketLifecycleConfigurationCommand.ts
index 2c147d18db10..91e6ee87dc48 100644
--- a/clients/client-s3/src/commands/GetBucketLifecycleConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketLifecycleConfigurationCommand.ts
@@ -34,25 +34,69 @@ export interface GetBucketLifecycleConfigurationCommandOutput
     __MetadataBearer {}
 
 /**
- * <note>
- *             <p>This operation is not supported by directory buckets.</p>
- *          </note>
- *          <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_GetBucketLifecycle.html">GetBucketLifecycle</a>. Accordingly,
- *             this section describes the latest API. The response describes the new filter element
- *             that you can use to specify a filter to select a subset of objects to which the rule
- *             applies. If you are using a previous version of the lifecycle configuration, it still
- *             works. For the earlier action, </p>
- *          </note>
- *          <p>Returns the lifecycle configuration information set on the bucket. For information about
+ * <p>Returns the lifecycle configuration information set on the bucket. For information about
  *          lifecycle configuration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html">Object Lifecycle
  *          Management</a>.</p>
- *          <p>To use this operation, you must have permission to perform the
- *             <code>s3:GetLifecycleConfiguration</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>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, which is compatible with the new
+ *          functionality. The previous version of the API supported filtering based only on an object
+ *          key name prefix, which is supported for general purpose buckets for backward compatibility.
+ *          For the related API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycle.html">GetBucketLifecycle</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>
+ *          </note>
+ *          <dl>
+ *             <dt>Permissions</dt>
+ *             <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:GetLifecycleConfiguration</code>
+ *                         permission.</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>
+ *                <ul>
+ *                   <li>
+ *                      <p>
+ *                         <b>Directory bucket permissions</b> -
+ *                         You must have the <code>s3express:GetLifecycleConfiguration</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>
+ *                            </code>. Virtual-hosted-style requests aren't supported.
+ * For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
+ *     <i>Amazon S3 User Guide</i>.</p>
+ *                      </note>
+ *                   </li>
+ *                </ul>
+ *             </dd>
+ *             <dt>HTTP Host header syntax</dt>
+ *             <dd>
+ *                <p>
+ *                   <b>Directory buckets </b> - The HTTP Host
+ *                   header syntax is
+ *                      <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
+ *             </dd>
+ *          </dl>
  *          <p>
  *             <code>GetBucketLifecycleConfiguration</code> has the following special error:</p>
  *          <ul>
diff --git a/clients/client-s3/src/commands/GetBucketLocationCommand.ts b/clients/client-s3/src/commands/GetBucketLocationCommand.ts
index c13f11641599..8135185e8fcd 100644
--- a/clients/client-s3/src/commands/GetBucketLocationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketLocationCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketLocationCommandOutput extends GetBucketLocationOutput,
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the Region the bucket resides in. You set the bucket's Region using the
  *             <code>LocationConstraint</code> request parameter in a <code>CreateBucket</code>
diff --git a/clients/client-s3/src/commands/GetBucketLoggingCommand.ts b/clients/client-s3/src/commands/GetBucketLoggingCommand.ts
index 0dabf2894284..960a6ea25914 100644
--- a/clients/client-s3/src/commands/GetBucketLoggingCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketLoggingCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketLoggingCommandOutput extends GetBucketLoggingOutput, _
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the logging status of a bucket and the permissions users have to view and modify
  *          that status.</p>
diff --git a/clients/client-s3/src/commands/GetBucketMetricsConfigurationCommand.ts b/clients/client-s3/src/commands/GetBucketMetricsConfigurationCommand.ts
index 731571782215..3d2d9b489991 100644
--- a/clients/client-s3/src/commands/GetBucketMetricsConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketMetricsConfigurationCommand.ts
@@ -35,7 +35,7 @@ export interface GetBucketMetricsConfigurationCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Gets a metrics configuration (specified by the metrics configuration ID) from the
  *          bucket. Note that this doesn't include the daily storage metrics.</p>
diff --git a/clients/client-s3/src/commands/GetBucketNotificationConfigurationCommand.ts b/clients/client-s3/src/commands/GetBucketNotificationConfigurationCommand.ts
index 9765d66f3180..d1d43c0c9e99 100644
--- a/clients/client-s3/src/commands/GetBucketNotificationConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketNotificationConfigurationCommand.ts
@@ -33,7 +33,7 @@ export interface GetBucketNotificationConfigurationCommandOutput extends Notific
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the notification configuration of a bucket.</p>
  *          <p>If notifications are not enabled on the bucket, the action returns an empty
diff --git a/clients/client-s3/src/commands/GetBucketOwnershipControlsCommand.ts b/clients/client-s3/src/commands/GetBucketOwnershipControlsCommand.ts
index a0a633453cc7..ca31f1880123 100644
--- a/clients/client-s3/src/commands/GetBucketOwnershipControlsCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketOwnershipControlsCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketOwnershipControlsCommandOutput extends GetBucketOwners
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Retrieves <code>OwnershipControls</code> for an Amazon S3 bucket. To use this operation, you
  *          must have the <code>s3:GetBucketOwnershipControls</code> permission. For more information
diff --git a/clients/client-s3/src/commands/GetBucketPolicyCommand.ts b/clients/client-s3/src/commands/GetBucketPolicyCommand.ts
index d473f43f4c3b..692066b7c2c1 100644
--- a/clients/client-s3/src/commands/GetBucketPolicyCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketPolicyCommand.ts
@@ -40,42 +40,51 @@ export interface GetBucketPolicyCommandOutput extends GetBucketPolicyOutput, __M
  *          <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>GetBucketPolicy</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>GetBucketPolicy</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>GetBucketPolicy</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>GetBucketPolicy</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:GetBucketPolicy</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>
+ *                         <b>General purpose bucket permissions</b> - The
+ *                            <code>s3:GetBucketPolicy</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:GetBucketPolicy</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:GetBucketPolicy</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>
diff --git a/clients/client-s3/src/commands/GetBucketPolicyStatusCommand.ts b/clients/client-s3/src/commands/GetBucketPolicyStatusCommand.ts
index 31c645f16e34..52e3680e9fdb 100644
--- a/clients/client-s3/src/commands/GetBucketPolicyStatusCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketPolicyStatusCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketPolicyStatusCommandOutput extends GetBucketPolicyStatu
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public.
  *          In order to use this operation, you must have the <code>s3:GetBucketPolicyStatus</code>
diff --git a/clients/client-s3/src/commands/GetBucketReplicationCommand.ts b/clients/client-s3/src/commands/GetBucketReplicationCommand.ts
index 6bd7801297e3..2884b3b675a7 100644
--- a/clients/client-s3/src/commands/GetBucketReplicationCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketReplicationCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketReplicationCommandOutput extends GetBucketReplicationO
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the replication configuration of a bucket.</p>
  *          <note>
diff --git a/clients/client-s3/src/commands/GetBucketRequestPaymentCommand.ts b/clients/client-s3/src/commands/GetBucketRequestPaymentCommand.ts
index b7adf552df76..b47c2471f4ca 100644
--- a/clients/client-s3/src/commands/GetBucketRequestPaymentCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketRequestPaymentCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketRequestPaymentCommandOutput extends GetBucketRequestPa
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the request payment configuration of a bucket. To use this version of the
  *          operation, you must be the bucket owner. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html">Requester Pays
diff --git a/clients/client-s3/src/commands/GetBucketTaggingCommand.ts b/clients/client-s3/src/commands/GetBucketTaggingCommand.ts
index 344072a22444..c7591ffbaba7 100644
--- a/clients/client-s3/src/commands/GetBucketTaggingCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketTaggingCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketTaggingCommandOutput extends GetBucketTaggingOutput, _
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the tag set associated with the bucket.</p>
  *          <p>To use this operation, you must have permission to perform the
diff --git a/clients/client-s3/src/commands/GetBucketVersioningCommand.ts b/clients/client-s3/src/commands/GetBucketVersioningCommand.ts
index d4e7f1ae7a6c..aa394707a27a 100644
--- a/clients/client-s3/src/commands/GetBucketVersioningCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketVersioningCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketVersioningCommandOutput extends GetBucketVersioningOut
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the versioning state of a bucket.</p>
  *          <p>To retrieve the versioning state of a bucket, you must be the bucket owner.</p>
diff --git a/clients/client-s3/src/commands/GetBucketWebsiteCommand.ts b/clients/client-s3/src/commands/GetBucketWebsiteCommand.ts
index 40765d3f278f..01d9428b1027 100644
--- a/clients/client-s3/src/commands/GetBucketWebsiteCommand.ts
+++ b/clients/client-s3/src/commands/GetBucketWebsiteCommand.ts
@@ -30,7 +30,7 @@ export interface GetBucketWebsiteCommandOutput extends GetBucketWebsiteOutput, _
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the website configuration for a bucket. To host website on Amazon S3, you can
  *          configure a bucket as website by adding a website configuration. For more information about
diff --git a/clients/client-s3/src/commands/GetObjectAclCommand.ts b/clients/client-s3/src/commands/GetObjectAclCommand.ts
index 44267b96163a..17289b4b64d6 100644
--- a/clients/client-s3/src/commands/GetObjectAclCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectAclCommand.ts
@@ -30,7 +30,7 @@ export interface GetObjectAclCommandOutput extends GetObjectAclOutput, __Metadat
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the access control list (ACL) of an object. To use this operation, you must have
  *             <code>s3:GetObjectAcl</code> permissions or <code>READ_ACP</code> access to the object.
diff --git a/clients/client-s3/src/commands/GetObjectAttributesCommand.ts b/clients/client-s3/src/commands/GetObjectAttributesCommand.ts
index 57c3a89a449f..052ed0223eae 100644
--- a/clients/client-s3/src/commands/GetObjectAttributesCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectAttributesCommand.ts
@@ -42,7 +42,8 @@ export interface GetObjectAttributesCommandOutput extends GetObjectAttributesOut
  *          can be returned with a single call to <code>GetObjectAttributes</code>.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
@@ -52,26 +53,29 @@ export interface GetObjectAttributesCommandOutput extends GetObjectAttributesOut
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - To use
- *                         <code>GetObjectAttributes</code>, you must have READ access to the object. The permissions that you need to use this operation depend on whether the
- *                         bucket is versioned. If the bucket is versioned, you need both the
- *                         <code>s3:GetObjectVersion</code> and <code>s3:GetObjectVersionAttributes</code>
- *                         permissions for this operation. If the bucket is not versioned, you need the
- *                         <code>s3:GetObject</code> and <code>s3:GetObjectAttributes</code> permissions.
- *                         For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html">Specifying Permissions in
- *                            a Policy</a> in the <i>Amazon S3 User Guide</i>. If the object
- *                         that you request does not exist, the error Amazon S3 returns depends on whether you
- *                         also have the <code>s3:ListBucket</code> permission.</p>
+ *                         <b>General purpose bucket permissions</b> - To
+ *                         use <code>GetObjectAttributes</code>, you must have READ access to the
+ *                         object. The permissions that you need to use this operation depend on
+ *                         whether the bucket is versioned. If the bucket is versioned, you need both
+ *                         the <code>s3:GetObjectVersion</code> and
+ *                            <code>s3:GetObjectVersionAttributes</code> permissions for this
+ *                         operation. If the bucket is not versioned, you need the
+ *                            <code>s3:GetObject</code> and <code>s3:GetObjectAttributes</code>
+ *                         permissions. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html">Specifying
+ *                            Permissions in a Policy</a> in the
+ *                            <i>Amazon S3 User Guide</i>. If the object that you request does
+ *                         not exist, the error Amazon S3 returns depends on whether you also have the
+ *                            <code>s3:ListBucket</code> permission.</p>
  *                      <ul>
  *                         <li>
- *                            <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3
- *                               returns an HTTP status code <code>404 Not Found</code> ("no such key")
- *                               error.</p>
+ *                            <p>If you have the <code>s3:ListBucket</code> permission on the
+ *                               bucket, Amazon S3 returns an HTTP status code <code>404 Not Found</code>
+ *                               ("no such key") error.</p>
  *                         </li>
  *                         <li>
- *                            <p>If you don't have the <code>s3:ListBucket</code> permission, Amazon S3 returns
- *                               an HTTP status code <code>403 Forbidden</code> ("access denied")
- *                               error.</p>
+ *                            <p>If you don't have the <code>s3:ListBucket</code> permission, Amazon S3
+ *                               returns an HTTP status code <code>403 Forbidden</code> ("access
+ *                               denied") error.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -83,9 +87,12 @@ export interface GetObjectAttributesCommandOutput extends GetObjectAttributesOut
  * Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
  *                            <code>CreateSession</code>
  *                         </a>.</p>
- *                      <p>If the object is encrypted with
- *                      SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
+ *                      <p>If
+ *                         the
+ *                         object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -93,16 +100,22 @@ export interface GetObjectAttributesCommandOutput extends GetObjectAttributesOut
  *             <dd>
  *                <note>
  *                   <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,
- *                   should not be sent for <code>HEAD</code> requests if your object uses server-side
- *                   encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer server-side
- *                   encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side encryption with Amazon S3
- *                   managed encryption keys (SSE-S3). The <code>x-amz-server-side-encryption</code> header is used when you <code>PUT</code> an object to S3 and want to specify the encryption method.
- *                   If you include this header in a <code>GET</code> request for an object that uses these types of keys,
- *                   you’ll get an HTTP <code>400 Bad Request</code> error. It's because the encryption method can't be changed when you retrieve the object.</p>
+ *                      should not be sent for <code>HEAD</code> requests if your object uses
+ *                      server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer
+ *                      server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side
+ *                      encryption with Amazon S3 managed encryption keys (SSE-S3). The
+ *                         <code>x-amz-server-side-encryption</code> header is used when you
+ *                         <code>PUT</code> an object to S3 and want to specify the encryption method.
+ *                      If you include this header in a <code>GET</code> request for an object that
+ *                      uses these types of keys, you’ll get an HTTP <code>400 Bad Request</code>
+ *                      error. It's because the encryption method can't be changed when you retrieve
+ *                      the object.</p>
  *                </note>
  *                <p>If you encrypt an object by using server-side encryption with customer-provided
- *                   encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the
- *                   metadata from the object, you must use the following headers to provide the encryption key for the server to be able to retrieve the object's metadata. The headers are: </p>
+ *                   encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve
+ *                   the metadata from the object, you must use the following headers to provide the
+ *                   encryption key for the server to be able to retrieve the object's metadata. The
+ *                   headers are: </p>
  *                <ul>
  *                   <li>
  *                      <p>
@@ -120,12 +133,13 @@ export interface GetObjectAttributesCommandOutput extends GetObjectAttributesOut
  *                      </p>
  *                   </li>
  *                </ul>
- *                <p>For more information about SSE-C, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html">Server-Side Encryption
- *                   (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3
- *                      User Guide</i>.</p>
+ *                <p>For more information about SSE-C, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html">Server-Side
+ *                      Encryption (Using Customer-Provided Encryption Keys)</a> in the
+ *                      <i>Amazon S3 User Guide</i>.</p>
  *                <note>
  *                   <p>
- *                      <b>Directory bucket permissions</b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+ *                      <b>Directory bucket permissions</b> -
+ *                      For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). 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, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>
@@ -134,43 +148,47 @@ export interface GetObjectAttributesCommandOutput extends GetObjectAttributesOut
  *             <dt>Versioning</dt>
  *             <dd>
  *                <p>
- *                   <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code>
- *                         to the <code>versionId</code> query parameter in the request.</p>
+ *                   <b>Directory buckets</b> -
+ *                   S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> to the
+ *                      <code>versionId</code> query parameter in the request.</p>
  *             </dd>
  *             <dt>Conditional request headers</dt>
  *             <dd>
  *                <p>Consider the following when using request headers:</p>
  *                <ul>
  *                   <li>
- *                      <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers
- *                         are present in the request as follows, then Amazon S3 returns the HTTP status code
- *                         <code>200 OK</code> and the data requested:</p>
+ *                      <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code>
+ *                         headers are present in the request as follows, then Amazon S3 returns the HTTP
+ *                         status code <code>200 OK</code> and the data requested:</p>
  *                      <ul>
  *                         <li>
  *                            <p>
- *                               <code>If-Match</code> condition evaluates to <code>true</code>.</p>
+ *                               <code>If-Match</code> condition evaluates to
+ *                               <code>true</code>.</p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <code>If-Unmodified-Since</code> condition evaluates to
- *                               <code>false</code>.</p>
+ *                                  <code>false</code>.</p>
  *                         </li>
  *                      </ul>
  *                      <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>.</p>
  *                   </li>
  *                   <li>
- *                      <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code>
- *                         headers are present in the request as follows, then Amazon S3 returns the HTTP status code
- *                         <code>304 Not Modified</code>:</p>
+ *                      <p>If both of the <code>If-None-Match</code> and
+ *                            <code>If-Modified-Since</code> headers are present in the request as
+ *                         follows, then Amazon S3 returns the HTTP status code <code>304 Not
+ *                            Modified</code>:</p>
  *                      <ul>
  *                         <li>
  *                            <p>
- *                               <code>If-None-Match</code> condition evaluates to <code>false</code>.</p>
+ *                               <code>If-None-Match</code> condition evaluates to
+ *                                  <code>false</code>.</p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <code>If-Modified-Since</code> condition evaluates to
- *                               <code>true</code>.</p>
+ *                                  <code>true</code>.</p>
  *                         </li>
  *                      </ul>
  *                      <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>.</p>
diff --git a/clients/client-s3/src/commands/GetObjectCommand.ts b/clients/client-s3/src/commands/GetObjectCommand.ts
index 154538a85f1a..eb860c7b0965 100644
--- a/clients/client-s3/src/commands/GetObjectCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectCommand.ts
@@ -41,16 +41,18 @@ export interface GetObjectCommandOutput extends Omit<GetObjectOutput, "Body">, _
  * <p>Retrieves an object from Amazon S3.</p>
  *          <p>In the <code>GetObject</code> request, specify the full key name for the object.</p>
  *          <p>
- *             <b>General purpose buckets</b> - Both the virtual-hosted-style requests and the path-style requests are supported. For a virtual hosted-style request example, if you have
- *          the object <code>photos/2006/February/sample.jpg</code>, specify the object key name as
- *             <code>/photos/2006/February/sample.jpg</code>. For a path-style request example, if you
- *          have the object <code>photos/2006/February/sample.jpg</code> in the bucket named
- *             <code>examplebucket</code>, specify the object key name as
+ *             <b>General purpose buckets</b> - Both the virtual-hosted-style
+ *          requests and the path-style requests are supported. For a virtual hosted-style request
+ *          example, if you have the object <code>photos/2006/February/sample.jpg</code>, specify the
+ *          object key name as <code>/photos/2006/February/sample.jpg</code>. For a path-style request
+ *          example, if you have the object <code>photos/2006/February/sample.jpg</code> in the bucket
+ *          named <code>examplebucket</code>, specify the object key name as
  *             <code>/examplebucket/photos/2006/February/sample.jpg</code>. For more information about
  *          request types, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingSpecifyBucket">HTTP Host
  *             Header Bucket Specification</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <p>
- *             <b>Directory buckets</b> - Only virtual-hosted-style requests are supported. For a virtual hosted-style request example, if you have the object <code>photos/2006/February/sample.jpg</code> in the bucket named <code>examplebucket--use1-az5--x-s3</code>, specify the object key name as <code>/photos/2006/February/sample.jpg</code>. Also, when you make requests to this API operation, your requests are sent to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *             <b>Directory buckets</b> -
+ *          Only virtual-hosted-style requests are supported. For a virtual hosted-style request example, if you have the object <code>photos/2006/February/sample.jpg</code> in the bucket named <code>examplebucket--use1-az5--x-s3</code>, specify the object key name as <code>/photos/2006/February/sample.jpg</code>. Also, when you make requests to this API operation, your requests are sent to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *             </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          <dl>
@@ -59,28 +61,35 @@ export interface GetObjectCommandOutput extends Omit<GetObjectOutput, "Body">, _
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - You must have the required permissions in a policy. To use <code>GetObject</code>, you must have the <code>READ</code>
- *                         access to the object (or version). If you grant <code>READ</code> access to the anonymous user, the <code>GetObject</code> operation
- *                         returns the object without using an authorization header. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html">Specifying permissions in
- *                            a policy</a> in the <i>Amazon S3 User Guide</i>.</p>
- *                      <p>If you include a <code>versionId</code> in your request header, you must have the
- *                         <code>s3:GetObjectVersion</code> permission to access a specific
- *                         version of an object. The <code>s3:GetObject</code> permission is not required in this scenario.</p>
- *                      <p>If you request the
- *                         current version of an object without a specific <code>versionId</code> in the request header, only
- *                         the <code>s3:GetObject</code> permission is required. The <code>s3:GetObjectVersion</code> permission is not required in this scenario.
- *                      </p>
- *                      <p>If the object that you request doesn’t exist, the error that
- *                         Amazon S3 returns depends on whether you also have the <code>s3:ListBucket</code>
+ *                         <b>General purpose bucket permissions</b> - You
+ *                         must have the required permissions in a policy. To use
+ *                            <code>GetObject</code>, you must have the <code>READ</code> access to the
+ *                         object (or version). If you grant <code>READ</code> access to the anonymous
+ *                         user, the <code>GetObject</code> operation returns the object without using
+ *                         an authorization header. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html">Specifying permissions in a policy</a> in the
+ *                            <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>If you include a <code>versionId</code> in your request header, you must
+ *                         have the <code>s3:GetObjectVersion</code> permission to access a specific
+ *                         version of an object. The <code>s3:GetObject</code> permission is not
+ *                         required in this scenario.</p>
+ *                      <p>If you request the current version of an object without a specific
+ *                            <code>versionId</code> in the request header, only the
+ *                            <code>s3:GetObject</code> permission is required. The
+ *                            <code>s3:GetObjectVersion</code> permission is not required in this
+ *                         scenario. </p>
+ *                      <p>If the object that you request doesn’t exist, the error that Amazon S3 returns
+ *                         depends on whether you also have the <code>s3:ListBucket</code>
  *                         permission.</p>
  *                      <ul>
  *                         <li>
- *                            <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3
- *                               returns an HTTP status code <code>404 Not Found</code> error.</p>
+ *                            <p>If you have the <code>s3:ListBucket</code> permission on the
+ *                               bucket, Amazon S3 returns an HTTP status code <code>404 Not Found</code>
+ *                               error.</p>
  *                         </li>
  *                         <li>
- *                            <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3 returns an
- *                               HTTP status code <code>403 Access Denied</code> error.</p>
+ *                            <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3
+ *                               returns an HTTP status code <code>403 Access Denied</code>
+ *                               error.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -92,50 +101,60 @@ export interface GetObjectCommandOutput extends Omit<GetObjectOutput, "Body">, _
  * Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
  *                            <code>CreateSession</code>
  *                         </a>.</p>
- *                      <p>If the object is encrypted using
- *                      SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
+ *                      <p>If
+ *                         the
+ *                         object is encrypted using SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
  *             <dt>Storage classes</dt>
  *             <dd>
- *                <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the
- *                   S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the
- *                   S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a
- *                   copy using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a>. Otherwise, this operation returns an
- *                   <code>InvalidObjectState</code> error. For information about restoring archived objects,
- *                   see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html">Restoring
- *                      Archived Objects</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval
+ *                   storage class, the S3 Glacier Deep Archive storage class, the
+ *                   S3 Intelligent-Tiering Archive Access tier, or the S3 Intelligent-Tiering Deep Archive Access tier,
+ *                   before you can retrieve the object you must first restore a copy using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a>. Otherwise, this operation returns an
+ *                      <code>InvalidObjectState</code> error. For information about restoring archived
+ *                   objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html">Restoring Archived
+ *                      Objects</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                <p>
- *                   <b>Directory buckets </b> - For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.
+ *                   <b>Directory buckets </b> -
+ *                   For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.
  * Unsupported storage class values won't write a destination object and will respond with the HTTP status code <code>400 Bad Request</code>.</p>
  *             </dd>
  *             <dt>Encryption</dt>
  *             <dd>
- *                <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>, should not
- *                   be sent for the <code>GetObject</code> requests, if your object uses server-side encryption with Amazon S3 managed encryption keys (SSE-S3), 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 include the header in your <code>GetObject</code> requests for the object that uses
- *                   these types of keys, you’ll get an HTTP <code>400 Bad Request</code> error.</p>
+ *                <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,
+ *                   should not be sent for the <code>GetObject</code> requests, if your object uses
+ *                   server-side encryption with Amazon S3 managed encryption keys (SSE-S3), 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 include the header in your
+ *                      <code>GetObject</code> requests for the object that uses these types of keys,
+ *                   you’ll get an HTTP <code>400 Bad Request</code> error.</p>
  *                <p>
- *                   <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
+ *                   <b>Directory buckets</b> -
+ *                   For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>.</p>
  *             </dd>
  *             <dt>Overriding response header values through the request</dt>
  *             <dd>
  *                <p>There are times when you want to override certain response header values of a
  *                      <code>GetObject</code> response. For example, you might override the
- *                      <code>Content-Disposition</code> response header value through your <code>GetObject</code>
- *                   request.</p>
- *                <p>You can override values for a set of response headers. These modified response header values are included only in a successful response, that is, when the HTTP status code <code>200 OK</code> is returned.
- *                   The headers you can override using the following query parameters in the request are a subset of the headers that Amazon S3 accepts when you create an object.
- *                </p>
- *                <p>The response headers that you can override for the
- *                   <code>GetObject</code> response are <code>Cache-Control</code>, <code>Content-Disposition</code>,
- *                   <code>Content-Encoding</code>, <code>Content-Language</code>, <code>Content-Type</code>, and <code>Expires</code>.</p>
- *                <p>To override values for a set of response headers in the
- *                   <code>GetObject</code> response, you can use the following query
- *                   parameters in the request.</p>
+ *                      <code>Content-Disposition</code> response header value through your
+ *                      <code>GetObject</code> request.</p>
+ *                <p>You can override values for a set of response headers. These modified response
+ *                   header values are included only in a successful response, that is, when the HTTP
+ *                   status code <code>200 OK</code> is returned. The headers you can override using
+ *                   the following query parameters in the request are a subset of the headers that
+ *                   Amazon S3 accepts when you create an object. </p>
+ *                <p>The response headers that you can override for the <code>GetObject</code>
+ *                   response are <code>Cache-Control</code>, <code>Content-Disposition</code>,
+ *                      <code>Content-Encoding</code>, <code>Content-Language</code>,
+ *                      <code>Content-Type</code>, and <code>Expires</code>.</p>
+ *                <p>To override values for a set of response headers in the <code>GetObject</code>
+ *                   response, you can use the following query parameters in the request.</p>
  *                <ul>
  *                   <li>
  *                      <p>
@@ -169,9 +188,9 @@ export interface GetObjectCommandOutput extends Omit<GetObjectOutput, "Body">, _
  *                   </li>
  *                </ul>
  *                <note>
- *                   <p>When you use these parameters, you must sign the request by using either an Authorization header or a
- *                      presigned URL. These parameters cannot be used with an
- *                      unsigned (anonymous) request.</p>
+ *                   <p>When you use these parameters, you must sign the request by using either an
+ *                      Authorization header or a presigned URL. These parameters cannot be used with
+ *                      an unsigned (anonymous) request.</p>
  *                </note>
  *             </dd>
  *             <dt>HTTP Host header syntax</dt>
@@ -277,13 +296,13 @@ export interface GetObjectCommandOutput extends Omit<GetObjectOutput, "Body">, _
  *
  * @throws {@link InvalidObjectState} (client fault)
  *  <p>Object is archived and inaccessible until restored.</p>
- *          <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the
- *          S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the
- *          S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a
- *          copy using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a>. Otherwise, this operation returns an
- *          <code>InvalidObjectState</code> error. For information about restoring archived objects,
- *          see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html">Restoring
- *             Archived Objects</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage
+ *          class, the S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access
+ *          tier, or the S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you
+ *          must first restore a copy using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a>. Otherwise, this
+ *          operation returns an <code>InvalidObjectState</code> error. For information about restoring
+ *          archived objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html">Restoring Archived Objects</a> in
+ *          the <i>Amazon S3 User Guide</i>.</p>
  *
  * @throws {@link NoSuchKey} (client fault)
  *  <p>The specified key does not exist.</p>
diff --git a/clients/client-s3/src/commands/GetObjectLegalHoldCommand.ts b/clients/client-s3/src/commands/GetObjectLegalHoldCommand.ts
index 901d338e310d..42a32695aa06 100644
--- a/clients/client-s3/src/commands/GetObjectLegalHoldCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectLegalHoldCommand.ts
@@ -30,7 +30,7 @@ export interface GetObjectLegalHoldCommandOutput extends GetObjectLegalHoldOutpu
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Gets an object's current legal hold status. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Locking
  *          Objects</a>.</p>
diff --git a/clients/client-s3/src/commands/GetObjectLockConfigurationCommand.ts b/clients/client-s3/src/commands/GetObjectLockConfigurationCommand.ts
index c5da4923a86d..0876d0b79f47 100644
--- a/clients/client-s3/src/commands/GetObjectLockConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectLockConfigurationCommand.ts
@@ -30,7 +30,7 @@ export interface GetObjectLockConfigurationCommandOutput extends GetObjectLockCo
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock
  *          configuration will be applied by default to every new object placed in the specified
diff --git a/clients/client-s3/src/commands/GetObjectRetentionCommand.ts b/clients/client-s3/src/commands/GetObjectRetentionCommand.ts
index 2242bcb15990..bb8dae51a5b9 100644
--- a/clients/client-s3/src/commands/GetObjectRetentionCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectRetentionCommand.ts
@@ -30,7 +30,7 @@ export interface GetObjectRetentionCommandOutput extends GetObjectRetentionOutpu
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Retrieves an object's retention settings. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Locking
  *          Objects</a>.</p>
diff --git a/clients/client-s3/src/commands/GetObjectTaggingCommand.ts b/clients/client-s3/src/commands/GetObjectTaggingCommand.ts
index 32326f4bc9dc..fc4903da3e36 100644
--- a/clients/client-s3/src/commands/GetObjectTaggingCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectTaggingCommand.ts
@@ -30,7 +30,7 @@ export interface GetObjectTaggingCommandOutput extends GetObjectTaggingOutput, _
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns the tag-set of an object. You send the GET request against the tagging
  *          subresource associated with the object.</p>
diff --git a/clients/client-s3/src/commands/GetObjectTorrentCommand.ts b/clients/client-s3/src/commands/GetObjectTorrentCommand.ts
index 9eefa303a570..a68e90485395 100644
--- a/clients/client-s3/src/commands/GetObjectTorrentCommand.ts
+++ b/clients/client-s3/src/commands/GetObjectTorrentCommand.ts
@@ -35,7 +35,7 @@ export interface GetObjectTorrentCommandOutput extends Omit<GetObjectTorrentOutp
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns torrent files from a bucket. BitTorrent can save you bandwidth when you're
  *          distributing large files.</p>
diff --git a/clients/client-s3/src/commands/GetPublicAccessBlockCommand.ts b/clients/client-s3/src/commands/GetPublicAccessBlockCommand.ts
index 86f7f8a66338..6686cf535f42 100644
--- a/clients/client-s3/src/commands/GetPublicAccessBlockCommand.ts
+++ b/clients/client-s3/src/commands/GetPublicAccessBlockCommand.ts
@@ -30,7 +30,7 @@ export interface GetPublicAccessBlockCommandOutput extends GetPublicAccessBlockO
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Retrieves the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use
  *          this operation, you must have the <code>s3:GetBucketPublicAccessBlock</code> permission.
diff --git a/clients/client-s3/src/commands/HeadBucketCommand.ts b/clients/client-s3/src/commands/HeadBucketCommand.ts
index 9ea3c2a1f3a3..3c7d914bfb51 100644
--- a/clients/client-s3/src/commands/HeadBucketCommand.ts
+++ b/clients/client-s3/src/commands/HeadBucketCommand.ts
@@ -29,24 +29,33 @@ export interface HeadBucketCommandInput extends HeadBucketRequest {}
 export interface HeadBucketCommandOutput extends HeadBucketOutput, __MetadataBearer {}
 
 /**
- * <p>You can use this operation to determine if a bucket exists and if you have permission to access it. The action returns a <code>200 OK</code> if the bucket exists and you have permission
- *          to access it.</p>
+ * <p>You can use this operation to determine if a bucket exists and if you have permission to
+ *          access it. The action returns a <code>200 OK</code> if the bucket exists and you have
+ *          permission to access it.</p>
  *          <note>
  *             <p>If the bucket does not exist or you do not have permission to access it, the
- *             <code>HEAD</code> request returns a generic <code>400 Bad Request</code>, <code>403
- *             Forbidden</code> or <code>404 Not Found</code> code. A message body is not included, so
- *          you cannot determine the exception beyond these HTTP response codes.</p>
+ *                <code>HEAD</code> request returns a generic <code>400 Bad Request</code>, <code>403
+ *                Forbidden</code> or <code>404 Not Found</code> code. A message body is not included,
+ *             so you cannot determine the exception beyond these HTTP response codes.</p>
  *          </note>
  *          <dl>
  *             <dt>Authentication and authorization</dt>
  *             <dd>
  *                <p>
- *                   <b>General purpose buckets</b> - Request to public buckets that grant the s3:ListBucket permission publicly do not need to be signed. All other <code>HeadBucket</code> requests must be authenticated and signed by using IAM credentials (access key ID and secret access key for the IAM identities). All headers with the <code>x-amz-</code> prefix, including
- *                         <code>x-amz-copy-source</code>, must be signed. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
+ *                   <b>General purpose buckets</b> - Request to public
+ *                   buckets that grant the s3:ListBucket permission publicly do not need to be signed.
+ *                   All other <code>HeadBucket</code> requests must be authenticated and signed by
+ *                   using IAM credentials (access key ID and secret access key for the IAM
+ *                   identities). All headers with the <code>x-amz-</code> prefix, including
+ *                      <code>x-amz-copy-source</code>, must be signed. For more information, see
+ *                      <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
  *                <p>
- *                   <b>Directory buckets</b> - You must use IAM credentials to authenticate and authorize your access to the <code>HeadBucket</code> API operation, instead of using the
- *                   temporary security credentials through the <code>CreateSession</code> API operation.</p>
- *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>
+ *                   <b>Directory buckets</b> - You must use IAM
+ *                   credentials to authenticate and authorize your access to the
+ *                      <code>HeadBucket</code> API operation, instead of using the temporary security
+ *                   credentials through the <code>CreateSession</code> API operation.</p>
+ *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your
+ *                   behalf.</p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
@@ -54,10 +63,13 @@ export interface HeadBucketCommandOutput extends HeadBucketOutput, __MetadataBea
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - To use this operation, you must have permissions to perform the
- *                         <code>s3:ListBucket</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/s3-access-control.html">Managing
- *                            access permissions to your Amazon S3 resources</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                         <b>General purpose bucket permissions</b> - To
+ *                         use this operation, you must have permissions to perform the
+ *                            <code>s3:ListBucket</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/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>
@@ -65,8 +77,12 @@ export interface HeadBucketCommandOutput extends HeadBucketOutput, __MetadataBea
  *                         You must have the <b>
  *                            <code>s3express:CreateSession</code>
  *                         </b> permission in the
- *                            <code>Action</code> element of a policy. By default, the session is in the <code>ReadWrite</code> mode. If you want to restrict the access, you can explicitly set the <code>s3express:SessionMode</code> condition key to <code>ReadOnly</code> on the bucket.</p>
- *                      <p>For more information about example bucket policies, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                            <code>Action</code> element of a policy. By default, the session is in
+ *                         the <code>ReadWrite</code> mode. If you want to restrict the access, you can
+ *                         explicitly set the <code>s3express:SessionMode</code> condition key to
+ *                            <code>ReadOnly</code> on the bucket.</p>
+ *                      <p>For more information about example bucket policies, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for
+ *                            S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                </ul>
  *             </dd>
diff --git a/clients/client-s3/src/commands/HeadObjectCommand.ts b/clients/client-s3/src/commands/HeadObjectCommand.ts
index 62a8c0751401..2aabdc1dd699 100644
--- a/clients/client-s3/src/commands/HeadObjectCommand.ts
+++ b/clients/client-s3/src/commands/HeadObjectCommand.ts
@@ -36,17 +36,19 @@ export interface HeadObjectCommandOutput extends HeadObjectOutput, __MetadataBea
 
 /**
  * <p>The <code>HEAD</code> operation retrieves metadata from an object without returning the
- *          object itself. This operation is useful if you're interested only in an object's metadata.</p>
+ *          object itself. This operation is useful if you're interested only in an object's
+ *          metadata.</p>
  *          <note>
- *             <p>A <code>HEAD</code> request has the same options as a <code>GET</code> operation on an
- *          object. The response is identical to the <code>GET</code> response except that there is no
- *          response body. Because of this, if the <code>HEAD</code> request generates an error, it
- *          returns a generic code, such as <code>400 Bad Request</code>, <code>403 Forbidden</code>, <code>404 Not
- *             Found</code>, <code>405 Method Not Allowed</code>, <code>412 Precondition Failed</code>, or <code>304 Not Modified</code>.
- *          It's not possible to retrieve the exact exception of these error codes.</p>
+ *             <p>A <code>HEAD</code> request has the same options as a <code>GET</code> operation on
+ *             an object. The response is identical to the <code>GET</code> response except that there
+ *             is no response body. Because of this, if the <code>HEAD</code> request generates an
+ *             error, it returns a generic code, such as <code>400 Bad Request</code>, <code>403
+ *                Forbidden</code>, <code>404 Not Found</code>, <code>405 Method Not Allowed</code>,
+ *                <code>412 Precondition Failed</code>, or <code>304 Not Modified</code>. It's not
+ *             possible to retrieve the exact exception of these error codes.</p>
  *          </note>
  *          <p>Request headers are limited to 8 KB in size. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonRequestHeaders.html">Common
- *          Request Headers</a>.</p>
+ *             Request Headers</a>.</p>
  *          <dl>
  *             <dt>Permissions</dt>
  *             <dd>
@@ -55,20 +57,25 @@ export interface HeadObjectCommandOutput extends HeadObjectOutput, __MetadataBea
  *                   <li>
  *                      <p>
  *                         <b>General purpose bucket permissions</b> - To
- *                         use <code>HEAD</code>, you must have the <code>s3:GetObject</code> permission. You need the relevant read object (or version) permission for this operation.
- *                         For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/list_amazons3.html">Actions, resources, and condition
- *                            keys for Amazon S3</a> in the <i>Amazon S3
- *                               User Guide</i>. For more information about the permissions to S3 API operations by S3 resource types, see <a href="/AmazonS3/latest/userguide/using-with-s3-policy-actions.html">Required permissions for Amazon S3 API operations</a> in the <i>Amazon S3 User Guide</i>.</p>
- *                      <p>If the object you request doesn't exist, the error that
- *                         Amazon S3 returns depends on whether you also have the <code>s3:ListBucket</code> permission.</p>
+ *                         use <code>HEAD</code>, you must have the <code>s3:GetObject</code>
+ *                         permission. You need the relevant read object (or version) permission for
+ *                         this operation. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/list_amazons3.html">Actions, resources, and
+ *                            condition keys for Amazon S3</a> in the <i>Amazon S3 User
+ *                            Guide</i>. For more information about the permissions to S3 API
+ *                         operations by S3 resource types, see <a href="/AmazonS3/latest/userguide/using-with-s3-policy-actions.html">Required permissions for Amazon S3 API operations</a> in the
+ *                            <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>If the object you request doesn't exist, the error that Amazon S3 returns
+ *                         depends on whether you also have the <code>s3:ListBucket</code>
+ *                         permission.</p>
  *                      <ul>
  *                         <li>
- *                            <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3
- *                               returns an HTTP status code <code>404 Not Found</code> error.</p>
+ *                            <p>If you have the <code>s3:ListBucket</code> permission on the
+ *                               bucket, Amazon S3 returns an HTTP status code <code>404 Not Found</code>
+ *                               error.</p>
  *                         </li>
  *                         <li>
- *                            <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3 returns
- *                               an HTTP status code <code>403 Forbidden</code> error.</p>
+ *                            <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3
+ *                               returns an HTTP status code <code>403 Forbidden</code> error.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -80,9 +87,11 @@ export interface HeadObjectCommandOutput extends HeadObjectOutput, __MetadataBea
  * Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
  *                            <code>CreateSession</code>
  *                         </a>.</p>
- *                      <p>If you enable <code>x-amz-checksum-mode</code> in the request and the object is encrypted with
- *                         Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key to retrieve the checksum of the object.</p>
+ *                      <p>If you enable <code>x-amz-checksum-mode</code> in the request and the
+ *                         object is encrypted with Amazon Web Services Key Management Service (Amazon Web Services KMS), you must
+ *                         also have the <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code>
+ *                         permissions in IAM identity-based policies and KMS key policies for the
+ *                         KMS key to retrieve the checksum of the object.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -90,16 +99,22 @@ export interface HeadObjectCommandOutput extends HeadObjectOutput, __MetadataBea
  *             <dd>
  *                <note>
  *                   <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,
- *                   should not be sent for <code>HEAD</code> requests if your object uses server-side
- *                   encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer server-side
- *                   encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side encryption with Amazon S3
- *                   managed encryption keys (SSE-S3). The <code>x-amz-server-side-encryption</code> header is used when you <code>PUT</code> an object to S3 and want to specify the encryption method.
- *                   If you include this header in a <code>HEAD</code> request for an object that uses these types of keys,
- *                   you’ll get an HTTP <code>400 Bad Request</code> error. It's because the encryption method can't be changed when you retrieve the object.</p>
+ *                      should not be sent for <code>HEAD</code> requests if your object uses
+ *                      server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer
+ *                      server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side
+ *                      encryption with Amazon S3 managed encryption keys (SSE-S3). The
+ *                         <code>x-amz-server-side-encryption</code> header is used when you
+ *                         <code>PUT</code> an object to S3 and want to specify the encryption method.
+ *                      If you include this header in a <code>HEAD</code> request for an object that
+ *                      uses these types of keys, you’ll get an HTTP <code>400 Bad Request</code>
+ *                      error. It's because the encryption method can't be changed when you retrieve
+ *                      the object.</p>
  *                </note>
  *                <p>If you encrypt an object by using server-side encryption with customer-provided
- *                encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the
- *                metadata from the object, you must use the following headers to provide the encryption key for the server to be able to retrieve the object's metadata. The headers are: </p>
+ *                   encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve
+ *                   the metadata from the object, you must use the following headers to provide the
+ *                   encryption key for the server to be able to retrieve the object's metadata. The
+ *                   headers are: </p>
  *                <ul>
  *                   <li>
  *                      <p>
@@ -117,12 +132,13 @@ export interface HeadObjectCommandOutput extends HeadObjectOutput, __MetadataBea
  *                      </p>
  *                   </li>
  *                </ul>
- *                <p>For more information about SSE-C, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html">Server-Side Encryption
- *                (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3
- *                   User Guide</i>.</p>
+ *                <p>For more information about SSE-C, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html">Server-Side
+ *                      Encryption (Using Customer-Provided Encryption Keys)</a> in the
+ *                      <i>Amazon S3 User Guide</i>.</p>
  *                <note>
  *                   <p>
- *                      <b>Directory bucket </b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
+ *                      <b>Directory bucket </b> -
+ *                      For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. </p>
  *                </note>
  *             </dd>
@@ -130,22 +146,28 @@ export interface HeadObjectCommandOutput extends HeadObjectOutput, __MetadataBea
  *             <dd>
  *                <ul>
  *                   <li>
- *                      <p>If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes <code>x-amz-delete-marker: true</code> in the response.</p>
+ *                      <p>If the current version of the object is a delete marker, Amazon S3 behaves as
+ *                         if the object was deleted and includes <code>x-amz-delete-marker:
+ *                            true</code> in the response.</p>
  *                   </li>
  *                   <li>
- *                      <p>If the specified version is a delete marker, the response returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified: timestamp</code> response header.</p>
+ *                      <p>If the specified version is a delete marker, the response returns a
+ *                            <code>405 Method Not Allowed</code> error and the <code>Last-Modified:
+ *                            timestamp</code> response header.</p>
  *                   </li>
  *                </ul>
  *                <note>
  *                   <ul>
  *                      <li>
  *                         <p>
- *                            <b>Directory buckets</b> - Delete marker is not supported by directory buckets.</p>
+ *                            <b>Directory buckets</b> -
+ *                            Delete marker is not supported for directory buckets.</p>
  *                      </li>
  *                      <li>
  *                         <p>
- *                            <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code>
- *                         to the <code>versionId</code> query parameter in the request.</p>
+ *                            <b>Directory buckets</b> -
+ *                            S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code>
+ *                            to the <code>versionId</code> query parameter in the request.</p>
  *                      </li>
  *                   </ul>
  *                </note>
diff --git a/clients/client-s3/src/commands/ListBucketAnalyticsConfigurationsCommand.ts b/clients/client-s3/src/commands/ListBucketAnalyticsConfigurationsCommand.ts
index d1329097476b..8cb9ce76269c 100644
--- a/clients/client-s3/src/commands/ListBucketAnalyticsConfigurationsCommand.ts
+++ b/clients/client-s3/src/commands/ListBucketAnalyticsConfigurationsCommand.ts
@@ -35,7 +35,7 @@ export interface ListBucketAnalyticsConfigurationsCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Lists the analytics configurations for the bucket. You can have up to 1,000 analytics
  *          configurations per bucket.</p>
diff --git a/clients/client-s3/src/commands/ListBucketIntelligentTieringConfigurationsCommand.ts b/clients/client-s3/src/commands/ListBucketIntelligentTieringConfigurationsCommand.ts
index 611057d338c1..7f7183e052f5 100644
--- a/clients/client-s3/src/commands/ListBucketIntelligentTieringConfigurationsCommand.ts
+++ b/clients/client-s3/src/commands/ListBucketIntelligentTieringConfigurationsCommand.ts
@@ -39,7 +39,7 @@ export interface ListBucketIntelligentTieringConfigurationsCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Lists the S3 Intelligent-Tiering configuration from the specified 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>
diff --git a/clients/client-s3/src/commands/ListBucketInventoryConfigurationsCommand.ts b/clients/client-s3/src/commands/ListBucketInventoryConfigurationsCommand.ts
index 2e1f59fc209e..201ca1c96e6c 100644
--- a/clients/client-s3/src/commands/ListBucketInventoryConfigurationsCommand.ts
+++ b/clients/client-s3/src/commands/ListBucketInventoryConfigurationsCommand.ts
@@ -39,7 +39,7 @@ export interface ListBucketInventoryConfigurationsCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns a list of inventory configurations for the bucket. You can have up to 1,000
  *          analytics configurations per bucket.</p>
diff --git a/clients/client-s3/src/commands/ListBucketMetricsConfigurationsCommand.ts b/clients/client-s3/src/commands/ListBucketMetricsConfigurationsCommand.ts
index 406ac588e6fb..0e40ae3b1a68 100644
--- a/clients/client-s3/src/commands/ListBucketMetricsConfigurationsCommand.ts
+++ b/clients/client-s3/src/commands/ListBucketMetricsConfigurationsCommand.ts
@@ -35,7 +35,7 @@ export interface ListBucketMetricsConfigurationsCommandOutput
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Lists the metrics configurations for the bucket. The metrics configurations are only for
  *          the request metrics of the bucket and do not provide information on daily storage metrics.
diff --git a/clients/client-s3/src/commands/ListBucketsCommand.ts b/clients/client-s3/src/commands/ListBucketsCommand.ts
index 230b28e1120b..77dc71f62345 100644
--- a/clients/client-s3/src/commands/ListBucketsCommand.ts
+++ b/clients/client-s3/src/commands/ListBucketsCommand.ts
@@ -30,17 +30,17 @@ export interface ListBucketsCommandOutput extends ListBucketsOutput, __MetadataB
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Returns a list of all buckets owned by the authenticated sender of the request. To use
- *          this operation, you must have the <code>s3:ListAllMyBuckets</code> permission. </p>
+ *          <p>Returns a list of all buckets owned by the authenticated sender of the request. To grant IAM permission to use
+ *          this operation, you must add the <code>s3:ListAllMyBuckets</code> policy action. </p>
  *          <p>For information about Amazon S3 buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html">Creating, configuring, and
  *             working with Amazon S3 buckets</a>.</p>
  *          <important>
- *             <p>We strongly recommend using only paginated requests. Unpaginated requests are only supported for
+ *             <p>We strongly recommend using only paginated <code>ListBuckets</code> requests. Unpaginated <code>ListBuckets</code> requests are only supported for
  *             Amazon Web Services accounts set to the default general purpose bucket quota of 10,000. If you have an approved
- *             general purpose bucket quota above 10,000, you must send paginated requests to list your account’s buckets.
- *             All unpaginated ListBuckets requests will be rejected for Amazon Web Services accounts with a general purpose bucket quota
+ *             general purpose bucket quota above 10,000, you must send paginated <code>ListBuckets</code> requests to list your account’s buckets.
+ *             All unpaginated <code>ListBuckets</code> requests will be rejected for Amazon Web Services accounts with a general purpose bucket quota
  *             greater than 10,000. </p>
  *          </important>
  * @example
diff --git a/clients/client-s3/src/commands/ListDirectoryBucketsCommand.ts b/clients/client-s3/src/commands/ListDirectoryBucketsCommand.ts
index f9b3ea42fe7e..39a85c75695a 100644
--- a/clients/client-s3/src/commands/ListDirectoryBucketsCommand.ts
+++ b/clients/client-s3/src/commands/ListDirectoryBucketsCommand.ts
@@ -29,7 +29,8 @@ export interface ListDirectoryBucketsCommandInput extends ListDirectoryBucketsRe
 export interface ListDirectoryBucketsCommandOutput extends ListDirectoryBucketsOutput, __MetadataBearer {}
 
 /**
- * <p>Returns a list of all Amazon S3 directory buckets owned by the authenticated sender of the request. For more information about directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
+ * <p>Returns a list of all Amazon S3 directory buckets owned by the authenticated sender of the
+ *          request. For more information about directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</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>
@@ -40,16 +41,21 @@ export interface ListDirectoryBucketsCommandOutput extends ListDirectoryBucketsO
  *          <dl>
  *             <dt>Permissions</dt>
  *             <dd>
- *                <p>You must have the <code>s3express:ListAllMyDirectoryBuckets</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>You must have the <code>s3express:ListAllMyDirectoryBuckets</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>
  *             </dd>
  *             <dt>HTTP Host header syntax</dt>
  *             <dd>
  *                <p>
- *                   <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
+ *                   <b>Directory buckets </b> - The HTTP Host
+ *                   header syntax is
+ *                      <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
  *             </dd>
  *          </dl>
  *          <note>
- *             <p> The <code>BucketRegion</code> response element is not part of the <code>ListDirectoryBuckets</code> Response Syntax.</p>
+ *             <p> The <code>BucketRegion</code> response element is not part of the
+ *                <code>ListDirectoryBuckets</code> Response Syntax.</p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
diff --git a/clients/client-s3/src/commands/ListMultipartUploadsCommand.ts b/clients/client-s3/src/commands/ListMultipartUploadsCommand.ts
index 372dc1f8870a..6a63c3c6efc6 100644
--- a/clients/client-s3/src/commands/ListMultipartUploadsCommand.ts
+++ b/clients/client-s3/src/commands/ListMultipartUploadsCommand.ts
@@ -29,39 +29,47 @@ export interface ListMultipartUploadsCommandInput extends ListMultipartUploadsRe
 export interface ListMultipartUploadsCommandOutput extends ListMultipartUploadsOutput, __MetadataBearer {}
 
 /**
- * <p>This operation lists in-progress multipart uploads in a bucket. An in-progress multipart upload is a
- *          multipart upload that has been initiated by the <code>CreateMultipartUpload</code> request, but
- *          has not yet been completed or aborted.</p>
+ * <p>This operation lists in-progress multipart uploads in a bucket. An in-progress multipart
+ *          upload is a multipart upload that has been initiated by the
+ *             <code>CreateMultipartUpload</code> request, but has not yet been completed or
+ *          aborted.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> -
- *             If multipart uploads in a directory bucket are in progress, you can't delete the bucket until all the in-progress multipart uploads are aborted or completed.
- *             To delete these in-progress multipart uploads, use the <code>ListMultipartUploads</code> operation to list the in-progress multipart
- *             uploads in the bucket and use the <code>AbortMultipartUpload</code> operation to abort all the in-progress multipart uploads.
- *             </p>
+ *                <b>Directory buckets</b> - If multipart uploads in
+ *             a directory bucket are in progress, you can't delete the bucket until all the
+ *             in-progress multipart uploads are aborted or completed. To delete these in-progress
+ *             multipart uploads, use the <code>ListMultipartUploads</code> operation to list the
+ *             in-progress multipart uploads in the bucket and use the
+ *                <code>AbortMultipartUpload</code> operation to abort all the in-progress multipart
+ *             uploads. </p>
  *          </note>
- *          <p>The <code>ListMultipartUploads</code> operation returns a maximum of 1,000 multipart uploads in the response. The limit of 1,000 multipart
- *          uploads is also the default
- *          value. You can further limit the number of uploads in a response by specifying the
- *          <code>max-uploads</code> request parameter. If there are more than 1,000 multipart uploads that
- *          satisfy your <code>ListMultipartUploads</code> request, the response returns an <code>IsTruncated</code> element
- *          with the value of <code>true</code>, a <code>NextKeyMarker</code> element, and a <code>NextUploadIdMarker</code> element.
- *          To list the remaining multipart uploads, you need to make subsequent <code>ListMultipartUploads</code> requests.
- *          In these requests, include two query parameters: <code>key-marker</code> and <code>upload-id-marker</code>.
- *          Set the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous response.
- *          Similarly, set the value of <code>upload-id-marker</code> to the <code>NextUploadIdMarker</code> value from the previous response.</p>
+ *          <p>The <code>ListMultipartUploads</code> operation returns a maximum of 1,000 multipart
+ *          uploads in the response. The limit of 1,000 multipart uploads is also the default value.
+ *          You can further limit the number of uploads in a response by specifying the
+ *             <code>max-uploads</code> request parameter. If there are more than 1,000 multipart
+ *          uploads that satisfy your <code>ListMultipartUploads</code> request, the response returns
+ *          an <code>IsTruncated</code> element with the value of <code>true</code>, a
+ *             <code>NextKeyMarker</code> element, and a <code>NextUploadIdMarker</code> element. To
+ *          list the remaining multipart uploads, you need to make subsequent
+ *             <code>ListMultipartUploads</code> requests. In these requests, include two query
+ *          parameters: <code>key-marker</code> and <code>upload-id-marker</code>. Set the value of
+ *             <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous
+ *          response. Similarly, set the value of <code>upload-id-marker</code> to the
+ *             <code>NextUploadIdMarker</code> value from the previous response.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> - The <code>upload-id-marker</code> element and
- *          the <code>NextUploadIdMarker</code> element aren't supported by directory buckets.
- *          To list the additional multipart uploads, you only need to set the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous response. </p>
+ *                <b>Directory buckets</b> - The
+ *                <code>upload-id-marker</code> element and the <code>NextUploadIdMarker</code> element
+ *             aren't supported by directory buckets. To list the additional multipart uploads, you
+ *             only need to set the value of <code>key-marker</code> to the <code>NextKeyMarker</code>
+ *             value from the previous response. </p>
  *          </note>
  *          <p>For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading Objects Using Multipart
- *          Upload</a> in the <i>Amazon S3
- *             User Guide</i>.</p>
+ *             Upload</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 Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
@@ -71,9 +79,10 @@ export interface ListMultipartUploadsCommandOutput extends ListMultipartUploadsO
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - For information about permissions required to use the multipart upload API, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload
- *                         and Permissions</a> in the <i>Amazon S3
- *                            User Guide</i>.</p>
+ *                         <b>General purpose bucket permissions</b> - For
+ *                         information about permissions required to use the multipart upload API, see
+ *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
+ *                            Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -91,22 +100,30 @@ export interface ListMultipartUploadsCommandOutput extends ListMultipartUploadsO
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - In the <code>ListMultipartUploads</code> response, the multipart uploads are sorted based on two criteria:</p>
+ *                         <b>General purpose bucket</b> - In the
+ *                            <code>ListMultipartUploads</code> response, the multipart uploads are
+ *                         sorted based on two criteria:</p>
  *                      <ul>
  *                         <li>
- *                            <p>Key-based sorting - Multipart uploads are initially sorted in ascending order based on their object keys.</p>
+ *                            <p>Key-based sorting - Multipart uploads are initially sorted
+ *                               in ascending order based on their object keys.</p>
  *                         </li>
  *                         <li>
- *                            <p>Time-based sorting - For uploads that share the same object key,
- *                               they are further sorted in ascending order based on the upload initiation time. Among uploads with the same key, the one that was initiated first will appear before the ones that were initiated later.</p>
+ *                            <p>Time-based sorting - For uploads that share the same object
+ *                               key, they are further sorted in ascending order based on the upload
+ *                               initiation time. Among uploads with the same key, the one that was
+ *                               initiated first will appear before the ones that were initiated
+ *                               later.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket</b> - In the <code>ListMultipartUploads</code> response, the multipart uploads aren't sorted lexicographically based on the object keys.
+ *                         <b>Directory bucket</b> - In the
+ *                            <code>ListMultipartUploads</code> response, the multipart uploads aren't
+ *                         sorted lexicographically based on the object keys.
  *
- *                         </p>
+ *                      </p>
  *                   </li>
  *                </ul>
  *             </dd>
diff --git a/clients/client-s3/src/commands/ListObjectVersionsCommand.ts b/clients/client-s3/src/commands/ListObjectVersionsCommand.ts
index ea5700fd7888..74159bd02e2d 100644
--- a/clients/client-s3/src/commands/ListObjectVersionsCommand.ts
+++ b/clients/client-s3/src/commands/ListObjectVersionsCommand.ts
@@ -30,7 +30,7 @@ export interface ListObjectVersionsCommandOutput extends ListObjectVersionsOutpu
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns metadata about all versions of the objects in a bucket. You can also use request
  *          parameters as selection criteria to return metadata about a subset of all the object
diff --git a/clients/client-s3/src/commands/ListObjectsCommand.ts b/clients/client-s3/src/commands/ListObjectsCommand.ts
index d4be20e19f9c..d912a235812d 100644
--- a/clients/client-s3/src/commands/ListObjectsCommand.ts
+++ b/clients/client-s3/src/commands/ListObjectsCommand.ts
@@ -30,7 +30,7 @@ export interface ListObjectsCommandOutput extends ListObjectsOutput, __MetadataB
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Returns some or all (up to 1,000) of the objects in a bucket. You can use the request
  *          parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK
diff --git a/clients/client-s3/src/commands/ListObjectsV2Command.ts b/clients/client-s3/src/commands/ListObjectsV2Command.ts
index 0897b22770f2..c8e43b6f81d6 100644
--- a/clients/client-s3/src/commands/ListObjectsV2Command.ts
+++ b/clients/client-s3/src/commands/ListObjectsV2Command.ts
@@ -33,24 +33,27 @@ export interface ListObjectsV2CommandOutput extends ListObjectsV2Output, __Metad
  *          use the request parameters as selection criteria to return a subset of the objects in a
  *          bucket. A <code>200 OK</code> response can contain valid or invalid XML. Make sure to
  *          design your application to parse the contents of the response and handle it appropriately.
- *
  *          For more information about listing objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ListingKeysUsingAPIs.html">Listing object keys
- *             programmatically</a> in the <i>Amazon S3 User Guide</i>. To get a list of your buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html">ListBuckets</a>.</p>
+ *             programmatically</a> in the <i>Amazon S3 User Guide</i>. To get a list of
+ *          your buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html">ListBuckets</a>.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>General purpose bucket</b> - For general purpose buckets, <code>ListObjectsV2</code> doesn't return prefixes that are related only to in-progress multipart uploads.</p>
+ *                      <b>General purpose bucket</b> - For general purpose buckets,
+ *                      <code>ListObjectsV2</code> doesn't return prefixes that are related only to
+ *                   in-progress multipart uploads.</p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> -
- *                For directory buckets, <code>ListObjectsV2</code> response includes the prefixes that are related only to in-progress multipart uploads.
- *               </p>
+ *                      <b>Directory buckets</b> - For
+ *                   directory buckets, <code>ListObjectsV2</code> response includes the prefixes that
+ *                   are related only to in-progress multipart uploads. </p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets</b> -
+ *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
@@ -62,11 +65,13 @@ export interface ListObjectsV2CommandOutput extends ListObjectsV2Output, __Metad
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - To use this operation, you must have READ access to the bucket. You must have permission to perform
- *                         the <code>s3:ListBucket</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> in the
- *                         <i>Amazon S3 User Guide</i>.</p>
+ *                         <b>General purpose bucket permissions</b> - To
+ *                         use this operation, you must have READ access to the bucket. You must have
+ *                         permission to perform the <code>s3:ListBucket</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> in the
+ *                            <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -84,11 +89,15 @@ export interface ListObjectsV2CommandOutput extends ListObjectsV2Output, __Metad
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - For general purpose buckets, <code>ListObjectsV2</code> returns objects in lexicographical order based on their key names.</p>
+ *                         <b>General purpose bucket</b> - For
+ *                         general purpose buckets, <code>ListObjectsV2</code> returns objects in
+ *                         lexicographical order based on their key names.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket</b> - For directory buckets, <code>ListObjectsV2</code> does not return objects in lexicographical order.</p>
+ *                         <b>Directory bucket</b> - For
+ *                         directory buckets, <code>ListObjectsV2</code> does not return objects in
+ *                         lexicographical order.</p>
  *                   </li>
  *                </ul>
  *             </dd>
diff --git a/clients/client-s3/src/commands/ListPartsCommand.ts b/clients/client-s3/src/commands/ListPartsCommand.ts
index bd052d6eb825..84de64e66d19 100644
--- a/clients/client-s3/src/commands/ListPartsCommand.ts
+++ b/clients/client-s3/src/commands/ListPartsCommand.ts
@@ -31,20 +31,22 @@ export interface ListPartsCommandOutput extends ListPartsOutput, __MetadataBeare
 
 /**
  * <p>Lists the parts that have been uploaded for a specific multipart upload.</p>
- *          <p>To use this operation, you must provide the <code>upload ID</code> in the request. You obtain this uploadID by sending the initiate multipart upload
- *          request through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.</p>
- *          <p>The <code>ListParts</code> request returns a maximum of 1,000 uploaded parts. The limit of 1,000 parts is also the default value. You can restrict the number of parts in a response by specifying the
- *             <code>max-parts</code> request parameter. If your multipart upload consists of more than
- *          1,000 parts, the response returns an <code>IsTruncated</code> field with the value of <code>true</code>,
- *          and a <code>NextPartNumberMarker</code> element. To list remaining uploaded parts, in subsequent <code>ListParts</code>
- *          requests, include the <code>part-number-marker</code> query string parameter and set its value to
- *          the <code>NextPartNumberMarker</code> field value from the previous response.</p>
+ *          <p>To use this operation, you must provide the <code>upload ID</code> in the request. You
+ *          obtain this uploadID by sending the initiate multipart upload request through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.</p>
+ *          <p>The <code>ListParts</code> request returns a maximum of 1,000 uploaded parts. The limit
+ *          of 1,000 parts is also the default value. You can restrict the number of parts in a
+ *          response by specifying the <code>max-parts</code> request parameter. If your multipart
+ *          upload consists of more than 1,000 parts, the response returns an <code>IsTruncated</code>
+ *          field with the value of <code>true</code>, and a <code>NextPartNumberMarker</code> element.
+ *          To list remaining uploaded parts, in subsequent <code>ListParts</code> requests, include
+ *          the <code>part-number-marker</code> query string parameter and set its value to the
+ *             <code>NextPartNumberMarker</code> field value from the previous response.</p>
  *          <p>For more information on multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading Objects Using Multipart
- *          Upload</a> in the <i>Amazon S3
- *             User Guide</i>.</p>
+ *             Upload</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 Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
@@ -54,12 +56,15 @@ export interface ListPartsCommandOutput extends ListPartsOutput, __MetadataBeare
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - For information about permissions required to use the multipart upload API, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload
- *                         and Permissions</a> in the <i>Amazon S3
- *                            User Guide</i>.</p>
- *                      <p>If the upload was created 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), you must have permission
- *                         to the <code>kms:Decrypt</code> action for the <code>ListParts</code> request to succeed.</p>
+ *                         <b>General purpose bucket permissions</b> - For
+ *                         information about permissions required to use the multipart upload API, see
+ *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
+ *                            Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>If the upload was created 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), you must have permission to the
+ *                            <code>kms:Decrypt</code> action for the <code>ListParts</code> request to
+ *                         succeed.</p>
  *                   </li>
  *                   <li>
  *                      <p>
diff --git a/clients/client-s3/src/commands/PutBucketAccelerateConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketAccelerateConfigurationCommand.ts
index 0a3945af0266..83dcc4dc13a5 100644
--- a/clients/client-s3/src/commands/PutBucketAccelerateConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketAccelerateConfigurationCommand.ts
@@ -33,7 +33,7 @@ export interface PutBucketAccelerateConfigurationCommandOutput extends __Metadat
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a
  *          bucket-level feature that enables you to perform faster data transfers to Amazon S3.</p>
diff --git a/clients/client-s3/src/commands/PutBucketAclCommand.ts b/clients/client-s3/src/commands/PutBucketAclCommand.ts
index b1963d325ae6..e1d95b2bfaa5 100644
--- a/clients/client-s3/src/commands/PutBucketAclCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketAclCommand.ts
@@ -30,7 +30,7 @@ export interface PutBucketAclCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the permissions on an existing bucket using access control lists (ACL). For more
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. To set the ACL of a
diff --git a/clients/client-s3/src/commands/PutBucketAnalyticsConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketAnalyticsConfigurationCommand.ts
index e23dd31cc275..6cf32096b131 100644
--- a/clients/client-s3/src/commands/PutBucketAnalyticsConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketAnalyticsConfigurationCommand.ts
@@ -32,7 +32,7 @@ export interface PutBucketAnalyticsConfigurationCommandOutput extends __Metadata
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets an analytics configuration for the bucket (specified by the analytics configuration
  *          ID). You can have up to 1,000 analytics configurations per bucket.</p>
diff --git a/clients/client-s3/src/commands/PutBucketCorsCommand.ts b/clients/client-s3/src/commands/PutBucketCorsCommand.ts
index 55c4c5d33fe9..7576aaaa7e33 100644
--- a/clients/client-s3/src/commands/PutBucketCorsCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketCorsCommand.ts
@@ -30,7 +30,7 @@ export interface PutBucketCorsCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists,
  *          Amazon S3 replaces it.</p>
diff --git a/clients/client-s3/src/commands/PutBucketEncryptionCommand.ts b/clients/client-s3/src/commands/PutBucketEncryptionCommand.ts
index 4d08df19335f..a9fbbbb3c38a 100644
--- a/clients/client-s3/src/commands/PutBucketEncryptionCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketEncryptionCommand.ts
@@ -29,8 +29,8 @@ export interface PutBucketEncryptionCommandInput extends PutBucketEncryptionRequ
 export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {}
 
 /**
- * <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>
@@ -48,30 +48,35 @@ export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {}
  *                   </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 for the lifetime of the bucket.
@@ -87,19 +92,21 @@ export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {}
  *                         <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>
@@ -107,17 +114,25 @@ export interface PutBucketEncryptionCommandOutput extends __MetadataBearer {}
  *                <ul>
  *                   <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>
+ *                         <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>
  *                   </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>
diff --git a/clients/client-s3/src/commands/PutBucketIntelligentTieringConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketIntelligentTieringConfigurationCommand.ts
index 913e67cdec21..7974bfe5c7b3 100644
--- a/clients/client-s3/src/commands/PutBucketIntelligentTieringConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketIntelligentTieringConfigurationCommand.ts
@@ -33,7 +33,7 @@ export interface PutBucketIntelligentTieringConfigurationCommandOutput extends _
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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>
diff --git a/clients/client-s3/src/commands/PutBucketInventoryConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketInventoryConfigurationCommand.ts
index e6c197c0bebe..977786c499a7 100644
--- a/clients/client-s3/src/commands/PutBucketInventoryConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketInventoryConfigurationCommand.ts
@@ -35,7 +35,7 @@ export interface PutBucketInventoryConfigurationCommandOutput extends __Metadata
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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
diff --git a/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts
index 9dd8deb0a1dc..7a5d1a98c227 100644
--- a/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts
@@ -35,26 +35,37 @@ export interface PutBucketLifecycleConfigurationCommandOutput
     __MetadataBearer {}
 
 /**
- * <note>
- *             <p>This operation is not supported by directory buckets.</p>
- *          </note>
- *          <p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle
+ * <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>
  *          <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 the related API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>.</p>
+ *                   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>
+ *                </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>
@@ -72,59 +83,87 @@ export interface PutBucketLifecycleConfigurationCommandOutput
  *                      Management</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html">Lifecycle Configuration
  *                      Elements</a>.</p>
  *             </dd>
- *             <dt>Permissions</dt>
  *             <dd>
- *                <p>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
- *                   get 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>
- *                         <code>s3:DeleteObject</code>
- *                      </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>
+ *                               <code>s3:DeleteObject</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>s3:DeleteObjectVersion</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <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>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                </ul>
+ *                <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>
+ *                      <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>
+ *                            </code>. Virtual-hosted-style requests aren't supported.
+ * For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
+ *     <i>Amazon S3 User Guide</i>.</p>
+ *                      </note>
  *                   </li>
+ *                </ul>
+ *             </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>
+ *                <ul>
  *                   <li>
  *                      <p>
- *                         <code>s3:DeleteObjectVersion</code>
+ *                         <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html">GetBucketLifecycleConfiguration</a>
  *                      </p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <code>s3:PutLifecycleConfiguration</code>
+ *                         <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html">DeleteBucketLifecycle</a>
  *                      </p>
  *                   </li>
  *                </ul>
- *                <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>
  *             </dd>
  *          </dl>
- *          <p>The following operations are related to
- *          <code>PutBucketLifecycleConfiguration</code>:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html">Examples of
- *                   Lifecycle Configuration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html">GetBucketLifecycleConfiguration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html">DeleteBucketLifecycle</a>
- *                </p>
- *             </li>
- *          </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
diff --git a/clients/client-s3/src/commands/PutBucketLoggingCommand.ts b/clients/client-s3/src/commands/PutBucketLoggingCommand.ts
index 6c825b4adaa8..e58d8d87528f 100644
--- a/clients/client-s3/src/commands/PutBucketLoggingCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketLoggingCommand.ts
@@ -30,7 +30,7 @@ export interface PutBucketLoggingCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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
diff --git a/clients/client-s3/src/commands/PutBucketMetricsConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketMetricsConfigurationCommand.ts
index 13264d52868d..95a70d2f579a 100644
--- a/clients/client-s3/src/commands/PutBucketMetricsConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketMetricsConfigurationCommand.ts
@@ -32,7 +32,7 @@ export interface PutBucketMetricsConfigurationCommandOutput extends __MetadataBe
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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
diff --git a/clients/client-s3/src/commands/PutBucketNotificationConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketNotificationConfigurationCommand.ts
index 8331cd01472e..6d8d0c374e02 100644
--- a/clients/client-s3/src/commands/PutBucketNotificationConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketNotificationConfigurationCommand.ts
@@ -32,7 +32,7 @@ export interface PutBucketNotificationConfigurationCommandOutput extends __Metad
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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
diff --git a/clients/client-s3/src/commands/PutBucketOwnershipControlsCommand.ts b/clients/client-s3/src/commands/PutBucketOwnershipControlsCommand.ts
index 65fec824b489..91e416224f94 100644
--- a/clients/client-s3/src/commands/PutBucketOwnershipControlsCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketOwnershipControlsCommand.ts
@@ -30,7 +30,7 @@ export interface PutBucketOwnershipControlsCommandOutput extends __MetadataBeare
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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
diff --git a/clients/client-s3/src/commands/PutBucketPolicyCommand.ts b/clients/client-s3/src/commands/PutBucketPolicyCommand.ts
index ddf473bb2ff0..6c134c1d7d65 100644
--- a/clients/client-s3/src/commands/PutBucketPolicyCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketPolicyCommand.ts
@@ -40,42 +40,51 @@ export interface PutBucketPolicyCommandOutput extends __MetadataBearer {}
  *          <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>
+ *                         <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>
  *                   </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>
diff --git a/clients/client-s3/src/commands/PutBucketReplicationCommand.ts b/clients/client-s3/src/commands/PutBucketReplicationCommand.ts
index f5023f652783..44433ae0b8ff 100644
--- a/clients/client-s3/src/commands/PutBucketReplicationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketReplicationCommand.ts
@@ -30,16 +30,15 @@ export interface PutBucketReplicationCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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">
+ *          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
diff --git a/clients/client-s3/src/commands/PutBucketRequestPaymentCommand.ts b/clients/client-s3/src/commands/PutBucketRequestPaymentCommand.ts
index 40b02d7774fe..58bb078aa5cb 100644
--- a/clients/client-s3/src/commands/PutBucketRequestPaymentCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketRequestPaymentCommand.ts
@@ -30,7 +30,7 @@ export interface PutBucketRequestPaymentCommandOutput extends __MetadataBearer {
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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)
diff --git a/clients/client-s3/src/commands/PutBucketTaggingCommand.ts b/clients/client-s3/src/commands/PutBucketTaggingCommand.ts
index 94a3a4d44075..41f1ed96767d 100644
--- a/clients/client-s3/src/commands/PutBucketTaggingCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketTaggingCommand.ts
@@ -30,7 +30,7 @@ export interface PutBucketTaggingCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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,
diff --git a/clients/client-s3/src/commands/PutBucketVersioningCommand.ts b/clients/client-s3/src/commands/PutBucketVersioningCommand.ts
index 34f8d2734a3c..418ed87f9838 100644
--- a/clients/client-s3/src/commands/PutBucketVersioningCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketVersioningCommand.ts
@@ -30,16 +30,13 @@ export interface PutBucketVersioningCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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. 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>
+ *             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>
diff --git a/clients/client-s3/src/commands/PutBucketWebsiteCommand.ts b/clients/client-s3/src/commands/PutBucketWebsiteCommand.ts
index 6f2a528dfee8..a211b6becdc1 100644
--- a/clients/client-s3/src/commands/PutBucketWebsiteCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketWebsiteCommand.ts
@@ -30,7 +30,7 @@ export interface PutBucketWebsiteCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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
diff --git a/clients/client-s3/src/commands/PutObjectAclCommand.ts b/clients/client-s3/src/commands/PutObjectAclCommand.ts
index 4724ddaa77c3..3af046afa4dc 100644
--- a/clients/client-s3/src/commands/PutObjectAclCommand.ts
+++ b/clients/client-s3/src/commands/PutObjectAclCommand.ts
@@ -31,7 +31,7 @@ export interface PutObjectAclCommandOutput extends PutObjectAclOutput, __Metadat
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Uses the <code>acl</code> subresource to set the access control list (ACL) permissions
  *          for a new or existing object in an S3 bucket. You must have the <code>WRITE_ACP</code>
diff --git a/clients/client-s3/src/commands/PutObjectCommand.ts b/clients/client-s3/src/commands/PutObjectCommand.ts
index a818ed1a0cb3..041a22c6e708 100644
--- a/clients/client-s3/src/commands/PutObjectCommand.ts
+++ b/clients/client-s3/src/commands/PutObjectCommand.ts
@@ -43,46 +43,49 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  *          <note>
  *             <ul>
  *                <li>
- *                   <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the
- *                entire object to the bucket. You cannot use <code>PutObject</code> to only update a
- *                single piece of metadata for an existing object. You must put the entire object with
- *                updated metadata if you want to update some values.</p>
+ *                   <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added
+ *                   the entire object to the bucket. You cannot use <code>PutObject</code> to only
+ *                   update a single piece of metadata for an existing object. You must put the entire
+ *                   object with updated metadata if you want to update some values.</p>
  *                </li>
  *                <li>
- *                   <p>If your bucket uses the bucket owner enforced setting for Object Ownership, ACLs are disabled and no longer affect permissions. All
- *                   objects written to the bucket by any account will be owned by the bucket owner.</p>
+ *                   <p>If your bucket uses the bucket owner enforced setting for Object Ownership,
+ *                   ACLs are disabled and no longer affect permissions. All objects written to the
+ *                   bucket by any account will be owned by the bucket owner.</p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets</b> -
+ *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
  *             </ul>
  *          </note>
  *          <p>Amazon S3 is a distributed system. If it receives multiple write requests for the same object
- *          simultaneously, it overwrites all but the last object written. However, Amazon S3 provides features that can modify this behavior:</p>
+ *          simultaneously, it overwrites all but the last object written. However, Amazon S3 provides
+ *          features that can modify this behavior:</p>
  *          <ul>
  *             <li>
  *                <p>
  *                   <b>S3 Object Lock</b> - To prevent objects from
- *             being deleted or overwritten, you can use <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html">Amazon S3 Object
- *                Lock</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                being deleted or overwritten, you can use <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html">Amazon S3 Object
+ *                   Lock</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                <note>
  *                   <p>This functionality is not supported for directory buckets.</p>
  *                </note>
  *             </li>
  *             <li>
  *                <p>
- *                   <b>S3 Versioning</b> - When you enable
- *             versioning for a bucket, if Amazon S3 receives multiple write requests for the same object
- *             simultaneously, it stores all versions of the objects. For each write request that is made to the same object, Amazon S3 automatically generates a unique version ID
- *             of that object being stored in Amazon S3.
- *            You can retrieve, replace, or delete any version of the object. For more information about versioning, see
- *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding Objects to
- *                Versioning-Enabled Buckets</a> in the <i>Amazon S3
- *                   User Guide</i>. For information about returning the versioning state
- *             of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
+ *                   <b>S3 Versioning</b> - When you enable versioning
+ *                for a bucket, if Amazon S3 receives multiple write requests for the same object
+ *                simultaneously, it stores all versions of the objects. For each write request that is
+ *                made to the same object, Amazon S3 automatically generates a unique version ID of that
+ *                object being stored in Amazon S3. You can retrieve, replace, or delete any version of the
+ *                object. For more information about versioning, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding
+ *                   Objects to Versioning-Enabled Buckets</a> in the <i>Amazon S3 User
+ *                   Guide</i>. For information about returning the versioning state of a
+ *                bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
  *                <note>
  *                   <p>This functionality is not supported for directory buckets.</p>
  *                </note>
@@ -94,28 +97,34 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - The following permissions are required in your policies when your
- *                         <code>PutObject</code> request includes specific headers.</p>
+ *                         <b>General purpose bucket permissions</b> - The
+ *                         following permissions are required in your policies when your
+ *                            <code>PutObject</code> request includes specific headers.</p>
  *                      <ul>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:PutObject</code>
- *                               </b> - To successfully complete the <code>PutObject</code> request, you must always have the <code>s3:PutObject</code> permission on a bucket to add an object
- *                                  to it.</p>
+ *                               </b> -
+ *                               To successfully complete the <code>PutObject</code> request, you must
+ *                               always have the <code>s3:PutObject</code> permission on a bucket to
+ *                               add an object to it.</p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:PutObjectAcl</code>
- *                               </b> - To successfully change the objects ACL of your <code>PutObject</code> request, you must have the <code>s3:PutObjectAcl</code>.</p>
+ *                               </b> - To successfully change the objects ACL of your
+ *                                  <code>PutObject</code> request, you must have the
+ *                                  <code>s3:PutObjectAcl</code>.</p>
  *                         </li>
  *                         <li>
  *                            <p>
  *                               <b>
  *                                  <code>s3:PutObjectTagging</code>
- *                               </b> - To successfully set the tag-set with your <code>PutObject</code> request, you
- *                                  must have the <code>s3:PutObjectTagging</code>.</p>
+ *                               </b> - To successfully set the tag-set with your
+ *                                  <code>PutObject</code> request, you must have the
+ *                                  <code>s3:PutObjectTagging</code>.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
@@ -127,9 +136,10 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  * Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
  *                            <code>CreateSession</code>
  *                         </a>.</p>
- *                      <p>If the object is encrypted with
- *                         SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
+ *                      <p>If the object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -138,15 +148,18 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - To ensure that data is not corrupted traversing the network, use the
- *                     <code>Content-MD5</code> header. When you use this header, Amazon S3 checks the object
- *                     against the provided MD5 value and, if they do not match, Amazon S3 returns an error. Alternatively, when the object's ETag is its MD5 digest,
- *                     you can calculate the MD5 while putting the object to Amazon S3 and compare the returned ETag to
- *                     the calculated MD5 value.</p>
+ *                         <b>General purpose bucket</b> - To ensure that
+ *                         data is not corrupted traversing the network, use the
+ *                            <code>Content-MD5</code> header. When you use this header, Amazon S3 checks
+ *                         the object against the provided MD5 value and, if they do not match, Amazon S3
+ *                         returns an error. Alternatively, when the object's ETag is its MD5 digest,
+ *                         you can calculate the MD5 while putting the object to Amazon S3 and compare the
+ *                         returned ETag to the calculated MD5 value.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket</b> - This functionality is not supported for directory buckets.</p>
+ *                         <b>Directory bucket</b> -
+ *                         This functionality is not supported for directory buckets.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -199,6 +212,7 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  *   GrantReadACP: "STRING_VALUE",
  *   GrantWriteACP: "STRING_VALUE",
  *   Key: "STRING_VALUE", // required
+ *   WriteOffsetBytes: Number("long"),
  *   Metadata: { // Metadata
  *     "<keys>": "STRING_VALUE",
  *   },
@@ -234,6 +248,7 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  * //   SSEKMSKeyId: "STRING_VALUE",
  * //   SSEKMSEncryptionContext: "STRING_VALUE",
  * //   BucketKeyEnabled: true || false,
+ * //   Size: Number("long"),
  * //   RequestCharged: "requester",
  * // };
  *
@@ -245,6 +260,39 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  * @see {@link PutObjectCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link EncryptionTypeMismatch} (client fault)
+ *  <p>
+ *          The existing object was created with a different encryption type.
+ *          Subsequent write requests must include the appropriate encryption
+ *          parameters in the request or while creating the session.
+ *       </p>
+ *
+ * @throws {@link InvalidRequest} (client fault)
+ *  <p>You may receive this error in multiple cases. Depending on the reason for the error, you may receive one of the messages below:</p>
+ *          <ul>
+ *             <li>
+ *                <p>Cannot specify both a write offset value and user-defined object metadata for existing objects.</p>
+ *             </li>
+ *             <li>
+ *                <p>Checksum Type mismatch occurred, expected checksum Type: sha1, actual checksum Type: crc32c.</p>
+ *             </li>
+ *             <li>
+ *                <p>Request body cannot be empty when 'write offset' is specified.</p>
+ *             </li>
+ *          </ul>
+ *
+ * @throws {@link InvalidWriteOffset} (client fault)
+ *  <p>
+ *          The write offset value that you specified does not match the current object size.
+ *       </p>
+ *
+ * @throws {@link TooManyParts} (client fault)
+ *  <p>
+ *          You have attempted to add more parts than the maximum of 10000
+ *          that are allowed for this object. You can use the CopyObject operation
+ *          to copy this object to another and then add more data to the newly copied object.
+ *       </p>
+ *
  * @throws {@link S3ServiceException}
  * <p>Base exception class for all service exceptions from S3 service.</p>
  *
diff --git a/clients/client-s3/src/commands/PutObjectLegalHoldCommand.ts b/clients/client-s3/src/commands/PutObjectLegalHoldCommand.ts
index 278ef5292dc7..2dcebf439f04 100644
--- a/clients/client-s3/src/commands/PutObjectLegalHoldCommand.ts
+++ b/clients/client-s3/src/commands/PutObjectLegalHoldCommand.ts
@@ -31,7 +31,7 @@ export interface PutObjectLegalHoldCommandOutput extends PutObjectLegalHoldOutpu
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Applies a legal hold configuration to the specified object. For more information, see
  *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Locking
diff --git a/clients/client-s3/src/commands/PutObjectLockConfigurationCommand.ts b/clients/client-s3/src/commands/PutObjectLockConfigurationCommand.ts
index 8b99cda53a4c..df5f27ceaeb2 100644
--- a/clients/client-s3/src/commands/PutObjectLockConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutObjectLockConfigurationCommand.ts
@@ -31,7 +31,7 @@ export interface PutObjectLockConfigurationCommandOutput extends PutObjectLockCo
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Places an Object Lock configuration on the specified bucket. The rule specified in the
  *          Object Lock configuration will be applied by default to every new object placed in the
@@ -48,8 +48,8 @@ export interface PutObjectLockConfigurationCommandOutput extends PutObjectLockCo
  *                      <code>Days</code> and <code>Years</code> at the same time.</p>
  *                </li>
  *                <li>
- *                   <p>You can enable Object Lock for new or existing buckets. For more
- *                   information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-configure.html">Configuring Object
+ *                   <p>You can enable Object Lock for new or existing buckets. For more information,
+ *                   see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-configure.html">Configuring Object
  *                      Lock</a>.</p>
  *                </li>
  *             </ul>
diff --git a/clients/client-s3/src/commands/PutObjectRetentionCommand.ts b/clients/client-s3/src/commands/PutObjectRetentionCommand.ts
index 587834590e1a..8e3aabf0a3cf 100644
--- a/clients/client-s3/src/commands/PutObjectRetentionCommand.ts
+++ b/clients/client-s3/src/commands/PutObjectRetentionCommand.ts
@@ -31,7 +31,7 @@ export interface PutObjectRetentionCommandOutput extends PutObjectRetentionOutpu
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Places an Object Retention configuration on an object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Locking Objects</a>.
  *          Users or accounts require the <code>s3:PutObjectRetention</code> permission in order to
diff --git a/clients/client-s3/src/commands/PutObjectTaggingCommand.ts b/clients/client-s3/src/commands/PutObjectTaggingCommand.ts
index f6f48c3d17c8..cbaf8768b2c3 100644
--- a/clients/client-s3/src/commands/PutObjectTaggingCommand.ts
+++ b/clients/client-s3/src/commands/PutObjectTaggingCommand.ts
@@ -31,7 +31,7 @@ export interface PutObjectTaggingCommandOutput extends PutObjectTaggingOutput, _
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the supplied tag-set to an object that already exists in a bucket. A tag is a
  *          key-value pair. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html">Object Tagging</a>.</p>
diff --git a/clients/client-s3/src/commands/PutPublicAccessBlockCommand.ts b/clients/client-s3/src/commands/PutPublicAccessBlockCommand.ts
index b3ab5faf036f..ba5e98693e36 100644
--- a/clients/client-s3/src/commands/PutPublicAccessBlockCommand.ts
+++ b/clients/client-s3/src/commands/PutPublicAccessBlockCommand.ts
@@ -30,7 +30,7 @@ export interface PutPublicAccessBlockCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Creates or modifies the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket.
  *          To use this operation, you must have the <code>s3:PutBucketPublicAccessBlock</code>
diff --git a/clients/client-s3/src/commands/RestoreObjectCommand.ts b/clients/client-s3/src/commands/RestoreObjectCommand.ts
index 11eaff639df1..3ee9ffc16793 100644
--- a/clients/client-s3/src/commands/RestoreObjectCommand.ts
+++ b/clients/client-s3/src/commands/RestoreObjectCommand.ts
@@ -31,7 +31,7 @@ export interface RestoreObjectCommandOutput extends RestoreObjectOutput, __Metad
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Restores an archived copy of an object back into Amazon S3</p>
  *          <p>This functionality is not supported for Amazon S3 on Outposts.</p>
diff --git a/clients/client-s3/src/commands/SelectObjectContentCommand.ts b/clients/client-s3/src/commands/SelectObjectContentCommand.ts
index af481e548ff8..6a0c3db78a68 100644
--- a/clients/client-s3/src/commands/SelectObjectContentCommand.ts
+++ b/clients/client-s3/src/commands/SelectObjectContentCommand.ts
@@ -36,7 +36,7 @@ export interface SelectObjectContentCommandOutput extends SelectObjectContentOut
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>This action filters the contents of an Amazon S3 object based on a simple structured query
  *          language (SQL) statement. In the request, along with the SQL expression, you must also
diff --git a/clients/client-s3/src/commands/UploadPartCommand.ts b/clients/client-s3/src/commands/UploadPartCommand.ts
index a842c4deb449..bdcbde264141 100644
--- a/clients/client-s3/src/commands/UploadPartCommand.ts
+++ b/clients/client-s3/src/commands/UploadPartCommand.ts
@@ -41,10 +41,9 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
 /**
  * <p>Uploads a part in a multipart upload.</p>
  *          <note>
- *             <p>In this operation, you provide new data as a part of an object in your request. However, you have an option
- *             to specify your existing Amazon S3 object as a data source for the part you are uploading. To
- *             upload a part from an existing object, you use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> operation.
- *          </p>
+ *             <p>In this operation, you provide new data as a part of an object in your request.
+ *             However, you have an option to specify your existing Amazon S3 object as a data source for
+ *             the part you are uploading. To upload a part from an existing object, you use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> operation. </p>
  *          </note>
  *          <p>You must initiate a multipart upload (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>)
  *          before you can upload any part. In response to your initiate request, Amazon S3 returns an
@@ -56,17 +55,17 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  *          <p>For information about maximum and minimum part sizes and other multipart upload
  *          specifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
- *             <p>After you initiate multipart upload and upload
- *          one or more parts, you must either complete or abort multipart upload in order to stop
- *          getting charged for storage of the uploaded parts. Only after you either complete or abort
- *          multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts
- *          storage.</p>
+ *             <p>After you initiate multipart upload and upload one or more parts, you must either
+ *             complete or abort multipart upload in order to stop getting charged for storage of the
+ *             uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up
+ *             the parts storage and stops charging you for the parts storage.</p>
  *          </note>
  *          <p>For more information on multipart uploads, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in the
- *          <i>Amazon S3 User Guide </i>.</p>
+ *             <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 Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
@@ -100,20 +99,24 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  * Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
  *                            <code>CreateSession</code>
  *                         </a>.</p>
- *                      <p>If the object is encrypted with
- *                         SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
+ *                      <p>If the object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
  *             <dt>Data integrity</dt>
  *             <dd>
  *                <p>
- *                   <b>General purpose bucket</b> - To ensure that data is not corrupted traversing the network, specify the
- *                      <code>Content-MD5</code> header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error. If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the
- *                         <code>x-amz-content-sha256</code> header as a checksum instead of
- *                         <code>Content-MD5</code>. For more information see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html">Authenticating
- *                            Requests: Using the Authorization Header (Amazon Web Services Signature Version 4)</a>. </p>
+ *                   <b>General purpose bucket</b> - To ensure that data
+ *                   is not corrupted traversing the network, specify the <code>Content-MD5</code>
+ *                   header in the upload part request. Amazon S3 checks the part data against the provided
+ *                   MD5 value. If they do not match, Amazon S3 returns an error. If the upload request is
+ *                   signed with Signature Version 4, then Amazon Web Services S3 uses the
+ *                      <code>x-amz-content-sha256</code> header as a checksum instead of
+ *                      <code>Content-MD5</code>. For more information see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html">Authenticating Requests: Using the Authorization Header (Amazon Web Services Signature
+ *                      Version 4)</a>. </p>
  *                <note>
  *                   <p>
  *                      <b>Directory buckets</b> - MD5 is not supported by directory buckets. You can use checksum algorithms to check object integrity.</p>
@@ -124,23 +127,28 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it
- *                         writes it to disks in its data centers and decrypts it when you access it. You have
- *                         mutually exclusive options to protect data using server-side encryption in Amazon S3, depending
- *                         on how you choose to manage the encryption keys. Specifically, the encryption key options
- *                         are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and Customer-Provided Keys
- *                         (SSE-C). Amazon S3 encrypts data with server-side encryption using Amazon S3 managed keys (SSE-S3) by
- *                         default. You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption
- *                         with other key options. The option you use depends on whether you want to use KMS keys
- *                         (SSE-KMS) or provide your own encryption key (SSE-C).</p>
- *                      <p>Server-side encryption is supported by the S3 Multipart Upload operations. Unless you are
- *                         using a customer-provided encryption key (SSE-C), you don't need to specify the encryption
- *                         parameters in each UploadPart request. Instead, you only need to specify the server-side
- *                         encryption parameters in the initial Initiate Multipart request. For more information, see
- *                         <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.</p>
- *                      <p>If you request server-side encryption using a customer-provided encryption key (SSE-C)
- *                         in your initiate multipart upload request, you must provide identical encryption
- *                         information in each part upload using the following request headers.</p>
+ *                         <b>General purpose bucket</b> - Server-side
+ *                         encryption is for data encryption at rest. Amazon S3 encrypts your data as it
+ *                         writes it to disks in its data centers and decrypts it when you access it.
+ *                         You have mutually exclusive options to protect data using server-side
+ *                         encryption in Amazon S3, depending on how you choose to manage the encryption
+ *                         keys. Specifically, the encryption key options are Amazon S3 managed keys
+ *                         (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and Customer-Provided Keys (SSE-C).
+ *                         Amazon S3 encrypts data with server-side encryption using Amazon S3 managed keys
+ *                         (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt data at rest
+ *                         using server-side encryption with other key options. The option you use
+ *                         depends on whether you want to use KMS keys (SSE-KMS) or provide your own
+ *                         encryption key (SSE-C).</p>
+ *                      <p>Server-side encryption is supported by the S3 Multipart Upload
+ *                         operations. Unless you are using a customer-provided encryption key (SSE-C),
+ *                         you don't need to specify the encryption parameters in each UploadPart
+ *                         request. Instead, you only need to specify the server-side encryption
+ *                         parameters in the initial Initiate Multipart request. For more information,
+ *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.</p>
+ *                      <p>If you request server-side encryption using a customer-provided
+ *                         encryption key (SSE-C) in your initiate multipart upload request, you must
+ *                         provide identical encryption information in each part upload using the
+ *                         following request headers.</p>
  *                      <ul>
  *                         <li>
  *                            <p>x-amz-server-side-encryption-customer-algorithm</p>
@@ -152,13 +160,14 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  *                            <p>x-amz-server-side-encryption-customer-key-MD5</p>
  *                         </li>
  *                      </ul>
- *                      <p>
- *                         For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using Server-Side
- *                            Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                      <p> For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using
+ *                            Server-Side Encryption</a> in the
+ *                            <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>).</p>
+ *                         <b>Directory buckets </b> -
+ *                         For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>).</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -170,7 +179,9 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  *                      </p>
  *                      <ul>
  *                         <li>
- *                            <p>Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.</p>
+ *                            <p>Description: The specified multipart upload does not exist. The
+ *                               upload ID might be invalid, or the multipart upload might have been
+ *                               aborted or completed.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 404 Not Found </p>
diff --git a/clients/client-s3/src/commands/UploadPartCopyCommand.ts b/clients/client-s3/src/commands/UploadPartCopyCommand.ts
index a330ba4d28b9..73e8739e5beb 100644
--- a/clients/client-s3/src/commands/UploadPartCopyCommand.ts
+++ b/clients/client-s3/src/commands/UploadPartCopyCommand.ts
@@ -36,43 +36,50 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
 
 /**
  * <p>Uploads a part by copying data from an existing object as data source. To specify the
- *          data source, you add the request header <code>x-amz-copy-source</code> in your request. To specify
- *          a byte range, you add the request header <code>x-amz-copy-source-range</code> in your
- *          request. </p>
+ *          data source, you add the request header <code>x-amz-copy-source</code> in your request. To
+ *          specify a byte range, you add the request header <code>x-amz-copy-source-range</code> in
+ *          your request. </p>
  *          <p>For information about maximum and minimum part sizes and other multipart upload
  *          specifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>. </p>
  *          <note>
- *             <p>Instead of copying data from an existing object as part data, you might use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>
- *             action to upload new data as a part of an object in your request.</p>
+ *             <p>Instead of copying data from an existing object as part data, you might use the
+ *                <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a> action to upload new data as a part of an object in your
+ *             request.</p>
  *          </note>
  *          <p>You must initiate a multipart upload before you can upload any part. In response to your
  *          initiate request, Amazon S3 returns the upload ID, a unique identifier that you must include in
  *          your upload part request.</p>
- *          <p>For conceptual information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading
- *          Objects Using Multipart Upload</a> in the
- *          <i>Amazon S3 User Guide</i>. For information about copying objects using a single atomic action vs. a multipart
- *          upload, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html">Operations on Objects</a> in
- *          the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>For conceptual information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading Objects Using Multipart
+ *             Upload</a> in the <i>Amazon S3 User Guide</i>. For information about
+ *          copying objects using a single atomic action vs. a multipart upload, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html">Operations on
+ *             Objects</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 Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
  *          <dl>
  *             <dt>Authentication and authorization</dt>
  *             <dd>
- *                <p>All <code>UploadPartCopy</code> requests must be authenticated and signed by using IAM credentials (access key ID and secret access key for the IAM identities). All headers with the <code>x-amz-</code> prefix, including
- *                         <code>x-amz-copy-source</code>, must be signed. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
+ *                <p>All <code>UploadPartCopy</code> requests must be authenticated and signed by
+ *                   using IAM credentials (access key ID and secret access key for the IAM
+ *                   identities). All headers with the <code>x-amz-</code> prefix, including
+ *                      <code>x-amz-copy-source</code>, must be signed. For more information, see
+ *                      <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
  *                <p>
- *                   <b>Directory buckets</b> - You must use IAM credentials to authenticate and authorize your access to the <code>UploadPartCopy</code> API operation, instead of using the
- *                   temporary security credentials through the <code>CreateSession</code> API operation.</p>
- *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>
+ *                   <b>Directory buckets</b> - You must use IAM
+ *                   credentials to authenticate and authorize your access to the
+ *                      <code>UploadPartCopy</code> API operation, instead of using the temporary
+ *                   security credentials through the <code>CreateSession</code> API operation.</p>
+ *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your
+ *                   behalf.</p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
- *                <p>You must have <code>READ</code> access to the source object and <code>WRITE</code>
- *                   access to the destination bucket.</p>
+ *                <p>You must have <code>READ</code> access to the source object and
+ *                      <code>WRITE</code> access to the destination bucket.</p>
  *                <ul>
  *                   <li>
  *                      <p>
@@ -118,8 +125,9 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
  *                   <li>
  *                      <p>
  *                         <b>Directory bucket permissions</b> -
- *                         You must have permissions in a bucket policy or an IAM identity-based policy based on the source and destination
- *                         bucket types in an <code>UploadPartCopy</code> operation.</p>
+ *                         You must have permissions in a bucket policy or an IAM identity-based policy based on the
+ *                         source and destination bucket types in an <code>UploadPartCopy</code>
+ *                         operation.</p>
  *                      <ul>
  *                         <li>
  *                            <p>If the source object that you want to copy is in a
@@ -134,19 +142,21 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
  *                         </li>
  *                         <li>
  *                            <p>If the copy destination is a directory bucket, you must have the
- *                               <b>
+ *                                  <b>
  *                                  <code>s3express:CreateSession</code>
  *                               </b> permission in the
- *                               <code>Action</code> element of a policy to write the object
- *                               to the destination. The <code>s3express:SessionMode</code> condition
- *                               key cannot be set to <code>ReadOnly</code> on the copy destination. </p>
+ *                                  <code>Action</code> element of a policy to write the object to the
+ *                               destination. The <code>s3express:SessionMode</code> condition key
+ *                               cannot be set to <code>ReadOnly</code> on the copy destination.
+ *                            </p>
  *                         </li>
  *                      </ul>
- *                      <p>If the object is encrypted with
- *                         SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
- *                      <p>For example policies, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the
- *                         <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>If the object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
+ *                      <p>For example policies, 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> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for
+ *                            S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -156,18 +166,22 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
  *                   <li>
  *                      <p>
  *                         <b>General purpose buckets </b> -
- *
- *                      For information about using server-side encryption with customer-provided
- *                            encryption keys with the <code>UploadPartCopy</code> operation, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>.
- *                      </p>
+ *                          For information about using
+ *                         server-side encryption with customer-provided encryption keys with the
+ *                            <code>UploadPartCopy</code> operation, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a> and
+ *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>. </p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). For more
+ *                         <b>Directory buckets </b> -
+ *                         For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). For more
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                      <note>
- *                         <p>For directory buckets, when you perform a <code>CreateMultipartUpload</code> operation and an <code>UploadPartCopy</code> operation,
- *                         the request headers you provide in the <code>CreateMultipartUpload</code> request must match the default encryption configuration of the destination bucket. </p>
+ *                         <p>For directory buckets, when you perform a
+ *                               <code>CreateMultipartUpload</code> operation and an
+ *                               <code>UploadPartCopy</code> operation, the request headers you provide
+ *                            in the <code>CreateMultipartUpload</code> request must match the default
+ *                            encryption configuration of the destination bucket. </p>
  *                      </note>
  *                      <p>S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
  * to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>
@@ -183,8 +197,8 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
  *                      <ul>
  *                         <li>
  *                            <p>Description: The specified multipart upload does not exist. The
- *                                  upload ID might be invalid, or the multipart upload might have been
- *                                  aborted or completed.</p>
+ *                               upload ID might be invalid, or the multipart upload might have been
+ *                               aborted or completed.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 404 Not Found</p>
@@ -197,7 +211,7 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
  *                      <ul>
  *                         <li>
  *                            <p>Description: The specified copy source is not supported as a
- *                                     byte-range copy source.</p>
+ *                               byte-range copy source.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 400 Bad Request</p>
diff --git a/clients/client-s3/src/commands/WriteGetObjectResponseCommand.ts b/clients/client-s3/src/commands/WriteGetObjectResponseCommand.ts
index c6b3f82655c3..6fa861e8ef8b 100644
--- a/clients/client-s3/src/commands/WriteGetObjectResponseCommand.ts
+++ b/clients/client-s3/src/commands/WriteGetObjectResponseCommand.ts
@@ -32,7 +32,7 @@ export interface WriteGetObjectResponseCommandOutput extends __MetadataBearer {}
 
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Passes transformed objects to a <code>GetObject</code> operation when using Object Lambda access points. For
  *          information about Object Lambda access points, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/transforming-objects.html">Transforming objects with
diff --git a/clients/client-s3/src/models/models_0.ts b/clients/client-s3/src/models/models_0.ts
index ca889d5c94b1..034dde19601f 100644
--- a/clients/client-s3/src/models/models_0.ts
+++ b/clients/client-s3/src/models/models_0.ts
@@ -69,7 +69,8 @@ export interface AbortMultipartUploadRequest {
   /**
    * <p>The bucket name to which the upload was taking place. </p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -104,9 +105,9 @@ export interface AbortMultipartUploadRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -120,6 +121,18 @@ export interface AbortMultipartUploadRequest {
    * @public
    */
   ExpectedBucketOwner?: string | undefined;
+
+  /**
+   * <p>If present, this header aborts an in progress multipart upload only if it was initiated on the provided timestamp.
+   *          If the initiated timestamp of the multipart upload does not match the provided value, the operation returns a <code>412 Precondition Failed</code> error.
+   *          If the initiated timestamp matches or if the multipart upload doesn’t exist, the operation returns a <code>204 Success (No Content)</code> response.
+   *       </p>
+   *          <note>
+   *             <p>This functionality is only supported for directory buckets.</p>
+   *          </note>
+   * @public
+   */
+  IfMatchInitiatedTime?: Date | undefined;
 }
 
 /**
@@ -573,14 +586,20 @@ export interface CompletedPart {
    *             <ul>
    *                <li>
    *                   <p>
-   *                      <b>General purpose buckets</b> - In <code>CompleteMultipartUpload</code>, when a additional checksum (including <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or
-   *                <code>x-amz-checksum-sha256</code>) is applied to each part, the <code>PartNumber</code> must start at 1 and
-   *                the part numbers must be consecutive. Otherwise, Amazon S3 generates an HTTP <code>400 Bad Request</code> status code and an <code>InvalidPartOrder</code> error code.</p>
+   *                      <b>General purpose buckets</b> - In
+   *                      <code>CompleteMultipartUpload</code>, when a additional checksum (including
+   *                      <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>,
+   *                      <code>x-amz-checksum-sha1</code>, or <code>x-amz-checksum-sha256</code>) is
+   *                   applied to each part, the <code>PartNumber</code> must start at 1 and the part
+   *                   numbers must be consecutive. Otherwise, Amazon S3 generates an HTTP <code>400 Bad
+   *                      Request</code> status code and an <code>InvalidPartOrder</code> error
+   *                   code.</p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets</b> - In <code>CompleteMultipartUpload</code>, the <code>PartNumber</code> must start at 1 and
-   *                the part numbers must be consecutive.</p>
+   *                      <b>Directory buckets</b> - In
+   *                      <code>CompleteMultipartUpload</code>, the <code>PartNumber</code> must start at
+   *                   1 and the part numbers must be consecutive.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -610,7 +629,8 @@ export interface CompleteMultipartUploadRequest {
   /**
    * <p>Name of the bucket to which the multipart upload was initiated.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -687,9 +707,9 @@ export interface CompleteMultipartUploadRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -705,8 +725,11 @@ export interface CompleteMultipartUploadRequest {
   ExpectedBucketOwner?: string | undefined;
 
   /**
-   * <p>Uploads the object only if the object key name does not already exist in the bucket specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>
-   *          <p>If a conflicting operation occurs during the upload S3 returns a <code>409 ConditionalRequestConflict</code> response.  On a 409 failure you should re-initiate the multipart upload with <code>CreateMultipartUpload</code> and re-upload each part.</p>
+   * <p>Uploads the object only if the object key name does not already exist in the bucket
+   *          specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>
+   *          <p>If a conflicting operation occurs during the upload S3 returns a <code>409
+   *             ConditionalRequestConflict</code> response. On a 409 failure you should re-initiate the
+   *          multipart upload with <code>CreateMultipartUpload</code> and re-upload each part.</p>
    *          <p>Expects the '*' (asterisk) character.</p>
    *          <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>, or <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html">Conditional requests</a> in the <i>Amazon S3 User Guide</i>.</p>
    * @public
@@ -715,9 +738,9 @@ export interface CompleteMultipartUploadRequest {
 
   /**
    * <p>The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is
-   *          required only when the object was created using a checksum algorithm or if
-   *          your bucket policy requires the use of SSE-C. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html#ssec-require-condition-key">Protecting data
-   *             using SSE-C keys</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *          required only when the object was created using a checksum algorithm or if your bucket
+   *          policy requires the use of SSE-C. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html#ssec-require-condition-key">Protecting data using SSE-C keys</a> in the <i>Amazon S3 User
+   *          Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -839,8 +862,8 @@ export interface CopyObjectOutput {
   VersionId?: string | undefined;
 
   /**
-   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,
-   *             <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>
+   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for
+   *          example, <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>
    * @public
    */
   ServerSideEncryption?: ServerSideEncryption | undefined;
@@ -857,8 +880,8 @@ export interface CopyObjectOutput {
 
   /**
    * <p>If server-side encryption with a customer-provided encryption key was requested, the
-   *          response will include this header to provide the round-trip message integrity verification of
-   *          the customer-provided encryption key.</p>
+   *          response will include this header to provide the round-trip message integrity verification
+   *          of the customer-provided encryption key.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -1018,25 +1041,23 @@ export type TaggingDirective = (typeof TaggingDirective)[keyof typeof TaggingDir
 export interface CopyObjectRequest {
   /**
    * <p>The canned access control list (ACL) to apply to the object.</p>
-   *          <p>When you copy an object, the ACL metadata is not preserved and is set
-   *          to <code>private</code> by default. Only the owner has full access
-   *          control. To override the default ACL setting,
-   *          specify a new ACL when you generate a copy request. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using
-   *             ACLs</a>. </p>
+   *          <p>When you copy an object, the ACL metadata is not preserved and is set to
+   *             <code>private</code> by default. Only the owner has full access control. To override the
+   *          default ACL setting, specify a new ACL when you generate a copy request. For more
+   *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. </p>
    *          <p>If the destination bucket that you're copying objects to uses the bucket owner enforced
-   *          setting for S3 Object Ownership, ACLs are disabled and no longer affect
-   *          permissions. Buckets that use this setting only accept <code>PUT</code> requests
-   *          that don't specify an ACL or <code>PUT</code> requests that specify bucket owner
-   *          full control ACLs, such as the <code>bucket-owner-full-control</code> canned ACL
-   *          or an equivalent form of this ACL expressed in the XML format. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling
-   *          ownership of objects and disabling ACLs</a> in the
-   *          <i>Amazon S3 User Guide</i>.</p>
+   *          setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions.
+   *          Buckets that use this setting only accept <code>PUT</code> requests that don't specify an
+   *          ACL or <code>PUT</code> requests that specify bucket owner full control ACLs, such as the
+   *             <code>bucket-owner-full-control</code> canned ACL or an equivalent form of this ACL
+   *          expressed in the XML format. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of
+   *             objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <ul>
    *                <li>
-   *                   <p>If your destination bucket uses the bucket owner enforced setting for Object Ownership,
-   *                   all objects written to the bucket by any account will be owned by the bucket
-   *                   owner.</p>
+   *                   <p>If your destination bucket uses the bucket owner enforced setting for Object
+   *                   Ownership, all objects written to the bucket by any account will be owned by the
+   *                   bucket owner.</p>
    *                </li>
    *                <li>
    *                   <p>This functionality is not supported for directory buckets.</p>
@@ -1053,7 +1074,8 @@ export interface CopyObjectRequest {
   /**
    * <p>The name of the destination bucket.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -1083,10 +1105,13 @@ export interface CopyObjectRequest {
    * <p>Indicates the algorithm that you want Amazon S3 to use to create the checksum for the object. For more information, see
    *     <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html">Checking object integrity</a> in
    *     the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>When you copy an object, if the source object has a checksum, that checksum value will be copied to
-   *          the new object by default. If the <code>CopyObject</code> request does not include this <code>x-amz-checksum-algorithm</code> header, the checksum algorithm will be copied from the source object to the destination object (if it's present on the source object). You can optionally
-   *          specify a different checksum algorithm to use with the
-   *          <code>x-amz-checksum-algorithm</code> header. Unrecognized or unsupported values will respond with the HTTP status code <code>400 Bad Request</code>.</p>
+   *          <p>When you copy an object, if the source object has a checksum, that checksum value will
+   *          be copied to the new object by default. If the <code>CopyObject</code> request does not
+   *          include this <code>x-amz-checksum-algorithm</code> header, the checksum algorithm will be
+   *          copied from the source object to the destination object (if it's present on the source
+   *          object). You can optionally specify a different checksum algorithm to use with the
+   *             <code>x-amz-checksum-algorithm</code> header. Unrecognized or unsupported values will
+   *          respond with the HTTP status code <code>400 Bad Request</code>.</p>
    *          <note>
    *             <p>For directory buckets, when you use Amazon Web Services SDKs, <code>CRC32</code> is the default checksum algorithm that's used for performance.</p>
    *          </note>
@@ -1095,7 +1120,9 @@ export interface CopyObjectRequest {
   ChecksumAlgorithm?: ChecksumAlgorithm | undefined;
 
   /**
-   * <p>Specifies presentational information for the object. Indicates whether an object should be displayed in a web browser or downloaded as a file. It allows specifying the desired filename for the downloaded file.</p>
+   * <p>Specifies presentational information for the object. Indicates whether an object should
+   *          be displayed in a web browser or downloaded as a file. It allows specifying the desired
+   *          filename for the downloaded file.</p>
    * @public
    */
   ContentDisposition?: string | undefined;
@@ -1124,20 +1151,23 @@ export interface CopyObjectRequest {
   ContentType?: string | undefined;
 
   /**
-   * <p>Specifies the source object for the copy operation. The source object
-   *          can be up to 5 GB. If the source object is an object that was uploaded by using a multipart upload, the object copy will be a single part object after the source object is copied to the destination bucket.</p>
-   *          <p>You specify the value of the copy source in one of two
-   *          formats, depending on whether you want to access the source object through an <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-points.html">access point</a>:</p>
+   * <p>Specifies the source object for the copy operation. The source object can be up to 5 GB.
+   *          If the source object is an object that was uploaded by using a multipart upload, the object
+   *          copy will be a single part object after the source object is copied to the destination
+   *          bucket.</p>
+   *          <p>You specify the value of the copy source in one of two formats, depending on whether you
+   *          want to access the source object through an <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-points.html">access point</a>:</p>
    *          <ul>
    *             <li>
    *                <p>For objects not accessed through an access point, specify the name of the source bucket
    *                and the key of the source object, separated by a slash (/). For example, to copy the
    *                object <code>reports/january.pdf</code> from the general purpose bucket
-   *                <code>awsexamplebucket</code>, use <code>awsexamplebucket/reports/january.pdf</code>.
-   *                The value must be URL-encoded. To copy the
-   *                object <code>reports/january.pdf</code> from the directory bucket
-   *                <code>awsexamplebucket--use1-az5--x-s3</code>, use <code>awsexamplebucket--use1-az5--x-s3/reports/january.pdf</code>.
-   *                The value must be URL-encoded.</p>
+   *                   <code>awsexamplebucket</code>, use
+   *                   <code>awsexamplebucket/reports/january.pdf</code>. The value must be URL-encoded.
+   *                To copy the object <code>reports/january.pdf</code> from the directory bucket
+   *                   <code>awsexamplebucket--use1-az5--x-s3</code>, use
+   *                   <code>awsexamplebucket--use1-az5--x-s3/reports/january.pdf</code>. The value must
+   *                be URL-encoded.</p>
    *             </li>
    *             <li>
    *                <p>For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format <code>arn:aws:s3:<Region>:<account-id>:accesspoint/<access-point-name>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through access point <code>my-access-point</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf</code>. The value must be URL encoded.</p>
@@ -1154,24 +1184,25 @@ export interface CopyObjectRequest {
    *                <p>Alternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format <code>arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through outpost <code>my-outpost</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf</code>. The value must be URL-encoded.  </p>
    *             </li>
    *          </ul>
-   *          <p>If your source bucket versioning is enabled, the <code>x-amz-copy-source</code> header by default identifies the current
-   *          version of an object to copy. If the current version is a delete marker, Amazon S3
-   *          behaves as if the object was deleted. To copy a different version, use the
-   *          <code>versionId</code> query parameter. Specifically, append <code>?versionId=<version-id></code>
-   *          to the value (for example,
-   *          <code>awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>).
+   *          <p>If your source bucket versioning is enabled, the <code>x-amz-copy-source</code> header
+   *          by default identifies the current version of an object to copy. If the current version is a
+   *          delete marker, Amazon S3 behaves as if the object was deleted. To copy a different version, use
+   *          the <code>versionId</code> query parameter. Specifically, append
+   *             <code>?versionId=<version-id></code> to the value (for example,
+   *             <code>awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>).
    *          If you don't specify a version ID, Amazon S3 copies the latest version of the source
    *          object.</p>
-   *          <p>If you enable versioning on the destination bucket, Amazon S3 generates a unique version
-   *          ID for the copied object. This version ID is different from the version ID
-   *          of the source object. Amazon S3 returns the version ID of the copied object in the
-   *          <code>x-amz-version-id</code> response header in the response.</p>
-   *          <p>If you do not enable versioning or suspend it on the destination bucket, the version
-   *          ID that Amazon S3 generates in the
-   *          <code>x-amz-version-id</code> response header is always null.</p>
+   *          <p>If you enable versioning on the destination bucket, Amazon S3 generates a unique version ID
+   *          for the copied object. This version ID is different from the version ID of the source
+   *          object. Amazon S3 returns the version ID of the copied object in the
+   *             <code>x-amz-version-id</code> response header in the response.</p>
+   *          <p>If you do not enable versioning or suspend it on the destination bucket, the version ID
+   *          that Amazon S3 generates in the <code>x-amz-version-id</code> response header is always
+   *          null.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets.</p>
+   *                <b>Directory buckets</b> -
+   *             S3 Versioning isn't enabled and supported for directory buckets.</p>
    *          </note>
    * @public
    */
@@ -1180,14 +1211,12 @@ export interface CopyObjectRequest {
   /**
    * <p>Copies the object if its entity tag (ETag) matches the specified tag.</p>
    *          <p> If both the <code>x-amz-copy-source-if-match</code> and
-   *          <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the
-   *          request and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the
-   *          data:</p>
+   *             <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request
+   *          and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the data:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>x-amz-copy-source-if-match</code> condition evaluates to
-   *                true</p>
+   *                   <code>x-amz-copy-source-if-match</code> condition evaluates to true</p>
    *             </li>
    *             <li>
    *                <p>
@@ -1202,14 +1231,13 @@ export interface CopyObjectRequest {
   /**
    * <p>Copies the object if it has been modified since the specified time.</p>
    *          <p>If both the <code>x-amz-copy-source-if-none-match</code> and
-   *          <code>x-amz-copy-source-if-modified-since</code> headers are present in the
-   *          request and evaluate as follows, Amazon S3 returns the <code>412 Precondition
-   *             Failed</code> response code:</p>
+   *             <code>x-amz-copy-source-if-modified-since</code> headers are present in the request and
+   *          evaluate as follows, Amazon S3 returns the <code>412 Precondition Failed</code> response
+   *          code:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>x-amz-copy-source-if-none-match</code> condition evaluates to
-   *                false</p>
+   *                   <code>x-amz-copy-source-if-none-match</code> condition evaluates to false</p>
    *             </li>
    *             <li>
    *                <p>
@@ -1224,14 +1252,13 @@ export interface CopyObjectRequest {
   /**
    * <p>Copies the object if its entity tag (ETag) is different than the specified ETag.</p>
    *          <p>If both the <code>x-amz-copy-source-if-none-match</code> and
-   *          <code>x-amz-copy-source-if-modified-since</code> headers are present in the
-   *          request and evaluate as follows, Amazon S3 returns the <code>412 Precondition
-   *             Failed</code> response code:</p>
+   *             <code>x-amz-copy-source-if-modified-since</code> headers are present in the request and
+   *          evaluate as follows, Amazon S3 returns the <code>412 Precondition Failed</code> response
+   *          code:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>x-amz-copy-source-if-none-match</code> condition evaluates to
-   *                false</p>
+   *                   <code>x-amz-copy-source-if-none-match</code> condition evaluates to false</p>
    *             </li>
    *             <li>
    *                <p>
@@ -1246,14 +1273,12 @@ export interface CopyObjectRequest {
   /**
    * <p>Copies the object if it hasn't been modified since the specified time.</p>
    *          <p> If both the <code>x-amz-copy-source-if-match</code> and
-   *          <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the
-   *          request and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the
-   *          data:</p>
+   *             <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request
+   *          and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the data:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>x-amz-copy-source-if-match</code> condition evaluates to
-   *                true</p>
+   *                   <code>x-amz-copy-source-if-match</code> condition evaluates to true</p>
    *             </li>
    *             <li>
    *                <p>
@@ -1349,20 +1374,21 @@ export interface CopyObjectRequest {
 
   /**
    * <p>Specifies whether the metadata is copied from the source object or replaced with
-   *          metadata that's provided in the request.
-   *         When copying an object, you can preserve all metadata (the default) or specify
-   *         new metadata. If this header isn’t specified, <code>COPY</code> is the default behavior.
-   *       </p>
+   *          metadata that's provided in the request. When copying an object, you can preserve all
+   *          metadata (the default) or specify new metadata. If this header isn’t specified,
+   *             <code>COPY</code> is the default behavior. </p>
    *          <p>
-   *             <b>General purpose bucket</b> - For general purpose buckets, when you grant permissions, you
-   *          can use the <code>s3:x-amz-metadata-directive</code> condition key to enforce
-   *          certain metadata behavior when objects are uploaded. For more information, see
-   *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/amazon-s3-policy-keys.html">Amazon S3 condition key examples</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             <b>General purpose bucket</b> - For general purpose buckets, when you
+   *          grant permissions, you can use the <code>s3:x-amz-metadata-directive</code> condition key
+   *          to enforce certain metadata behavior when objects are uploaded. For more information, see
+   *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/amazon-s3-policy-keys.html">Amazon S3
+   *             condition key examples</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>
-   *                <code>x-amz-website-redirect-location</code> is unique to each object and is not copied when using the
-   *             <code>x-amz-metadata-directive</code> header. To copy the value, you
-   *             must specify <code>x-amz-website-redirect-location</code> in the request header.</p>
+   *                <code>x-amz-website-redirect-location</code> is unique to each object and is not
+   *             copied when using the <code>x-amz-metadata-directive</code> header. To copy the value,
+   *             you must specify <code>x-amz-website-redirect-location</code> in the request
+   *             header.</p>
    *          </note>
    * @public
    */
@@ -1408,37 +1434,36 @@ export interface CopyObjectRequest {
   TaggingDirective?: TaggingDirective | undefined;
 
   /**
-   * <p>The server-side encryption algorithm used when storing this object in Amazon S3. Unrecognized or unsupported values won’t write a destination object and will receive a <code>400 Bad Request</code> response. </p>
-   *          <p>Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket.
-   *          When copying an object, if you don't specify encryption information in your copy
-   *          request, the encryption setting of the target object is set to the default
-   *          encryption configuration of the destination bucket. By default, all buckets have a
-   *          base level of encryption configuration that uses server-side encryption with Amazon S3
-   *          managed keys (SSE-S3). If the destination bucket has a different default encryption
-   *          configuration, Amazon S3 uses
-   *          the corresponding encryption key to encrypt the target
-   *          object copy.</p>
-   *          <p>With server-side
-   *          encryption, Amazon S3 encrypts your data as it writes your data to disks in its data
-   *          centers and decrypts the data when you access it. For more information about server-side encryption, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Using
-   *             Server-Side Encryption</a> in the
-   *          <i>Amazon S3 User Guide</i>.</p>
+   * <p>The server-side encryption algorithm used when storing this object in Amazon S3. Unrecognized
+   *          or unsupported values won’t write a destination object and will receive a <code>400 Bad
+   *             Request</code> response. </p>
+   *          <p>Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket. When
+   *          copying an object, if you don't specify encryption information in your copy request, the
+   *          encryption setting of the target object is set to the default encryption configuration of
+   *          the destination bucket. By default, all buckets have a base level of encryption
+   *          configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the
+   *          destination bucket has a different default encryption configuration, Amazon S3 uses the
+   *          corresponding encryption key to encrypt the target object copy.</p>
+   *          <p>With server-side encryption, Amazon S3 encrypts your data as it writes your data to disks in
+   *          its data centers and decrypts the data when you access it. For more information about
+   *          server-side encryption, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Using Server-Side Encryption</a>
+   *          in the <i>Amazon S3 User Guide</i>.</p>
    *          <p>
    *             <b>General purpose buckets </b>
    *          </p>
    *          <ul>
    *             <li>
-   *                <p>For general purpose buckets, there are the following supported options for server-side encryption: server-side encryption with Key Management Service (KMS) keys
-   *             (SSE-KMS), dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), and
-   *             server-side encryption with customer-provided encryption keys (SSE-C). Amazon S3 uses
-   *             the corresponding KMS key, or a customer-provided key to encrypt the target
-   *             object copy.</p>
+   *                <p>For general purpose buckets, there are the following supported options for server-side
+   *                encryption: server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer
+   *                server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), and server-side encryption
+   *                with customer-provided encryption keys (SSE-C). Amazon S3 uses the corresponding
+   *                KMS key, or a customer-provided key to encrypt the target object copy.</p>
    *             </li>
    *             <li>
    *                <p>When you perform a <code>CopyObject</code> operation, if you want to use a
    *                different type of encryption setting for the target object, you can specify
-   *                appropriate encryption-related headers to encrypt the target object with an Amazon S3 managed key, a
-   *                KMS key, or a customer-provided key. If the encryption setting in
+   *                appropriate encryption-related headers to encrypt the target object with an Amazon S3
+   *                managed key, a KMS key, or a customer-provided key. If the encryption setting in
    *                your request is different from the default encryption configuration of the
    *                destination bucket, the encryption setting in your request takes precedence. </p>
    *             </li>
@@ -1454,10 +1479,19 @@ export interface CopyObjectRequest {
    *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>To encrypt new object copies to a directory bucket with SSE-KMS, we recommend you specify SSE-KMS as the directory bucket's default encryption configuration with a KMS key (specifically, a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a>).
-   *             The <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. 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 for the lifetime of the bucket. After you specify a customer managed key for SSE-KMS, you can't override the customer managed key for the bucket's SSE-KMS configuration.
-   *             Then, when you perform a <code>CopyObject</code> operation and want to specify server-side encryption settings for new object copies with SSE-KMS in the encryption-related request headers, you must ensure the encryption key is the same customer managed key that you specified for the directory bucket's default encryption configuration.
-   *             </p>
+   *                <p>To encrypt new object copies to a directory bucket with SSE-KMS, we recommend you
+   *                specify SSE-KMS as the directory bucket's default encryption configuration with
+   *                a KMS key (specifically, a <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a>).
+   *                The <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. 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 for the lifetime of the bucket. After you specify a customer managed key for
+   *                SSE-KMS, you can't override the customer managed key for the bucket's SSE-KMS
+   *                configuration. Then, when you perform a <code>CopyObject</code> operation and want to
+   *                specify server-side encryption settings for new object copies with SSE-KMS in the
+   *                encryption-related request headers, you must ensure the encryption key is the same
+   *                customer managed key that you specified for the directory bucket's default encryption
+   *                configuration.
+   *                </p>
    *             </li>
    *          </ul>
    * @public
@@ -1465,54 +1499,55 @@ export interface CopyObjectRequest {
   ServerSideEncryption?: ServerSideEncryption | undefined;
 
   /**
-   * <p>If the <code>x-amz-storage-class</code> header is not used, the copied object will be stored in the
-   *          <code>STANDARD</code> Storage Class by default. The <code>STANDARD</code> storage class provides high durability and
-   *          high availability. Depending on performance needs, you can specify a different Storage
-   *          Class.
-   *       </p>
+   * <p>If the <code>x-amz-storage-class</code> header is not used, the copied object will be
+   *          stored in the <code>STANDARD</code> Storage Class by default. The <code>STANDARD</code>
+   *          storage class provides high durability and high availability. Depending on performance
+   *          needs, you can specify a different Storage Class. </p>
    *          <note>
    *             <ul>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets </b> - For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.
+   *                      <b>Directory buckets </b> -
+   *                   For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.
    * Unsupported storage class values won't write a destination object and will respond with the HTTP status code <code>400 Bad Request</code>.</p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Amazon S3 on Outposts </b> - S3 on Outposts only uses the <code>OUTPOSTS</code> Storage Class.</p>
+   *                      <b>Amazon S3 on Outposts </b> - S3 on Outposts only
+   *                   uses the <code>OUTPOSTS</code> Storage Class.</p>
    *                </li>
    *             </ul>
    *          </note>
-   *          <p>You can use the <code>CopyObject</code> action to change the storage class of
-   *          an object that is already stored in Amazon S3 by using the <code>x-amz-storage-class</code>
-   *          header. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a> in
-   *          the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>Before using an object as a source object for the copy operation, you must restore a copy of it if it meets any of the following conditions:</p>
+   *          <p>You can use the <code>CopyObject</code> action to change the storage class of an object
+   *          that is already stored in Amazon S3 by using the <code>x-amz-storage-class</code> header. For
+   *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a> in the
+   *             <i>Amazon S3 User Guide</i>.</p>
+   *          <p>Before using an object as a source object for the copy operation, you must restore a
+   *          copy of it if it meets any of the following conditions:</p>
    *          <ul>
    *             <li>
    *                <p>The storage class of the source object is <code>GLACIER</code> or
-   *             <code>DEEP_ARCHIVE</code>.</p>
+   *                   <code>DEEP_ARCHIVE</code>.</p>
    *             </li>
    *             <li>
-   *                <p>The storage class of the source object is
-   *             <code>INTELLIGENT_TIERING</code> and it's <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering-overview.html#intel-tiering-tier-definition">S3 Intelligent-Tiering access tier</a> is
-   *             <code>Archive Access</code> or <code>Deep Archive Access</code>.</p>
+   *                <p>The storage class of the source object is <code>INTELLIGENT_TIERING</code> and
+   *                it's <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering-overview.html#intel-tiering-tier-definition">S3 Intelligent-Tiering access tier</a> is <code>Archive Access</code> or
+   *                   <code>Deep Archive Access</code>.</p>
    *             </li>
    *          </ul>
-   *          <p>For more
-   *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html">Copying
-   *                Objects</a> in
-   *          the <i>Amazon S3 User Guide</i>.</p>
+   *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html">Copying
+   *             Objects</a> in the <i>Amazon S3 User Guide</i>.</p>
    * @public
    */
   StorageClass?: StorageClass | undefined;
 
   /**
-   * <p>If the destination bucket is configured as a website, redirects requests for this object copy to another
-   *          object in the same bucket or to an external URL. Amazon S3 stores the value of this header in
-   *          the object metadata. This value is unique to each object and is not copied when using the
-   *             <code>x-amz-metadata-directive</code> header. Instead, you may opt to provide this
-   *          header in combination with the <code>x-amz-metadata-directive</code> header.</p>
+   * <p>If the destination bucket is configured as a website, redirects requests for this object
+   *          copy to another object in the same bucket or to an external URL. Amazon S3 stores the value of
+   *          this header in the object metadata. This value is unique to each object and is not copied
+   *          when using the <code>x-amz-metadata-directive</code> header. Instead, you may opt to
+   *          provide this header in combination with the <code>x-amz-metadata-directive</code>
+   *          header.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -1522,13 +1557,13 @@ export interface CopyObjectRequest {
 
   /**
    * <p>Specifies the algorithm to use when encrypting the object (for example,
-   *          <code>AES256</code>).</p>
-   *          <p>When you perform a <code>CopyObject</code> operation, if you want to use a
-   *          different type of encryption setting for the target object, you can specify
-   *          appropriate encryption-related headers to encrypt the target object with an Amazon S3 managed key, a
-   *          KMS key, or a customer-provided key. If the encryption setting in
-   *          your request is different from the default encryption configuration of the
-   *          destination bucket, the encryption setting in your request takes precedence. </p>
+   *             <code>AES256</code>).</p>
+   *          <p>When you perform a <code>CopyObject</code> operation, if you want to use a different
+   *          type of encryption setting for the target object, you can specify appropriate
+   *          encryption-related headers to encrypt the target object with an Amazon S3 managed key, a
+   *          KMS key, or a customer-provided key. If the encryption setting in your request is
+   *          different from the default encryption configuration of the destination bucket, the
+   *          encryption setting in your request takes precedence. </p>
    *          <note>
    *             <p>This functionality is not supported when the destination bucket is a directory bucket.</p>
    *          </note>
@@ -1560,14 +1595,15 @@ export interface CopyObjectRequest {
   SSECustomerKeyMD5?: string | undefined;
 
   /**
-   * <p>Specifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption. All GET and PUT requests for an
-   *          object protected by KMS will fail if they're not made via SSL or using SigV4. For
-   *          information about configuring any of the officially supported Amazon Web Services SDKs and Amazon Web Services CLI, see
-   *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version">Specifying the
+   * <p>Specifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption.
+   *          All GET and PUT requests for an object protected by KMS will fail if they're not made via
+   *          SSL or using SigV4. For information about configuring any of the officially supported Amazon Web Services
+   *          SDKs and Amazon Web Services CLI, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version">Specifying the
    *             Signature Version in Request Authentication</a> in the
    *             <i>Amazon S3 User Guide</i>.</p>
    *          <p>
-   *             <b>Directory buckets</b> - If you specify <code>x-amz-server-side-encryption</code> with <code>aws:kms</code>, the <code>
+   *             <b>Directory buckets</b> -
+   *          If you specify <code>x-amz-server-side-encryption</code> with <code>aws:kms</code>, the <code>
    *          x-amz-server-side-encryption-aws-kms-key-id</code> header is implicitly assigned the ID of the KMS
    *          symmetric encryption customer managed key that's configured for your directory bucket's default encryption setting.
    *          If you want to specify the <code>
@@ -1580,12 +1616,16 @@ export interface CopyObjectRequest {
   SSEKMSKeyId?: string | undefined;
 
   /**
-   * <p>Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use for the destination object encryption. The value of
-   *          this header is a base64-encoded UTF-8 string holding JSON with the encryption context
-   *          key-value pairs.</p>
+   * <p>Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use
+   *          for the destination object encryption. The value of this header is a base64-encoded UTF-8
+   *          string holding JSON with the encryption context key-value pairs.</p>
    *          <p>
-   *             <b>General purpose buckets</b> - This value must be explicitly added to specify encryption context for
-   *          <code>CopyObject</code> requests if you want an additional encryption context for your destination object. The additional encryption context of the source object won't be copied to the destination object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html#encryption-context">Encryption context</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             <b>General purpose buckets</b> - This value must be explicitly
+   *          added to specify encryption context for <code>CopyObject</code> requests if you want an
+   *          additional encryption context for your destination object. The additional encryption
+   *          context of the source object won't be copied to the destination object. For more
+   *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html#encryption-context">Encryption
+   *             context</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <p>
    *             <b>Directory buckets</b> - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported. </p>
    * @public
@@ -1594,17 +1634,17 @@ export interface CopyObjectRequest {
 
   /**
    * <p>Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with
-   *          server-side encryption using Key Management Service (KMS) keys (SSE-KMS). If a target object uses SSE-KMS, you can enable an S3 Bucket Key for the
-   *          object.</p>
-   *          <p>Setting this header to
-   *          <code>true</code> causes Amazon S3 to use an S3 Bucket Key for object encryption with
-   *          SSE-KMS. Specifying this header with a COPY action doesn’t affect bucket-level settings for S3
-   *          Bucket Key.</p>
+   *          server-side encryption using Key Management Service (KMS) keys (SSE-KMS). If a target object uses
+   *          SSE-KMS, you can enable an S3 Bucket Key for the object.</p>
+   *          <p>Setting this header to <code>true</code> causes Amazon S3 to use an S3 Bucket Key for object
+   *          encryption with SSE-KMS. Specifying this header with a COPY action doesn’t affect
+   *          bucket-level settings for S3 Bucket Key.</p>
    *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the
-   *          <i>Amazon S3 User Guide</i>.</p>
+   *             <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
+   *                <b>Directory buckets</b> -
+   *             S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
    * to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>
    *          </note>
    * @public
@@ -1613,11 +1653,10 @@ export interface CopyObjectRequest {
 
   /**
    * <p>Specifies the algorithm to use when decrypting the source object (for example,
-   *          <code>AES256</code>).</p>
-   *          <p>If
-   *       the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
-   *       necessary encryption information in your request so that Amazon S3 can decrypt the
-   *       object for copying.</p>
+   *             <code>AES256</code>).</p>
+   *          <p>If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
+   *          necessary encryption information in your request so that Amazon S3 can decrypt the object for
+   *          copying.</p>
    *          <note>
    *             <p>This functionality is not supported when the source object is in a directory bucket.</p>
    *          </note>
@@ -1627,12 +1666,11 @@ export interface CopyObjectRequest {
 
   /**
    * <p>Specifies the customer-provided encryption key for Amazon S3 to use to decrypt the source
-   *          object. The encryption key provided in this header must be the same one that was used when the
-   *          source object was created.</p>
-   *          <p>If
-   *          the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
-   *          necessary encryption information in your request so that Amazon S3 can decrypt the
-   *          object for copying.</p>
+   *          object. The encryption key provided in this header must be the same one that was used when
+   *          the source object was created.</p>
+   *          <p>If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
+   *          necessary encryption information in your request so that Amazon S3 can decrypt the object for
+   *          copying.</p>
    *          <note>
    *             <p>This functionality is not supported when the source object is in a directory bucket.</p>
    *          </note>
@@ -1644,10 +1682,9 @@ export interface CopyObjectRequest {
    * <p>Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses
    *          this header for a message integrity check to ensure that the encryption key was transmitted
    *          without error.</p>
-   *          <p>If
-   *          the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
-   *          necessary encryption information in your request so that Amazon S3 can decrypt the
-   *          object for copying.</p>
+   *          <p>If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the
+   *          necessary encryption information in your request so that Amazon S3 can decrypt the object for
+   *          copying.</p>
    *          <note>
    *             <p>This functionality is not supported when the source object is in a directory bucket.</p>
    *          </note>
@@ -1658,9 +1695,9 @@ export interface CopyObjectRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -1670,10 +1707,12 @@ export interface CopyObjectRequest {
   RequestPayer?: RequestPayer | undefined;
 
   /**
-   * <p>The tag-set for the object copy in the destination bucket. This value must be used in conjunction
-   *          with the <code>x-amz-tagging-directive</code> if you choose <code>REPLACE</code> for the <code>x-amz-tagging-directive</code>. If you choose <code>COPY</code> for the <code>x-amz-tagging-directive</code>, you don't need to set
-   *          the <code>x-amz-tagging</code> header, because the tag-set will be copied from the source object directly. The tag-set must be encoded as URL Query
-   *          parameters.</p>
+   * <p>The tag-set for the object copy in the destination bucket. This value must be used in
+   *          conjunction with the <code>x-amz-tagging-directive</code> if you choose
+   *             <code>REPLACE</code> for the <code>x-amz-tagging-directive</code>. If you choose
+   *             <code>COPY</code> for the <code>x-amz-tagging-directive</code>, you don't need to set
+   *          the <code>x-amz-tagging</code> header, because the tag-set will be copied from the source
+   *          object directly. The tag-set must be encoded as URL Query parameters.</p>
    *          <p>The default value is the empty value.</p>
    *          <note>
    *             <p>
@@ -1869,8 +1908,8 @@ export const BucketType = {
 export type BucketType = (typeof BucketType)[keyof typeof BucketType];
 
 /**
- * <p>Specifies the information about the bucket that will be created. For more information about directory buckets, see
- *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
+ * <p>Specifies the information about the bucket that will be created. For more information
+ *          about directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
  *             <p>This functionality is only supported by directory buckets.</p>
  *          </note>
@@ -1905,8 +1944,8 @@ export type LocationType = (typeof LocationType)[keyof typeof LocationType];
 
 /**
  * <p>Specifies the location where the bucket will be created.</p>
- *          <p>For directory buckets, the location type is Availability Zone. For more information about directory buckets, see
- *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>For directory buckets, the location type is Availability Zone. For more information about
+ *          directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
  *             <p>This functionality is only supported by directory buckets.</p>
  *          </note>
@@ -1921,7 +1960,8 @@ export interface LocationInfo {
 
   /**
    * <p>The name of the location where the bucket will be created.</p>
-   *          <p>For directory buckets, the name of the location is the AZ ID of the Availability Zone where the bucket will be created. An example AZ ID value is <code>usw2-az1</code>.</p>
+   *          <p>For directory buckets, the name of the location is the AZ ID of the Availability Zone where the
+   *          bucket will be created. An example AZ ID value is <code>usw2-az1</code>.</p>
    * @public
    */
   Name?: string | undefined;
@@ -1978,8 +2018,8 @@ export interface CreateBucketConfiguration {
    *          reside in Europe, you will probably find it advantageous to create buckets in the Europe
    *          (Ireland) Region. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro">Accessing a
    *             bucket</a> in the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>If you don't specify a Region,
-   *          the bucket is created in the US East (N. Virginia) Region (us-east-1) by default.</p>
+   *          <p>If you don't specify a Region, the bucket is created in the US East (N. Virginia) Region
+   *          (us-east-1) by default.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -2117,22 +2157,25 @@ export interface CreateBucketRequest {
   /**
    * <p>The container element for object ownership for a bucket's ownership controls.</p>
    *          <p>
-   *             <code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket
-   *          owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned
-   *          ACL.</p>
+   *             <code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to
+   *          the bucket owner if the objects are uploaded with the
+   *             <code>bucket-owner-full-control</code> canned ACL.</p>
    *          <p>
-   *             <code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with
-   *          the <code>bucket-owner-full-control</code> canned ACL.</p>
+   *             <code>ObjectWriter</code> - The uploading account will own the object if the object is
+   *          uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
    *          <p>
-   *             <code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect
-   *          permissions. The bucket owner automatically owns and has full control over every object in
-   *          the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner
-   *          full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL
-   *          in XML format that grants the same permissions).</p>
-   *          <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend
-   *       keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see
-   *       <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.
-   *       </p>
+   *             <code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no
+   *          longer affect permissions. The bucket owner automatically owns and has full control over
+   *          every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL
+   *          or specify bucket owner full control ACLs (such as the predefined
+   *             <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that
+   *          grants the same permissions).</p>
+   *          <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and
+   *          ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where
+   *          you must control access for each object individually. For more information about S3 Object
+   *          Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of
+   *             objects and disabling ACLs for your bucket</a> in the
+   *             <i>Amazon S3 User Guide</i>. </p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
    *          </note>
@@ -2150,8 +2193,8 @@ export interface CreateMultipartUploadOutput {
    *          multipart uploads and the prefix in the lifecycle rule matches the object name in the
    *          request, the response includes this header. The header indicates when the initiated
    *          multipart upload becomes eligible for an abort operation. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">
-   *             Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle
-   *             Configuration</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration</a> in
+   *          the <i>Amazon S3 User Guide</i>.</p>
    *          <p>The response also includes the <code>x-amz-abort-rule-id</code> header that provides the
    *          ID of the lifecycle configuration rule that defines the abort action.</p>
    *          <note>
@@ -2195,8 +2238,8 @@ export interface CreateMultipartUploadOutput {
   UploadId?: string | undefined;
 
   /**
-   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,
-   *             <code>AES256</code>, <code>aws:kms</code>).</p>
+   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for
+   *          example, <code>AES256</code>, <code>aws:kms</code>).</p>
    * @public
    */
   ServerSideEncryption?: ServerSideEncryption | undefined;
@@ -2213,8 +2256,8 @@ export interface CreateMultipartUploadOutput {
 
   /**
    * <p>If server-side encryption with a customer-provided encryption key was requested, the
-   *          response will include this header to provide the round-trip message integrity verification of
-   *          the customer-provided encryption key.</p>
+   *          response will include this header to provide the round-trip message integrity verification
+   *          of the customer-provided encryption key.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -2264,17 +2307,16 @@ export interface CreateMultipartUploadOutput {
  */
 export interface CreateMultipartUploadRequest {
   /**
-   * <p>The canned ACL to apply to the object. Amazon S3 supports a set of
-   *          predefined ACLs, known as <i>canned ACLs</i>. Each canned ACL
-   *          has a predefined set of grantees and permissions. For more information, see
-   *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned
-   *             ACL</a> in the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>By default, all objects are private. Only the owner has full access
-   *          control. When uploading an object, you can grant access permissions to individual
-   *          Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then
-   *          added to the access control list (ACL) on the new object. For more information, see
-   *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>.  One way to
-   *          grant the permissions using the request headers is to specify a canned ACL with the <code>x-amz-acl</code> request header.</p>
+   * <p>The canned ACL to apply to the object. Amazon S3 supports a set of predefined ACLs, known as
+   *             <i>canned ACLs</i>. Each canned ACL has a predefined set of grantees and
+   *          permissions. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned ACL</a> in the
+   *             <i>Amazon S3 User Guide</i>.</p>
+   *          <p>By default, all objects are private. Only the owner has full access control. When
+   *          uploading an object, you can grant access permissions to individual Amazon Web Services accounts or to
+   *          predefined groups defined by Amazon S3. These permissions are then added to the access control
+   *          list (ACL) on the new object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. One way to grant
+   *          the permissions using the request headers is to specify a canned ACL with the
+   *             <code>x-amz-acl</code> request header.</p>
    *          <note>
    *             <ul>
    *                <li>
@@ -2290,9 +2332,11 @@ export interface CreateMultipartUploadRequest {
   ACL?: ObjectCannedACL | undefined;
 
   /**
-   * <p>The name of the bucket where the multipart upload is initiated and where the object is uploaded.</p>
+   * <p>The name of the bucket where the multipart upload is initiated and where the object is
+   *          uploaded.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -2354,30 +2398,29 @@ export interface CreateMultipartUploadRequest {
   Expires?: Date | undefined;
 
   /**
-   * <p>Specify access permissions explicitly to give the grantee READ, READ_ACP, and WRITE_ACP permissions on the object.</p>
-   *          <p>By default, all objects are private. Only the owner has full access
-   *          control. When uploading an object, you can use this header to explicitly grant access
-   *          permissions to specific Amazon Web Services accounts or groups.
-   *          This header maps to specific permissions that Amazon S3 supports in an ACL. For
-   *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL)
-   *             Overview</a> in the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>You specify each grantee as a type=value pair, where the type is one of
-   *          the following:</p>
+   * <p>Specify access permissions explicitly to give the grantee READ, READ_ACP, and WRITE_ACP
+   *          permissions on the object.</p>
+   *          <p>By default, all objects are private. Only the owner has full access control. When
+   *          uploading an object, you can use this header to explicitly grant access permissions to
+   *          specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
+   *          supports in an ACL. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL) Overview</a>
+   *          in the <i>Amazon S3 User Guide</i>.</p>
+   *          <p>You specify each grantee as a type=value pair, where the type is one of the
+   *          following:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>id</code> – if the value specified is the canonical user ID
-   *                of an Amazon Web Services account</p>
+   *                   <code>id</code> – if the value specified is the canonical user ID of an
+   *                Amazon Web Services account</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>uri</code> – if you are granting permissions to a predefined
-   *                group</p>
+   *                   <code>uri</code> – if you are granting permissions to a predefined group</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>emailAddress</code> – if the value specified is the email
-   *                address of an Amazon Web Services account</p>
+   *                   <code>emailAddress</code> – if the value specified is the email address of an
+   *                Amazon Web Services account</p>
    *                <note>
    *                   <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
    *                   <ul>
@@ -2429,30 +2472,29 @@ export interface CreateMultipartUploadRequest {
   GrantFullControl?: string | undefined;
 
   /**
-   * <p>Specify access permissions explicitly to allow grantee to read the object data and its metadata.</p>
-   *          <p>By default, all objects are private. Only the owner has full access
-   *          control. When uploading an object, you can use this header to explicitly grant access
-   *          permissions to specific Amazon Web Services accounts or groups.
-   *          This header maps to specific permissions that Amazon S3 supports in an ACL. For
-   *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL)
-   *             Overview</a> in the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>You specify each grantee as a type=value pair, where the type is one of
-   *          the following:</p>
+   * <p>Specify access permissions explicitly to allow grantee to read the object data and its
+   *          metadata.</p>
+   *          <p>By default, all objects are private. Only the owner has full access control. When
+   *          uploading an object, you can use this header to explicitly grant access permissions to
+   *          specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
+   *          supports in an ACL. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL) Overview</a>
+   *          in the <i>Amazon S3 User Guide</i>.</p>
+   *          <p>You specify each grantee as a type=value pair, where the type is one of the
+   *          following:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>id</code> – if the value specified is the canonical user ID
-   *                of an Amazon Web Services account</p>
+   *                   <code>id</code> – if the value specified is the canonical user ID of an
+   *                Amazon Web Services account</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>uri</code> – if you are granting permissions to a predefined
-   *                group</p>
+   *                   <code>uri</code> – if you are granting permissions to a predefined group</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>emailAddress</code> – if the value specified is the email
-   *                address of an Amazon Web Services account</p>
+   *                   <code>emailAddress</code> – if the value specified is the email address of an
+   *                Amazon Web Services account</p>
    *                <note>
    *                   <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
    *                   <ul>
@@ -2505,29 +2547,27 @@ export interface CreateMultipartUploadRequest {
 
   /**
    * <p>Specify access permissions explicitly to allows grantee to read the object ACL.</p>
-   *          <p>By default, all objects are private. Only the owner has full access
-   *          control. When uploading an object, you can use this header to explicitly grant access
-   *          permissions to specific Amazon Web Services accounts or groups.
-   *          This header maps to specific permissions that Amazon S3 supports in an ACL. For
-   *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL)
-   *             Overview</a> in the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>You specify each grantee as a type=value pair, where the type is one of
-   *          the following:</p>
+   *          <p>By default, all objects are private. Only the owner has full access control. When
+   *          uploading an object, you can use this header to explicitly grant access permissions to
+   *          specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
+   *          supports in an ACL. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL) Overview</a>
+   *          in the <i>Amazon S3 User Guide</i>.</p>
+   *          <p>You specify each grantee as a type=value pair, where the type is one of the
+   *          following:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>id</code> – if the value specified is the canonical user ID
-   *                of an Amazon Web Services account</p>
+   *                   <code>id</code> – if the value specified is the canonical user ID of an
+   *                Amazon Web Services account</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>uri</code> – if you are granting permissions to a predefined
-   *                group</p>
+   *                   <code>uri</code> – if you are granting permissions to a predefined group</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>emailAddress</code> – if the value specified is the email
-   *                address of an Amazon Web Services account</p>
+   *                   <code>emailAddress</code> – if the value specified is the email address of an
+   *                Amazon Web Services account</p>
    *                <note>
    *                   <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
    *                   <ul>
@@ -2579,30 +2619,29 @@ export interface CreateMultipartUploadRequest {
   GrantReadACP?: string | undefined;
 
   /**
-   * <p>Specify access permissions explicitly to allows grantee to allow grantee to write the ACL for the applicable object.</p>
-   *          <p>By default, all objects are private. Only the owner has full access
-   *          control. When uploading an object, you can use this header to explicitly grant access
-   *          permissions to specific Amazon Web Services accounts or groups.
-   *          This header maps to specific permissions that Amazon S3 supports in an ACL. For
-   *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL)
-   *             Overview</a> in the <i>Amazon S3 User Guide</i>.</p>
-   *          <p>You specify each grantee as a type=value pair, where the type is one of
-   *          the following:</p>
+   * <p>Specify access permissions explicitly to allows grantee to allow grantee to write the
+   *          ACL for the applicable object.</p>
+   *          <p>By default, all objects are private. Only the owner has full access control. When
+   *          uploading an object, you can use this header to explicitly grant access permissions to
+   *          specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3
+   *          supports in an ACL. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL) Overview</a>
+   *          in the <i>Amazon S3 User Guide</i>.</p>
+   *          <p>You specify each grantee as a type=value pair, where the type is one of the
+   *          following:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>id</code> – if the value specified is the canonical user ID
-   *                of an Amazon Web Services account</p>
+   *                   <code>id</code> – if the value specified is the canonical user ID of an
+   *                Amazon Web Services account</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>uri</code> – if you are granting permissions to a predefined
-   *                group</p>
+   *                   <code>uri</code> – if you are granting permissions to a predefined group</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>emailAddress</code> – if the value specified is the email
-   *                address of an Amazon Web Services account</p>
+   *                   <code>emailAddress</code> – if the value specified is the email address of an
+   *                Amazon Web Services account</p>
    *                <note>
    *                   <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
    *                   <ul>
@@ -2666,16 +2705,16 @@ export interface CreateMultipartUploadRequest {
   Metadata?: Record<string, string> | undefined;
 
   /**
-   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,
-   *             <code>AES256</code>, <code>aws:kms</code>).</p>
+   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for
+   *          example, <code>AES256</code>, <code>aws:kms</code>).</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+   *                   <b>Directory buckets </b> -
+   *                For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). 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, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>
+   *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>In the Zonal endpoint API calls (except <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request.
    *                             You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request.
    *                             You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and
@@ -2698,16 +2737,17 @@ export interface CreateMultipartUploadRequest {
   /**
    * <p>By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The
    *          STANDARD storage class provides high durability and high availability. Depending on
-   *          performance needs, you can specify a different Storage Class. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a> in the
-   *             <i>Amazon S3 User Guide</i>.</p>
+   *          performance needs, you can specify a different Storage Class. For more information, see
+   *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage
+   *             Classes</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <ul>
    *                <li>
-   *                   <p>For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.</p>
+   *                   <p>For directory buckets, only the S3 Express One Zone storage class is supported to store
+   *                   newly created objects.</p>
    *                </li>
    *                <li>
-   *                   <p>Amazon S3 on Outposts only uses
-   *                the OUTPOSTS Storage Class.</p>
+   *                   <p>Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -2727,8 +2767,7 @@ export interface CreateMultipartUploadRequest {
   WebsiteRedirectLocation?: string | undefined;
 
   /**
-   * <p>Specifies the algorithm to use when encrypting the object (for example,
-   *          AES256).</p>
+   * <p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -2749,9 +2788,9 @@ export interface CreateMultipartUploadRequest {
   SSECustomerKey?: string | undefined;
 
   /**
-   * <p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to RFC 1321. Amazon S3 uses
-   *          this header for a message integrity check to ensure that the encryption key was transmitted
-   *          without error.</p>
+   * <p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to
+   *          RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption
+   *          key was transmitted without error.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -2809,9 +2848,9 @@ export interface CreateMultipartUploadRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -2875,25 +2914,32 @@ export interface CreateMultipartUploadRequest {
  * <p>The established temporary security credentials of the session.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> - These session credentials are only supported for the authentication and authorization of Zonal endpoint API operations on directory buckets.</p>
+ *                <b>Directory buckets</b> - These session
+ *             credentials are only supported for the authentication and authorization of Zonal endpoint API operations
+ *             on directory buckets.</p>
  *          </note>
  * @public
  */
 export interface SessionCredentials {
   /**
-   * <p>A unique identifier that's associated with a secret access key. The access key ID and the secret access key are used together to sign programmatic Amazon Web Services requests cryptographically. </p>
+   * <p>A unique identifier that's associated with a secret access key. The access key ID and
+   *          the secret access key are used together to sign programmatic Amazon Web Services requests
+   *          cryptographically. </p>
    * @public
    */
   AccessKeyId: string | undefined;
 
   /**
-   * <p>A key that's used with the access key ID to cryptographically sign programmatic Amazon Web Services requests. Signing a request identifies the sender and prevents the request from being altered. </p>
+   * <p>A key that's used with the access key ID to cryptographically sign programmatic Amazon Web Services
+   *          requests. Signing a request identifies the sender and prevents the request from being
+   *          altered. </p>
    * @public
    */
   SecretAccessKey: string | undefined;
 
   /**
-   * <p>A part of the temporary security credentials. The session token is used to validate the temporary security credentials.
+   * <p>A part of the temporary security credentials. The session token is used to validate the
+   *          temporary security credentials.
    *
    *       </p>
    * @public
@@ -2901,8 +2947,10 @@ export interface SessionCredentials {
   SessionToken: string | undefined;
 
   /**
-   * <p>Temporary security credentials expire after a specified interval. After temporary credentials expire, any calls that you make with those credentials will fail. So you must generate a new set of temporary credentials.
-   *          Temporary credentials cannot be extended or refreshed beyond the original specified interval.</p>
+   * <p>Temporary security credentials expire after a specified interval. After temporary
+   *          credentials expire, any calls that you make with those credentials will fail. So you must
+   *          generate a new set of temporary credentials. Temporary credentials cannot be extended or
+   *          refreshed beyond the original specified interval.</p>
    * @public
    */
   Expiration: Date | undefined;
@@ -3212,6 +3260,10 @@ export interface DeleteBucketLifecycleRequest {
 
   /**
    * <p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   ExpectedBucketOwner?: string | undefined;
@@ -3353,9 +3405,10 @@ export interface DeleteBucketWebsiteRequest {
  */
 export interface DeleteObjectOutput {
   /**
-   * <p>Indicates whether the specified object version that was permanently deleted was (true) or was
-   *          not (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or
-   *          not (false) the current version of the object is a delete marker.</p>
+   * <p>Indicates whether the specified object version that was permanently deleted was (true)
+   *          or was not (false) a delete marker before deletion. In a simple DELETE, this header
+   *          indicates whether (true) or not (false) the current version of the object is a delete
+   *          marker.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -3391,7 +3444,8 @@ export interface DeleteObjectRequest {
   /**
    * <p>The bucket name of the bucket containing the object. </p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -3440,9 +3494,9 @@ export interface DeleteObjectRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -3467,6 +3521,45 @@ export interface DeleteObjectRequest {
    * @public
    */
   ExpectedBucketOwner?: string | undefined;
+
+  /**
+   * <p>The <code>If-Match</code> header field makes the request method conditional on ETags. If the ETag value does not match, the operation returns
+   *          a <code>412 Precondition Failed</code> error. If the ETag matches or if the object doesn't exist, the operation will return a <code>204 Success (No
+   *          Content) response</code>.</p>
+   *          <p>For more information about conditional requests, see <a href="https://docs.aws.amazon.com/https:/tools.ietf.org/html/rfc7232">RFC 7232</a>.</p>
+   *          <note>
+   *             <p>This functionality is only supported for directory buckets.</p>
+   *          </note>
+   * @public
+   */
+  IfMatch?: string | undefined;
+
+  /**
+   * <p>If present, the object is deleted only if its modification times matches the provided
+   *             <code>Timestamp</code>. If the <code>Timestamp</code> values do not match, the operation
+   *          returns a <code>412 Precondition Failed</code> error. If the <code>Timestamp</code> matches
+   *          or if the object doesn’t exist, the operation returns a <code>204 Success (No
+   *             Content)</code> response.</p>
+   *          <note>
+   *             <p>This functionality is only supported for directory buckets.</p>
+   *          </note>
+   * @public
+   */
+  IfMatchLastModifiedTime?: Date | undefined;
+
+  /**
+   * <p>If present, the object is deleted only if its size matches the provided size in bytes. If the <code>Size</code> value does not match, the operation returns a <code>412 Precondition Failed</code> error. If the <code>Size</code> matches or if the object doesn’t exist,
+   *          the operation returns a <code>204 Success (No Content)</code> response.</p>
+   *          <note>
+   *             <p>This functionality is only supported for directory buckets.</p>
+   *          </note>
+   *          <important>
+   *             <p>You can use the <code>If-Match</code>, <code>x-amz-if-match-last-modified-time</code> and <code>x-amz-if-match-size</code>
+   *          conditional headers in conjunction with each-other or individually.</p>
+   *          </important>
+   * @public
+   */
+  IfMatchSize?: number | undefined;
 }
 
 /**
@@ -3490,9 +3583,10 @@ export interface DeletedObject {
   VersionId?: string | undefined;
 
   /**
-   * <p>Indicates whether the specified object version that was permanently deleted was (true) or was
-   *          not (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or
-   *          not (false) the current version of the object is a delete marker.</p>
+   * <p>Indicates whether the specified object version that was permanently deleted was (true)
+   *          or was not (false) a delete marker before deletion. In a simple DELETE, this header
+   *          indicates whether (true) or not (false) the current version of the object is a delete
+   *          marker.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -5465,6 +5559,35 @@ export interface ObjectIdentifier {
    * @public
    */
   VersionId?: string | undefined;
+
+  /**
+   * <p>An entity tag (ETag) is an identifier assigned by a web server to a specific version of a resource found at a URL.
+   *          This header field makes the request method conditional on <code>ETags</code>. </p>
+   *          <note>
+   *             <p>Entity tags (ETags) for S3 Express One Zone are random alphanumeric strings unique to the object. </p>
+   *          </note>
+   * @public
+   */
+  ETag?: string | undefined;
+
+  /**
+   * <p>If present, the objects are deleted only if its modification times matches the provided <code>Timestamp</code>.
+   *       </p>
+   *          <note>
+   *             <p>This functionality is only supported for directory buckets.</p>
+   *          </note>
+   * @public
+   */
+  LastModifiedTime?: Date | undefined;
+
+  /**
+   * <p>If present, the objects are deleted only if its size matches the provided size in bytes. </p>
+   *          <note>
+   *             <p>This functionality is only supported for directory buckets.</p>
+   *          </note>
+   * @public
+   */
+  Size?: number | undefined;
 }
 
 /**
@@ -5476,9 +5599,10 @@ export interface Delete {
    * <p>The object to delete.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - For directory buckets, an object that's composed entirely of
-   *       whitespace characters is not supported by the <code>DeleteObjects</code> API operation. The request will receive a <code>400 Bad Request</code> error
-   *       and none of the objects in the request will be deleted.</p>
+   *                <b>Directory buckets</b> - For directory buckets,
+   *             an object that's composed entirely of whitespace characters is not supported by the
+   *                <code>DeleteObjects</code> API operation. The request will receive a <code>400 Bad
+   *                Request</code> error and none of the objects in the request will be deleted.</p>
    *          </note>
    * @public
    */
@@ -5499,7 +5623,8 @@ export interface DeleteObjectsRequest {
   /**
    * <p>The bucket name containing the objects to delete. </p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -5529,11 +5654,12 @@ export interface DeleteObjectsRequest {
    * <p>The concatenation of the authentication device's serial number, a space, and the value
    *          that is displayed on your authentication device. Required to permanently delete a versioned
    *          object if versioning is configured with MFA delete enabled.</p>
-   *          <p>When performing the <code>DeleteObjects</code> operation on an MFA delete enabled bucket, which attempts to delete the specified
-   *          versioned objects, you must include an MFA token. If you don't provide an MFA token, the entire
-   *          request will fail, even if there are non-versioned objects that you are trying to delete. If you
-   *          provide an invalid token, whether there are versioned object keys in the request or not, the
-   *          entire Multi-Object Delete request will fail. For information about MFA Delete, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete"> MFA
+   *          <p>When performing the <code>DeleteObjects</code> operation on an MFA delete enabled
+   *          bucket, which attempts to delete the specified versioned objects, you must include an MFA
+   *          token. If you don't provide an MFA token, the entire request will fail, even if there are
+   *          non-versioned objects that you are trying to delete. If you provide an invalid token,
+   *          whether there are versioned object keys in the request or not, the entire Multi-Object
+   *          Delete request will fail. For information about MFA Delete, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete"> MFA
    *             Delete</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -5545,9 +5671,9 @@ export interface DeleteObjectsRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -5727,9 +5853,9 @@ export interface GetBucketAccelerateConfigurationRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -6154,25 +6280,28 @@ export interface GetBucketCorsRequest {
 /**
  * <p>Describes the default server-side encryption to apply to new objects in the bucket. If a
  *          PUT Object request doesn't specify any server-side encryption, this default encryption will
- *          be applied. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTencryption.html">PutBucketEncryption</a>.</p>
+ *          be applied. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTencryption.html">PutBucketEncryption</a>.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>General purpose buckets</b> - If you don't specify a customer managed key at configuration, Amazon S3 automatically creates
- *                   an Amazon Web Services KMS key (<code>aws/s3</code>) in your Amazon Web Services account the first time that you add an object encrypted
- *                   with SSE-KMS to a bucket. By default, Amazon S3 uses this KMS key for SSE-KMS. </p>
+ *                      <b>General purpose buckets</b> - If you don't specify
+ *                   a customer managed key at configuration, Amazon S3 automatically creates an Amazon Web Services KMS key
+ *                      (<code>aws/s3</code>) in your Amazon Web Services account the first time that you add an
+ *                   object encrypted with SSE-KMS to a bucket. By default, Amazon S3 uses this KMS key
+ *                   for SSE-KMS. </p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - 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 for the lifetime of the bucket.
+ *                      <b>Directory buckets</b> -
+ *                   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 for the lifetime of the bucket.
  * The <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported.
  * </p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.</p>
+ *                      <b>Directory buckets</b> -
+ *                   For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.</p>
  *                </li>
  *             </ul>
  *          </note>
@@ -6195,12 +6324,14 @@ export interface ServerSideEncryptionByDefault {
    *             <ul>
    *                <li>
    *                   <p>
-   *                      <b>General purpose buckets</b> - This parameter is allowed if and only if <code>SSEAlgorithm</code> is set to
-   *                   <code>aws:kms</code> or <code>aws:kms:dsse</code>.</p>
+   *                      <b>General purpose buckets</b> - This parameter is
+   *                   allowed if and only if <code>SSEAlgorithm</code> is set to <code>aws:kms</code> or
+   *                      <code>aws:kms:dsse</code>.</p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets</b> - This parameter is allowed if and only if <code>SSEAlgorithm</code> is set to
+   *                      <b>Directory buckets</b> - This parameter is
+   *                   allowed if and only if <code>SSEAlgorithm</code> is set to
    *                   <code>aws:kms</code>.</p>
    *                </li>
    *             </ul>
@@ -6213,7 +6344,8 @@ export interface ServerSideEncryptionByDefault {
    *                </p>
    *             </li>
    *             <li>
-   *                <p>Key ARN: <code>arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab</code>
+   *                <p>Key ARN:
+   *                   <code>arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab</code>
    *                </p>
    *             </li>
    *             <li>
@@ -6227,16 +6359,18 @@ export interface ServerSideEncryptionByDefault {
    *             <ul>
    *                <li>
    *                   <p>
-   *                      <b>General purpose buckets</b> - 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. Also, if you use a key ID, you can run into a LogDestination undeliverable error when creating
-   *                   a VPC flow log.
-   *                </p>
+   *                      <b>General purpose buckets</b> - 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. Also, if you
+   *                   use a key ID, you can run into a LogDestination undeliverable error when creating
+   *                   a VPC flow log. </p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets</b> - 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>
+   *                      <b>Directory buckets</b> -
+   *                   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>
    *             </ul>
    *          </note>
@@ -6255,14 +6389,16 @@ export interface ServerSideEncryptionByDefault {
  *             <ul>
  *                <li>
  *                   <p>
- *                      <b>General purpose buckets</b> - 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>
+ *                      <b>General purpose buckets</b> - 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>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - 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>
+ *                      <b>Directory buckets</b> -
+ *                   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>
  *             </ul>
  *          </note>
@@ -6286,12 +6422,14 @@ export interface ServerSideEncryptionRule {
    *             <ul>
    *                <li>
    *                   <p>
-   *                      <b>General purpose buckets</b> - By default, S3 Bucket Key is not enabled. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the
-   *                <i>Amazon S3 User Guide</i>.</p>
+   *                      <b>General purpose buckets</b> - By default, S3
+   *                   Bucket Key is not enabled. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the
+   *                      <i>Amazon S3 User Guide</i>.</p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets</b> - S3 Bucket Keys are always enabled for <code>GET</code> and <code>PUT</code> operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
+   *                      <b>Directory buckets</b> -
+   *                   S3 Bucket Keys are always enabled for <code>GET</code> and <code>PUT</code> operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
    * to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a>, <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>, <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-objects-Batch-Ops">the Copy operation in Batch Operations</a>, or
    *                             <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-import-job">the import jobs</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>
    *                </li>
@@ -6821,6 +6959,10 @@ export interface LifecycleExpiration {
   /**
    * <p>Indicates at what date the object is to be moved or deleted. The date value must conform
    *          to the ISO 8601 format. The time is always midnight UTC.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   Date?: Date | undefined;
@@ -6836,6 +6978,10 @@ export interface LifecycleExpiration {
    * <p>Indicates whether Amazon S3 will remove a delete marker with no noncurrent versions. If set
    *          to true, the delete marker will be expired; if set to false the policy takes no action.
    *          This cannot be specified with Days or Date in a Lifecycle Expiration Policy.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   ExpiredObjectDeleteMarker?: boolean | undefined;
@@ -6876,8 +7022,10 @@ export interface LifecycleRuleAndOperator {
 
 /**
  * <p>The <code>Filter</code> is used to identify objects that a Lifecycle Rule applies to. A
- *          <code>Filter</code> can have exactly one of <code>Prefix</code>, <code>Tag</code>, <code>ObjectSizeGreaterThan</code>, <code>ObjectSizeLessThan</code>, or
- *          <code>And</code> specified. If the <code>Filter</code> element is left empty, the Lifecycle Rule applies to all objects in the bucket.</p>
+ *             <code>Filter</code> can have exactly one of <code>Prefix</code>, <code>Tag</code>,
+ *             <code>ObjectSizeGreaterThan</code>, <code>ObjectSizeLessThan</code>, or <code>And</code>
+ *          specified. If the <code>Filter</code> element is left empty, the Lifecycle Rule applies to
+ *          all objects in the bucket.</p>
  * @public
  */
 export interface LifecycleRuleFilter {
@@ -6894,6 +7042,10 @@ export interface LifecycleRuleFilter {
 
   /**
    * <p>This tag must exist in the object's tag set in order for the rule to apply.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   Tag?: Tag | undefined;
@@ -6924,6 +7076,10 @@ export interface LifecycleRuleFilter {
  *          deletes the noncurrent object versions. You set this lifecycle configuration action on a
  *          bucket that has versioning enabled (or suspended) to request that Amazon S3 delete noncurrent
  *          object versions at a specific period in the object's lifetime.</p>
+ *          <note>
+ *             <p>This parameter applies to general purpose buckets only. It is not supported for
+ *             directory bucket lifecycle configurations.</p>
+ *          </note>
  * @public
  */
 export interface NoncurrentVersionExpiration {
@@ -6933,6 +7089,10 @@ export interface NoncurrentVersionExpiration {
    *          noncurrent days calculations, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#non-current-days-calculations">How
    *             Amazon S3 Calculates When an Object Became Noncurrent</a> in the
    *             <i>Amazon S3 User Guide</i>.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   NoncurrentDays?: number | undefined;
@@ -6943,6 +7103,10 @@ export interface NoncurrentVersionExpiration {
    *          versions beyond the specified number to retain. For more information about noncurrent
    *          versions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html">Lifecycle configuration
    *             elements</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   NewerNoncurrentVersions?: number | undefined;
@@ -7085,6 +7249,10 @@ export interface LifecycleRule {
    *             <code>Filter</code> must have exactly one of <code>Prefix</code>, <code>Tag</code>, or
    *             <code>And</code> specified. <code>Filter</code> is required if the
    *             <code>LifecycleRule</code> does not contain a <code>Prefix</code> element.</p>
+   *          <note>
+   *             <p>
+   *                <code>Tag</code> filters are not supported for directory buckets.</p>
+   *          </note>
    * @public
    */
   Filter?: LifecycleRuleFilter | undefined;
@@ -7098,16 +7266,24 @@ export interface LifecycleRule {
 
   /**
    * <p>Specifies when an Amazon S3 object transitions to a specified storage class.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   Transitions?: Transition[] | undefined;
 
   /**
-   * <p> Specifies the transition rule for the lifecycle rule that describes when noncurrent
+   * <p>Specifies the transition rule for the lifecycle rule that describes when noncurrent
    *          objects transition to a specific storage class. If your bucket is versioning-enabled (or
    *          versioning is suspended), you can set this action to request that Amazon S3 transition
    *          noncurrent object versions to a specific storage class at a set period in the object's
-   *          lifetime. </p>
+   *          lifetime.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   NoncurrentVersionTransitions?: NoncurrentVersionTransition[] | undefined;
@@ -7117,6 +7293,10 @@ export interface LifecycleRule {
    *          deletes the noncurrent object versions. You set this lifecycle configuration action on a
    *          bucket that has versioning enabled (or suspended) to request that Amazon S3 delete noncurrent
    *          object versions at a specific period in the object's lifetime.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   NoncurrentVersionExpiration?: NoncurrentVersionExpiration | undefined;
@@ -7157,19 +7337,30 @@ export interface GetBucketLifecycleConfigurationOutput {
   Rules?: LifecycleRule[] | undefined;
 
   /**
-   * <p>Indicates which default minimum object size behavior is applied to the lifecycle configuration.</p>
+   * <p>Indicates which default minimum object size behavior is applied to the lifecycle
+   *          configuration.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not transition to any storage class by default. </p>
+   *                   <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not
+   *                transition to any storage class by default.</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>varies_by_storage_class</code> - Objects smaller than 128 KB will transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes will prevent transitions smaller than 128 KB.
-   *          </p>
+   *                   <code>varies_by_storage_class</code> - Objects smaller than 128 KB will
+   *                transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By
+   *                default, all other storage classes will prevent transitions smaller than 128 KB.
+   *             </p>
    *             </li>
    *          </ul>
-   *          <p>To customize the minimum object size for any transition you can add a filter that specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in the body of your transition rule.  Custom filters always take precedence over the default transition behavior.</p>
+   *          <p>To customize the minimum object size for any transition you can add a filter that
+   *          specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in
+   *          the body of your transition rule. Custom filters always take precedence over the default
+   *          transition behavior.</p>
    * @public
    */
   TransitionDefaultMinimumObjectSize?: TransitionDefaultMinimumObjectSize | undefined;
@@ -7189,6 +7380,10 @@ export interface GetBucketLifecycleConfigurationRequest {
 
   /**
    * <p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   ExpectedBucketOwner?: string | undefined;
@@ -7286,14 +7481,15 @@ export type PartitionDateSource = (typeof PartitionDateSource)[keyof typeof Part
  *          <p>
  *             <code>[DestinationPrefix][SourceAccountId]/[SourceRegion]/[SourceBucket]/[YYYY]/[MM]/[DD]/[YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]</code>
  *          </p>
- *          <p>PartitionedPrefix defaults to EventTime delivery when server access logs are delivered.</p>
+ *          <p>PartitionedPrefix defaults to EventTime delivery when server access logs are
+ *          delivered.</p>
  * @public
  */
 export interface PartitionedPrefix {
   /**
    * <p>Specifies the partition date source for the partitioned prefix.
-   *          <code>PartitionDateSource</code> can be <code>EventTime</code> or
-   *          <code>DeliveryTime</code>.</p>
+   *             <code>PartitionDateSource</code> can be <code>EventTime</code> or
+   *             <code>DeliveryTime</code>.</p>
    *          <p>For <code>DeliveryTime</code>, the time in the log file names corresponds to the
    *          delivery time for the log files. </p>
    *          <p> For <code>EventTime</code>, The logs delivered are for a specific day only. The year,
@@ -7305,7 +7501,8 @@ export interface PartitionedPrefix {
 }
 
 /**
- * <p>To use simple format for S3 keys for log objects, set SimplePrefix to an empty object.</p>
+ * <p>To use simple format for S3 keys for log objects, set SimplePrefix to an empty
+ *          object.</p>
  *          <p>
  *             <code>[DestinationPrefix][YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]</code>
  *          </p>
@@ -7314,12 +7511,14 @@ export interface PartitionedPrefix {
 export interface SimplePrefix {}
 
 /**
- * <p>Amazon S3 key format for log objects. Only one format, PartitionedPrefix or SimplePrefix, is allowed.</p>
+ * <p>Amazon S3 key format for log objects. Only one format, PartitionedPrefix or
+ *          SimplePrefix, is allowed.</p>
  * @public
  */
 export interface TargetObjectKeyFormat {
   /**
-   * <p>To use the simple format for S3 keys for log objects. To specify SimplePrefix format, set SimplePrefix to \{\}.</p>
+   * <p>To use the simple format for S3 keys for log objects. To specify SimplePrefix format,
+   *          set SimplePrefix to \{\}.</p>
    * @public
    */
   SimplePrefix?: SimplePrefix | undefined;
@@ -7671,7 +7870,14 @@ export const FilterRuleName = {
 export type FilterRuleName = (typeof FilterRuleName)[keyof typeof FilterRuleName];
 
 /**
- * <p>Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned to an object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of the object key name. A prefix is a specific string of characters at the beginning of an object key name, which you can use to organize objects. For example, you can start the key names of related objects with a prefix, such as <code>2023-</code> or  <code>engineering/</code>. Then, you can use <code>FilterRule</code> to find objects in a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it is at the end of the object key name instead of at the beginning.</p>
+ * <p>Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned
+ *          to an object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of
+ *          the object key name. A prefix is a specific string of characters at the beginning of an
+ *          object key name, which you can use to organize objects. For example, you can start the key
+ *          names of related objects with a prefix, such as <code>2023-</code> or
+ *             <code>engineering/</code>. Then, you can use <code>FilterRule</code> to find objects in
+ *          a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it
+ *          is at the end of the object key name instead of at the beginning.</p>
  * @public
  */
 export interface FilterRule {
@@ -7872,22 +8078,25 @@ export interface OwnershipControlsRule {
   /**
    * <p>The container element for object ownership for a bucket's ownership controls.</p>
    *          <p>
-   *             <code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket
-   *          owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned
-   *          ACL.</p>
+   *             <code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to
+   *          the bucket owner if the objects are uploaded with the
+   *             <code>bucket-owner-full-control</code> canned ACL.</p>
    *          <p>
-   *             <code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with
-   *          the <code>bucket-owner-full-control</code> canned ACL.</p>
+   *             <code>ObjectWriter</code> - The uploading account will own the object if the object is
+   *          uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>
    *          <p>
-   *             <code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect
-   *          permissions. The bucket owner automatically owns and has full control over every object in
-   *          the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner
-   *          full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL
-   *          in XML format that grants the same permissions).</p>
-   *          <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend
-   *       keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see
-   *       <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.
-   *       </p>
+   *             <code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no
+   *          longer affect permissions. The bucket owner automatically owns and has full control over
+   *          every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL
+   *          or specify bucket owner full control ACLs (such as the predefined
+   *             <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that
+   *          grants the same permissions).</p>
+   *          <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and
+   *          ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where
+   *          you must control access for each object individually. For more information about S3 Object
+   *          Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling ownership of
+   *             objects and disabling ACLs for your bucket</a> in the
+   *             <i>Amazon S3 User Guide</i>. </p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>
    *          </note>
@@ -8078,10 +8287,10 @@ export interface DeleteMarkerReplication {
  * <p>Specifies encryption-related information for an Amazon S3 bucket that is a destination for
  *          replicated objects.</p>
  *          <note>
- *             <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>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>
  *          </note>
  * @public
  */
@@ -8264,10 +8473,10 @@ export type ExistingObjectReplicationStatus =
   (typeof ExistingObjectReplicationStatus)[keyof typeof ExistingObjectReplicationStatus];
 
 /**
- * <p>Optional configuration to replicate existing source bucket objects.
- *       </p>
+ * <p>Optional configuration to replicate existing source bucket objects. </p>
  *          <note>
- *             <p>This parameter is no longer supported. To replicate existing objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html">Replicating existing objects with S3 Batch Replication</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *             <p>This parameter is no longer supported. To replicate existing objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html">Replicating existing objects with S3 Batch Replication</a> in the
+ *                <i>Amazon S3 User Guide</i>.</p>
  *          </note>
  * @public
  */
@@ -8527,10 +8736,10 @@ export interface ReplicationRule {
   SourceSelectionCriteria?: SourceSelectionCriteria | undefined;
 
   /**
-   * <p>Optional configuration to replicate existing source bucket objects.
-   *       </p>
+   * <p>Optional configuration to replicate existing source bucket objects. </p>
    *          <note>
-   *             <p>This parameter is no longer supported. To replicate existing objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html">Replicating existing objects with S3 Batch Replication</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             <p>This parameter is no longer supported. To replicate existing objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html">Replicating existing objects with S3 Batch Replication</a> in the
+   *                <i>Amazon S3 User Guide</i>.</p>
    *          </note>
    * @public
    */
@@ -9027,10 +9236,14 @@ export interface GetObjectOutput {
    *          <note>
    *             <ul>
    *                <li>
-   *                   <p>If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes <code>x-amz-delete-marker: true</code> in the response.</p>
+   *                   <p>If the current version of the object is a delete marker, Amazon S3 behaves as if the
+   *                   object was deleted and includes <code>x-amz-delete-marker: true</code> in the
+   *                   response.</p>
    *                </li>
    *                <li>
-   *                   <p>If the specified version in the request is a delete marker, the response returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified: timestamp</code> response header.</p>
+   *                   <p>If the specified version in the request is a delete marker, the response
+   *                   returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified:
+   *                      timestamp</code> response header.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -9047,9 +9260,9 @@ export interface GetObjectOutput {
   /**
    * <p>If the object expiration is configured (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html">
    *                <code>PutBucketLifecycleConfiguration</code>
-   *             </a>), the response includes
-   *          this header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value
-   *          pairs providing object expiration information. The value of the <code>rule-id</code> is
+   *             </a>), the response includes this
+   *          header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value pairs
+   *          providing object expiration information. The value of the <code>rule-id</code> is
    *          URL-encoded.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -9062,7 +9275,8 @@ export interface GetObjectOutput {
    * <p>Provides information about object restoration action and expiration time of the restored
    *          object copy.</p>
    *          <note>
-   *             <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *             <p>This functionality is not supported for directory buckets.
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -9071,7 +9285,10 @@ export interface GetObjectOutput {
   /**
    * <p>Date and time when the object was last modified.</p>
    *          <p>
-   *             <b>General purpose buckets </b> - When you specify a <code>versionId</code> of the object in your request, if the specified version in the request is a delete marker, the response returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified: timestamp</code> response header.</p>
+   *             <b>General purpose buckets </b> - When you specify a
+   *             <code>versionId</code> of the object in your request, if the specified version in the
+   *          request is a delete marker, the response returns a <code>405 Method Not Allowed</code>
+   *          error and the <code>Last-Modified: timestamp</code> response header.</p>
    * @public
    */
   LastModified?: Date | undefined;
@@ -9122,9 +9339,10 @@ export interface GetObjectOutput {
   ChecksumSHA256?: string | undefined;
 
   /**
-   * <p>This is set to the number of metadata entries not returned in the headers that are prefixed with <code>x-amz-meta-</code>. This can happen if you create metadata using an API like SOAP that supports more
-   *          flexible metadata than the REST API. For example, using SOAP, you can create metadata whose
-   *          values are not legal HTTP headers.</p>
+   * <p>This is set to the number of metadata entries not returned in the headers that are
+   *          prefixed with <code>x-amz-meta-</code>. This can happen if you create metadata using an API
+   *          like SOAP that supports more flexible metadata than the REST API. For example, using SOAP,
+   *          you can create metadata whose values are not legal HTTP headers.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -9228,8 +9446,8 @@ export interface GetObjectOutput {
 
   /**
    * <p>If server-side encryption with a customer-provided encryption key was requested, the
-   *          response will include this header to provide the round-trip message integrity verification of
-   *          the customer-provided encryption key.</p>
+   *          response will include this header to provide the round-trip message integrity verification
+   *          of the customer-provided encryption key.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -9244,8 +9462,8 @@ export interface GetObjectOutput {
   SSEKMSKeyId?: string | undefined;
 
   /**
-   * <p>Indicates whether the object uses an S3 Bucket Key for server-side encryption
-   *          with Key Management Service (KMS) keys (SSE-KMS).</p>
+   * <p>Indicates whether the object uses an S3 Bucket Key for server-side encryption with
+   *          Key Management Service (KMS) keys (SSE-KMS).</p>
    * @public
    */
   BucketKeyEnabled?: boolean | undefined;
@@ -9255,7 +9473,8 @@ export interface GetObjectOutput {
    *          objects except for S3 Standard storage class objects.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets </b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *                <b>Directory buckets </b> -
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -9290,7 +9509,8 @@ export interface GetObjectOutput {
   PartsCount?: number | undefined;
 
   /**
-   * <p>The number of tags, if any, on the object, when you have the relevant permission to read object tags.</p>
+   * <p>The number of tags, if any, on the object, when you have the relevant permission to read
+   *          object tags.</p>
    *          <p>You can use <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html">GetObjectTagging</a> to retrieve
    *          the tag set associated with an object.</p>
    *          <note>
@@ -9349,7 +9569,8 @@ export interface GetObjectRequest {
   /**
    * <p>The bucket name containing the object. </p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -9372,10 +9593,12 @@ export interface GetObjectRequest {
   Bucket: string | undefined;
 
   /**
-   * <p>Return the object only if its entity tag (ETag) is the same as the one specified in this header;
-   *          otherwise, return a <code>412 Precondition Failed</code> error.</p>
-   *          <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are present in the request as follows: <code>If-Match</code> condition
-   *          evaluates to <code>true</code>, and; <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>
+   * <p>Return the object only if its entity tag (ETag) is the same as the one specified in this
+   *          header; otherwise, return a <code>412 Precondition Failed</code> error.</p>
+   *          <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are
+   *          present in the request as follows: <code>If-Match</code> condition evaluates to
+   *             <code>true</code>, and; <code>If-Unmodified-Since</code> condition evaluates to
+   *             <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>
    *          <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>.</p>
    * @public
    */
@@ -9384,21 +9607,23 @@ export interface GetObjectRequest {
   /**
    * <p>Return the object only if it has been modified since the specified time; otherwise,
    *          return a <code>304 Not Modified</code> error.</p>
-   *          <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are present in the request as follows:<code> If-None-Match</code>
-   *          condition evaluates to <code>false</code>, and; <code>If-Modified-Since</code> condition evaluates to <code>true</code>; then, S3 returns <code>304 Not Modified</code>
-   *                   status code.</p>
+   *          <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are
+   *          present in the request as follows:<code> If-None-Match</code> condition evaluates to
+   *             <code>false</code>, and; <code>If-Modified-Since</code> condition evaluates to
+   *             <code>true</code>; then, S3 returns <code>304 Not Modified</code> status code.</p>
    *          <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>.</p>
    * @public
    */
   IfModifiedSince?: Date | undefined;
 
   /**
-   * <p>Return the object only if its entity tag (ETag) is different from the one specified in this header;
-   *          otherwise, return a <code>304 Not Modified</code> error.</p>
-   *          <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code>
-   *          headers are present in the request as follows:<code> If-None-Match</code>
-   *          condition evaluates to <code>false</code>, and; <code>If-Modified-Since</code>
-   *          condition evaluates to <code>true</code>; then, S3 returns <code>304 Not Modified</code> HTTP status code.</p>
+   * <p>Return the object only if its entity tag (ETag) is different from the one specified in
+   *          this header; otherwise, return a <code>304 Not Modified</code> error.</p>
+   *          <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are
+   *          present in the request as follows:<code> If-None-Match</code> condition evaluates to
+   *             <code>false</code>, and; <code>If-Modified-Since</code> condition evaluates to
+   *             <code>true</code>; then, S3 returns <code>304 Not Modified</code> HTTP status
+   *          code.</p>
    *          <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>.</p>
    * @public
    */
@@ -9407,10 +9632,10 @@ export interface GetObjectRequest {
   /**
    * <p>Return the object only if it has not been modified since the specified time; otherwise,
    *          return a <code>412 Precondition Failed</code> error.</p>
-   *          <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code>
-   *                   headers are present in the request as follows: <code>If-Match</code> condition
-   *                   evaluates to <code>true</code>, and; <code>If-Unmodified-Since</code> condition
-   *                   evaluates to <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>
+   *          <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are
+   *          present in the request as follows: <code>If-Match</code> condition evaluates to
+   *             <code>true</code>, and; <code>If-Unmodified-Since</code> condition evaluates to
+   *             <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>
    *          <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>.</p>
    * @public
    */
@@ -9471,19 +9696,28 @@ export interface GetObjectRequest {
 
   /**
    * <p>Version ID used to reference a specific version of the object.</p>
-   *          <p>By default, the <code>GetObject</code> operation returns the current version of an object. To return a different version, use the <code>versionId</code> subresource.</p>
+   *          <p>By default, the <code>GetObject</code> operation returns the current version of an
+   *          object. To return a different version, use the <code>versionId</code> subresource.</p>
    *          <note>
    *             <ul>
    *                <li>
-   *                   <p>If you include a <code>versionId</code> in your request header, you must have the <code>s3:GetObjectVersion</code> permission to access a specific version of an object. The <code>s3:GetObject</code> permission is not required in this scenario.</p>
+   *                   <p>If you include a <code>versionId</code> in your request header, you must have
+   *                   the <code>s3:GetObjectVersion</code> permission to access a specific version of an
+   *                   object. The <code>s3:GetObject</code> permission is not required in this
+   *                   scenario.</p>
    *                </li>
    *                <li>
-   *                   <p>If you request the current version of an object without a specific <code>versionId</code> in the request header, only the <code>s3:GetObject</code> permission is required. The <code>s3:GetObjectVersion</code> permission is not required in this scenario.</p>
+   *                   <p>If you request the current version of an object without a specific
+   *                      <code>versionId</code> in the request header, only the
+   *                      <code>s3:GetObject</code> permission is required. The
+   *                      <code>s3:GetObjectVersion</code> permission is not required in this
+   *                   scenario.</p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code>
-   *                   to the <code>versionId</code> query parameter in the request.</p>
+   *                      <b>Directory buckets</b> -
+   *                   S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> to the
+   *                      <code>versionId</code> query parameter in the request.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -9494,7 +9728,7 @@ export interface GetObjectRequest {
 
   /**
    * <p>Specifies the algorithm to use when decrypting the object (for example,
-   *          <code>AES256</code>).</p>
+   *             <code>AES256</code>).</p>
    *          <p>If you encrypt an object by using server-side encryption with customer-provided
    *          encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,
    *          you must use the following headers:</p>
@@ -9516,7 +9750,8 @@ export interface GetObjectRequest {
    *             </li>
    *          </ul>
    *          <p>For more information about SSE-C, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html">Server-Side Encryption
-   *          (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             (Using Customer-Provided Encryption Keys)</a> in the
+   *             <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -9525,9 +9760,10 @@ export interface GetObjectRequest {
   SSECustomerAlgorithm?: string | undefined;
 
   /**
-   * <p>Specifies the customer-provided encryption key that you originally provided for Amazon S3 to encrypt the data before storing it. This
-   *          value is used to decrypt the object when recovering it and must match the one used when
-   *          storing the data. The key must be appropriate for use with the algorithm specified in the
+   * <p>Specifies the customer-provided encryption key that you originally provided for Amazon S3 to
+   *          encrypt the data before storing it. This value is used to decrypt the object when
+   *          recovering it and must match the one used when storing the data. The key must be
+   *          appropriate for use with the algorithm specified in the
    *             <code>x-amz-server-side-encryption-customer-algorithm</code> header.</p>
    *          <p>If you encrypt an object by using server-side encryption with customer-provided
    *          encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,
@@ -9550,7 +9786,8 @@ export interface GetObjectRequest {
    *             </li>
    *          </ul>
    *          <p>For more information about SSE-C, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html">Server-Side Encryption
-   *          (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             (Using Customer-Provided Encryption Keys)</a> in the
+   *             <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -9559,9 +9796,9 @@ export interface GetObjectRequest {
   SSECustomerKey?: string | undefined;
 
   /**
-   * <p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to RFC 1321. Amazon S3 uses
-   *          this header for a message integrity check to ensure that the encryption key was transmitted
-   *          without error.</p>
+   * <p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to
+   *          RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption
+   *          key was transmitted without error.</p>
    *          <p>If you encrypt an object by using server-side encryption with customer-provided
    *          encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,
    *          you must use the following headers:</p>
@@ -9583,7 +9820,8 @@ export interface GetObjectRequest {
    *             </li>
    *          </ul>
    *          <p>For more information about SSE-C, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html">Server-Side Encryption
-   *          (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             (Using Customer-Provided Encryption Keys)</a> in the
+   *             <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -9594,9 +9832,9 @@ export interface GetObjectRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -9622,10 +9860,10 @@ export interface GetObjectRequest {
   /**
    * <p>To retrieve the checksum, this mode must be enabled.</p>
    *          <p>
-   *             <b>General purpose buckets</b> - In addition, if you enable checksum mode and the object is uploaded with a
-   *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html">checksum</a>
-   *          and encrypted with an Key Management Service (KMS) key, you must have permission to use the
-   *          <code>kms:Decrypt</code> action to retrieve the checksum.</p>
+   *             <b>General purpose buckets</b> - In addition, if you enable
+   *          checksum mode and the object is uploaded with a <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html">checksum</a> and encrypted with an
+   *          Key Management Service (KMS) key, you must have permission to use the <code>kms:Decrypt</code> action
+   *          to retrieve the checksum.</p>
    * @public
    */
   ChecksumMode?: ChecksumMode | undefined;
@@ -9633,13 +9871,13 @@ export interface GetObjectRequest {
 
 /**
  * <p>Object is archived and inaccessible until restored.</p>
- *          <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the
- *          S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the
- *          S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a
- *          copy using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a>. Otherwise, this operation returns an
- *          <code>InvalidObjectState</code> error. For information about restoring archived objects,
- *          see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html">Restoring
- *             Archived Objects</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage
+ *          class, the S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access
+ *          tier, or the S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you
+ *          must first restore a copy using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a>. Otherwise, this
+ *          operation returns an <code>InvalidObjectState</code> error. For information about restoring
+ *          archived objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html">Restoring Archived Objects</a> in
+ *          the <i>Amazon S3 User Guide</i>.</p>
  * @public
  */
 export class InvalidObjectState extends __BaseException {
@@ -9741,9 +9979,9 @@ export interface GetObjectAclRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -9902,13 +10140,19 @@ export interface GetObjectAttributesParts {
    *             <ul>
    *                <li>
    *                   <p>
-   *                      <b>General purpose buckets</b> - For <code>GetObjectAttributes</code>, if a additional checksum (including <code>x-amz-checksum-crc32</code>,
-   *                <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or
-   *                <code>x-amz-checksum-sha256</code>) isn't applied to the object specified in the request, the response doesn't return <code>Part</code>.</p>
+   *                      <b>General purpose buckets</b> - For
+   *                      <code>GetObjectAttributes</code>, if a additional checksum (including
+   *                      <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>,
+   *                      <code>x-amz-checksum-sha1</code>, or <code>x-amz-checksum-sha256</code>) isn't
+   *                   applied to the object specified in the request, the response doesn't return
+   *                      <code>Part</code>.</p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets</b> - For <code>GetObjectAttributes</code>, no matter whether a additional checksum is applied to the object specified in the request, the response returns <code>Part</code>.</p>
+   *                      <b>Directory buckets</b> - For
+   *                      <code>GetObjectAttributes</code>, no matter whether a additional checksum is
+   *                   applied to the object specified in the request, the response returns
+   *                      <code>Part</code>.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -9933,7 +10177,7 @@ export interface GetObjectAttributesOutput {
   DeleteMarker?: boolean | undefined;
 
   /**
-   * <p>The creation date of the object.</p>
+   * <p>Date and time when the object was last modified.</p>
    * @public
    */
   LastModified?: Date | undefined;
@@ -9982,7 +10226,8 @@ export interface GetObjectAttributesOutput {
    *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a>.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *                <b>Directory buckets</b> -
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -10019,7 +10264,8 @@ export interface GetObjectAttributesRequest {
   /**
    * <p>The name of the bucket that contains the object.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -10048,8 +10294,8 @@ export interface GetObjectAttributesRequest {
   /**
    * <p>The version ID used to reference a specific version of the object.</p>
    *          <note>
-   *             <p>S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code>
-   *          to the <code>versionId</code> query parameter in the request.</p>
+   *             <p>S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> to the
+   *                <code>versionId</code> query parameter in the request.</p>
    *          </note>
    * @public
    */
@@ -10103,9 +10349,9 @@ export interface GetObjectAttributesRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -10180,9 +10426,9 @@ export interface GetObjectLegalHoldRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -10226,8 +10472,8 @@ export const ObjectLockRetentionMode = {
 export type ObjectLockRetentionMode = (typeof ObjectLockRetentionMode)[keyof typeof ObjectLockRetentionMode];
 
 /**
- * <p>The container element for optionally specifying the default Object Lock retention settings for new
- *          objects placed in the specified bucket.</p>
+ * <p>The container element for optionally specifying the default Object Lock retention
+ *          settings for new objects placed in the specified bucket.</p>
  *          <note>
  *             <ul>
  *                <li>
@@ -10395,9 +10641,9 @@ export interface GetObjectRetentionRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -10468,9 +10714,9 @@ export interface GetObjectTaggingRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -10522,9 +10768,9 @@ export interface GetObjectTorrentRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -10646,7 +10892,8 @@ export interface HeadBucketOutput {
 
   /**
    * <p>The name of the location where the bucket will be created.</p>
-   *          <p>For directory buckets, the AZ ID of the Availability Zone where the bucket is created. An example AZ ID value is <code>usw2-az1</code>.</p>
+   *          <p>For directory buckets, the AZ ID of the Availability Zone where the bucket is created. An example
+   *          AZ ID value is <code>usw2-az1</code>.</p>
    *          <note>
    *             <p>This functionality is only supported by directory buckets.</p>
    *          </note>
@@ -10677,7 +10924,8 @@ export interface HeadBucketRequest {
   /**
    * <p>The bucket name.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -10766,9 +11014,9 @@ export interface HeadObjectOutput {
   /**
    * <p>If the object expiration is configured (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html">
    *                <code>PutBucketLifecycleConfiguration</code>
-   *             </a>), the response includes
-   *          this header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value
-   *          pairs providing object expiration information. The value of the <code>rule-id</code> is
+   *             </a>), the response includes this
+   *          header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value pairs
+   *          providing object expiration information. The value of the <code>rule-id</code> is
    *          URL-encoded.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -10790,7 +11038,8 @@ export interface HeadObjectOutput {
    *             <code>ongoing-request="true"</code>.</p>
    *          <p>For more information about archiving objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html#lifecycle-transition-general-considerations">Transitioning Objects: General Considerations</a>.</p>
    *          <note>
-   *             <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *             <p>This functionality is not supported for directory buckets.
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -10939,8 +11188,8 @@ export interface HeadObjectOutput {
   WebsiteRedirectLocation?: string | undefined;
 
   /**
-   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,
-   *             <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>
+   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for
+   *          example, <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>
    * @public
    */
   ServerSideEncryption?: ServerSideEncryption | undefined;
@@ -10963,8 +11212,8 @@ export interface HeadObjectOutput {
 
   /**
    * <p>If server-side encryption with a customer-provided encryption key was requested, the
-   *          response will include this header to provide the round-trip message integrity verification of
-   *          the customer-provided encryption key.</p>
+   *          response will include this header to provide the round-trip message integrity verification
+   *          of the customer-provided encryption key.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -10979,8 +11228,8 @@ export interface HeadObjectOutput {
   SSEKMSKeyId?: string | undefined;
 
   /**
-   * <p>Indicates whether the object uses an S3 Bucket Key for server-side encryption
-   *          with Key Management Service (KMS) keys (SSE-KMS).</p>
+   * <p>Indicates whether the object uses an S3 Bucket Key for server-side encryption with
+   *          Key Management Service (KMS) keys (SSE-KMS).</p>
    * @public
    */
   BucketKeyEnabled?: boolean | undefined;
@@ -10991,7 +11240,8 @@ export interface HeadObjectOutput {
    *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a>.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets </b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *                <b>Directory buckets </b> -
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -11103,7 +11353,8 @@ export interface HeadObjectRequest {
   /**
    * <p>The name of the bucket that contains the object.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -11126,9 +11377,8 @@ export interface HeadObjectRequest {
   /**
    * <p>Return the object only if its entity tag (ETag) is the same as the one specified;
    *          otherwise, return a 412 (precondition failed) error.</p>
-   *          <p>If both of the <code>If-Match</code> and
-   *          <code>If-Unmodified-Since</code> headers are present in the request as
-   *          follows:</p>
+   *          <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are
+   *          present in the request as follows:</p>
    *          <ul>
    *             <li>
    *                <p>
@@ -11136,8 +11386,7 @@ export interface HeadObjectRequest {
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>If-Unmodified-Since</code> condition evaluates to
-   *                <code>false</code>;</p>
+   *                   <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>;</p>
    *             </li>
    *          </ul>
    *          <p>Then Amazon S3 returns <code>200 OK</code> and the data requested.</p>
@@ -11149,19 +11398,16 @@ export interface HeadObjectRequest {
   /**
    * <p>Return the object only if it has been modified since the specified time; otherwise,
    *          return a 304 (not modified) error.</p>
-   *          <p>If both of the <code>If-None-Match</code> and
-   *          <code>If-Modified-Since</code> headers are present in the request as
-   *          follows:</p>
+   *          <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are
+   *          present in the request as follows:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>If-None-Match</code> condition evaluates to <code>false</code>,
-   *                and;</p>
+   *                   <code>If-None-Match</code> condition evaluates to <code>false</code>, and;</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>If-Modified-Since</code> condition evaluates to
-   *                <code>true</code>;</p>
+   *                   <code>If-Modified-Since</code> condition evaluates to <code>true</code>;</p>
    *             </li>
    *          </ul>
    *          <p>Then Amazon S3 returns the <code>304 Not Modified</code> response code.</p>
@@ -11173,19 +11419,16 @@ export interface HeadObjectRequest {
   /**
    * <p>Return the object only if its entity tag (ETag) is different from the one specified;
    *          otherwise, return a 304 (not modified) error.</p>
-   *          <p>If both of the <code>If-None-Match</code> and
-   *          <code>If-Modified-Since</code> headers are present in the request as
-   *          follows:</p>
+   *          <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are
+   *          present in the request as follows:</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>If-None-Match</code> condition evaluates to <code>false</code>,
-   *                and;</p>
+   *                   <code>If-None-Match</code> condition evaluates to <code>false</code>, and;</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>If-Modified-Since</code> condition evaluates to
-   *                <code>true</code>;</p>
+   *                   <code>If-Modified-Since</code> condition evaluates to <code>true</code>;</p>
    *             </li>
    *          </ul>
    *          <p>Then Amazon S3 returns the <code>304 Not Modified</code> response code.</p>
@@ -11197,9 +11440,8 @@ export interface HeadObjectRequest {
   /**
    * <p>Return the object only if it has not been modified since the specified time; otherwise,
    *          return a 412 (precondition failed) error.</p>
-   *          <p>If both of the <code>If-Match</code> and
-   *          <code>If-Unmodified-Since</code> headers are present in the request as
-   *          follows:</p>
+   *          <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are
+   *          present in the request as follows:</p>
    *          <ul>
    *             <li>
    *                <p>
@@ -11207,8 +11449,7 @@ export interface HeadObjectRequest {
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>If-Unmodified-Since</code> condition evaluates to
-   *                <code>false</code>;</p>
+   *                   <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>;</p>
    *             </li>
    *          </ul>
    *          <p>Then Amazon S3 returns <code>200 OK</code> and the data requested.</p>
@@ -11277,8 +11518,7 @@ export interface HeadObjectRequest {
   VersionId?: string | undefined;
 
   /**
-   * <p>Specifies the algorithm to use when encrypting the object (for example,
-   *          AES256).</p>
+   * <p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -11312,9 +11552,9 @@ export interface HeadObjectRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -11340,14 +11580,17 @@ export interface HeadObjectRequest {
   /**
    * <p>To retrieve the checksum, this parameter must be enabled.</p>
    *          <p>
-   *             <b>General purpose buckets</b> - If you enable checksum mode and the object is uploaded with a
-   *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html">checksum</a>
+   *             <b>General purpose buckets</b> -
+   *          If you enable checksum mode and the object is uploaded with a
+   *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html">checksum</a>
    *          and encrypted with an Key Management Service (KMS) key, you must have permission to use the
-   *          <code>kms:Decrypt</code> action to retrieve the checksum.</p>
+   *             <code>kms:Decrypt</code> action to retrieve the checksum.</p>
    *          <p>
-   *             <b>Directory buckets</b> - If you enable <code>ChecksumMode</code> and the object is encrypted with
-   *          Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the
-   *          <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key to retrieve the checksum of the object.</p>
+   *             <b>Directory buckets</b> - If you enable
+   *             <code>ChecksumMode</code> and the object is encrypted with Amazon Web Services Key Management Service
+   *          (Amazon Web Services KMS), you must also have the <code>kms:GenerateDataKey</code> and
+   *             <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key
+   *          policies for the KMS key to retrieve the checksum of the object.</p>
    * @public
    */
   ChecksumMode?: ChecksumMode | undefined;
@@ -11595,7 +11838,7 @@ export interface ListBucketMetricsConfigurationsRequest {
 }
 
 /**
- * <p> In terms of implementation, a Bucket is a resource.  </p>
+ * <p> In terms of implementation, a Bucket is a resource. </p>
  * @public
  */
 export interface Bucket {
@@ -11614,7 +11857,8 @@ export interface Bucket {
 
   /**
    * <p>
-   *             <code>BucketRegion</code> indicates the Amazon Web Services region where the bucket is located. If the request contains at least one valid parameter, it is included in the response.</p>
+   *             <code>BucketRegion</code> indicates the Amazon Web Services region where the bucket is located. If the
+   *          request contains at least one valid parameter, it is included in the response.</p>
    * @public
    */
   BucketRegion?: string | undefined;
@@ -11638,8 +11882,10 @@ export interface ListBucketsOutput {
 
   /**
    * <p>
-   *             <code>ContinuationToken</code> is included in the
-   *          response when there are more buckets that can be listed with pagination. The next <code>ListBuckets</code> request to Amazon S3 can be continued with this <code>ContinuationToken</code>. <code>ContinuationToken</code> is obfuscated and is not a real bucket.</p>
+   *             <code>ContinuationToken</code> is included in the response when there are more buckets
+   *          that can be listed with pagination. The next <code>ListBuckets</code> request to Amazon S3 can
+   *          be continued with this <code>ContinuationToken</code>. <code>ContinuationToken</code> is
+   *          obfuscated and is not a real bucket.</p>
    * @public
    */
   ContinuationToken?: string | undefined;
@@ -11657,7 +11903,9 @@ export interface ListBucketsOutput {
  */
 export interface ListBucketsRequest {
   /**
-   * <p>Maximum number of buckets to be returned in response. When the number is more than the count of buckets that are owned by an Amazon Web Services account, return all the buckets in response.</p>
+   * <p>Maximum number of buckets to be returned in response. When the number is more than the
+   *          count of buckets that are owned by an Amazon Web Services account, return all the buckets in
+   *          response.</p>
    * @public
    */
   MaxBuckets?: number | undefined;
@@ -11666,7 +11914,7 @@ export interface ListBucketsRequest {
    * <p>
    *             <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on
    *          this bucket with a token. <code>ContinuationToken</code> is obfuscated and is not a real
-   *          key. You can use this <code>ContinuationToken</code> for pagination of the list results.  </p>
+   *          key. You can use this <code>ContinuationToken</code> for pagination of the list results. </p>
    *          <p>Length Constraints: Minimum length of 0. Maximum length of 1024.</p>
    *          <p>Required: No.</p>
    *          <note>
@@ -11679,15 +11927,22 @@ export interface ListBucketsRequest {
   ContinuationToken?: string | undefined;
 
   /**
-   * <p>Limits the response to bucket names that begin with the specified bucket name prefix.</p>
+   * <p>Limits the response to bucket names that begin with the specified bucket name
+   *          prefix.</p>
    * @public
    */
   Prefix?: string | undefined;
 
   /**
-   * <p>Limits the response to buckets that are located in the specified Amazon Web Services Region. The Amazon Web Services Region must be expressed according to the Amazon Web Services Region code, such as <code>us-west-2</code> for the US West (Oregon) Region. For a list of the valid values for all of the Amazon Web Services Regions, see <a href="https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region">Regions and Endpoints</a>.</p>
+   * <p>Limits the response to buckets that are located in the specified Amazon Web Services Region. The Amazon Web Services
+   *          Region must be expressed according to the Amazon Web Services Region code, such as <code>us-west-2</code>
+   *          for the US West (Oregon) Region. For a list of the valid values for all of the Amazon Web Services
+   *          Regions, see <a href="https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region">Regions and Endpoints</a>.</p>
    *          <note>
-   *             <p>Requests made to a Regional endpoint that is different from the <code>bucket-region</code> parameter are not supported. For example, if you want to limit the response to your buckets in Region <code>us-west-2</code>, the request must be made to an endpoint in Region <code>us-west-2</code>.</p>
+   *             <p>Requests made to a Regional endpoint that is different from the
+   *                <code>bucket-region</code> parameter are not supported. For example, if you want to
+   *             limit the response to your buckets in Region <code>us-west-2</code>, the request must be
+   *             made to an endpoint in Region <code>us-west-2</code>.</p>
    *          </note>
    * @public
    */
@@ -11706,7 +11961,8 @@ export interface ListDirectoryBucketsOutput {
 
   /**
    * <p>If <code>ContinuationToken</code> was sent with the request, it is included in the
-   *          response. You can use the returned <code>ContinuationToken</code> for pagination of the list response.</p>
+   *          response. You can use the returned <code>ContinuationToken</code> for pagination of the
+   *          list response.</p>
    * @public
    */
   ContinuationToken?: string | undefined;
@@ -11718,14 +11974,18 @@ export interface ListDirectoryBucketsOutput {
 export interface ListDirectoryBucketsRequest {
   /**
    * <p>
-   *             <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on buckets in this account with a token. <code>ContinuationToken</code> is obfuscated and is not a real
-   *          bucket name. You can use this <code>ContinuationToken</code> for the pagination of the list results.  </p>
+   *             <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on
+   *          buckets in this account with a token. <code>ContinuationToken</code> is obfuscated and is
+   *          not a real bucket name. You can use this <code>ContinuationToken</code> for the pagination
+   *          of the list results. </p>
    * @public
    */
   ContinuationToken?: string | undefined;
 
   /**
-   * <p>Maximum number of buckets to be returned in response. When the number is more than the count of buckets that are owned by an Amazon Web Services account, return all the buckets in response.</p>
+   * <p>Maximum number of buckets to be returned in response. When the number is more than the
+   *          count of buckets that are owned by an Amazon Web Services account, return all the buckets in
+   *          response.</p>
    * @public
    */
   MaxDirectoryBuckets?: number | undefined;
@@ -11769,8 +12029,9 @@ export interface Initiator {
    *          principal is an IAM User, it provides a user ARN value.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - If the principal is an Amazon Web Services account, it provides the Amazon Web Services account ID. If the
-   *          principal is an IAM User, it provides a user ARN value.</p>
+   *                <b>Directory buckets</b> - If the principal is an
+   *             Amazon Web Services account, it provides the Amazon Web Services account ID. If the principal is an IAM User, it
+   *             provides a user ARN value.</p>
    *          </note>
    * @public
    */
@@ -11813,7 +12074,8 @@ export interface MultipartUpload {
    * <p>The class of storage used to store the object.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *                <b>Directory buckets</b> -
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -11823,7 +12085,8 @@ export interface MultipartUpload {
    * <p>Specifies the owner of the object that is part of the multipart upload. </p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - The bucket owner is returned as the object owner for all the objects.</p>
+   *                <b>Directory buckets</b> - The bucket owner is
+   *             returned as the object owner for all the objects.</p>
    *          </note>
    * @public
    */
@@ -11864,7 +12127,7 @@ export interface ListMultipartUploadsOutput {
    *          begin. If key-marker is not specified, the upload-id-marker parameter is ignored.
    *          Otherwise, any multipart uploads for a key equal to the key-marker might be included in the
    *          list only if they have an upload ID lexicographically greater than the specified
-   *          <code>upload-id-marker</code>.</p>
+   *             <code>upload-id-marker</code>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -11975,7 +12238,8 @@ export interface ListMultipartUploadsRequest {
   /**
    * <p>The name of the bucket to which the multipart upload was initiated. </p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -12022,7 +12286,7 @@ export interface ListMultipartUploadsRequest {
    *          <note>
    *             <p>When using the URL encoding type, non-ASCII characters that are used in an object's
    *             key name will be percent-encoded according to UTF-8 code values. For example, the object
-   *             <code>test_file(3).png</code> will appear as
+   *                <code>test_file(3).png</code> will appear as
    *             <code>test_file%283%29.png</code>.</p>
    *          </note>
    * @public
@@ -12035,26 +12299,30 @@ export interface ListMultipartUploadsRequest {
    *             <ul>
    *                <li>
    *                   <p>
-   *                      <b>General purpose buckets</b> - For general purpose buckets, <code>key-marker</code>
-   *                is an object key. Together with <code>upload-id-marker</code>, this parameter specifies the multipart
-   *                upload after which listing should begin.</p>
-   *                   <p>If <code>upload-id-marker</code> is not specified, only the keys lexicographically
-   *                   greater than the specified <code>key-marker</code> will be included in the list.</p>
-   *                   <p>If <code>upload-id-marker</code> is specified, any multipart uploads for a key equal to
-   *                   the <code>key-marker</code> might also be included, provided those multipart uploads have
-   *                   upload IDs lexicographically greater than the specified
-   *                   <code>upload-id-marker</code>.</p>
+   *                      <b>General purpose buckets</b> - For
+   *                   general purpose buckets, <code>key-marker</code> is an object key. Together with
+   *                      <code>upload-id-marker</code>, this parameter specifies the multipart upload
+   *                   after which listing should begin.</p>
+   *                   <p>If <code>upload-id-marker</code> is not specified, only the keys
+   *                   lexicographically greater than the specified <code>key-marker</code> will be
+   *                   included in the list.</p>
+   *                   <p>If <code>upload-id-marker</code> is specified, any multipart uploads for a key
+   *                   equal to the <code>key-marker</code> might also be included, provided those
+   *                   multipart uploads have upload IDs lexicographically greater than the specified
+   *                      <code>upload-id-marker</code>.</p>
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets</b> - For directory buckets, <code>key-marker</code>
-   *                is obfuscated and isn't a real object key.
-   *                The <code>upload-id-marker</code> parameter isn't supported by directory buckets.
-   *                To list the additional multipart uploads, you only need to set the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous response.
-   *             </p>
-   *                   <p>In the <code>ListMultipartUploads</code> response, the multipart uploads aren't sorted lexicographically based on the object keys.
+   *                      <b>Directory buckets</b> - For
+   *                   directory buckets, <code>key-marker</code> is obfuscated and isn't a real object
+   *                   key. The <code>upload-id-marker</code> parameter isn't supported by
+   *                   directory buckets. To list the additional multipart uploads, you only need to set
+   *                   the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from
+   *                   the previous response. </p>
+   *                   <p>In the <code>ListMultipartUploads</code> response, the multipart uploads aren't
+   *                   sorted lexicographically based on the object keys.
    *
-   *                   </p>
+   *                </p>
    *                </li>
    *             </ul>
    *          </note>
@@ -12104,9 +12372,9 @@ export interface ListMultipartUploadsRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -12122,7 +12390,8 @@ export interface ListMultipartUploadsRequest {
  *          and how to work with archived objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/archived-objects.html"> Working with archived
  *             objects</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
- *             <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+ *             <p>This functionality is not supported for directory buckets.
+ *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
  *          </note>
  * @public
  */
@@ -12244,7 +12513,8 @@ export interface _Object {
    * <p>The class of storage used to store the object.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *                <b>Directory buckets</b> -
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -12254,7 +12524,8 @@ export interface _Object {
    * <p>The owner of the object</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - The bucket owner is returned as the object owner.</p>
+   *                <b>Directory buckets</b> - The bucket owner is
+   *             returned as the object owner.</p>
    *          </note>
    * @public
    */
@@ -12266,7 +12537,8 @@ export interface _Object {
    *          and how to work with archived objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/archived-objects.html"> Working with archived
    *             objects</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
-   *             <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *             <p>This functionality is not supported for directory buckets.
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -12410,7 +12682,8 @@ export interface ListObjectsRequest {
   /**
    * <p>The name of the bucket containing the objects.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -12447,7 +12720,7 @@ export interface ListObjectsRequest {
    *          <note>
    *             <p>When using the URL encoding type, non-ASCII characters that are used in an object's
    *             key name will be percent-encoded according to UTF-8 code values. For example, the object
-   *             <code>test_file(3).png</code> will appear as
+   *                <code>test_file(3).png</code> will appear as
    *             <code>test_file%283%29.png</code>.</p>
    *          </note>
    * @public
@@ -12553,8 +12826,9 @@ export interface ListObjectsV2Output {
   MaxKeys?: number | undefined;
 
   /**
-   * <p>All of the keys (up to 1,000) that share the same prefix are grouped together. When counting the total numbers of returns by this API operation,
-   *          this group of keys is considered as one item.</p>
+   * <p>All of the keys (up to 1,000) that share the same prefix are grouped together. When
+   *          counting the total numbers of returns by this API operation, this group of keys is
+   *          considered as one item.</p>
    *          <p>A response can contain <code>CommonPrefixes</code> only if you specify a
    *          delimiter.</p>
    *          <p>
@@ -12576,9 +12850,12 @@ export interface ListObjectsV2Output {
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets </b> - When you query <code>ListObjectsV2</code> with a delimiter during in-progress multipart uploads, the
-   *                <code>CommonPrefixes</code> response parameter contains the prefixes that are associated with the in-progress multipart uploads.
-   *                For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *                      <b>Directory buckets </b> - When you query
+   *                      <code>ListObjectsV2</code> with a delimiter during in-progress multipart
+   *                   uploads, the <code>CommonPrefixes</code> response parameter contains the prefixes
+   *                   that are associated with the in-progress multipart uploads. For more information
+   *                   about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in
+   *                   the <i>Amazon S3 User Guide</i>.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -12609,7 +12886,9 @@ export interface ListObjectsV2Output {
 
   /**
    * <p> If <code>ContinuationToken</code> was sent with the request, it is included in the
-   *          response. You can use the returned <code>ContinuationToken</code> for pagination of the list response. You can use this <code>ContinuationToken</code> for pagination of the list results. </p>
+   *          response. You can use the returned <code>ContinuationToken</code> for pagination of the
+   *          list response. You can use this <code>ContinuationToken</code> for pagination of the list
+   *          results. </p>
    * @public
    */
   ContinuationToken?: string | undefined;
@@ -12650,7 +12929,8 @@ export interface ListObjectsV2Output {
 export interface ListObjectsV2Request {
   /**
    * <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -12680,9 +12960,12 @@ export interface ListObjectsV2Request {
    *                </li>
    *                <li>
    *                   <p>
-   *                      <b>Directory buckets </b> - When you query <code>ListObjectsV2</code> with a delimiter during in-progress multipart uploads, the
-   *             <code>CommonPrefixes</code> response parameter contains the prefixes that are associated with the in-progress multipart uploads.
-   *                For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *                      <b>Directory buckets </b> - When you query
+   *                      <code>ListObjectsV2</code> with a delimiter during in-progress multipart
+   *                   uploads, the <code>CommonPrefixes</code> response parameter contains the prefixes
+   *                   that are associated with the in-progress multipart uploads. For more information
+   *                   about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in
+   *                   the <i>Amazon S3 User Guide</i>.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -12701,7 +12984,7 @@ export interface ListObjectsV2Request {
    *          <note>
    *             <p>When using the URL encoding type, non-ASCII characters that are used in an object's
    *             key name will be percent-encoded according to UTF-8 code values. For example, the object
-   *             <code>test_file(3).png</code> will appear as
+   *                <code>test_file(3).png</code> will appear as
    *             <code>test_file%283%29.png</code>.</p>
    *          </note>
    * @public
@@ -12730,7 +13013,8 @@ export interface ListObjectsV2Request {
    * <p>
    *             <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on
    *          this bucket with a token. <code>ContinuationToken</code> is obfuscated and is not a real
-   *          key. You can use this <code>ContinuationToken</code> for pagination of the list results.  </p>
+   *          key. You can use this <code>ContinuationToken</code> for pagination of the list results.
+   *       </p>
    * @public
    */
   ContinuationToken?: string | undefined;
@@ -12741,7 +13025,8 @@ export interface ListObjectsV2Request {
    *          field to <code>true</code>.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - For directory buckets, the bucket owner is returned as the object owner for all objects.</p>
+   *                <b>Directory buckets</b> - For directory buckets,
+   *             the bucket owner is returned as the object owner for all objects.</p>
    *          </note>
    * @public
    */
@@ -13051,7 +13336,7 @@ export interface ListObjectVersionsRequest {
    *          <note>
    *             <p>When using the URL encoding type, non-ASCII characters that are used in an object's
    *             key name will be percent-encoded according to UTF-8 code values. For example, the object
-   *             <code>test_file(3).png</code> will appear as
+   *                <code>test_file(3).png</code> will appear as
    *             <code>test_file%283%29.png</code>.</p>
    *          </note>
    * @public
@@ -13100,9 +13385,9 @@ export interface ListObjectVersionsRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -13265,8 +13550,8 @@ export interface ListPartsOutput {
   IsTruncated?: boolean | undefined;
 
   /**
-   * <p>Container for elements related to a particular part. A response can contain zero or
-   *          more <code>Part</code> elements.</p>
+   * <p>Container for elements related to a particular part. A response can contain zero or more
+   *             <code>Part</code> elements.</p>
    * @public
    */
   Parts?: Part[] | undefined;
@@ -13286,18 +13571,19 @@ export interface ListPartsOutput {
    *          and display name.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - The bucket owner is returned as the object owner for all the parts.</p>
+   *                <b>Directory buckets</b> - The bucket owner is
+   *             returned as the object owner for all the parts.</p>
    *          </note>
    * @public
    */
   Owner?: Owner | undefined;
 
   /**
-   * <p>The class of storage used to store the uploaded
-   *          object.</p>
+   * <p>The class of storage used to store the uploaded object.</p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
+   *                <b>Directory buckets</b> -
+   *             Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>
    *          </note>
    * @public
    */
@@ -13327,7 +13613,8 @@ export interface ListPartsRequest {
   /**
    * <p>The name of the bucket to which the parts are being uploaded. </p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -13375,9 +13662,9 @@ export interface ListPartsRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -13774,19 +14061,30 @@ export interface PutBucketInventoryConfigurationRequest {
  */
 export interface PutBucketLifecycleConfigurationOutput {
   /**
-   * <p>Indicates which default minimum object size behavior is applied to the lifecycle configuration.</p>
+   * <p>Indicates which default minimum object size behavior is applied to the lifecycle
+   *          configuration.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not transition to any storage class by default. </p>
+   *                   <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not
+   *                transition to any storage class by default. </p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>varies_by_storage_class</code> - Objects smaller than 128 KB will transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes will prevent transitions smaller than 128 KB.
-   *          </p>
+   *                   <code>varies_by_storage_class</code> - Objects smaller than 128 KB will
+   *                transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By
+   *                default, all other storage classes will prevent transitions smaller than 128 KB.
+   *             </p>
    *             </li>
    *          </ul>
-   *          <p>To customize the minimum object size for any transition you can add a filter that specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in the body of your transition rule.  Custom filters always take precedence over the default transition behavior.</p>
+   *          <p>To customize the minimum object size for any transition you can add a filter that
+   *          specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in
+   *          the body of your transition rule. Custom filters always take precedence over the default
+   *          transition behavior.</p>
    * @public
    */
   TransitionDefaultMinimumObjectSize?: TransitionDefaultMinimumObjectSize | undefined;
@@ -13838,24 +14136,39 @@ export interface PutBucketLifecycleConfigurationRequest {
 
   /**
    * <p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    * @public
    */
   ExpectedBucketOwner?: string | undefined;
 
   /**
-   * <p>Indicates which default minimum object size behavior is applied to the lifecycle configuration.</p>
+   * <p>Indicates which default minimum object size behavior is applied to the lifecycle
+   *          configuration.</p>
+   *          <note>
+   *             <p>This parameter applies to general purpose buckets only. It is not supported for
+   *             directory bucket lifecycle configurations.</p>
+   *          </note>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not transition to any storage class by default. </p>
+   *                   <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not
+   *                transition to any storage class by default. </p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <code>varies_by_storage_class</code> - Objects smaller than 128 KB will transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes will prevent transitions smaller than 128 KB.
-   *          </p>
+   *                   <code>varies_by_storage_class</code> - Objects smaller than 128 KB will
+   *                transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By
+   *                default, all other storage classes will prevent transitions smaller than 128 KB.
+   *             </p>
    *             </li>
    *          </ul>
-   *          <p>To customize the minimum object size for any transition you can add a filter that specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in the body of your transition rule.  Custom filters always take precedence over the default transition behavior.</p>
+   *          <p>To customize the minimum object size for any transition you can add a filter that
+   *          specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in
+   *          the body of your transition rule. Custom filters always take precedence over the default
+   *          transition behavior.</p>
    * @public
    */
   TransitionDefaultMinimumObjectSize?: TransitionDefaultMinimumObjectSize | undefined;
diff --git a/clients/client-s3/src/models/models_1.ts b/clients/client-s3/src/models/models_1.ts
index 0fa81c155e0e..535215162c45 100644
--- a/clients/client-s3/src/models/models_1.ts
+++ b/clients/client-s3/src/models/models_1.ts
@@ -184,7 +184,8 @@ export interface PutBucketPolicyRequest {
 
   /**
    * <p>The bucket policy as a JSON document.</p>
-   *          <p>For directory buckets, the only IAM action supported in the bucket policy is <code>s3express:CreateSession</code>.</p>
+   *          <p>For directory buckets, the only IAM action supported in the bucket policy is
+   *             <code>s3express:CreateSession</code>.</p>
    * @public
    */
   Policy: string | undefined;
@@ -537,15 +538,92 @@ export interface PutBucketWebsiteRequest {
   ExpectedBucketOwner?: string | undefined;
 }
 
+/**
+ * <p>
+ *          The existing object was created with a different encryption type.
+ *          Subsequent write requests must include the appropriate encryption
+ *          parameters in the request or while creating the session.
+ *       </p>
+ * @public
+ */
+export class EncryptionTypeMismatch extends __BaseException {
+  readonly name: "EncryptionTypeMismatch" = "EncryptionTypeMismatch";
+  readonly $fault: "client" = "client";
+  /**
+   * @internal
+   */
+  constructor(opts: __ExceptionOptionType<EncryptionTypeMismatch, __BaseException>) {
+    super({
+      name: "EncryptionTypeMismatch",
+      $fault: "client",
+      ...opts,
+    });
+    Object.setPrototypeOf(this, EncryptionTypeMismatch.prototype);
+  }
+}
+
+/**
+ * <p>You may receive this error in multiple cases. Depending on the reason for the error, you may receive one of the messages below:</p>
+ *          <ul>
+ *             <li>
+ *                <p>Cannot specify both a write offset value and user-defined object metadata for existing objects.</p>
+ *             </li>
+ *             <li>
+ *                <p>Checksum Type mismatch occurred, expected checksum Type: sha1, actual checksum Type: crc32c.</p>
+ *             </li>
+ *             <li>
+ *                <p>Request body cannot be empty when 'write offset' is specified.</p>
+ *             </li>
+ *          </ul>
+ * @public
+ */
+export class InvalidRequest extends __BaseException {
+  readonly name: "InvalidRequest" = "InvalidRequest";
+  readonly $fault: "client" = "client";
+  /**
+   * @internal
+   */
+  constructor(opts: __ExceptionOptionType<InvalidRequest, __BaseException>) {
+    super({
+      name: "InvalidRequest",
+      $fault: "client",
+      ...opts,
+    });
+    Object.setPrototypeOf(this, InvalidRequest.prototype);
+  }
+}
+
+/**
+ * <p>
+ *          The write offset value that you specified does not match the current object size.
+ *       </p>
+ * @public
+ */
+export class InvalidWriteOffset extends __BaseException {
+  readonly name: "InvalidWriteOffset" = "InvalidWriteOffset";
+  readonly $fault: "client" = "client";
+  /**
+   * @internal
+   */
+  constructor(opts: __ExceptionOptionType<InvalidWriteOffset, __BaseException>) {
+    super({
+      name: "InvalidWriteOffset",
+      $fault: "client",
+      ...opts,
+    });
+    Object.setPrototypeOf(this, InvalidWriteOffset.prototype);
+  }
+}
+
 /**
  * @public
  */
 export interface PutObjectOutput {
   /**
-   * <p>If the expiration is configured for the object (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html">PutBucketLifecycleConfiguration</a>) in the <i>Amazon S3 User Guide</i>, the response includes this header. It
-   *          includes the <code>expiry-date</code> and <code>rule-id</code> key-value pairs that provide
-   *          information about object expiration. The value of the <code>rule-id</code> is
-   *          URL-encoded.</p>
+   * <p>If the expiration is configured for the object (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html">PutBucketLifecycleConfiguration</a>) in the <i>Amazon S3 User Guide</i>,
+   *          the response includes this header. It includes the <code>expiry-date</code> and
+   *             <code>rule-id</code> key-value pairs that provide information about object expiration.
+   *          The value of the <code>rule-id</code> is URL-encoded.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -556,12 +634,13 @@ export interface PutObjectOutput {
   /**
    * <p>Entity tag for the uploaded object.</p>
    *          <p>
-   *             <b>General purpose buckets </b> - To ensure that data is not corrupted traversing the network,
-   *          for objects where the
-   *          ETag is the MD5 digest of the object, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to
-   *       the calculated MD5 value.</p>
+   *             <b>General purpose buckets </b> - To ensure that data is not
+   *          corrupted traversing the network, for objects where the ETag is the MD5 digest of the
+   *          object, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned
+   *          ETag to the calculated MD5 value.</p>
    *          <p>
-   *             <b>Directory buckets </b> - The ETag for the object in a directory bucket isn't the MD5 digest of the object.</p>
+   *             <b>Directory buckets </b> - The ETag for the object in
+   *          a directory bucket isn't the MD5 digest of the object.</p>
    * @public
    */
   ETag?: string | undefined;
@@ -614,10 +693,9 @@ export interface PutObjectOutput {
    *          for the object being stored. Amazon S3 returns this ID in the response. When you enable
    *          versioning for a bucket, if Amazon S3 receives multiple write requests for the same object
    *          simultaneously, it stores all of the objects. For more information about versioning, see
-   *          <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding Objects to
-   *             Versioning-Enabled Buckets</a> in the <i>Amazon S3
-   *                User Guide</i>. For information about returning the versioning state
-   *          of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
+   *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding Objects to
+   *             Versioning-Enabled Buckets</a> in the <i>Amazon S3 User Guide</i>. For
+   *          information about returning the versioning state of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -637,8 +715,8 @@ export interface PutObjectOutput {
 
   /**
    * <p>If server-side encryption with a customer-provided encryption key was requested, the
-   *          response will include this header to provide the round-trip message integrity verification of
-   *          the customer-provided encryption key.</p>
+   *          response will include this header to provide the round-trip message integrity verification
+   *          of the customer-provided encryption key.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -669,6 +747,17 @@ export interface PutObjectOutput {
    */
   BucketKeyEnabled?: boolean | undefined;
 
+  /**
+   * <p>
+   *          The size of the object in bytes. This will only be present if you append to an object.
+   *       </p>
+   *          <note>
+   *             <p>This functionality is only supported for objects in the Amazon S3 Express One Zone storage class in directory buckets.</p>
+   *          </note>
+   * @public
+   */
+  Size?: number | undefined;
+
   /**
    * <p>If present, indicates that the requester was successfully charged for the
    *          request.</p>
@@ -686,7 +775,7 @@ export interface PutObjectOutput {
 export interface PutObjectRequest {
   /**
    * <p>The canned ACL to apply to the object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned
-   *          ACL</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             ACL</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <p>When adding a new object, you can use headers to grant ACL-based permissions to
    *          individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are
    *          then added to the ACL on the object. By default, all objects are private. Only the owner
@@ -699,7 +788,7 @@ export interface PutObjectRequest {
    *          specify bucket owner full control ACLs, such as the <code>bucket-owner-full-control</code>
    *          canned ACL or an equivalent form of this ACL expressed in the XML format. PUT requests that
    *          contain other ACLs (for example, custom grants to certain Amazon Web Services accounts) fail and return a
-   *          <code>400</code> error with the error code <code>AccessControlListNotSupported</code>.
+   *             <code>400</code> error with the error code <code>AccessControlListNotSupported</code>.
    *          For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html"> Controlling ownership of
    *             objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
@@ -725,7 +814,8 @@ export interface PutObjectRequest {
   /**
    * <p>The bucket name to which the PUT action was initiated. </p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -786,10 +876,10 @@ export interface PutObjectRequest {
    *          Content-MD5 mechanism as an end-to-end integrity check. For more information about REST
    *          request authentication, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
    *          <note>
-   *             <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is required for any request to upload an
-   *          object with a retention period configured using Amazon S3 Object Lock. For more
-   *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object">Uploading objects to an Object Lock enabled bucket
-   *          </a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is
+   *             required for any request to upload an object with a retention period configured using
+   *             Amazon S3 Object Lock. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object">Uploading objects to an Object Lock enabled bucket </a> in the
+   *                <i>Amazon S3 User Guide</i>.</p>
    *          </note>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -844,10 +934,10 @@ export interface PutObjectRequest {
    *             <code>ChecksumAlgorithm</code> parameter and uses the checksum algorithm that matches the provided value in <code>x-amz-checksum-<i>algorithm</i>
    *             </code>.</p>
    *          <note>
-   *             <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is required for any request to upload an
-   *          object with a retention period configured using Amazon S3 Object Lock. For more
-   *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object">Uploading objects to an Object Lock enabled bucket
-   *          </a> in the <i>Amazon S3 User Guide</i>.</p>
+   *             <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is
+   *             required for any request to upload an object with a retention period configured using
+   *             Amazon S3 Object Lock. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object">Uploading objects to an Object Lock enabled bucket </a> in the
+   *                <i>Amazon S3 User Guide</i>.</p>
    *          </note>
    *          <p>For directory buckets, when you use Amazon Web Services SDKs, <code>CRC32</code> is the default checksum algorithm that's used for performance.</p>
    * @public
@@ -898,8 +988,11 @@ export interface PutObjectRequest {
   Expires?: Date | undefined;
 
   /**
-   * <p>Uploads the object only if the object key name does not already exist in the bucket specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>
-   *          <p>If a conflicting operation occurs during the upload S3 returns a <code>409 ConditionalRequestConflict</code> response. On a 409 failure you should retry the upload.</p>
+   * <p>Uploads the object only if the object key name does not already exist in the bucket
+   *          specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>
+   *          <p>If a conflicting operation occurs during the upload S3 returns a <code>409
+   *             ConditionalRequestConflict</code> response. On a 409 failure you should retry the
+   *          upload.</p>
    *          <p>Expects the '*' (asterisk) character.</p>
    *          <p>For more information about conditional requests, see <a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>, or <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html">Conditional requests</a> in the <i>Amazon S3 User Guide</i>.</p>
    * @public
@@ -976,6 +1069,19 @@ export interface PutObjectRequest {
    */
   Key: string | undefined;
 
+  /**
+   * <p>
+   *          Specifies the offset for appending data to existing objects in bytes.
+   *          The offset must be equal to the size of the existing object being appended to.
+   *          If no object exists, setting this header to 0 will create a new object.
+   *       </p>
+   *          <note>
+   *             <p>This functionality is only supported for objects in the Amazon S3 Express One Zone storage class in directory buckets.</p>
+   *          </note>
+   * @public
+   */
+  WriteOffsetBytes?: number | undefined;
+
   /**
    * <p>A map of metadata to store with the object in S3.</p>
    * @public
@@ -983,27 +1089,28 @@ export interface PutObjectRequest {
   Metadata?: Record<string, string> | undefined;
 
   /**
-   * <p>The server-side encryption algorithm that was used when you store this object in Amazon S3 (for example,
-   *             <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>
+   * <p>The server-side encryption algorithm that was used when you store this object in Amazon S3
+   *          (for example, <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>
    *          <ul>
    *             <li>
    *                <p>
-   *                   <b>General purpose buckets </b> - You have four mutually exclusive options to protect data using server-side encryption in
-   *             Amazon S3, depending on how you choose to manage the encryption keys. Specifically, the
-   *             encryption key options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS or
-   *             DSSE-KMS), and customer-provided keys (SSE-C). Amazon S3 encrypts data with server-side
-   *             encryption by using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to
-   *             encrypt data at rest by using server-side encryption with other key options. For more
-   *             information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using Server-Side
-   *                Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *                   <b>General purpose buckets </b> - You have four mutually
+   *                exclusive options to protect data using server-side encryption in Amazon S3, depending on
+   *                how you choose to manage the encryption keys. Specifically, the encryption key
+   *                options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS or DSSE-KMS), and
+   *                customer-provided keys (SSE-C). Amazon S3 encrypts data with server-side encryption by
+   *                using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt
+   *                data at rest by using server-side encryption with other key options. For more
+   *                information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using Server-Side
+   *                   Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>
    *             </li>
    *             <li>
    *                <p>
-   *                   <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+   *                   <b>Directory buckets </b> -
+   *                For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). 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, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>
+   *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>In the Zonal endpoint API calls (except <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request.
    *                             You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request.
    *                             You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and
@@ -1026,16 +1133,17 @@ export interface PutObjectRequest {
   /**
    * <p>By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The
    *          STANDARD storage class provides high durability and high availability. Depending on
-   *          performance needs, you can specify a different Storage Class. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a> in the
-   *             <i>Amazon S3 User Guide</i>.</p>
+   *          performance needs, you can specify a different Storage Class. For more information, see
+   *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage
+   *             Classes</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <ul>
    *                <li>
-   *                   <p>For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.</p>
+   *                   <p>For directory buckets, only the S3 Express One Zone storage class is supported to store
+   *                   newly created objects.</p>
    *                </li>
    *                <li>
-   *                   <p>Amazon S3 on Outposts only uses
-   *                the OUTPOSTS Storage Class.</p>
+   *                   <p>Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.</p>
    *                </li>
    *             </ul>
    *          </note>
@@ -1046,8 +1154,8 @@ export interface PutObjectRequest {
   /**
    * <p>If the bucket is configured as a website, redirects requests for this object to another
    *          object in the same bucket or to an external URL. Amazon S3 stores the value of this header in
-   *          the object metadata. For information about object metadata, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html">Object Key and Metadata</a> in the <i>Amazon S3
-   *                User Guide</i>.</p>
+   *          the object metadata. For information about object metadata, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html">Object Key and Metadata</a> in the
+   *             <i>Amazon S3 User Guide</i>.</p>
    *          <p>In the following example, the request header sets the redirect to an object
    *          (anotherPage.html) in the same bucket:</p>
    *          <p>
@@ -1060,8 +1168,7 @@ export interface PutObjectRequest {
    *          </p>
    *          <p>For more information about website hosting in Amazon S3, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html">Hosting Websites on Amazon S3</a> and
    *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html">How to
-   *                Configure Website Page Redirects</a> in the <i>Amazon S3
-   *                   User Guide</i>. </p>
+   *             Configure Website Page Redirects</a> in the <i>Amazon S3 User Guide</i>. </p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -1071,7 +1178,7 @@ export interface PutObjectRequest {
 
   /**
    * <p>Specifies the algorithm to use when encrypting the object (for example,
-   *          <code>AES256</code>).</p>
+   *             <code>AES256</code>).</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -1157,9 +1264,9 @@ export interface PutObjectRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -1199,7 +1306,8 @@ export interface PutObjectRequest {
 
   /**
    * <p>Specifies whether a legal hold will be applied to this object. For more information
-   *          about S3 Object Lock, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Object Lock</a> in the <i>Amazon S3 User Guide</i>.</p>
+   *          about S3 Object Lock, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html">Object Lock</a> in the
+   *             <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -1214,6 +1322,30 @@ export interface PutObjectRequest {
   ExpectedBucketOwner?: string | undefined;
 }
 
+/**
+ * <p>
+ *          You have attempted to add more parts than the maximum of 10000
+ *          that are allowed for this object. You can use the CopyObject operation
+ *          to copy this object to another and then add more data to the newly copied object.
+ *       </p>
+ * @public
+ */
+export class TooManyParts extends __BaseException {
+  readonly name: "TooManyParts" = "TooManyParts";
+  readonly $fault: "client" = "client";
+  /**
+   * @internal
+   */
+  constructor(opts: __ExceptionOptionType<TooManyParts, __BaseException>) {
+    super({
+      name: "TooManyParts",
+      $fault: "client",
+      ...opts,
+    });
+    Object.setPrototypeOf(this, TooManyParts.prototype);
+  }
+}
+
 /**
  * @public
  */
@@ -1328,9 +1460,9 @@ export interface PutObjectAclRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -1400,9 +1532,9 @@ export interface PutObjectLegalHoldRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -1479,9 +1611,9 @@ export interface PutObjectLockConfigurationRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -1568,9 +1700,9 @@ export interface PutObjectRetentionRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -1692,9 +1824,9 @@ export interface PutObjectTaggingRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -2352,9 +2484,9 @@ export interface RestoreObjectRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -2774,8 +2906,8 @@ export interface SelectObjectContentRequest {
  */
 export interface UploadPartOutput {
   /**
-   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,
-   *             <code>AES256</code>, <code>aws:kms</code>).</p>
+   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for
+   *          example, <code>AES256</code>, <code>aws:kms</code>).</p>
    * @public
    */
   ServerSideEncryption?: ServerSideEncryption | undefined;
@@ -2834,8 +2966,8 @@ export interface UploadPartOutput {
 
   /**
    * <p>If server-side encryption with a customer-provided encryption key was requested, the
-   *          response will include this header to provide the round-trip message integrity verification of
-   *          the customer-provided encryption key.</p>
+   *          response will include this header to provide the round-trip message integrity verification
+   *          of the customer-provided encryption key.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -2880,7 +3012,8 @@ export interface UploadPartRequest {
   /**
    * <p>The name of the bucket to which the multipart upload was initiated.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -2988,8 +3121,7 @@ export interface UploadPartRequest {
   UploadId: string | undefined;
 
   /**
-   * <p>Specifies the algorithm to use when encrypting the object (for example,
-   *          AES256).</p>
+   * <p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -3024,9 +3156,9 @@ export interface UploadPartRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -3117,8 +3249,8 @@ export interface UploadPartCopyOutput {
   CopyPartResult?: CopyPartResult | undefined;
 
   /**
-   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,
-   *             <code>AES256</code>, <code>aws:kms</code>).</p>
+   * <p>The server-side encryption algorithm used when you store this object in Amazon S3 (for
+   *          example, <code>AES256</code>, <code>aws:kms</code>).</p>
    * @public
    */
   ServerSideEncryption?: ServerSideEncryption | undefined;
@@ -3135,8 +3267,8 @@ export interface UploadPartCopyOutput {
 
   /**
    * <p>If server-side encryption with a customer-provided encryption key was requested, the
-   *          response will include this header to provide the round-trip message integrity verification of
-   *          the customer-provided encryption key.</p>
+   *          response will include this header to provide the round-trip message integrity verification
+   *          of the customer-provided encryption key.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
    *          </note>
@@ -3175,7 +3307,8 @@ export interface UploadPartCopyRequest {
   /**
    * <p>The bucket name.</p>
    *          <p>
-   *             <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
+   *             <b>Directory buckets</b> -
+   *          When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>
    *                <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>
    *                <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>
    *                <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming
@@ -3221,22 +3354,22 @@ export interface UploadPartCopyRequest {
    *                <p>Alternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format <code>arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through outpost <code>my-outpost</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf</code>. The value must be URL-encoded.  </p>
    *             </li>
    *          </ul>
-   *          <p>If your bucket has versioning enabled, you could have multiple versions of the
-   *          same object. By default, <code>x-amz-copy-source</code> identifies the current
-   *          version of the source object to copy.
-   *          To copy a specific version of the source object to copy, append <code>?versionId=<version-id></code>
-   *          to the <code>x-amz-copy-source</code> request header (for example,
-   *          <code>x-amz-copy-source: /awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>).
-   *          </p>
-   *          <p>If the current version is a delete marker and you
-   *          don't specify a versionId in the <code>x-amz-copy-source</code> request header, Amazon S3 returns a
-   *          <code>404 Not Found</code> error, because the object does not exist. If you specify versionId in the
-   *          <code>x-amz-copy-source</code> and the versionId is a delete marker, Amazon S3
-   *          returns an HTTP <code>400 Bad Request</code> error, because you are not allowed to specify a delete marker
-   *          as a version for the <code>x-amz-copy-source</code>. </p>
+   *          <p>If your bucket has versioning enabled, you could have multiple versions of the same
+   *          object. By default, <code>x-amz-copy-source</code> identifies the current version of the
+   *          source object to copy. To copy a specific version of the source object to copy, append
+   *             <code>?versionId=<version-id></code> to the <code>x-amz-copy-source</code> request
+   *          header (for example, <code>x-amz-copy-source:
+   *             /awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>). </p>
+   *          <p>If the current version is a delete marker and you don't specify a versionId in the
+   *             <code>x-amz-copy-source</code> request header, Amazon S3 returns a <code>404 Not Found</code>
+   *          error, because the object does not exist. If you specify versionId in the
+   *             <code>x-amz-copy-source</code> and the versionId is a delete marker, Amazon S3 returns an
+   *          HTTP <code>400 Bad Request</code> error, because you are not allowed to specify a delete
+   *          marker as a version for the <code>x-amz-copy-source</code>. </p>
    *          <note>
    *             <p>
-   *                <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets.</p>
+   *                <b>Directory buckets</b> -
+   *             S3 Versioning isn't enabled and supported for directory buckets.</p>
    *          </note>
    * @public
    */
@@ -3244,16 +3377,15 @@ export interface UploadPartCopyRequest {
 
   /**
    * <p>Copies the object if its entity tag (ETag) matches the specified tag.</p>
-   *          <p>If both of the
-   *       <code>x-amz-copy-source-if-match</code> and
-   *       <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the
-   *       request as follows:</p>
+   *          <p>If both of the <code>x-amz-copy-source-if-match</code> and
+   *             <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request as
+   *          follows:</p>
    *          <p>
    *             <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,
    *          and;</p>
    *          <p>
    *             <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to
-   *          <code>false</code>;</p>
+   *             <code>false</code>;</p>
    *          <p>Amazon S3 returns <code>200 OK</code> and copies the data.
    *          </p>
    * @public
@@ -3262,16 +3394,15 @@ export interface UploadPartCopyRequest {
 
   /**
    * <p>Copies the object if it has been modified since the specified time.</p>
-   *          <p>If both of the
-   *       <code>x-amz-copy-source-if-none-match</code> and
-   *       <code>x-amz-copy-source-if-modified-since</code> headers are present in the
-   *       request as follows:</p>
+   *          <p>If both of the <code>x-amz-copy-source-if-none-match</code> and
+   *             <code>x-amz-copy-source-if-modified-since</code> headers are present in the request as
+   *          follows:</p>
    *          <p>
-   *             <code>x-amz-copy-source-if-none-match</code> condition evaluates to
-   *          <code>false</code>, and;</p>
+   *             <code>x-amz-copy-source-if-none-match</code> condition evaluates to <code>false</code>,
+   *          and;</p>
    *          <p>
    *             <code>x-amz-copy-source-if-modified-since</code> condition evaluates to
-   *          <code>true</code>;</p>
+   *             <code>true</code>;</p>
    *          <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.
    *          </p>
    * @public
@@ -3280,16 +3411,15 @@ export interface UploadPartCopyRequest {
 
   /**
    * <p>Copies the object if its entity tag (ETag) is different than the specified ETag.</p>
-   *          <p>If both of the
-   *       <code>x-amz-copy-source-if-none-match</code> and
-   *       <code>x-amz-copy-source-if-modified-since</code> headers are present in the
-   *       request as follows:</p>
+   *          <p>If both of the <code>x-amz-copy-source-if-none-match</code> and
+   *             <code>x-amz-copy-source-if-modified-since</code> headers are present in the request as
+   *          follows:</p>
    *          <p>
-   *             <code>x-amz-copy-source-if-none-match</code> condition evaluates to
-   *          <code>false</code>, and;</p>
+   *             <code>x-amz-copy-source-if-none-match</code> condition evaluates to <code>false</code>,
+   *          and;</p>
    *          <p>
    *             <code>x-amz-copy-source-if-modified-since</code> condition evaluates to
-   *          <code>true</code>;</p>
+   *             <code>true</code>;</p>
    *          <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.
    *          </p>
    * @public
@@ -3298,16 +3428,15 @@ export interface UploadPartCopyRequest {
 
   /**
    * <p>Copies the object if it hasn't been modified since the specified time.</p>
-   *          <p>If both of the
-   *          <code>x-amz-copy-source-if-match</code> and
-   *          <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the
-   *          request as follows:</p>
+   *          <p>If both of the <code>x-amz-copy-source-if-match</code> and
+   *             <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request as
+   *          follows:</p>
    *          <p>
    *             <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,
    *          and;</p>
    *          <p>
    *             <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to
-   *          <code>false</code>;</p>
+   *             <code>false</code>;</p>
    *          <p>Amazon S3 returns <code>200 OK</code> and copies the data.
    *          </p>
    * @public
@@ -3343,8 +3472,7 @@ export interface UploadPartCopyRequest {
   UploadId: string | undefined;
 
   /**
-   * <p>Specifies the algorithm to use when encrypting the object (for example,
-   *          AES256).</p>
+   * <p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>
    *          <note>
    *             <p>This functionality is not supported when the destination bucket is a directory bucket.</p>
    *          </note>
@@ -3378,7 +3506,7 @@ export interface UploadPartCopyRequest {
 
   /**
    * <p>Specifies the algorithm to use when decrypting the source object (for example,
-   *          <code>AES256</code>).</p>
+   *             <code>AES256</code>).</p>
    *          <note>
    *             <p>This functionality is not supported when the source object is in a directory bucket.</p>
    *          </note>
@@ -3411,9 +3539,9 @@ export interface UploadPartCopyRequest {
   /**
    * <p>Confirms that the requester knows that they will be charged for the request. Bucket
    *          owners need not specify this parameter in their requests. If either the source or
-   *          destination S3 bucket has Requester Pays enabled, the requester will pay for
-   *          corresponding charges to copy the object. For information about downloading objects from
-   *          Requester Pays buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
+   *          destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding
+   *          charges to copy the object. For information about downloading objects from Requester Pays
+   *          buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html">Downloading Objects in
    *             Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>
    *          <note>
    *             <p>This functionality is not supported for directory buckets.</p>
@@ -3777,8 +3905,9 @@ export interface WriteGetObjectResponseRequest {
   SSECustomerAlgorithm?: string | undefined;
 
   /**
-   * <p> If present, specifies the ID (Key ID, Key ARN, or Key Alias) of the Amazon Web Services Key Management Service (Amazon Web Services KMS) symmetric
-   *          encryption customer managed key that was used for stored in Amazon S3 object. </p>
+   * <p> If present, specifies the ID (Key ID, Key ARN, or Key Alias) of the Amazon Web Services Key
+   *          Management Service (Amazon Web Services KMS) symmetric encryption customer managed key that was used for stored in
+   *          Amazon S3 object. </p>
    * @public
    */
   SSEKMSKeyId?: string | undefined;
diff --git a/clients/client-s3/src/protocols/Aws_restXml.ts b/clients/client-s3/src/protocols/Aws_restXml.ts
index a0e2a0bd1736..c4973d6e6f81 100644
--- a/clients/client-s3/src/protocols/Aws_restXml.ts
+++ b/clients/client-s3/src/protocols/Aws_restXml.ts
@@ -419,9 +419,12 @@ import {
   CSVInput,
   CSVOutput,
   Encryption,
+  EncryptionTypeMismatch,
   EndEvent,
   GlacierJobParameters,
   InputSerialization,
+  InvalidRequest,
+  InvalidWriteOffset,
   JSONInput,
   JSONOutput,
   MetadataEntry,
@@ -442,6 +445,7 @@ import {
   Stats,
   StatsEvent,
   Tagging,
+  TooManyParts,
   VersioningConfiguration,
   WebsiteConfiguration,
 } from "../models/models_1";
@@ -458,6 +462,7 @@ export const se_AbortMultipartUploadCommand = async (
   const headers: any = map({}, isSerializableHeaderValue, {
     [_xarp]: input[_RP]!,
     [_xaebo]: input[_EBO]!,
+    [_xaimit]: [() => isSerializableHeaderValue(input[_IMIT]), () => __dateToUtcString(input[_IMIT]!).toString()],
   });
   b.bp("/{Key+}");
   b.p("Bucket", () => input.Bucket!, "{Bucket}", false);
@@ -971,6 +976,9 @@ export const se_DeleteObjectCommand = async (
     [_xarp]: input[_RP]!,
     [_xabgr]: [() => isSerializableHeaderValue(input[_BGR]), () => input[_BGR]!.toString()],
     [_xaebo]: input[_EBO]!,
+    [_im]: input[_IM]!,
+    [_xaimlmt]: [() => isSerializableHeaderValue(input[_IMLMT]), () => __dateToUtcString(input[_IMLMT]!).toString()],
+    [_xaims]: [() => isSerializableHeaderValue(input[_IMS]), () => input[_IMS]!.toString()],
   });
   b.bp("/{Key+}");
   b.p("Bucket", () => input.Bucket!, "{Bucket}", false);
@@ -1498,7 +1506,7 @@ export const se_GetObjectCommand = async (
   const b = rb(input, context);
   const headers: any = map({}, isSerializableHeaderValue, {
     [_im]: input[_IM]!,
-    [_ims]: [() => isSerializableHeaderValue(input[_IMS]), () => __dateToUtcString(input[_IMS]!).toString()],
+    [_ims]: [() => isSerializableHeaderValue(input[_IMSf]), () => __dateToUtcString(input[_IMSf]!).toString()],
     [_inm]: input[_INM]!,
     [_ius]: [() => isSerializableHeaderValue(input[_IUS]), () => __dateToUtcString(input[_IUS]!).toString()],
     [_ra]: input[_R]!,
@@ -1747,7 +1755,7 @@ export const se_HeadObjectCommand = async (
   const b = rb(input, context);
   const headers: any = map({}, isSerializableHeaderValue, {
     [_im]: input[_IM]!,
-    [_ims]: [() => isSerializableHeaderValue(input[_IMS]), () => __dateToUtcString(input[_IMS]!).toString()],
+    [_ims]: [() => isSerializableHeaderValue(input[_IMSf]), () => __dateToUtcString(input[_IMSf]!).toString()],
     [_inm]: input[_INM]!,
     [_ius]: [() => isSerializableHeaderValue(input[_IUS]), () => __dateToUtcString(input[_IUS]!).toString()],
     [_ra]: input[_R]!,
@@ -2637,6 +2645,7 @@ export const se_PutObjectCommand = async (
     [_xagr]: input[_GR]!,
     [_xagra]: input[_GRACP]!,
     [_xagwa]: input[_GWACP]!,
+    [_xawob]: [() => isSerializableHeaderValue(input[_WOB]), () => input[_WOB]!.toString()],
     [_xasse]: input[_SSE]!,
     [_xasc]: input[_SC]!,
     [_xawrl]: input[_WRL]!,
@@ -5154,6 +5163,7 @@ export const de_PutObjectCommand = async (
     [_SSEKMSKI]: [, output.headers[_xasseakki]],
     [_SSEKMSEC]: [, output.headers[_xassec]],
     [_BKE]: [() => void 0 !== output.headers[_xassebke], () => __parseBoolean(output.headers[_xassebke])],
+    [_Si]: [() => void 0 !== output.headers[_xaos], () => __strictParseLong(output.headers[_xaos])],
     [_RC]: [, output.headers[_xarc]],
   });
   await collectBody(output.body, context);
@@ -5408,6 +5418,18 @@ const de_CommandError = async (output: __HttpResponse, context: __SerdeContext):
     case "NotFound":
     case "com.amazonaws.s3#NotFound":
       throw await de_NotFoundRes(parsedOutput, context);
+    case "EncryptionTypeMismatch":
+    case "com.amazonaws.s3#EncryptionTypeMismatch":
+      throw await de_EncryptionTypeMismatchRes(parsedOutput, context);
+    case "InvalidRequest":
+    case "com.amazonaws.s3#InvalidRequest":
+      throw await de_InvalidRequestRes(parsedOutput, context);
+    case "InvalidWriteOffset":
+    case "com.amazonaws.s3#InvalidWriteOffset":
+      throw await de_InvalidWriteOffsetRes(parsedOutput, context);
+    case "TooManyParts":
+    case "com.amazonaws.s3#TooManyParts":
+      throw await de_TooManyPartsRes(parsedOutput, context);
     case "ObjectAlreadyInActiveTierError":
     case "com.amazonaws.s3#ObjectAlreadyInActiveTierError":
       throw await de_ObjectAlreadyInActiveTierErrorRes(parsedOutput, context);
@@ -5451,6 +5473,22 @@ const de_BucketAlreadyOwnedByYouRes = async (
   return __decorateServiceException(exception, parsedOutput.body);
 };
 
+/**
+ * deserializeAws_restXmlEncryptionTypeMismatchRes
+ */
+const de_EncryptionTypeMismatchRes = async (
+  parsedOutput: any,
+  context: __SerdeContext
+): Promise<EncryptionTypeMismatch> => {
+  const contents: any = map({});
+  const data: any = parsedOutput.body;
+  const exception = new EncryptionTypeMismatch({
+    $metadata: deserializeMetadata(parsedOutput),
+    ...contents,
+  });
+  return __decorateServiceException(exception, parsedOutput.body);
+};
+
 /**
  * deserializeAws_restXmlInvalidObjectStateRes
  */
@@ -5470,6 +5508,32 @@ const de_InvalidObjectStateRes = async (parsedOutput: any, context: __SerdeConte
   return __decorateServiceException(exception, parsedOutput.body);
 };
 
+/**
+ * deserializeAws_restXmlInvalidRequestRes
+ */
+const de_InvalidRequestRes = async (parsedOutput: any, context: __SerdeContext): Promise<InvalidRequest> => {
+  const contents: any = map({});
+  const data: any = parsedOutput.body;
+  const exception = new InvalidRequest({
+    $metadata: deserializeMetadata(parsedOutput),
+    ...contents,
+  });
+  return __decorateServiceException(exception, parsedOutput.body);
+};
+
+/**
+ * deserializeAws_restXmlInvalidWriteOffsetRes
+ */
+const de_InvalidWriteOffsetRes = async (parsedOutput: any, context: __SerdeContext): Promise<InvalidWriteOffset> => {
+  const contents: any = map({});
+  const data: any = parsedOutput.body;
+  const exception = new InvalidWriteOffset({
+    $metadata: deserializeMetadata(parsedOutput),
+    ...contents,
+  });
+  return __decorateServiceException(exception, parsedOutput.body);
+};
+
 /**
  * deserializeAws_restXmlNoSuchBucketRes
  */
@@ -5554,6 +5618,19 @@ const de_ObjectNotInActiveTierErrorRes = async (
   return __decorateServiceException(exception, parsedOutput.body);
 };
 
+/**
+ * deserializeAws_restXmlTooManyPartsRes
+ */
+const de_TooManyPartsRes = async (parsedOutput: any, context: __SerdeContext): Promise<TooManyParts> => {
+  const contents: any = map({});
+  const data: any = parsedOutput.body;
+  const exception = new TooManyParts({
+    $metadata: deserializeMetadata(parsedOutput),
+    ...contents,
+  });
+  return __decorateServiceException(exception, parsedOutput.body);
+};
+
 /**
  * deserializeAws_restXmlSelectObjectContentEventStream
  */
@@ -6685,6 +6762,13 @@ const se_ObjectIdentifier = (input: ObjectIdentifier, context: __SerdeContext):
   if (input[_VI] != null) {
     bn.c(__XmlNode.of(_OVI, input[_VI]).n(_VI));
   }
+  bn.cc(input, _ETa);
+  if (input[_LMT] != null) {
+    bn.c(__XmlNode.of(_LMT, __dateToUtcString(input[_LMT]).toString()).n(_LMT));
+  }
+  if (input[_Si] != null) {
+    bn.c(__XmlNode.of(_Si, String(input[_Si])).n(_Si));
+  }
   return bn;
 };
 
@@ -9833,7 +9917,10 @@ const _II = "InventoryId";
 const _IIOV = "InventoryIncludedObjectVersions";
 const _IL = "IsLatest";
 const _IM = "IfMatch";
-const _IMS = "IfModifiedSince";
+const _IMIT = "IfMatchInitiatedTime";
+const _IMLMT = "IfMatchLastModifiedTime";
+const _IMS = "IfMatchSize";
+const _IMSf = "IfModifiedSince";
 const _INM = "IfNoneMatch";
 const _IOF = "InventoryOptionalField";
 const _IOV = "IncludedObjectVersions";
@@ -9876,6 +9963,7 @@ const _LFC = "LambdaFunctionConfigurations";
 const _LFCa = "LambdaFunctionConfiguration";
 const _LI = "LocationInfo";
 const _LM = "LastModified";
+const _LMT = "LastModifiedTime";
 const _LNAS = "LocationNameAsString";
 const _LP = "LocationPrefix";
 const _LR = "LifecycleRule";
@@ -10102,6 +10190,7 @@ const _VIM = "VersionIdMarker";
 const _Va = "Value";
 const _Ve = "Versions";
 const _WC = "WebsiteConfiguration";
+const _WOB = "WriteOffsetBytes";
 const _WRL = "WebsiteRedirectLocation";
 const _Y = "Years";
 const _a = "analytics";
@@ -10258,6 +10347,9 @@ const _xagr = "x-amz-grant-read";
 const _xagra = "x-amz-grant-read-acp";
 const _xagw = "x-amz-grant-write";
 const _xagwa = "x-amz-grant-write-acp";
+const _xaimit = "x-amz-if-match-initiated-time";
+const _xaimlmt = "x-amz-if-match-last-modified-time";
+const _xaims = "x-amz-if-match-size";
 const _xam = "x-amz-mfa";
 const _xamd = "x-amz-metadata-directive";
 const _xamm = "x-amz-missing-meta";
@@ -10269,6 +10361,7 @@ const _xaolm = "x-amz-object-lock-mode";
 const _xaolrud = "x-amz-object-lock-retain-until-date";
 const _xaoo = "x-amz-object-ownership";
 const _xaooa = "x-amz-optional-object-attributes";
+const _xaos = "x-amz-object-size";
 const _xapnm = "x-amz-part-number-marker";
 const _xar = "x-amz-restore";
 const _xarc = "x-amz-request-charged";
@@ -10293,5 +10386,6 @@ const _xatc = "x-amz-tagging-count";
 const _xatd = "x-amz-tagging-directive";
 const _xatdmos = "x-amz-transition-default-minimum-object-size";
 const _xavi = "x-amz-version-id";
+const _xawob = "x-amz-write-offset-bytes";
 const _xawrl = "x-amz-website-redirect-location";
 const _xi = "x-id";
diff --git a/codegen/sdk-codegen/aws-models/s3.json b/codegen/sdk-codegen/aws-models/s3.json
index a520f661cb99..b51b48c40b70 100644
--- a/codegen/sdk-codegen/aws-models/s3.json
+++ b/codegen/sdk-codegen/aws-models/s3.json
@@ -60,7 +60,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>This operation aborts a multipart upload. After a multipart upload is aborted, no\n         additional parts can be uploaded using that upload ID. The storage consumed by any\n         previously uploaded parts will be freed. However, if any part uploads are currently in\n         progress, those part uploads might or might not succeed. As a result, it might be necessary\n         to abort a given multipart upload multiple times in order to completely free all storage\n         consumed by all parts. </p>\n         <p>To verify that all parts have been removed and prevent getting charged for the part\n         storage, you should call the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a> API operation and ensure that\n         the parts list is empty.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - \n                  If multipart uploads in a directory bucket are in progress, you can't delete the bucket until all the in-progress multipart uploads are aborted or completed. \n                  To delete these in-progress multipart uploads, use the\n               <code>ListMultipartUploads</code> operation to list the in-progress multipart\n               uploads in the bucket and use the <code>AbortMultipartUpload</code> operation to\n               abort all the in-progress multipart uploads.\n               </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For information about permissions required to use the multipart upload, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload\n                        and Permissions</a> in the <i>Amazon S3\n                           User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>AbortMultipartUpload</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>This operation aborts a multipart upload. After a multipart upload is aborted, no\n         additional parts can be uploaded using that upload ID. The storage consumed by any\n         previously uploaded parts will be freed. However, if any part uploads are currently in\n         progress, those part uploads might or might not succeed. As a result, it might be necessary\n         to abort a given multipart upload multiple times in order to completely free all storage\n         consumed by all parts. </p>\n         <p>To verify that all parts have been removed and prevent getting charged for the part\n         storage, you should call the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a> API operation and ensure\n         that the parts list is empty.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - If multipart\n                  uploads in a directory bucket are in progress, you can't delete the bucket until\n                  all the in-progress multipart uploads are aborted or completed. To delete these\n                  in-progress multipart uploads, use the <code>ListMultipartUploads</code> operation\n                  to list the in-progress multipart uploads in the bucket and use the\n                     <code>AbortMultipartUpload</code> operation to abort all the in-progress\n                  multipart uploads. </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For\n                        information about permissions required to use the multipart upload, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload and\n                           Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>AbortMultipartUpload</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To abort a multipart upload",
@@ -100,7 +100,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket name to which the upload was taking place. </p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The bucket name to which the upload was taking place. </p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -139,6 +139,13 @@
             "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>",
             "smithy.api#httpHeader": "x-amz-expected-bucket-owner"
           }
+        },
+        "IfMatchInitiatedTime": {
+          "target": "com.amazonaws.s3#IfMatchInitiatedTime",
+          "traits": {
+            "smithy.api#documentation": "<p>If present, this header aborts an in progress multipart upload only if it was initiated on the provided timestamp.\n         If the initiated timestamp of the multipart upload does not match the provided value, the operation returns a <code>412 Precondition Failed</code> error. \n         If the initiated timestamp matches or if the multipart upload doesn’t exist, the operation returns a <code>204 Success (No Content)</code> response. \n      </p>\n         <note>\n            <p>This functionality is only supported for directory buckets.</p>\n         </note>",
+            "smithy.api#httpHeader": "x-amz-if-match-initiated-time"
+          }
         }
       },
       "traits": {
@@ -17623,12 +17630,12 @@
         "BucketRegion": {
           "target": "com.amazonaws.s3#BucketRegion",
           "traits": {
-            "smithy.api#documentation": "<p>\n            <code>BucketRegion</code> indicates the Amazon Web Services region where the bucket is located. If the request contains at least one valid parameter, it is included in the response.</p>"
+            "smithy.api#documentation": "<p>\n            <code>BucketRegion</code> indicates the Amazon Web Services region where the bucket is located. If the\n         request contains at least one valid parameter, it is included in the response.</p>"
           }
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p> In terms of implementation, a Bucket is a resource.  </p>"
+        "smithy.api#documentation": "<p> In terms of implementation, a Bucket is a resource. </p>"
       }
     },
     "com.amazonaws.s3#BucketAccelerateStatus": {
@@ -17712,7 +17719,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Specifies the information about the bucket that will be created. For more information about directory buckets, see \n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is only supported by directory buckets.</p>\n         </note>"
+        "smithy.api#documentation": "<p>Specifies the information about the bucket that will be created. For more information\n         about directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is only supported by directory buckets.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#BucketKeyEnabled": {
@@ -18293,7 +18300,7 @@
         "target": "com.amazonaws.s3#CompleteMultipartUploadOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Completes a multipart upload by assembling previously uploaded parts.</p>\n         <p>You first initiate the multipart upload and then upload all parts using the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n         operation or the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>\n         operation. After successfully uploading all relevant parts of an upload, you call this\n         <code>CompleteMultipartUpload</code> operation to complete the upload. Upon receiving this request, Amazon S3 concatenates all the parts\n         in ascending order by part number to create a new object. In the CompleteMultipartUpload \n         request, you must provide the parts list and ensure that the parts list is complete.\n         The CompleteMultipartUpload API operation concatenates the parts that you provide in the list. For each part in the list,\n         you must provide the <code>PartNumber</code> value and the <code>ETag</code> value that are returned after that part\n         was uploaded.</p>\n         <p>The processing of a CompleteMultipartUpload request could take several minutes to\n         finalize. After Amazon S3 begins processing the request, it sends an HTTP response header that\n         specifies a <code>200 OK</code> response. While processing is in progress, Amazon S3 periodically sends white\n         space characters to keep the connection from timing out. A request could fail after the\n         initial <code>200 OK</code> response has been sent. This means that a <code>200 OK</code> response can\n         contain either a success or an error. The error response might be embedded in the <code>200 OK</code> response. \n         If you call this API operation directly, make sure to design\n         your application to parse the contents of the response and handle it appropriately. If you\n         use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the embedded error and apply\n         error handling per your configuration settings (including automatically retrying the\n         request as appropriate). If the condition persists, the SDKs throw an exception (or, for\n         the SDKs that don't use exceptions, they return an error). </p>\n         <p>Note that if <code>CompleteMultipartUpload</code> fails, applications should be prepared\n         to retry any failed requests (including 500 error responses). For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html\">Amazon S3 Error Best\n         Practices</a>.</p>\n         <important>\n            <p>You can't use <code>Content-Type: application/x-www-form-urlencoded</code> for the \n            CompleteMultipartUpload requests. Also, if you don't provide a\n               <code>Content-Type</code> header, <code>CompleteMultipartUpload</code> can still return a <code>200\n            OK</code> response.</p>\n         </important>\n         <p>For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n         Upload</a> in the <i>Amazon S3\n            User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For\n                        information about permissions required to use the multipart upload API, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload and\n                           Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     <p>If you provide an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html\">additional checksum\n                        value</a> in your <code>MultipartUpload</code> requests and the\n                        object is encrypted with Key Management Service, you must have permission to use the\n                        <code>kms:Decrypt</code> action for the\n                        <code>CompleteMultipartUpload</code> request to succeed.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted with\n                        SSE-KMS, you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special errors</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>Error Code: <code>EntityTooSmall</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: Your proposed upload is smaller than the minimum allowed object\n                           size. Each part must be at least 5 MB in size, except the last part.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>InvalidPart</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: One or more of the specified parts could not be found. The part\n                           might not have been uploaded, or the specified ETag might not have\n                           matched the uploaded part's ETag.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>InvalidPartOrder</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The list of parts was not in ascending order. The parts list\n                           must be specified in order by part number.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>NoSuchUpload</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified multipart upload does not exist. The upload ID\n                           might be invalid, or the multipart upload might have been aborted or\n                           completed.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 404 Not Found</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CompleteMultipartUpload</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Completes a multipart upload by assembling previously uploaded parts.</p>\n         <p>You first initiate the multipart upload and then upload all parts using the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n         operation or the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a> operation.\n         After successfully uploading all relevant parts of an upload, you call this\n            <code>CompleteMultipartUpload</code> operation to complete the upload. Upon receiving\n         this request, Amazon S3 concatenates all the parts in ascending order by part number to create a\n         new object. In the CompleteMultipartUpload request, you must provide the parts list and\n         ensure that the parts list is complete. The CompleteMultipartUpload API operation\n         concatenates the parts that you provide in the list. For each part in the list, you must\n         provide the <code>PartNumber</code> value and the <code>ETag</code> value that are returned\n         after that part was uploaded.</p>\n         <p>The processing of a CompleteMultipartUpload request could take several minutes to\n         finalize. After Amazon S3 begins processing the request, it sends an HTTP response header that\n         specifies a <code>200 OK</code> response. While processing is in progress, Amazon S3\n         periodically sends white space characters to keep the connection from timing out. A request\n         could fail after the initial <code>200 OK</code> response has been sent. This means that a\n            <code>200 OK</code> response can contain either a success or an error. The error\n         response might be embedded in the <code>200 OK</code> response. If you call this API\n         operation directly, make sure to design your application to parse the contents of the\n         response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition.\n         The SDKs detect the embedded error and apply error handling per your configuration settings\n         (including automatically retrying the request as appropriate). If the condition persists,\n         the SDKs throw an exception (or, for the SDKs that don't use exceptions, they return an\n         error). </p>\n         <p>Note that if <code>CompleteMultipartUpload</code> fails, applications should be prepared\n         to retry any failed requests (including 500 error responses). For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html\">Amazon S3 Error\n            Best Practices</a>.</p>\n         <important>\n            <p>You can't use <code>Content-Type: application/x-www-form-urlencoded</code> for the\n            CompleteMultipartUpload requests. Also, if you don't provide a <code>Content-Type</code>\n            header, <code>CompleteMultipartUpload</code> can still return a <code>200 OK</code>\n            response.</p>\n         </important>\n         <p>For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n            Upload</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For\n                        information about permissions required to use the multipart upload API, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload and\n                           Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     <p>If you provide an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html\">additional checksum\n                           value</a> in your <code>MultipartUpload</code> requests and the\n                        object is encrypted with Key Management Service, you must have permission to use the\n                           <code>kms:Decrypt</code> action for the\n                           <code>CompleteMultipartUpload</code> request to succeed.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted with SSE-KMS, you must also have the\n                           <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions\n                        in IAM identity-based policies and KMS key policies for the KMS\n                        key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special errors</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>Error Code: <code>EntityTooSmall</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: Your proposed upload is smaller than the minimum\n                              allowed object size. Each part must be at least 5 MB in size, except\n                              the last part.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>InvalidPart</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: One or more of the specified parts could not be found.\n                              The part might not have been uploaded, or the specified ETag might not\n                              have matched the uploaded part's ETag.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>InvalidPartOrder</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The list of parts was not in ascending order. The\n                              parts list must be specified in order by part number.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>NoSuchUpload</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified multipart upload does not exist. The\n                              upload ID might be invalid, or the multipart upload might have been\n                              aborted or completed.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 404 Not Found</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CompleteMultipartUpload</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To complete multipart upload",
@@ -18434,7 +18441,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>Name of the bucket to which the multipart upload was initiated.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>Name of the bucket to which the multipart upload was initiated.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -18513,14 +18520,14 @@
         "IfNoneMatch": {
           "target": "com.amazonaws.s3#IfNoneMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Uploads the object only if the object key name does not already exist in the bucket specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>\n         <p>If a conflicting operation occurs during the upload S3 returns a <code>409 ConditionalRequestConflict</code> response.  On a 409 failure you should re-initiate the multipart upload with <code>CreateMultipartUpload</code> and re-upload each part.</p>\n         <p>Expects the '*' (asterisk) character.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>, or <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html\">Conditional requests</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>Uploads the object only if the object key name does not already exist in the bucket\n         specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>\n         <p>If a conflicting operation occurs during the upload S3 returns a <code>409\n            ConditionalRequestConflict</code> response. On a 409 failure you should re-initiate the\n         multipart upload with <code>CreateMultipartUpload</code> and re-upload each part.</p>\n         <p>Expects the '*' (asterisk) character.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>, or <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html\">Conditional requests</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpHeader": "If-None-Match"
           }
         },
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is\n         required only when the object was created using a checksum algorithm or if\n         your bucket policy requires the use of SSE-C. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html#ssec-require-condition-key\">Protecting data\n            using SSE-C keys</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The server-side encryption (SSE) algorithm used to encrypt the object. This parameter is\n         required only when the object was created using a checksum algorithm or if your bucket\n         policy requires the use of SSE-C. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html#ssec-require-condition-key\">Protecting data using SSE-C keys</a> in the <i>Amazon S3 User\n         Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
@@ -18595,7 +18602,7 @@
         "PartNumber": {
           "target": "com.amazonaws.s3#PartNumber",
           "traits": {
-            "smithy.api#documentation": "<p>Part number that identifies the part. This is a positive integer between 1 and\n         10,000.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - In <code>CompleteMultipartUpload</code>, when a additional checksum (including <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or \n               <code>x-amz-checksum-sha256</code>) is applied to each part, the <code>PartNumber</code> must start at 1 and \n               the part numbers must be consecutive. Otherwise, Amazon S3 generates an HTTP <code>400 Bad Request</code> status code and an <code>InvalidPartOrder</code> error code.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - In <code>CompleteMultipartUpload</code>, the <code>PartNumber</code> must start at 1 and \n               the part numbers must be consecutive.</p>\n               </li>\n            </ul>\n         </note>"
+            "smithy.api#documentation": "<p>Part number that identifies the part. This is a positive integer between 1 and\n         10,000.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - In\n                     <code>CompleteMultipartUpload</code>, when a additional checksum (including\n                     <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>,\n                     <code>x-amz-checksum-sha1</code>, or <code>x-amz-checksum-sha256</code>) is\n                  applied to each part, the <code>PartNumber</code> must start at 1 and the part\n                  numbers must be consecutive. Otherwise, Amazon S3 generates an HTTP <code>400 Bad\n                     Request</code> status code and an <code>InvalidPartOrder</code> error\n                  code.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - In\n                     <code>CompleteMultipartUpload</code>, the <code>PartNumber</code> must start at\n                  1 and the part numbers must be consecutive.</p>\n               </li>\n            </ul>\n         </note>"
           }
         }
       },
@@ -18697,7 +18704,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>Creates a copy of an object that is already stored in Amazon S3.</p>\n         <note>\n            <p>You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your\n            object up to 5 GB in size in a single atomic action using this API. However, to copy an\n            object greater than 5 GB, you must use the multipart upload Upload Part - Copy\n            (UploadPartCopy) API. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjctsUsingRESTMPUapi.html\">Copy Object Using the\n               REST Multipart Upload API</a>.</p>\n         </note>\n         <p>You can copy individual objects between general purpose buckets, between directory buckets, and \n         between general purpose buckets and directory buckets.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>Amazon S3 supports copy operations using Multi-Region Access Points only as a destination when using the Multi-Region Access Point ARN. </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>VPC endpoints don't support cross-Region requests (including copies). If you're using VPC endpoints, your source and destination buckets should be in the same Amazon Web Services Region as your VPC endpoint.</p>\n               </li>\n            </ul>\n         </note>\n         <p>Both the\n      Region that you want to copy the object from and the Region that you want to copy the\n      object to must be enabled for your account. For more information about how to enable a Region for your account, see <a href=\"https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#manage-acct-regions-enable-standalone\">Enable \n         or disable a Region for standalone accounts</a> in the\n         <i>Amazon Web Services Account Management Guide</i>.</p>\n         <important>\n            <p>Amazon S3 transfer acceleration does not support cross-Region copies. If you request a\n            cross-Region copy using a transfer acceleration endpoint, you get a <code>400 Bad\n               Request</code> error. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer\n                  Acceleration</a>.</p>\n         </important>\n         <dl>\n            <dt>Authentication and authorization</dt>\n            <dd>\n               <p>All <code>CopyObject</code> requests must be authenticated and signed by using IAM credentials (access key ID and secret access key for the IAM identities). All headers with the <code>x-amz-</code> prefix, including\n                        <code>x-amz-copy-source</code>, must be signed. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n               <p>\n                  <b>Directory buckets</b> - You must use the IAM credentials to authenticate and authorize your access to the <code>CopyObject</code> API operation, instead of using the \n                  temporary security credentials through the <code>CreateSession</code> API operation.</p>\n               <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have\n                  <i>read</i> access to the source object and <i>write</i>\n                  access to the destination bucket.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> -\n                        You must have permissions in an IAM policy based on the source and destination\n                        bucket types in a <code>CopyObject</code> operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object is in a general purpose bucket, you must have\n                                 <b>\n                                 <code>s3:GetObject</code>\n                              </b>\n                              permission to read the source object that is being copied. </p>\n                        </li>\n                        <li>\n                           <p>If the destination bucket is a general purpose bucket, you must have\n                                 <b>\n                                 <code>s3:PutObject</code>\n                              </b>\n                              permission to write the object copy to the destination bucket. </p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have permissions in a bucket policy or an IAM identity-based policy based on the source and destination\n                        bucket types in a <code>CopyObject</code> operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object that you want to copy is in a\n                              directory bucket, you must have the <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in\n                              the <code>Action</code> element of a policy to read the object. By default, the session is in the <code>ReadWrite</code> mode. If you want to restrict the access, you can explicitly set the <code>s3express:SessionMode</code> condition key to <code>ReadOnly</code> on the copy source bucket.</p>\n                        </li>\n                        <li>\n                           <p>If the copy destination is a directory bucket, you must have the <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in the\n                                 <code>Action</code> element of a policy to write the object\n                              to the destination. The <code>s3express:SessionMode</code> condition\n                              key can't be set to <code>ReadOnly</code> on the copy destination bucket. </p>\n                        </li>\n                     </ul>\n                     <p>If the object is encrypted with\n                        SSE-KMS, you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>\n                     <p>For example policies, 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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Response and special errors</dt>\n            <dd>\n               <p>When the request is an HTTP 1.1 request, the response is chunk encoded. When\n                  the request is not an HTTP 1.1 request, the response would not contain the\n                     <code>Content-Length</code>. You always need to read the entire response body\n                  to check if the copy succeeds. </p>\n               <ul>\n                  <li>\n                     <p>If the copy is successful, you receive a response with information about the copied\n                     object.</p>\n                  </li>\n                  <li>\n                     <p>A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3\n                        is copying the files. A <code>200 OK</code> response can contain either a success or an error.</p>\n                     <ul>\n                        <li>\n                           <p>If the error occurs before the copy action starts, you receive a\n                           standard Amazon S3 error.</p>\n                        </li>\n                        <li>\n                           <p>If the error occurs during the copy operation, the error response is\n                           embedded in the <code>200 OK</code> response. For example, in a cross-region copy, you \n                           may encounter throttling and receive a <code>200 OK</code> response. \n                           For more information, see <a href=\"https://repost.aws/knowledge-center/s3-resolve-200-internalerror\">Resolve \n                           the Error 200 response when copying objects to Amazon S3</a>. \n                           The <code>200 OK</code> status code means the copy was accepted, but  \n                           it doesn't mean the copy is complete. Another example is \n                           when you disconnect from Amazon S3 before the copy is complete, Amazon S3 might cancel the copy and you may receive a <code>200 OK</code> response. \n                           You must stay connected to Amazon S3 until the entire response is successfully received and processed.</p>\n                           <p>If you call this API operation directly, make\n                              sure to design your application to parse the content of the response and handle it\n                              appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the\n                              embedded error and apply error handling per your configuration settings (including\n                              automatically retrying the request as appropriate). If the condition persists, the SDKs\n                              throw an exception (or, for the SDKs that don't use exceptions, they return an \n                              error).</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Charge</dt>\n            <dd>\n               <p>The copy request charge is based on the storage class and Region that you specify for\n                  the destination object. The request can also result in a data retrieval charge for the\n                  source if the source storage class bills for data retrieval. If the copy source is in a different region, the data transfer is billed to the copy source account. For pricing information, see\n                  <a href=\"http://aws.amazon.com/s3/pricing/\">Amazon S3 pricing</a>.</p>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CopyObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Creates a copy of an object that is already stored in Amazon S3.</p>\n         <note>\n            <p>You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your\n            object up to 5 GB in size in a single atomic action using this API. However, to copy an\n            object greater than 5 GB, you must use the multipart upload Upload Part - Copy\n            (UploadPartCopy) API. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjctsUsingRESTMPUapi.html\">Copy Object Using the\n               REST Multipart Upload API</a>.</p>\n         </note>\n         <p>You can copy individual objects between general purpose buckets, between directory buckets,\n         and between general purpose buckets and directory buckets.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>Amazon S3 supports copy operations using Multi-Region Access Points only as a\n                  destination when using the Multi-Region Access Point ARN. </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> -\n                  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>VPC endpoints don't support cross-Region requests (including copies). If you're\n                  using VPC endpoints, your source and destination buckets should be in the same\n                  Amazon Web Services Region as your VPC endpoint.</p>\n               </li>\n            </ul>\n         </note>\n         <p>Both the Region that you want to copy the object from and the Region that you want to\n         copy the object to must be enabled for your account. For more information about how to\n         enable a Region for your account, see <a href=\"https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html#manage-acct-regions-enable-standalone\">Enable or disable a Region for standalone accounts</a> in the <i>Amazon Web Services\n            Account Management Guide</i>.</p>\n         <important>\n            <p>Amazon S3 transfer acceleration does not support cross-Region copies. If you request a\n            cross-Region copy using a transfer acceleration endpoint, you get a <code>400 Bad\n               Request</code> error. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer\n            Acceleration</a>.</p>\n         </important>\n         <dl>\n            <dt>Authentication and authorization</dt>\n            <dd>\n               <p>All <code>CopyObject</code> requests must be authenticated and signed by using\n                  IAM credentials (access key ID and secret access key for the IAM identities).\n                  All headers with the <code>x-amz-</code> prefix, including\n                     <code>x-amz-copy-source</code>, must be signed. For more information, see\n                     <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n               <p>\n                  <b>Directory buckets</b> - You must use the\n                  IAM credentials to authenticate and authorize your access to the\n                     <code>CopyObject</code> API operation, instead of using the temporary security\n                  credentials through the <code>CreateSession</code> API operation.</p>\n               <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your\n                  behalf.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have <i>read</i> access to the source object and\n                     <i>write</i> access to the destination bucket.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - You\n                        must have permissions in an IAM policy based on the source and destination\n                        bucket types in a <code>CopyObject</code> operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object is in a general purpose bucket, you must have\n                                 <b>\n                                 <code>s3:GetObject</code>\n                              </b>\n                              permission to read the source object that is being copied. </p>\n                        </li>\n                        <li>\n                           <p>If the destination bucket is a general purpose bucket, you must have\n                                 <b>\n                                 <code>s3:PutObject</code>\n                              </b>\n                              permission to write the object copy to the destination bucket. </p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have permissions in a bucket policy or an IAM identity-based policy based on the\n                        source and destination bucket types in a <code>CopyObject</code>\n                        operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object that you want to copy is in a\n                              directory bucket, you must have the <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in\n                              the <code>Action</code> element of a policy to read the object. By\n                              default, the session is in the <code>ReadWrite</code> mode. If you\n                              want to restrict the access, you can explicitly set the\n                                 <code>s3express:SessionMode</code> condition key to\n                                 <code>ReadOnly</code> on the copy source bucket.</p>\n                        </li>\n                        <li>\n                           <p>If the copy destination is a directory bucket, you must have the\n                                 <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in the\n                                 <code>Action</code> element of a policy to write the object to the\n                              destination. The <code>s3express:SessionMode</code> condition key\n                              can't be set to <code>ReadOnly</code> on the copy destination bucket.\n                           </p>\n                        </li>\n                     </ul>\n                     <p>If the object is encrypted with SSE-KMS, you must also have the\n                           <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions\n                        in IAM identity-based policies and KMS key policies for the KMS\n                        key.</p>\n                     <p>For example policies, 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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for\n                           S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Response and special errors</dt>\n            <dd>\n               <p>When the request is an HTTP 1.1 request, the response is chunk encoded. When\n                  the request is not an HTTP 1.1 request, the response would not contain the\n                     <code>Content-Length</code>. You always need to read the entire response body\n                  to check if the copy succeeds. </p>\n               <ul>\n                  <li>\n                     <p>If the copy is successful, you receive a response with information about\n                        the copied object.</p>\n                  </li>\n                  <li>\n                     <p>A copy request might return an error when Amazon S3 receives the copy request\n                        or while Amazon S3 is copying the files. A <code>200 OK</code> response can\n                        contain either a success or an error.</p>\n                     <ul>\n                        <li>\n                           <p>If the error occurs before the copy action starts, you receive a\n                              standard Amazon S3 error.</p>\n                        </li>\n                        <li>\n                           <p>If the error occurs during the copy operation, the error response\n                              is embedded in the <code>200 OK</code> response. For example, in a\n                              cross-region copy, you may encounter throttling and receive a\n                                 <code>200 OK</code> response. For more information, see <a href=\"https://repost.aws/knowledge-center/s3-resolve-200-internalerror\">Resolve the Error 200 response when copying objects to\n                                 Amazon S3</a>. The <code>200 OK</code> status code means the copy\n                              was accepted, but it doesn't mean the copy is complete. Another\n                              example is when you disconnect from Amazon S3 before the copy is complete,\n                              Amazon S3 might cancel the copy and you may receive a <code>200 OK</code>\n                              response. You must stay connected to Amazon S3 until the entire response is\n                              successfully received and processed.</p>\n                           <p>If you call this API operation directly, make sure to design your\n                              application to parse the content of the response and handle it\n                              appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The\n                              SDKs detect the embedded error and apply error handling per your\n                              configuration settings (including automatically retrying the request\n                              as appropriate). If the condition persists, the SDKs throw an\n                              exception (or, for the SDKs that don't use exceptions, they return an\n                              error).</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Charge</dt>\n            <dd>\n               <p>The copy request charge is based on the storage class and Region that you\n                  specify for the destination object. The request can also result in a data\n                  retrieval charge for the source if the source storage class bills for data\n                  retrieval. If the copy source is in a different region, the data transfer is\n                  billed to the copy source account. For pricing information, see <a href=\"http://aws.amazon.com/s3/pricing/\">Amazon S3 pricing</a>.</p>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CopyObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To copy an object",
@@ -18761,7 +18768,7 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,\n            <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for\n         example, <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
@@ -18775,7 +18782,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification of\n         the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification\n         of the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -18817,14 +18824,14 @@
         "ACL": {
           "target": "com.amazonaws.s3#ObjectCannedACL",
           "traits": {
-            "smithy.api#documentation": "<p>The canned access control list (ACL) to apply to the object.</p>\n         <p>When you copy an object, the ACL metadata is not preserved and is set\n         to <code>private</code> by default. Only the owner has full access\n         control. To override the default ACL setting,\n         specify a new ACL when you generate a copy request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using\n            ACLs</a>. </p>\n         <p>If the destination bucket that you're copying objects to uses the bucket owner enforced\n         setting for S3 Object Ownership, ACLs are disabled and no longer affect\n         permissions. Buckets that use this setting only accept <code>PUT</code> requests\n         that don't specify an ACL or <code>PUT</code> requests that specify bucket owner\n         full control ACLs, such as the <code>bucket-owner-full-control</code> canned ACL\n         or an equivalent form of this ACL expressed in the XML format. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling\n         ownership of objects and disabling ACLs</a> in the\n         <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>If your destination bucket uses the bucket owner enforced setting for Object Ownership,\n                  all objects written to the bucket by any account will be owned by the bucket\n                  owner.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>The canned access control list (ACL) to apply to the object.</p>\n         <p>When you copy an object, the ACL metadata is not preserved and is set to\n            <code>private</code> by default. Only the owner has full access control. To override the\n         default ACL setting, specify a new ACL when you generate a copy request. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. </p>\n         <p>If the destination bucket that you're copying objects to uses the bucket owner enforced\n         setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions.\n         Buckets that use this setting only accept <code>PUT</code> requests that don't specify an\n         ACL or <code>PUT</code> requests that specify bucket owner full control ACLs, such as the\n            <code>bucket-owner-full-control</code> canned ACL or an equivalent form of this ACL\n         expressed in the XML format. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling ownership of\n            objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>If your destination bucket uses the bucket owner enforced setting for Object\n                  Ownership, all objects written to the bucket by any account will be owned by the\n                  bucket owner.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-acl"
           }
         },
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the destination bucket.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the destination bucket.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -18842,14 +18849,14 @@
         "ChecksumAlgorithm": {
           "target": "com.amazonaws.s3#ChecksumAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates the algorithm that you want Amazon S3 to use to create the checksum for the object. For more information, see\n    <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html\">Checking object integrity</a> in\n    the <i>Amazon S3 User Guide</i>.</p>\n         <p>When you copy an object, if the source object has a checksum, that checksum value will be copied to\n         the new object by default. If the <code>CopyObject</code> request does not include this <code>x-amz-checksum-algorithm</code> header, the checksum algorithm will be copied from the source object to the destination object (if it's present on the source object). You can optionally\n         specify a different checksum algorithm to use with the\n         <code>x-amz-checksum-algorithm</code> header. Unrecognized or unsupported values will respond with the HTTP status code <code>400 Bad Request</code>.</p>\n         <note>\n            <p>For directory buckets, when you use Amazon Web Services SDKs, <code>CRC32</code> is the default checksum algorithm that's used for performance.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Indicates the algorithm that you want Amazon S3 to use to create the checksum for the object. For more information, see\n    <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html\">Checking object integrity</a> in\n    the <i>Amazon S3 User Guide</i>.</p>\n         <p>When you copy an object, if the source object has a checksum, that checksum value will\n         be copied to the new object by default. If the <code>CopyObject</code> request does not\n         include this <code>x-amz-checksum-algorithm</code> header, the checksum algorithm will be\n         copied from the source object to the destination object (if it's present on the source\n         object). You can optionally specify a different checksum algorithm to use with the\n            <code>x-amz-checksum-algorithm</code> header. Unrecognized or unsupported values will\n         respond with the HTTP status code <code>400 Bad Request</code>.</p>\n         <note>\n            <p>For directory buckets, when you use Amazon Web Services SDKs, <code>CRC32</code> is the default checksum algorithm that's used for performance.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-checksum-algorithm"
           }
         },
         "ContentDisposition": {
           "target": "com.amazonaws.s3#ContentDisposition",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies presentational information for the object. Indicates whether an object should be displayed in a web browser or downloaded as a file. It allows specifying the desired filename for the downloaded file.</p>",
+            "smithy.api#documentation": "<p>Specifies presentational information for the object. Indicates whether an object should\n         be displayed in a web browser or downloaded as a file. It allows specifying the desired\n         filename for the downloaded file.</p>",
             "smithy.api#httpHeader": "Content-Disposition"
           }
         },
@@ -18877,7 +18884,7 @@
         "CopySource": {
           "target": "com.amazonaws.s3#CopySource",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the source object for the copy operation. The source object \n         can be up to 5 GB. If the source object is an object that was uploaded by using a multipart upload, the object copy will be a single part object after the source object is copied to the destination bucket.</p>\n         <p>You specify the value of the copy source in one of two\n         formats, depending on whether you want to access the source object through an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-points.html\">access point</a>:</p>\n         <ul>\n            <li>\n               <p>For objects not accessed through an access point, specify the name of the source bucket\n               and the key of the source object, separated by a slash (/). For example, to copy the\n               object <code>reports/january.pdf</code> from the general purpose bucket \n               <code>awsexamplebucket</code>, use <code>awsexamplebucket/reports/january.pdf</code>.\n               The value must be URL-encoded. To copy the\n               object <code>reports/january.pdf</code> from the directory bucket \n               <code>awsexamplebucket--use1-az5--x-s3</code>, use <code>awsexamplebucket--use1-az5--x-s3/reports/january.pdf</code>.\n               The value must be URL-encoded.</p>\n            </li>\n            <li>\n               <p>For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format <code>arn:aws:s3:<Region>:<account-id>:accesspoint/<access-point-name>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through access point <code>my-access-point</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf</code>. The value must be URL encoded.</p>\n               <note>\n                  <ul>\n                     <li>\n                        <p>Amazon S3 supports copy operations using Access points only when the source and destination buckets are in the same Amazon Web Services Region.</p>\n                     </li>\n                     <li>\n                        <p>Access points are not supported by directory buckets.</p>\n                     </li>\n                  </ul>\n               </note>\n               <p>Alternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format <code>arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through outpost <code>my-outpost</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf</code>. The value must be URL-encoded.  </p>\n            </li>\n         </ul>\n         <p>If your source bucket versioning is enabled, the <code>x-amz-copy-source</code> header by default identifies the current\n         version of an object to copy. If the current version is a delete marker, Amazon S3\n         behaves as if the object was deleted. To copy a different version, use the\n         <code>versionId</code> query parameter. Specifically, append <code>?versionId=<version-id></code>\n         to the value (for example,\n         <code>awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>).\n         If you don't specify a version ID, Amazon S3 copies the latest version of the source\n         object.</p>\n         <p>If you enable versioning on the destination bucket, Amazon S3 generates a unique version\n         ID for the copied object. This version ID is different from the version ID\n         of the source object. Amazon S3 returns the version ID of the copied object in the\n         <code>x-amz-version-id</code> response header in the response.</p>\n         <p>If you do not enable versioning or suspend it on the destination bucket, the version\n         ID that Amazon S3 generates in the\n         <code>x-amz-version-id</code> response header is always null.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the source object for the copy operation. The source object can be up to 5 GB.\n         If the source object is an object that was uploaded by using a multipart upload, the object\n         copy will be a single part object after the source object is copied to the destination\n         bucket.</p>\n         <p>You specify the value of the copy source in one of two formats, depending on whether you\n         want to access the source object through an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-points.html\">access point</a>:</p>\n         <ul>\n            <li>\n               <p>For objects not accessed through an access point, specify the name of the source bucket\n               and the key of the source object, separated by a slash (/). For example, to copy the\n               object <code>reports/january.pdf</code> from the general purpose bucket\n                  <code>awsexamplebucket</code>, use\n                  <code>awsexamplebucket/reports/january.pdf</code>. The value must be URL-encoded.\n               To copy the object <code>reports/january.pdf</code> from the directory bucket\n                  <code>awsexamplebucket--use1-az5--x-s3</code>, use\n                  <code>awsexamplebucket--use1-az5--x-s3/reports/january.pdf</code>. The value must\n               be URL-encoded.</p>\n            </li>\n            <li>\n               <p>For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format <code>arn:aws:s3:<Region>:<account-id>:accesspoint/<access-point-name>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through access point <code>my-access-point</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf</code>. The value must be URL encoded.</p>\n               <note>\n                  <ul>\n                     <li>\n                        <p>Amazon S3 supports copy operations using Access points only when the source and destination buckets are in the same Amazon Web Services Region.</p>\n                     </li>\n                     <li>\n                        <p>Access points are not supported by directory buckets.</p>\n                     </li>\n                  </ul>\n               </note>\n               <p>Alternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format <code>arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through outpost <code>my-outpost</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf</code>. The value must be URL-encoded.  </p>\n            </li>\n         </ul>\n         <p>If your source bucket versioning is enabled, the <code>x-amz-copy-source</code> header\n         by default identifies the current version of an object to copy. If the current version is a\n         delete marker, Amazon S3 behaves as if the object was deleted. To copy a different version, use\n         the <code>versionId</code> query parameter. Specifically, append\n            <code>?versionId=<version-id></code> to the value (for example,\n            <code>awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>).\n         If you don't specify a version ID, Amazon S3 copies the latest version of the source\n         object.</p>\n         <p>If you enable versioning on the destination bucket, Amazon S3 generates a unique version ID\n         for the copied object. This version ID is different from the version ID of the source\n         object. Amazon S3 returns the version ID of the copied object in the\n            <code>x-amz-version-id</code> response header in the response.</p>\n         <p>If you do not enable versioning or suspend it on the destination bucket, the version ID\n         that Amazon S3 generates in the <code>x-amz-version-id</code> response header is always\n         null.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            S3 Versioning isn't enabled and supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-copy-source",
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -18888,28 +18895,28 @@
         "CopySourceIfMatch": {
           "target": "com.amazonaws.s3#CopySourceIfMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) matches the specified tag.</p>\n         <p> If both the <code>x-amz-copy-source-if-match</code> and\n         <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the\n         request and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the\n         data:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-match</code> condition evaluates to\n               true</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n               false</p>\n            </li>\n         </ul>",
+            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) matches the specified tag.</p>\n         <p> If both the <code>x-amz-copy-source-if-match</code> and\n            <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request\n         and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the data:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-match</code> condition evaluates to true</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n               false</p>\n            </li>\n         </ul>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-match"
           }
         },
         "CopySourceIfModifiedSince": {
           "target": "com.amazonaws.s3#CopySourceIfModifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if it has been modified since the specified time.</p>\n         <p>If both the <code>x-amz-copy-source-if-none-match</code> and\n         <code>x-amz-copy-source-if-modified-since</code> headers are present in the\n         request and evaluate as follows, Amazon S3 returns the <code>412 Precondition\n            Failed</code> response code:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-none-match</code> condition evaluates to\n               false</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n               true</p>\n            </li>\n         </ul>",
+            "smithy.api#documentation": "<p>Copies the object if it has been modified since the specified time.</p>\n         <p>If both the <code>x-amz-copy-source-if-none-match</code> and\n            <code>x-amz-copy-source-if-modified-since</code> headers are present in the request and\n         evaluate as follows, Amazon S3 returns the <code>412 Precondition Failed</code> response\n         code:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-none-match</code> condition evaluates to false</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n               true</p>\n            </li>\n         </ul>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-modified-since"
           }
         },
         "CopySourceIfNoneMatch": {
           "target": "com.amazonaws.s3#CopySourceIfNoneMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) is different than the specified ETag.</p>\n         <p>If both the <code>x-amz-copy-source-if-none-match</code> and\n         <code>x-amz-copy-source-if-modified-since</code> headers are present in the\n         request and evaluate as follows, Amazon S3 returns the <code>412 Precondition\n            Failed</code> response code:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-none-match</code> condition evaluates to\n               false</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n               true</p>\n            </li>\n         </ul>",
+            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) is different than the specified ETag.</p>\n         <p>If both the <code>x-amz-copy-source-if-none-match</code> and\n            <code>x-amz-copy-source-if-modified-since</code> headers are present in the request and\n         evaluate as follows, Amazon S3 returns the <code>412 Precondition Failed</code> response\n         code:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-none-match</code> condition evaluates to false</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n               true</p>\n            </li>\n         </ul>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-none-match"
           }
         },
         "CopySourceIfUnmodifiedSince": {
           "target": "com.amazonaws.s3#CopySourceIfUnmodifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if it hasn't been modified since the specified time.</p>\n         <p> If both the <code>x-amz-copy-source-if-match</code> and\n         <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the\n         request and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the\n         data:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-match</code> condition evaluates to\n               true</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n               false</p>\n            </li>\n         </ul>",
+            "smithy.api#documentation": "<p>Copies the object if it hasn't been modified since the specified time.</p>\n         <p> If both the <code>x-amz-copy-source-if-match</code> and\n            <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request\n         and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the data:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-match</code> condition evaluates to true</p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n               false</p>\n            </li>\n         </ul>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-unmodified-since"
           }
         },
@@ -18969,7 +18976,7 @@
         "MetadataDirective": {
           "target": "com.amazonaws.s3#MetadataDirective",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies whether the metadata is copied from the source object or replaced with\n         metadata that's provided in the request. \n        When copying an object, you can preserve all metadata (the default) or specify\n        new metadata. If this header isn’t specified, <code>COPY</code> is the default behavior. \n      </p>\n         <p>\n            <b>General purpose bucket</b> - For general purpose buckets, when you grant permissions, you\n         can use the <code>s3:x-amz-metadata-directive</code> condition key to enforce\n         certain metadata behavior when objects are uploaded. For more information, see\n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/amazon-s3-policy-keys.html\">Amazon S3 condition key examples</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <code>x-amz-website-redirect-location</code> is unique to each object and is not copied when using the\n            <code>x-amz-metadata-directive</code> header. To copy the value, you \n            must specify <code>x-amz-website-redirect-location</code> in the request header.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies whether the metadata is copied from the source object or replaced with\n         metadata that's provided in the request. When copying an object, you can preserve all\n         metadata (the default) or specify new metadata. If this header isn’t specified,\n            <code>COPY</code> is the default behavior. </p>\n         <p>\n            <b>General purpose bucket</b> - For general purpose buckets, when you\n         grant permissions, you can use the <code>s3:x-amz-metadata-directive</code> condition key\n         to enforce certain metadata behavior when objects are uploaded. For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/amazon-s3-policy-keys.html\">Amazon S3\n            condition key examples</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <code>x-amz-website-redirect-location</code> is unique to each object and is not\n            copied when using the <code>x-amz-metadata-directive</code> header. To copy the value,\n            you must specify <code>x-amz-website-redirect-location</code> in the request\n            header.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-metadata-directive"
           }
         },
@@ -18983,28 +18990,28 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm used when storing this object in Amazon S3. Unrecognized or unsupported values won’t write a destination object and will receive a <code>400 Bad Request</code> response. </p>\n         <p>Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket.\n         When copying an object, if you don't specify encryption information in your copy\n         request, the encryption setting of the target object is set to the default\n         encryption configuration of the destination bucket. By default, all buckets have a\n         base level of encryption configuration that uses server-side encryption with Amazon S3\n         managed keys (SSE-S3). If the destination bucket has a different default encryption\n         configuration, Amazon S3 uses\n         the corresponding encryption key to encrypt the target\n         object copy.</p>\n         <p>With server-side\n         encryption, Amazon S3 encrypts your data as it writes your data to disks in its data\n         centers and decrypts the data when you access it. For more information about server-side encryption, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Using\n            Server-Side Encryption</a> in the\n         <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>General purpose buckets </b>\n         </p>\n         <ul>\n            <li>\n               <p>For general purpose buckets, there are the following supported options for server-side encryption: server-side encryption with Key Management Service (KMS) keys\n            (SSE-KMS), dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), and \n            server-side encryption with customer-provided encryption keys (SSE-C). Amazon S3 uses\n            the corresponding KMS key, or a customer-provided key to encrypt the target\n            object copy.</p>\n            </li>\n            <li>\n               <p>When you perform a <code>CopyObject</code> operation, if you want to use a\n               different type of encryption setting for the target object, you can specify \n               appropriate encryption-related headers to encrypt the target object with an Amazon S3 managed key, a\n               KMS key, or a customer-provided key. If the encryption setting in\n               your request is different from the default encryption configuration of the\n               destination bucket, the encryption setting in your request takes precedence. </p>\n            </li>\n         </ul>\n         <p>\n            <b>Directory buckets </b>\n         </p>\n         <ul>\n            <li>\n               <p>For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n            </li>\n            <li>\n               <p>To encrypt new object copies to a directory bucket with SSE-KMS, we recommend you specify SSE-KMS as the directory bucket's default encryption configuration with a KMS key (specifically, a <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk\">customer managed key</a>). \n            The <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. 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 for the lifetime of the bucket. After you specify a customer managed key for SSE-KMS, you can't override the customer managed key for the bucket's SSE-KMS configuration. \n            Then, when you perform a <code>CopyObject</code> operation and want to specify server-side encryption settings for new object copies with SSE-KMS in the encryption-related request headers, you must ensure the encryption key is the same customer managed key that you specified for the directory bucket's default encryption configuration. \n            </p>\n            </li>\n         </ul>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm used when storing this object in Amazon S3. Unrecognized\n         or unsupported values won’t write a destination object and will receive a <code>400 Bad\n            Request</code> response. </p>\n         <p>Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket. When\n         copying an object, if you don't specify encryption information in your copy request, the\n         encryption setting of the target object is set to the default encryption configuration of\n         the destination bucket. By default, all buckets have a base level of encryption\n         configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the\n         destination bucket has a different default encryption configuration, Amazon S3 uses the\n         corresponding encryption key to encrypt the target object copy.</p>\n         <p>With server-side encryption, Amazon S3 encrypts your data as it writes your data to disks in\n         its data centers and decrypts the data when you access it. For more information about\n         server-side encryption, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Using Server-Side Encryption</a>\n         in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>General purpose buckets </b>\n         </p>\n         <ul>\n            <li>\n               <p>For general purpose buckets, there are the following supported options for server-side\n               encryption: server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer\n               server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), and server-side encryption\n               with customer-provided encryption keys (SSE-C). Amazon S3 uses the corresponding\n               KMS key, or a customer-provided key to encrypt the target object copy.</p>\n            </li>\n            <li>\n               <p>When you perform a <code>CopyObject</code> operation, if you want to use a\n               different type of encryption setting for the target object, you can specify\n               appropriate encryption-related headers to encrypt the target object with an Amazon S3\n               managed key, a KMS key, or a customer-provided key. If the encryption setting in\n               your request is different from the default encryption configuration of the\n               destination bucket, the encryption setting in your request takes precedence. </p>\n            </li>\n         </ul>\n         <p>\n            <b>Directory buckets </b>\n         </p>\n         <ul>\n            <li>\n               <p>For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n            </li>\n            <li>\n               <p>To encrypt new object copies to a directory bucket with SSE-KMS, we recommend you\n               specify SSE-KMS as the directory bucket's default encryption configuration with\n               a KMS key (specifically, a <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk\">customer managed key</a>).\n               The <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. Your SSE-KMS\n               configuration can only support 1 <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk\">customer managed key</a> per\n               directory bucket for the lifetime of the bucket. After you specify a customer managed key for\n               SSE-KMS, you can't override the customer managed key for the bucket's SSE-KMS\n               configuration. Then, when you perform a <code>CopyObject</code> operation and want to\n               specify server-side encryption settings for new object copies with SSE-KMS in the\n               encryption-related request headers, you must ensure the encryption key is the same\n               customer managed key that you specified for the directory bucket's default encryption\n               configuration.\n               </p>\n            </li>\n         </ul>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>If the <code>x-amz-storage-class</code> header is not used, the copied object will be stored in the\n         <code>STANDARD</code> Storage Class by default. The <code>STANDARD</code> storage class provides high durability and\n         high availability. Depending on performance needs, you can specify a different Storage\n         Class.\n      </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects. \nUnsupported storage class values won't write a destination object and will respond with the HTTP status code <code>400 Bad Request</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Amazon S3 on Outposts </b> - S3 on Outposts only uses the <code>OUTPOSTS</code> Storage Class.</p>\n               </li>\n            </ul>\n         </note>\n         <p>You can use the <code>CopyObject</code> action to change the storage class of\n         an object that is already stored in Amazon S3 by using the <code>x-amz-storage-class</code> \n         header. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a> in\n         the <i>Amazon S3 User Guide</i>.</p>\n         <p>Before using an object as a source object for the copy operation, you must restore a copy of it if it meets any of the following conditions:</p>\n         <ul>\n            <li>\n               <p>The storage class of the source object is <code>GLACIER</code> or\n            <code>DEEP_ARCHIVE</code>.</p>\n            </li>\n            <li>\n               <p>The storage class of the source object is\n            <code>INTELLIGENT_TIERING</code> and it's <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering-overview.html#intel-tiering-tier-definition\">S3 Intelligent-Tiering access tier</a> is\n            <code>Archive Access</code> or <code>Deep Archive Access</code>.</p>\n            </li>\n         </ul>\n         <p>For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html\">Copying\n               Objects</a> in\n         the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>If the <code>x-amz-storage-class</code> header is not used, the copied object will be\n         stored in the <code>STANDARD</code> Storage Class by default. The <code>STANDARD</code>\n         storage class provides high durability and high availability. Depending on performance\n         needs, you can specify a different Storage Class. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> -\n                  For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects. \nUnsupported storage class values won't write a destination object and will respond with the HTTP status code <code>400 Bad Request</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Amazon S3 on Outposts </b> - S3 on Outposts only\n                  uses the <code>OUTPOSTS</code> Storage Class.</p>\n               </li>\n            </ul>\n         </note>\n         <p>You can use the <code>CopyObject</code> action to change the storage class of an object\n         that is already stored in Amazon S3 by using the <code>x-amz-storage-class</code> header. For\n         more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>Before using an object as a source object for the copy operation, you must restore a\n         copy of it if it meets any of the following conditions:</p>\n         <ul>\n            <li>\n               <p>The storage class of the source object is <code>GLACIER</code> or\n                  <code>DEEP_ARCHIVE</code>.</p>\n            </li>\n            <li>\n               <p>The storage class of the source object is <code>INTELLIGENT_TIERING</code> and\n               it's <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering-overview.html#intel-tiering-tier-definition\">S3 Intelligent-Tiering access tier</a> is <code>Archive Access</code> or\n                  <code>Deep Archive Access</code>.</p>\n            </li>\n         </ul>\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html\">Copying\n            Objects</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpHeader": "x-amz-storage-class"
           }
         },
         "WebsiteRedirectLocation": {
           "target": "com.amazonaws.s3#WebsiteRedirectLocation",
           "traits": {
-            "smithy.api#documentation": "<p>If the destination bucket is configured as a website, redirects requests for this object copy to another\n         object in the same bucket or to an external URL. Amazon S3 stores the value of this header in\n         the object metadata. This value is unique to each object and is not copied when using the\n            <code>x-amz-metadata-directive</code> header. Instead, you may opt to provide this\n         header in combination with the <code>x-amz-metadata-directive</code> header.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If the destination bucket is configured as a website, redirects requests for this object\n         copy to another object in the same bucket or to an external URL. Amazon S3 stores the value of\n         this header in the object metadata. This value is unique to each object and is not copied\n         when using the <code>x-amz-metadata-directive</code> header. Instead, you may opt to\n         provide this header in combination with the <code>x-amz-metadata-directive</code>\n         header.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-website-redirect-location"
           }
         },
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n         <code>AES256</code>).</p>\n         <p>When you perform a <code>CopyObject</code> operation, if you want to use a\n         different type of encryption setting for the target object, you can specify \n         appropriate encryption-related headers to encrypt the target object with an Amazon S3 managed key, a\n         KMS key, or a customer-provided key. If the encryption setting in\n         your request is different from the default encryption configuration of the\n         destination bucket, the encryption setting in your request takes precedence. </p>\n         <note>\n            <p>This functionality is not supported when the destination bucket is a directory bucket.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n            <code>AES256</code>).</p>\n         <p>When you perform a <code>CopyObject</code> operation, if you want to use a different\n         type of encryption setting for the target object, you can specify appropriate\n         encryption-related headers to encrypt the target object with an Amazon S3 managed key, a\n         KMS key, or a customer-provided key. If the encryption setting in your request is\n         different from the default encryption configuration of the destination bucket, the\n         encryption setting in your request takes precedence. </p>\n         <note>\n            <p>This functionality is not supported when the destination bucket is a directory bucket.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
@@ -19025,42 +19032,42 @@
         "SSEKMSKeyId": {
           "target": "com.amazonaws.s3#SSEKMSKeyId",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption. All GET and PUT requests for an\n         object protected by KMS will fail if they're not made via SSL or using SigV4. For\n         information about configuring any of the officially supported Amazon Web Services SDKs and Amazon Web Services CLI, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version\">Specifying the\n            Signature Version in Request Authentication</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Directory buckets</b> - If you specify <code>x-amz-server-side-encryption</code> with <code>aws:kms</code>, the <code>\n         x-amz-server-side-encryption-aws-kms-key-id</code> header is implicitly assigned the ID of the KMS \n         symmetric encryption customer managed key that's configured for your directory bucket's default encryption setting. \n         If you want to specify the <code>\n         x-amz-server-side-encryption-aws-kms-key-id</code> header explicitly, you can only specify it with the ID (Key ID or Key ARN) of the KMS \n         customer managed key that's configured for your directory bucket's default encryption setting. Otherwise, you get an HTTP <code>400 Bad Request</code> error. Only use the key ID or key ARN. The key alias format of the KMS key isn't supported. 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 for the lifetime of the bucket. \nThe <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n</p>",
+            "smithy.api#documentation": "<p>Specifies the KMS key ID (Key ID, Key ARN, or Key Alias) to use for object encryption.\n         All GET and PUT requests for an object protected by KMS will fail if they're not made via\n         SSL or using SigV4. For information about configuring any of the officially supported Amazon Web Services\n         SDKs and Amazon Web Services CLI, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version\">Specifying the\n            Signature Version in Request Authentication</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Directory buckets</b> -\n         If you specify <code>x-amz-server-side-encryption</code> with <code>aws:kms</code>, the <code>\n         x-amz-server-side-encryption-aws-kms-key-id</code> header is implicitly assigned the ID of the KMS \n         symmetric encryption customer managed key that's configured for your directory bucket's default encryption setting. \n         If you want to specify the <code>\n         x-amz-server-side-encryption-aws-kms-key-id</code> header explicitly, you can only specify it with the ID (Key ID or Key ARN) of the KMS \n         customer managed key that's configured for your directory bucket's default encryption setting. Otherwise, you get an HTTP <code>400 Bad Request</code> error. Only use the key ID or key ARN. The key alias format of the KMS key isn't supported. 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 for the lifetime of the bucket. \nThe <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-aws-kms-key-id"
           }
         },
         "SSEKMSEncryptionContext": {
           "target": "com.amazonaws.s3#SSEKMSEncryptionContext",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use for the destination object encryption. The value of\n         this header is a base64-encoded UTF-8 string holding JSON with the encryption context\n         key-value pairs.</p>\n         <p>\n            <b>General purpose buckets</b> - This value must be explicitly added to specify encryption context for \n         <code>CopyObject</code> requests if you want an additional encryption context for your destination object. The additional encryption context of the source object won't be copied to the destination object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html#encryption-context\">Encryption context</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Directory buckets</b> - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported. </p>",
+            "smithy.api#documentation": "<p>Specifies the Amazon Web Services KMS Encryption Context as an additional encryption context to use\n         for the destination object encryption. The value of this header is a base64-encoded UTF-8\n         string holding JSON with the encryption context key-value pairs.</p>\n         <p>\n            <b>General purpose buckets</b> - This value must be explicitly\n         added to specify encryption context for <code>CopyObject</code> requests if you want an\n         additional encryption context for your destination object. The additional encryption\n         context of the source object won't be copied to the destination object. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html#encryption-context\">Encryption\n            context</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Directory buckets</b> - You can optionally provide an explicit encryption context value. The value must match the default encryption context - the bucket Amazon Resource Name (ARN). An additional encryption context value is not supported. </p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-context"
           }
         },
         "BucketKeyEnabled": {
           "target": "com.amazonaws.s3#BucketKeyEnabled",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with\n         server-side encryption using Key Management Service (KMS) keys (SSE-KMS). If a target object uses SSE-KMS, you can enable an S3 Bucket Key for the\n         object.</p>\n         <p>Setting this header to\n         <code>true</code> causes Amazon S3 to use an S3 Bucket Key for object encryption with\n         SSE-KMS. Specifying this header with a COPY action doesn’t affect bucket-level settings for S3\n         Bucket Key.</p>\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html\">Amazon S3 Bucket Keys</a> in the\n         <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies whether Amazon S3 should use an S3 Bucket Key for object encryption with\n         server-side encryption using Key Management Service (KMS) keys (SSE-KMS). If a target object uses\n         SSE-KMS, you can enable an S3 Bucket Key for the object.</p>\n         <p>Setting this header to <code>true</code> causes Amazon S3 to use an S3 Bucket Key for object\n         encryption with SSE-KMS. Specifying this header with a COPY action doesn’t affect\n         bucket-level settings for S3 Bucket Key.</p>\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html\">Amazon S3 Bucket Keys</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled"
           }
         },
         "CopySourceSSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#CopySourceSSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when decrypting the source object (for example,\n         <code>AES256</code>).</p>\n         <p>If\n      the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the\n      necessary encryption information in your request so that Amazon S3 can decrypt the\n      object for copying.</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when decrypting the source object (for example,\n            <code>AES256</code>).</p>\n         <p>If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the\n         necessary encryption information in your request so that Amazon S3 can decrypt the object for\n         copying.</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-copy-source-server-side-encryption-customer-algorithm"
           }
         },
         "CopySourceSSECustomerKey": {
           "target": "com.amazonaws.s3#CopySourceSSECustomerKey",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the customer-provided encryption key for Amazon S3 to use to decrypt the source\n         object. The encryption key provided in this header must be the same one that was used when the\n         source object was created.</p>\n         <p>If\n         the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the\n         necessary encryption information in your request so that Amazon S3 can decrypt the\n         object for copying.</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the customer-provided encryption key for Amazon S3 to use to decrypt the source\n         object. The encryption key provided in this header must be the same one that was used when\n         the source object was created.</p>\n         <p>If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the\n         necessary encryption information in your request so that Amazon S3 can decrypt the object for\n         copying.</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-copy-source-server-side-encryption-customer-key"
           }
         },
         "CopySourceSSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#CopySourceSSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses\n         this header for a message integrity check to ensure that the encryption key was transmitted\n         without error.</p>\n         <p>If\n         the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the\n         necessary encryption information in your request so that Amazon S3 can decrypt the\n         object for copying.</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. Amazon S3 uses\n         this header for a message integrity check to ensure that the encryption key was transmitted\n         without error.</p>\n         <p>If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the\n         necessary encryption information in your request so that Amazon S3 can decrypt the object for\n         copying.</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-copy-source-server-side-encryption-customer-key-MD5"
           }
         },
@@ -19073,7 +19080,7 @@
         "Tagging": {
           "target": "com.amazonaws.s3#TaggingHeader",
           "traits": {
-            "smithy.api#documentation": "<p>The tag-set for the object copy in the destination bucket. This value must be used in conjunction\n         with the <code>x-amz-tagging-directive</code> if you choose <code>REPLACE</code> for the <code>x-amz-tagging-directive</code>. If you choose <code>COPY</code> for the <code>x-amz-tagging-directive</code>, you don't need to set \n         the <code>x-amz-tagging</code> header, because the tag-set will be copied from the source object directly. The tag-set must be encoded as URL Query\n         parameters.</p>\n         <p>The default value is the empty value.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets in a <code>CopyObject</code> operation, only the empty tag-set is supported. Any requests that attempt to write non-empty tags into directory buckets will receive a <code>501 Not Implemented</code> status code. \nWhen the destination bucket is a directory bucket, you will receive a <code>501 Not Implemented</code> response in any of the following situations:</p>\n            <ul>\n               <li>\n                  <p>When you attempt to <code>COPY</code> the tag-set from an S3 source object that has non-empty tags.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a source object and set a non-empty value to <code>x-amz-tagging</code>.</p>\n               </li>\n               <li>\n                  <p>When you don't set the <code>x-amz-tagging-directive</code> header and the source object has non-empty tags. This is because the default value of <code>x-amz-tagging-directive</code> is <code>COPY</code>.</p>\n               </li>\n            </ul>\n            <p>Because only the empty tag-set is supported for directory buckets in a <code>CopyObject</code> operation, the following situations are allowed:</p>\n            <ul>\n               <li>\n                  <p>When you attempt to <code>COPY</code> the tag-set from a directory bucket source object that has no tags to a general purpose bucket. It copies an empty tag-set to the destination object.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a directory bucket source object and set the <code>x-amz-tagging</code> value of the directory bucket destination object to empty.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a general purpose bucket source object that has non-empty tags and set the <code>x-amz-tagging</code> value of the directory bucket destination object to empty.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a directory bucket source object and don't set the <code>x-amz-tagging</code> value of the directory bucket destination object. This is because the default value of <code>x-amz-tagging</code> is the empty value.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>The tag-set for the object copy in the destination bucket. This value must be used in\n         conjunction with the <code>x-amz-tagging-directive</code> if you choose\n            <code>REPLACE</code> for the <code>x-amz-tagging-directive</code>. If you choose\n            <code>COPY</code> for the <code>x-amz-tagging-directive</code>, you don't need to set\n         the <code>x-amz-tagging</code> header, because the tag-set will be copied from the source\n         object directly. The tag-set must be encoded as URL Query parameters.</p>\n         <p>The default value is the empty value.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets in a <code>CopyObject</code> operation, only the empty tag-set is supported. Any requests that attempt to write non-empty tags into directory buckets will receive a <code>501 Not Implemented</code> status code. \nWhen the destination bucket is a directory bucket, you will receive a <code>501 Not Implemented</code> response in any of the following situations:</p>\n            <ul>\n               <li>\n                  <p>When you attempt to <code>COPY</code> the tag-set from an S3 source object that has non-empty tags.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a source object and set a non-empty value to <code>x-amz-tagging</code>.</p>\n               </li>\n               <li>\n                  <p>When you don't set the <code>x-amz-tagging-directive</code> header and the source object has non-empty tags. This is because the default value of <code>x-amz-tagging-directive</code> is <code>COPY</code>.</p>\n               </li>\n            </ul>\n            <p>Because only the empty tag-set is supported for directory buckets in a <code>CopyObject</code> operation, the following situations are allowed:</p>\n            <ul>\n               <li>\n                  <p>When you attempt to <code>COPY</code> the tag-set from a directory bucket source object that has no tags to a general purpose bucket. It copies an empty tag-set to the destination object.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a directory bucket source object and set the <code>x-amz-tagging</code> value of the directory bucket destination object to empty.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a general purpose bucket source object that has non-empty tags and set the <code>x-amz-tagging</code> value of the directory bucket destination object to empty.</p>\n               </li>\n               <li>\n                  <p>When you attempt to <code>REPLACE</code> the tag-set of a directory bucket source object and don't set the <code>x-amz-tagging</code> value of the directory bucket destination object. This is because the default value of <code>x-amz-tagging</code> is the empty value.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-tagging"
           }
         },
@@ -19258,7 +19265,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This action creates an Amazon S3 bucket. To create an Amazon S3 on Outposts bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_control_CreateBucket.html\">\n                  <code>CreateBucket</code>\n               </a>.</p>\n         </note>\n         <p>Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a\n         valid Amazon Web Services Access Key ID to authenticate requests. Anonymous requests are never allowed to\n         create buckets. By creating the bucket, you become the bucket owner.</p>\n         <p>There are two types of buckets: general purpose buckets and directory buckets. For more\n         information about these bucket types, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html\">Creating, configuring, and\n            working with Amazon S3 buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you send your <code>CreateBucket</code> request to the <code>s3.amazonaws.com</code> global endpoint,\n                  the request goes to the <code>us-east-1</code> Region. So the signature\n                  calculations in Signature Version 4 must use <code>us-east-1</code> as the Region, even\n                  if the location constraint in the request specifies another Region where the bucket is\n                  to be created. If you create a bucket in a Region other than US East (N. Virginia), your\n                  application must be able to handle 307 redirect. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html\">Virtual hosting of\n                     buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <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>\n                     </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - In addition to the <code>s3:CreateBucket</code> permission, the following permissions are\n                     required in a policy when your <code>CreateBucket</code> request includes specific\n                     headers: </p>\n                     <ul>\n                        <li>\n                           <p>\n                              <b>Access control lists (ACLs)</b> - In your <code>CreateBucket</code> request, if you specify an access control list (ACL) \n                              and set it to <code>public-read</code>, <code>public-read-write</code>,\n                              <code>authenticated-read</code>, or if you explicitly specify any other custom ACLs, both <code>s3:CreateBucket</code> and\n                              <code>s3:PutBucketAcl</code> permissions are required. In your <code>CreateBucket</code> request, if you set the ACL to <code>private</code>, \n                              or if you don't specify any ACLs, only the <code>s3:CreateBucket</code> permission is required.\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>Object Lock</b> - In your\n                              <code>CreateBucket</code> request, if you set \n                              <code>x-amz-bucket-object-lock-enabled</code> to true, the  \n                              <code>s3:PutBucketObjectLockConfiguration</code> and\n                              <code>s3:PutBucketVersioning</code> permissions are required.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>S3 Object Ownership</b> - If your\n                              <code>CreateBucket</code> request includes the\n                              <code>x-amz-object-ownership</code> header, then the\n                              <code>s3:PutBucketOwnershipControls</code> permission is required.</p>\n                           <important>\n                              <p> To set an ACL on a bucket as part of a\n                                    <code>CreateBucket</code> request, you must explicitly set S3\n                                 Object Ownership for the bucket to a different value than the\n                                 default, <code>BucketOwnerEnforced</code>. Additionally, if your\n                                 desired bucket ACL grants public access, you must first create the\n                                 bucket (without the bucket ACL) and then explicitly disable Block\n                                 Public Access on the bucket before using <code>PutBucketAcl</code>\n                                 to set the ACL. If you try to create a bucket with a public ACL,\n                                 the request will fail. </p>\n                              <p> For the majority of modern use cases in S3, we recommend\n                                 that you keep all Block Public Access settings enabled and keep\n                                 ACLs disabled. If you would like to share data with users outside\n                                 of your account, you can use bucket policies as needed. For more\n                                 information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling ownership of objects and disabling ACLs for your\n                                    bucket </a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html\">Blocking public access to your Amazon S3 storage </a> in\n                                 the <i>Amazon S3 User Guide</i>. </p>\n                           </important>\n                        </li>\n                        <li>\n                           <p>\n                              <b>S3 Block Public Access</b> - If your\n                              specific use case requires granting public access to your S3 resources, you\n                              can disable Block Public Access. Specifically, you can create a new bucket with Block\n                              Public Access enabled, then separately call the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">\n                                 <code>DeletePublicAccessBlock</code>\n                              </a> API. To use this operation, you must have the\n                              <code>s3:PutBucketPublicAccessBlock</code> permission. For more information about S3 Block Public\n                              Access, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html\">Blocking\n                                 public access to your Amazon S3 storage </a> in the\n                              <i>Amazon S3 User Guide</i>. </p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - You must have the <code>s3express:CreateBucket</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>\n                     <important>\n                        <p>The permissions for ACLs, Object Lock, S3 Object Ownership, and S3 Block Public Access are not supported for directory buckets.  \n                        For directory buckets, all Block Public Access settings are enabled at the bucket level and S3  \n                        Object Ownership is set to Bucket owner enforced (ACLs disabled). These settings can't be modified.\n                     </p>\n                        <p>For more information about permissions for creating and working with \n                           directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the <i>Amazon S3 User Guide</i>. \n                           For more information about supported S3 features for directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html#s3-express-features\">Features of S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     </important>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CreateBucket</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This action creates an Amazon S3 bucket. To create an Amazon S3 on Outposts bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_control_CreateBucket.html\">\n                  <code>CreateBucket</code>\n               </a>.</p>\n         </note>\n         <p>Creates a new S3 bucket. To create a bucket, you must set up Amazon S3 and have a valid Amazon Web Services\n         Access Key ID to authenticate requests. Anonymous requests are never allowed to create\n         buckets. By creating the bucket, you become the bucket owner.</p>\n         <p>There are two types of buckets: general purpose buckets and directory buckets. For more\n         information about these bucket types, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html\">Creating, configuring, and\n            working with Amazon S3 buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you send your\n                     <code>CreateBucket</code> request to the <code>s3.amazonaws.com</code> global\n                  endpoint, the request goes to the <code>us-east-1</code> Region. So the signature\n                  calculations in Signature Version 4 must use <code>us-east-1</code> as the Region,\n                  even if the location constraint in the request specifies another Region where the\n                  bucket is to be created. If you create a bucket in a Region other than US East (N.\n                  Virginia), your application must be able to handle 307 redirect. For more\n                  information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html\">Virtual hosting of\n                     buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <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>\n                     </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - In\n                        addition to the <code>s3:CreateBucket</code> permission, the following\n                        permissions are required in a policy when your <code>CreateBucket</code>\n                        request includes specific headers: </p>\n                     <ul>\n                        <li>\n                           <p>\n                              <b>Access control lists (ACLs)</b>\n                              - In your <code>CreateBucket</code> request, if you specify an\n                              access control list (ACL) and set it to <code>public-read</code>,\n                                 <code>public-read-write</code>, <code>authenticated-read</code>, or\n                              if you explicitly specify any other custom ACLs, both\n                                 <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code>\n                              permissions are required. In your <code>CreateBucket</code> request,\n                              if you set the ACL to <code>private</code>, or if you don't specify\n                              any ACLs, only the <code>s3:CreateBucket</code> permission is\n                              required. </p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>Object Lock</b> - In your\n                                 <code>CreateBucket</code> request, if you set\n                                 <code>x-amz-bucket-object-lock-enabled</code> to true, the\n                                 <code>s3:PutBucketObjectLockConfiguration</code> and\n                                 <code>s3:PutBucketVersioning</code> permissions are\n                              required.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>S3 Object Ownership</b> - If\n                              your <code>CreateBucket</code> request includes the\n                                 <code>x-amz-object-ownership</code> header, then the\n                                 <code>s3:PutBucketOwnershipControls</code> permission is\n                              required.</p>\n                           <important>\n                              <p> To set an ACL on a bucket as part of a\n                                    <code>CreateBucket</code> request, you must explicitly set S3\n                                 Object Ownership for the bucket to a different value than the\n                                 default, <code>BucketOwnerEnforced</code>. Additionally, if your\n                                 desired bucket ACL grants public access, you must first create the\n                                 bucket (without the bucket ACL) and then explicitly disable Block\n                                 Public Access on the bucket before using <code>PutBucketAcl</code>\n                                 to set the ACL. If you try to create a bucket with a public ACL,\n                                 the request will fail. </p>\n                              <p> For the majority of modern use cases in S3, we recommend that\n                                 you keep all Block Public Access settings enabled and keep ACLs\n                                 disabled. If you would like to share data with users outside of\n                                 your account, you can use bucket policies as needed. For more\n                                 information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling ownership of objects and disabling ACLs for your\n                                    bucket </a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html\">Blocking public access to your Amazon S3 storage </a> in\n                                 the <i>Amazon S3 User Guide</i>. </p>\n                           </important>\n                        </li>\n                        <li>\n                           <p>\n                              <b>S3 Block Public Access</b> - If\n                              your specific use case requires granting public access to your S3\n                              resources, you can disable Block Public Access. Specifically, you can\n                              create a new bucket with Block Public Access enabled, then separately\n                              call the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">\n                                 <code>DeletePublicAccessBlock</code>\n                              </a> API. To use this operation, you must have the\n                                 <code>s3:PutBucketPublicAccessBlock</code> permission. For more\n                              information about S3 Block Public Access, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html\">Blocking public access to your Amazon S3 storage </a> in the\n                                 <i>Amazon S3 User Guide</i>. </p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have the <code>s3express:CreateBucket</code> permission in\n                        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.\n                        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>\n                     <important>\n                        <p>The permissions for ACLs, Object Lock, S3 Object Ownership, and S3\n                           Block Public Access are not supported for directory buckets. For\n                           directory buckets, all Block Public Access settings are enabled at the\n                           bucket level and S3 Object Ownership is set to Bucket owner enforced\n                           (ACLs disabled). These settings can't be modified. </p>\n                        <p>For more information about permissions for creating and working with\n                           directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the\n                              <i>Amazon S3 User Guide</i>. For more information about\n                           supported S3 features for directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-one-zone.html#s3-express-features\">Features of S3 Express One Zone</a> in the\n                              <i>Amazon S3 User Guide</i>.</p>\n                     </important>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CreateBucket</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To create a bucket in a specific region",
@@ -19305,7 +19312,7 @@
         "LocationConstraint": {
           "target": "com.amazonaws.s3#BucketLocationConstraint",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the Region where the bucket will be created. You might choose a Region to\n         optimize latency, minimize costs, or address regulatory requirements. For example, if you\n         reside in Europe, you will probably find it advantageous to create buckets in the Europe\n         (Ireland) Region. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro\">Accessing a\n            bucket</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>If you don't specify a Region,\n         the bucket is created in the US East (N. Virginia) Region (us-east-1) by default.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Specifies the Region where the bucket will be created. You might choose a Region to\n         optimize latency, minimize costs, or address regulatory requirements. For example, if you\n         reside in Europe, you will probably find it advantageous to create buckets in the Europe\n         (Ireland) Region. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro\">Accessing a\n            bucket</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>If you don't specify a Region, the bucket is created in the US East (N. Virginia) Region\n         (us-east-1) by default.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
           }
         },
         "Location": {
@@ -19431,7 +19438,7 @@
         "target": "com.amazonaws.s3#CreateMultipartUploadOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>This action initiates a multipart upload and returns an upload ID. This upload ID is\n         used to associate all of the parts in the specific multipart upload. You specify this\n         upload ID in each of your subsequent upload part requests (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>). You also include this\n         upload ID in the final request to either complete or abort the multipart upload\n         request. For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>After you initiate a multipart upload and upload one or more parts, to stop being\n            charged for storing the uploaded parts, you must either complete or abort the multipart\n            upload. Amazon S3 frees up the space used to store the parts and stops charging you for\n            storing them only after you either complete or abort a multipart upload. </p>\n         </note>\n         <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the created multipart  \n         upload must be completed within the number of days specified in the bucket lifecycle\n         configuration. Otherwise, the incomplete multipart upload becomes eligible for an abort\n         action and Amazon S3 aborts the multipart upload. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config\">Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle\n            Configuration</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - S3 Lifecycle is not supported by directory buckets.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Request signing</dt>\n            <dd>\n               <p>For request signing, multipart upload is just a series of regular requests. You initiate\n               a multipart upload, send one or more requests to upload parts, and then complete the\n               multipart upload process. You sign each request individually. There is nothing special\n               about signing multipart upload requests. For more information about signing, 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> in the <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        perform a multipart upload with encryption using an Key Management Service (KMS)\n                        KMS key, the requester must have permission to the\n                           <code>kms:Decrypt</code> and <code>kms:GenerateDataKey</code> actions on\n                        the key. The requester must also have permissions for the\n                           <code>kms:GenerateDataKey</code> action for the\n                           <code>CreateMultipartUpload</code> API. Then, the requester needs\n                        permissions for the <code>kms:Decrypt</code> action on the\n                           <code>UploadPart</code> and <code>UploadPartCopy</code> APIs. These\n                        permissions are required because Amazon S3 must decrypt and read data from the\n                        encrypted file parts before it completes the multipart upload. For more\n                        information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting data\n                           using server-side encryption with Amazon Web Services KMS</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose buckets</b> - Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it\n                        writes it to disks in its data centers and decrypts it when you access it. Amazon S3\n                        automatically encrypts all new objects that are uploaded to an S3 bucket. When doing a\n                        multipart upload, if you don't specify encryption information in your request, the\n                        encryption setting of the uploaded parts is set to the default encryption configuration of\n                        the destination bucket. By default, all buckets have a base level of encryption\n                        configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the\n                        destination bucket has a default encryption configuration that uses server-side encryption\n                        with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided encryption key (SSE-C),\n                        Amazon S3 uses the corresponding KMS key, or a customer-provided key to encrypt the uploaded\n                        parts. When you perform a CreateMultipartUpload operation, if you want to use a different\n                        type of encryption setting for the uploaded parts, you can request that Amazon S3 encrypts the\n                        object with a different encryption key (such as an Amazon S3 managed key, a KMS key, or a customer-provided key). When the encryption\n                        setting in your request is different from the default encryption configuration of the\n                        destination bucket, the encryption setting in your request takes precedence. If you choose\n                        to provide your own encryption key, the request headers you provide in <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n                        and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a> requests must match the headers you used in the <code>CreateMultipartUpload</code> request.</p>\n                     <ul>\n                        <li>\n                           <p>Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key\n                              (<code>aws/s3</code>) and KMS customer managed keys stored in Key Management Service (KMS) –\n                              If you want Amazon Web Services to manage the keys used to encrypt data, specify the\n                              following headers in the request.</p>\n                           <ul>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-aws-kms-key-id</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-context</code>\n                                 </p>\n                              </li>\n                           </ul>\n                           <note>\n                              <ul>\n                                 <li>\n                                    <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but\n                                    don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>,\n                                    Amazon S3 uses the Amazon Web Services managed key (<code>aws/s3</code> key) in KMS to\n                                    protect the data.</p>\n                                 </li>\n                                 <li>\n                                    <p>To perform a multipart upload with encryption by using an Amazon Web Services KMS key, the requester\n                                    must have permission to the <code>kms:Decrypt</code> and <code>kms:GenerateDataKey*</code>\n                                    actions on the key. These permissions are required because Amazon S3 must decrypt and read data\n                                    from the encrypted file parts before it completes the multipart upload. For more\n                                    information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API\n                                       and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting data using\n                                          server-side encryption with Amazon Web Services KMS</a> in the\n                                    <i>Amazon S3 User Guide</i>.</p>\n                                 </li>\n                                 <li>\n                                    <p>If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account as the KMS key,\n                                    then you must have these permissions on the key policy. If your IAM user or role is in a different account from the key, then you must have the permissions on both the key\n                                    policy and your IAM user or role.</p>\n                                 </li>\n                                 <li>\n                                    <p>All <code>GET</code> and <code>PUT</code> requests for an object\n                                       protected by KMS fail if you don't make them by using Secure Sockets\n                                       Layer (SSL), Transport Layer Security (TLS), or Signature Version\n                                       4. For information about configuring any of the officially supported Amazon Web Services\n                                       SDKs and Amazon Web Services CLI, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version\">Specifying the Signature Version in Request Authentication</a>\n                                       in the <i>Amazon S3 User Guide</i>.</p>\n                                 </li>\n                              </ul>\n                           </note>\n                           <p>For more information about server-side encryption with KMS keys\n                              (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting Data\n                                 Using Server-Side Encryption with KMS keys</a> in the <i>Amazon S3 User Guide</i>.</p>\n                        </li>\n                        <li>\n                           <p>Use customer-provided encryption keys (SSE-C) – If you want to manage\n                              your own encryption keys, provide all the following headers in the\n                              request.</p>\n                           <ul>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-customer-algorithm</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-customer-key</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-customer-key-MD5</code>\n                                 </p>\n                              </li>\n                           </ul>\n                           <p>For more information about server-side encryption with customer-provided\n                              encryption keys (SSE-C), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html\">\n                                 Protecting data using server-side encryption with customer-provided\n                                 encryption keys (SSE-C)</a> in the <i>Amazon S3 User Guide</i>.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n                     <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request. \n                            You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n                     <note>\n                        <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            So in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          the encryption request headers must match the default encryption configuration of the directory bucket.\n\n</p>\n                     </note>\n                     <note>\n                        <p>For directory buckets, when you perform a <code>CreateMultipartUpload</code> operation and an <code>UploadPartCopy</code> operation,  \n                        the request headers you provide in the <code>CreateMultipartUpload</code> request must match the default encryption configuration of the destination bucket. </p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CreateMultipartUpload</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>This action initiates a multipart upload and returns an upload ID. This upload ID is\n         used to associate all of the parts in the specific multipart upload. You specify this\n         upload ID in each of your subsequent upload part requests (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>). You also include this\n         upload ID in the final request to either complete or abort the multipart upload request.\n         For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>After you initiate a multipart upload and upload one or more parts, to stop being\n            charged for storing the uploaded parts, you must either complete or abort the multipart\n            upload. Amazon S3 frees up the space used to store the parts and stops charging you for\n            storing them only after you either complete or abort a multipart upload. </p>\n         </note>\n         <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the\n         created multipart upload must be completed within the number of days specified in the\n         bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible\n         for an abort action and Amazon S3 aborts the multipart upload. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config\">Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle\n         Configuration</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> -\n                  S3 Lifecycle is not supported by directory buckets.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> -\n                  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Request signing</dt>\n            <dd>\n               <p>For request signing, multipart upload is just a series of regular requests. You\n                  initiate a multipart upload, send one or more requests to upload parts, and then\n                  complete the multipart upload process. You sign each request individually. There\n                  is nothing special about signing multipart upload requests. For more information\n                  about signing, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html\">Authenticating\n                     Requests (Amazon Web Services Signature Version 4)</a> in the\n                     <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        perform a multipart upload with encryption using an Key Management Service (KMS)\n                        KMS key, the requester must have permission to the\n                           <code>kms:Decrypt</code> and <code>kms:GenerateDataKey</code> actions on\n                        the key. The requester must also have permissions for the\n                           <code>kms:GenerateDataKey</code> action for the\n                           <code>CreateMultipartUpload</code> API. Then, the requester needs\n                        permissions for the <code>kms:Decrypt</code> action on the\n                           <code>UploadPart</code> and <code>UploadPartCopy</code> APIs. These\n                        permissions are required because Amazon S3 must decrypt and read data from the\n                        encrypted file parts before it completes the multipart upload. For more\n                        information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting data\n                           using server-side encryption with Amazon Web Services KMS</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose buckets</b> - Server-side\n                        encryption is for data encryption at rest. Amazon S3 encrypts your data as it\n                        writes it to disks in its data centers and decrypts it when you access it.\n                        Amazon S3 automatically encrypts all new objects that are uploaded to an S3\n                        bucket. When doing a multipart upload, if you don't specify encryption\n                        information in your request, the encryption setting of the uploaded parts is\n                        set to the default encryption configuration of the destination bucket. By\n                        default, all buckets have a base level of encryption configuration that uses\n                        server-side encryption with Amazon S3 managed keys (SSE-S3). If the destination\n                        bucket has a default encryption configuration that uses server-side\n                        encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided\n                        encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a\n                        customer-provided key to encrypt the uploaded parts. When you perform a\n                        CreateMultipartUpload operation, if you want to use a different type of\n                        encryption setting for the uploaded parts, you can request that Amazon S3\n                        encrypts the object with a different encryption key (such as an Amazon S3 managed\n                        key, a KMS key, or a customer-provided key). When the encryption setting\n                        in your request is different from the default encryption configuration of\n                        the destination bucket, the encryption setting in your request takes\n                        precedence. If you choose to provide your own encryption key, the request\n                        headers you provide in <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a> and\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>\n                        requests must match the headers you used in the\n                           <code>CreateMultipartUpload</code> request.</p>\n                     <ul>\n                        <li>\n                           <p>Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key\n                                 (<code>aws/s3</code>) and KMS customer managed keys stored in Key Management Service\n                              (KMS) – If you want Amazon Web Services to manage the keys used to encrypt data,\n                              specify the following headers in the request.</p>\n                           <ul>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-aws-kms-key-id</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-context</code>\n                                 </p>\n                              </li>\n                           </ul>\n                           <note>\n                              <ul>\n                                 <li>\n                                    <p>If you specify\n                                          <code>x-amz-server-side-encryption:aws:kms</code>, but\n                                       don't provide\n                                          <code>x-amz-server-side-encryption-aws-kms-key-id</code>,\n                                       Amazon S3 uses the Amazon Web Services managed key (<code>aws/s3</code> key) in\n                                       KMS to protect the data.</p>\n                                 </li>\n                                 <li>\n                                    <p>To perform a multipart upload with encryption by using an\n                                       Amazon Web Services KMS key, the requester must have permission to the\n                                          <code>kms:Decrypt</code> and\n                                          <code>kms:GenerateDataKey*</code> actions on the key.\n                                       These permissions are required because Amazon S3 must decrypt and\n                                       read data from the encrypted file parts before it completes\n                                       the multipart upload. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting data using server-side encryption with Amazon Web Services\n                                          KMS</a> in the\n                                       <i>Amazon S3 User Guide</i>.</p>\n                                 </li>\n                                 <li>\n                                    <p>If your Identity and Access Management (IAM) user or role is in the same\n                                       Amazon Web Services account as the KMS key, then you must have these\n                                       permissions on the key policy. If your IAM user or role is\n                                       in a different account from the key, then you must have the\n                                       permissions on both the key policy and your IAM user or\n                                       role.</p>\n                                 </li>\n                                 <li>\n                                    <p>All <code>GET</code> and <code>PUT</code> requests for an\n                                       object protected by KMS fail if you don't make them by\n                                       using Secure Sockets Layer (SSL), Transport Layer Security\n                                       (TLS), or Signature Version 4. For information about\n                                       configuring any of the officially supported Amazon Web Services SDKs and\n                                       Amazon Web Services CLI, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version\">Specifying the Signature Version in\n                                          Request Authentication</a> in the\n                                          <i>Amazon S3 User Guide</i>.</p>\n                                 </li>\n                              </ul>\n                           </note>\n                           <p>For more information about server-side encryption with KMS keys\n                              (SSE-KMS), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting\n                                 Data Using Server-Side Encryption with KMS keys</a> in the\n                                 <i>Amazon S3 User Guide</i>.</p>\n                        </li>\n                        <li>\n                           <p>Use customer-provided encryption keys (SSE-C) – If you want to\n                              manage your own encryption keys, provide all the following headers in\n                              the request.</p>\n                           <ul>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-customer-algorithm</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-customer-key</code>\n                                 </p>\n                              </li>\n                              <li>\n                                 <p>\n                                    <code>x-amz-server-side-encryption-customer-key-MD5</code>\n                                 </p>\n                              </li>\n                           </ul>\n                           <p>For more information about server-side encryption with\n                              customer-provided encryption keys (SSE-C), see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html\"> Protecting data using server-side encryption with\n                                 customer-provided encryption keys (SSE-C)</a> in the\n                                 <i>Amazon S3 User Guide</i>.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory buckets</b> -\n                        For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n                     <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request. \n                            You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n                     <note>\n                        <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            So in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          the encryption request headers must match the default encryption configuration of the directory bucket.\n\n</p>\n                     </note>\n                     <note>\n                        <p>For directory buckets, when you perform a\n                              <code>CreateMultipartUpload</code> operation and an\n                              <code>UploadPartCopy</code> operation, the request headers you provide\n                           in the <code>CreateMultipartUpload</code> request must match the default\n                           encryption configuration of the destination bucket. </p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>CreateMultipartUpload</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To initiate a multipart upload",
@@ -19460,7 +19467,7 @@
         "AbortDate": {
           "target": "com.amazonaws.s3#AbortDate",
           "traits": {
-            "smithy.api#documentation": "<p>If the bucket has a lifecycle rule configured with an action to abort incomplete\n         multipart uploads and the prefix in the lifecycle rule matches the object name in the\n         request, the response includes this header. The header indicates when the initiated\n         multipart upload becomes eligible for an abort operation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config\">\n            Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle\n            Configuration</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>The response also includes the <code>x-amz-abort-rule-id</code> header that provides the\n         ID of the lifecycle configuration rule that defines the abort action.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If the bucket has a lifecycle rule configured with an action to abort incomplete\n         multipart uploads and the prefix in the lifecycle rule matches the object name in the\n         request, the response includes this header. The header indicates when the initiated\n         multipart upload becomes eligible for an abort operation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config\">\n            Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration</a> in\n         the <i>Amazon S3 User Guide</i>.</p>\n         <p>The response also includes the <code>x-amz-abort-rule-id</code> header that provides the\n         ID of the lifecycle configuration rule that defines the abort action.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-abort-date"
           }
         },
@@ -19493,7 +19500,7 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,\n            <code>AES256</code>, <code>aws:kms</code>).</p>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for\n         example, <code>AES256</code>, <code>aws:kms</code>).</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
@@ -19507,7 +19514,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification of\n         the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification\n         of the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -19557,14 +19564,14 @@
         "ACL": {
           "target": "com.amazonaws.s3#ObjectCannedACL",
           "traits": {
-            "smithy.api#documentation": "<p>The canned ACL to apply to the object. Amazon S3 supports a set of\n         predefined ACLs, known as <i>canned ACLs</i>. Each canned ACL\n         has a predefined set of grantees and permissions. For more information, see\n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned\n            ACL</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>By default, all objects are private. Only the owner has full access\n         control. When uploading an object, you can grant access permissions to individual\n         Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then\n         added to the access control list (ACL) on the new object. For more information, see\n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>.  One way to\n         grant the permissions using the request headers is to specify a canned ACL with the <code>x-amz-acl</code> request header.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>The canned ACL to apply to the object. Amazon S3 supports a set of predefined ACLs, known as\n            <i>canned ACLs</i>. Each canned ACL has a predefined set of grantees and\n         permissions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned ACL</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>By default, all objects are private. Only the owner has full access control. When\n         uploading an object, you can grant access permissions to individual Amazon Web Services accounts or to\n         predefined groups defined by Amazon S3. These permissions are then added to the access control\n         list (ACL) on the new object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. One way to grant\n         the permissions using the request headers is to specify a canned ACL with the\n            <code>x-amz-acl</code> request header.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-acl"
           }
         },
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the bucket where the multipart upload is initiated and where the object is uploaded.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the bucket where the multipart upload is initiated and where the object is\n         uploaded.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -19617,28 +19624,28 @@
         "GrantFullControl": {
           "target": "com.amazonaws.s3#GrantFullControl",
           "traits": {
-            "smithy.api#documentation": "<p>Specify access permissions explicitly to give the grantee READ, READ_ACP, and WRITE_ACP permissions on the object.</p>\n         <p>By default, all objects are private. Only the owner has full access\n         control. When uploading an object, you can use this header to explicitly grant access\n         permissions to specific Amazon Web Services accounts or groups.\n         This header maps to specific permissions that Amazon S3 supports in an ACL. For\n         more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n            Overview</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of\n         the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID\n               of an Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined\n               group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email\n               address of an Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>Specify access permissions explicitly to give the grantee READ, READ_ACP, and WRITE_ACP\n         permissions on the object.</p>\n         <p>By default, all objects are private. Only the owner has full access control. When\n         uploading an object, you can use this header to explicitly grant access permissions to\n         specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3\n         supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of the\n         following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID of an\n               Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email address of an\n               Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-grant-full-control"
           }
         },
         "GrantRead": {
           "target": "com.amazonaws.s3#GrantRead",
           "traits": {
-            "smithy.api#documentation": "<p>Specify access permissions explicitly to allow grantee to read the object data and its metadata.</p>\n         <p>By default, all objects are private. Only the owner has full access\n         control. When uploading an object, you can use this header to explicitly grant access\n         permissions to specific Amazon Web Services accounts or groups.\n         This header maps to specific permissions that Amazon S3 supports in an ACL. For\n         more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n            Overview</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of\n         the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID\n               of an Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined\n               group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email\n               address of an Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>Specify access permissions explicitly to allow grantee to read the object data and its\n         metadata.</p>\n         <p>By default, all objects are private. Only the owner has full access control. When\n         uploading an object, you can use this header to explicitly grant access permissions to\n         specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3\n         supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of the\n         following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID of an\n               Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email address of an\n               Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-grant-read"
           }
         },
         "GrantReadACP": {
           "target": "com.amazonaws.s3#GrantReadACP",
           "traits": {
-            "smithy.api#documentation": "<p>Specify access permissions explicitly to allows grantee to read the object ACL.</p>\n         <p>By default, all objects are private. Only the owner has full access\n         control. When uploading an object, you can use this header to explicitly grant access\n         permissions to specific Amazon Web Services accounts or groups.\n         This header maps to specific permissions that Amazon S3 supports in an ACL. For\n         more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n            Overview</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of\n         the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID\n               of an Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined\n               group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email\n               address of an Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>Specify access permissions explicitly to allows grantee to read the object ACL.</p>\n         <p>By default, all objects are private. Only the owner has full access control. When\n         uploading an object, you can use this header to explicitly grant access permissions to\n         specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3\n         supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of the\n         following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID of an\n               Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email address of an\n               Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-grant-read-acp"
           }
         },
         "GrantWriteACP": {
           "target": "com.amazonaws.s3#GrantWriteACP",
           "traits": {
-            "smithy.api#documentation": "<p>Specify access permissions explicitly to allows grantee to allow grantee to write the ACL for the applicable object.</p>\n         <p>By default, all objects are private. Only the owner has full access\n         control. When uploading an object, you can use this header to explicitly grant access\n         permissions to specific Amazon Web Services accounts or groups.\n         This header maps to specific permissions that Amazon S3 supports in an ACL. For\n         more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n            Overview</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of\n         the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID\n               of an Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined\n               group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email\n               address of an Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>Specify access permissions explicitly to allows grantee to allow grantee to write the\n         ACL for the applicable object.</p>\n         <p>By default, all objects are private. Only the owner has full access control. When\n         uploading an object, you can use this header to explicitly grant access permissions to\n         specific Amazon Web Services accounts or groups. This header maps to specific permissions that Amazon S3\n         supports in an ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         in the <i>Amazon S3 User Guide</i>.</p>\n         <p>You specify each grantee as a type=value pair, where the type is one of the\n         following:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>id</code> – if the value specified is the canonical user ID of an\n               Amazon Web Services account</p>\n            </li>\n            <li>\n               <p>\n                  <code>uri</code> – if you are granting permissions to a predefined group</p>\n            </li>\n            <li>\n               <p>\n                  <code>emailAddress</code> – if the value specified is the email address of an\n               Amazon Web Services account</p>\n               <note>\n                  <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                  <ul>\n                     <li>\n                        <p>US East (N. Virginia)</p>\n                     </li>\n                     <li>\n                        <p>US West (N. California)</p>\n                     </li>\n                     <li>\n                        <p> US West (Oregon)</p>\n                     </li>\n                     <li>\n                        <p> Asia Pacific (Singapore)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Sydney)</p>\n                     </li>\n                     <li>\n                        <p>Asia Pacific (Tokyo)</p>\n                     </li>\n                     <li>\n                        <p>Europe (Ireland)</p>\n                     </li>\n                     <li>\n                        <p>South America (São Paulo)</p>\n                     </li>\n                  </ul>\n                  <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n               </note>\n            </li>\n         </ul>\n         <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>\n         <p>\n            <code>x-amz-grant-read: id=\"11112222333\", id=\"444455556666\" </code>\n         </p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-grant-write-acp"
           }
         },
@@ -19663,14 +19670,14 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,\n            <code>AES256</code>, <code>aws:kms</code>).</p>\n         <ul>\n            <li>\n               <p>\n                  <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>.         \n            </p>\n               <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request. \n                            You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n               <note>\n                  <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            So in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          the encryption request headers must match the default encryption configuration of the directory bucket.\n\n</p>\n               </note>\n            </li>\n         </ul>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for\n         example, <code>AES256</code>, <code>aws:kms</code>).</p>\n         <ul>\n            <li>\n               <p>\n                  <b>Directory buckets </b> -\n               For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n               <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request. \n                            You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n               <note>\n                  <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            So in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          the encryption request headers must match the default encryption configuration of the directory bucket.\n\n</p>\n               </note>\n            </li>\n         </ul>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The\n         STANDARD storage class provides high durability and high availability. Depending on\n         performance needs, you can specify a different Storage Class. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.</p>\n               </li>\n               <li>\n                  <p>Amazon S3 on Outposts only uses\n               the OUTPOSTS Storage Class.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The\n         STANDARD storage class provides high durability and high availability. Depending on\n         performance needs, you can specify a different Storage Class. For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage\n            Classes</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>For directory buckets, only the S3 Express One Zone storage class is supported to store\n                  newly created objects.</p>\n               </li>\n               <li>\n                  <p>Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-storage-class"
           }
         },
@@ -19684,7 +19691,7 @@
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n         AES256).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
@@ -19698,7 +19705,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to RFC 1321. Amazon S3 uses\n         this header for a message integrity check to ensure that the encryption key was transmitted\n         without error.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to\n         RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption\n         key was transmitted without error.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -19790,7 +19797,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>Creates a session that establishes temporary security credentials to support fast authentication and authorization for the Zonal endpoint API operations on directory buckets. \n         For more information about Zonal endpoint API operations that include the Availability Zone in the request endpoint, see \n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-APIs.html\">S3 Express One Zone  APIs</a> in the <i>Amazon S3 User Guide</i>. \n      </p>\n         <p>To make Zonal endpoint API requests on a directory bucket, use the <code>CreateSession</code>\n         API operation. Specifically, you grant <code>s3express:CreateSession</code> permission to a\n         bucket in a bucket policy or an IAM identity-based policy. Then, you use IAM credentials to make the\n            <code>CreateSession</code> API request on the bucket, which returns temporary security\n         credentials that include the access key ID, secret access key, session token, and\n         expiration. These credentials have associated permissions to access the Zonal endpoint API operations. After\n         the session is created, you don’t need to use other policies to grant permissions to each\n         Zonal endpoint API individually. Instead, in your Zonal endpoint API requests, you sign your requests by\n         applying the temporary security credentials of the session to the request headers and\n         following the SigV4 protocol for authentication. You also apply the session token to the\n            <code>x-amz-s3session-token</code> request header for authorization. Temporary security\n         credentials are scoped to the bucket and expire after 5 minutes. After the expiration time,\n         any calls that you make with those credentials will fail. You must use IAM credentials\n         again to make a <code>CreateSession</code> API request that generates a new set of\n         temporary credentials for use. Temporary credentials cannot be extended or refreshed beyond\n         the original specified interval.</p>\n         <p>If you use Amazon Web Services SDKs, SDKs handle the session token refreshes automatically to avoid\n         service interruptions when a session expires. We recommend that you use the Amazon Web Services SDKs to\n         initiate and manage requests to the CreateSession API. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-optimizing-performance-guidelines-design-patterns.html#s3-express-optimizing-performance-session-authentication\">Performance guidelines and design patterns</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>You must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>\n                        <code>CopyObject</code> API operation</b> - Unlike other Zonal endpoint API operations, the <code>CopyObject</code> API operation doesn't use the temporary security credentials returned from the <code>CreateSession</code> API operation for authentication and authorization. For information about authentication and authorization of the <code>CopyObject</code> API operation on directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>\n                        <code>HeadBucket</code> API operation</b> - Unlike other Zonal endpoint API operations, the <code>HeadBucket</code> API operation doesn't use the temporary security credentials returned from the <code>CreateSession</code> API operation for authentication and authorization. For information about authentication and authorization of the <code>HeadBucket</code> API operation on directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html\">HeadBucket</a>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To obtain temporary security credentials, you must create a bucket policy or an IAM identity-based policy that\n                  grants <code>s3express:CreateSession</code> permission to the bucket. In a\n                  policy, you can have the <code>s3express:SessionMode</code> condition key to\n                  control who can create a <code>ReadWrite</code> or <code>ReadOnly</code> session.\n                  For more information about <code>ReadWrite</code> or <code>ReadOnly</code>\n                  sessions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html#API_CreateSession_RequestParameters\">\n                     <code>x-amz-create-session-mode</code>\n                  </a>. For example policies, see\n                     <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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the\n                     <i>Amazon S3 User Guide</i>. </p>\n               <p>To grant cross-account access to Zonal endpoint API operations, the bucket policy should also grant both accounts the <code>s3express:CreateSession</code> permission.</p>\n               <p>If you want to encrypt objects 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>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <p>For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n               <p>For <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-differences.html#s3-express-differences-api-operations\">Zonal endpoint (object-level) API operations</a> except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>,  \nyou authenticate and authorize requests through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">CreateSession</a> for low latency. \n                            To encrypt new objects in a directory bucket with SSE-KMS, you must specify SSE-KMS as the directory bucket's default encryption configuration with a KMS key (specifically, a <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk\">customer managed key</a>). Then, when a session is created for Zonal endpoint API operations, new objects are automatically encrypted and decrypted with SSE-KMS and S3 Bucket Keys during the session.</p>\n               <note>\n                  <p>\n                            Only 1 <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk\">customer managed key</a> is supported per directory bucket for the lifetime of the bucket. The <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n                            After you specify SSE-KMS as your bucket's default encryption configuration with a customer managed key, you can't change the customer managed key for the bucket's SSE-KMS configuration.\n                            </p>\n               </note>\n               <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, \n                            you can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) from the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n               <note>\n                  <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            Also, in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          it's not supported to override the values of the encryption settings from the <code>CreateSession</code> request. \n\n</p>\n               </note>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>",
+        "smithy.api#documentation": "<p>Creates a session that establishes temporary security credentials to support fast\n         authentication and authorization for the Zonal endpoint API operations on directory buckets. For more\n         information about Zonal endpoint API operations that include the Availability Zone in the request endpoint, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-APIs.html\">S3 Express One Zone\n            APIs</a> in the <i>Amazon S3 User Guide</i>. </p>\n         <p>To make Zonal endpoint API requests on a directory bucket, use the <code>CreateSession</code>\n         API operation. Specifically, you grant <code>s3express:CreateSession</code> permission to a\n         bucket in a bucket policy or an IAM identity-based policy. Then, you use IAM credentials to make the\n            <code>CreateSession</code> API request on the bucket, which returns temporary security\n         credentials that include the access key ID, secret access key, session token, and\n         expiration. These credentials have associated permissions to access the Zonal endpoint API operations. After\n         the session is created, you don’t need to use other policies to grant permissions to each\n         Zonal endpoint API individually. Instead, in your Zonal endpoint API requests, you sign your requests by\n         applying the temporary security credentials of the session to the request headers and\n         following the SigV4 protocol for authentication. You also apply the session token to the\n            <code>x-amz-s3session-token</code> request header for authorization. Temporary security\n         credentials are scoped to the bucket and expire after 5 minutes. After the expiration time,\n         any calls that you make with those credentials will fail. You must use IAM credentials\n         again to make a <code>CreateSession</code> API request that generates a new set of\n         temporary credentials for use. Temporary credentials cannot be extended or refreshed beyond\n         the original specified interval.</p>\n         <p>If you use Amazon Web Services SDKs, SDKs handle the session token refreshes automatically to avoid\n         service interruptions when a session expires. We recommend that you use the Amazon Web Services SDKs to\n         initiate and manage requests to the CreateSession API. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-optimizing-performance-guidelines-design-patterns.html#s3-express-optimizing-performance-session-authentication\">Performance guidelines and design patterns</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>You must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>\n                        <code>CopyObject</code> API operation</b> -\n                  Unlike other Zonal endpoint API operations, the <code>CopyObject</code> API operation doesn't use\n                  the temporary security credentials returned from the <code>CreateSession</code>\n                  API operation for authentication and authorization. For information about\n                  authentication and authorization of the <code>CopyObject</code> API operation on\n                  directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>\n                        <code>HeadBucket</code> API operation</b> -\n                  Unlike other Zonal endpoint API operations, the <code>HeadBucket</code> API operation doesn't use\n                  the temporary security credentials returned from the <code>CreateSession</code>\n                  API operation for authentication and authorization. For information about\n                  authentication and authorization of the <code>HeadBucket</code> API operation on\n                  directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html\">HeadBucket</a>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To obtain temporary security credentials, you must create\n                  a bucket policy or an IAM identity-based policy that grants <code>s3express:CreateSession</code>\n                  permission to the bucket. In a policy, you can have the\n                     <code>s3express:SessionMode</code> condition key to control who can create a\n                     <code>ReadWrite</code> or <code>ReadOnly</code> session. For more information\n                  about <code>ReadWrite</code> or <code>ReadOnly</code> sessions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html#API_CreateSession_RequestParameters\">\n                     <code>x-amz-create-session-mode</code>\n                  </a>. For example policies, see\n                     <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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for\n                     S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>. </p>\n               <p>To grant cross-account access to Zonal endpoint API operations, the bucket policy should also\n                  grant both accounts the <code>s3express:CreateSession</code> permission.</p>\n               <p>If you want to encrypt objects with SSE-KMS, you must also have the\n                     <code>kms:GenerateDataKey</code> and the <code>kms:Decrypt</code> permissions\n                  in IAM identity-based policies and KMS key policies for the target KMS\n                  key.</p>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <p>For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n               <p>For <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-differences.html#s3-express-differences-api-operations\">Zonal endpoint (object-level) API operations</a> except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>,  \nyou authenticate and authorize requests through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">CreateSession</a> for low latency. \n                            To encrypt new objects in a directory bucket with SSE-KMS, you must specify SSE-KMS as the directory bucket's default encryption configuration with a KMS key (specifically, a <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk\">customer managed key</a>). Then, when a session is created for Zonal endpoint API operations, new objects are automatically encrypted and decrypted with SSE-KMS and S3 Bucket Keys during the session.</p>\n               <note>\n                  <p>\n                            Only 1 <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk\">customer managed key</a> is supported per directory bucket for the lifetime of the bucket. The <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n                            After you specify SSE-KMS as your bucket's default encryption configuration with a customer managed key, you can't change the customer managed key for the bucket's SSE-KMS configuration.\n                            </p>\n               </note>\n               <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, \n                            you can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) from the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n               <note>\n                  <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            Also, in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          it's not supported to override the values of the encryption settings from the <code>CreateSession</code> request. \n\n</p>\n               </note>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?session",
@@ -19951,7 +19958,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>The container element for optionally specifying the default Object Lock retention settings for new\n         objects placed in the specified bucket.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>The <code>DefaultRetention</code> settings require both a mode and a\n                  period.</p>\n               </li>\n               <li>\n                  <p>The <code>DefaultRetention</code> period can be either <code>Days</code> or\n                     <code>Years</code> but you must select one. You cannot specify\n                     <code>Days</code> and <code>Years</code> at the same time.</p>\n               </li>\n            </ul>\n         </note>"
+        "smithy.api#documentation": "<p>The container element for optionally specifying the default Object Lock retention\n         settings for new objects placed in the specified bucket.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>The <code>DefaultRetention</code> settings require both a mode and a\n                  period.</p>\n               </li>\n               <li>\n                  <p>The <code>DefaultRetention</code> period can be either <code>Days</code> or\n                     <code>Years</code> but you must select one. You cannot specify\n                     <code>Days</code> and <code>Years</code> at the same time.</p>\n               </li>\n            </ul>\n         </note>"
       }
     },
     "com.amazonaws.s3#Delete": {
@@ -19960,7 +19967,7 @@
         "Objects": {
           "target": "com.amazonaws.s3#ObjectIdentifierList",
           "traits": {
-            "smithy.api#documentation": "<p>The object to delete.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets, an object that's composed entirely of \n      whitespace characters is not supported by the <code>DeleteObjects</code> API operation. The request will receive a <code>400 Bad Request</code> error \n      and none of the objects in the request will be deleted.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The object to delete.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets,\n            an object that's composed entirely of whitespace characters is not supported by the\n               <code>DeleteObjects</code> API operation. The request will receive a <code>400 Bad\n               Request</code> error and none of the objects in the request will be deleted.</p>\n         </note>",
             "smithy.api#required": {},
             "smithy.api#xmlFlattened": {},
             "smithy.api#xmlName": "Object"
@@ -19986,7 +19993,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Deletes the S3 bucket. All objects (including all object versions and delete markers) in\n         the bucket must be deleted before the bucket itself can be deleted.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - If multipart uploads in a directory bucket are in progress, you can't delete the bucket until all the in-progress multipart uploads are aborted or completed.</p>\n               </li>\n               <li>\n                  <p>\n                     <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>\n                     </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - You must have the <code>s3:DeleteBucket</code> permission on the specified bucket in a policy.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - You must have the <code>s3express:DeleteBucket</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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteBucket</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Deletes the S3 bucket. All objects (including all object versions and delete markers) in\n         the bucket must be deleted before the bucket itself can be deleted.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - If multipart\n                  uploads in a directory bucket are in progress, you can't delete the bucket until\n                  all the in-progress multipart uploads are aborted or completed.</p>\n               </li>\n               <li>\n                  <p>\n                     <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>\n                     </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - You\n                        must have the <code>s3:DeleteBucket</code> permission on the specified\n                        bucket in a policy.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have the <code>s3express:DeleteBucket</code> permission in\n                        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.\n                        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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteBucket</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete a bucket",
@@ -20017,7 +20024,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Deletes an analytics configuration for the bucket (specified by the analytics\n         configuration ID).</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class\n            Analysis</a>. </p>\n         <p>The following operations are related to\n         <code>DeleteBucketAnalyticsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAnalyticsConfiguration.html\">GetBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html\">ListBucketAnalyticsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAnalyticsConfiguration.html\">PutBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Deletes an analytics configuration for the bucket (specified by the analytics\n         configuration ID).</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class\n            Analysis</a>. </p>\n         <p>The following operations are related to\n         <code>DeleteBucketAnalyticsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAnalyticsConfiguration.html\">GetBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html\">ListBucketAnalyticsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAnalyticsConfiguration.html\">PutBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "DELETE",
           "uri": "/{Bucket}?analytics",
@@ -20073,7 +20080,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Deletes the <code>cors</code> configuration information set for the bucket.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:PutBucketCORS</code> action. The bucket owner has this permission by default\n         and can grant this permission to others. </p>\n         <p>For information about <code>cors</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\">Enabling Cross-Origin Resource Sharing</a> in\n         the <i>Amazon S3 User Guide</i>.</p>\n         <p class=\"title\">\n            <b>Related Resources</b>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketCors.html\">PutBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTOPTIONSobject.html\">RESTOPTIONSobject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Deletes the <code>cors</code> configuration information set for the bucket.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:PutBucketCORS</code> action. The bucket owner has this permission by default\n         and can grant this permission to others. </p>\n         <p>For information about <code>cors</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\">Enabling Cross-Origin Resource Sharing</a> in\n         the <i>Amazon S3 User Guide</i>.</p>\n         <p class=\"title\">\n            <b>Related Resources</b>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketCors.html\">PutBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTOPTIONSobject.html\">RESTOPTIONSobject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete cors configuration on a bucket.",
@@ -20130,7 +20137,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<p>This implementation of the DELETE action resets the default encryption for the bucket as\n         server-side encryption with Amazon S3 managed keys (SSE-S3).</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - 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\n                  Default Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption configuration in directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html\">Setting default server-side encryption behavior \n                  for directory buckets</a>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The <code>s3:PutEncryptionConfiguration</code> permission is required in a policy. \n                        The bucket owner has this permission\n                        by default. The bucket owner can grant this permission to others. For more information\n                        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\n                              Access Permissions to Your Amazon S3 Resources</a>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteBucketEncryption</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketEncryption.html\">PutBucketEncryption</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketEncryption.html\">GetBucketEncryption</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>This implementation of the DELETE action resets the default encryption for the bucket as\n         server-side encryption with Amazon S3 managed keys (SSE-S3).</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - For information\n                  about the bucket default encryption feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html\">Amazon S3 Bucket Default\n                     Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption\n                  configuration in directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html\">Setting\n                     default server-side encryption behavior for directory buckets</a>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                           <code>s3:PutEncryptionConfiguration</code> permission is required in a\n                        policy. The bucket owner has this permission by default. The bucket owner\n                        can grant this permission to others. For more information about permissions,\n                        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\n                           Permissions to Your Amazon S3 Resources</a>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        To grant access to this API operation, you must have the\n                           <code>s3express:PutEncryptionConfiguration</code> permission in\n                        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.\n                        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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteBucketEncryption</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketEncryption.html\">PutBucketEncryption</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketEncryption.html\">GetBucketEncryption</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "DELETE",
           "uri": "/{Bucket}?encryption",
@@ -20178,7 +20185,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Deletes the S3 Intelligent-Tiering configuration from the specified bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>DeleteBucketIntelligentTieringConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketIntelligentTieringConfiguration.html\">GetBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketIntelligentTieringConfiguration.html\">PutBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketIntelligentTieringConfigurations.html\">ListBucketIntelligentTieringConfigurations</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Deletes the S3 Intelligent-Tiering configuration from the specified bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>DeleteBucketIntelligentTieringConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketIntelligentTieringConfiguration.html\">GetBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketIntelligentTieringConfiguration.html\">PutBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketIntelligentTieringConfigurations.html\">ListBucketIntelligentTieringConfigurations</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "DELETE",
           "uri": "/{Bucket}?intelligent-tiering",
@@ -20227,7 +20234,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Deletes an inventory configuration (identified by the inventory ID) from the\n         bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>.</p>\n         <p>Operations related to <code>DeleteBucketInventoryConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketInventoryConfiguration.html\">GetBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketInventoryConfiguration.html\">PutBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketInventoryConfigurations.html\">ListBucketInventoryConfigurations</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Deletes an inventory configuration (identified by the inventory ID) from the\n         bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>.</p>\n         <p>Operations related to <code>DeleteBucketInventoryConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketInventoryConfiguration.html\">GetBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketInventoryConfiguration.html\">PutBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketInventoryConfigurations.html\">ListBucketInventoryConfigurations</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "DELETE",
           "uri": "/{Bucket}?inventory",
@@ -20283,7 +20290,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the\n         lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your\n         objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of\n         rules contained in the deleted lifecycle configuration.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:PutLifecycleConfiguration</code> action. By default, the bucket owner has this\n         permission and the bucket owner can grant this permission to others.</p>\n         <p>There is usually some time lag before lifecycle configuration deletion is fully\n         propagated to all the Amazon S3 systems.</p>\n         <p>For more information about the object expiration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#intro-lifecycle-rules-actions\">Elements to Describe Lifecycle Actions</a>.</p>\n         <p>Related actions include:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the\n         lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your\n         objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of\n         rules contained in the deleted lifecycle configuration.</p>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - By\n                        default, all Amazon S3 resources are private, including buckets, objects, and\n                        related subresources (for example, lifecycle configuration and website\n                        configuration). Only the resource owner (that is, the Amazon Web Services account that\n                        created it) can access the resource. The resource owner can optionally grant\n                        access permissions to others by writing an access policy. For this\n                        operation, a user must have the <code>s3:PutLifecycleConfiguration</code>\n                        permission.</p>\n                     <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing Access\n                           Permissions to Your Amazon S3 Resources</a>.</p>\n                  </li>\n               </ul>\n               <ul>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have the <code>s3express:PutLifecycleConfiguration</code>\n                        permission in an IAM identity-based policy to use this operation.\n                        Cross-account access to this API operation isn't supported. The resource\n                        owner can optionally grant access permissions to others by creating a role\n                        or user for them as long as they are within the same account as the owner\n                        and resource.</p>\n                     <p>For more information about directory bucket policies and permissions, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html\">Authorizing Regional endpoint APIs with IAM</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                     <note>\n                        <p>\n                           <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>\n                           </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n         </dl>\n         <dl>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host\n                  header syntax is\n                     <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>For more information about the object expiration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#intro-lifecycle-rules-actions\">Elements to Describe Lifecycle Actions</a>.</p>\n         <p>Related actions include:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete lifecycle configuration on a bucket.",
@@ -20322,7 +20329,7 @@
         "ExpectedBucketOwner": {
           "target": "com.amazonaws.s3#AccountId",
           "traits": {
-            "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>",
+            "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-expected-bucket-owner"
           }
         }
@@ -20340,7 +20347,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the\n         metrics configuration ID) from the bucket. Note that this doesn't include the daily storage\n         metrics.</p>\n         <p> To use this operation, you must have permissions to perform the\n            <code>s3:PutMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <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\n            Amazon CloudWatch</a>. </p>\n         <p>The following operations are related to\n         <code>DeleteBucketMetricsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetricsConfiguration.html\">GetBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketMetricsConfiguration.html\">PutBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketMetricsConfigurations.html\">ListBucketMetricsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Deletes a metrics configuration for the Amazon CloudWatch request metrics (specified by the\n         metrics configuration ID) from the bucket. Note that this doesn't include the daily storage\n         metrics.</p>\n         <p> To use this operation, you must have permissions to perform the\n            <code>s3:PutMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <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\n            Amazon CloudWatch</a>. </p>\n         <p>The following operations are related to\n         <code>DeleteBucketMetricsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetricsConfiguration.html\">GetBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketMetricsConfiguration.html\">PutBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketMetricsConfigurations.html\">ListBucketMetricsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "DELETE",
           "uri": "/{Bucket}?metrics",
@@ -20396,7 +20403,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Removes <code>OwnershipControls</code> for an Amazon S3 bucket. To use this operation, you\n         must have the <code>s3:PutBucketOwnershipControls</code> permission. For more information\n         about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <p>For information about Amazon S3 Object Ownership, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/about-object-ownership.html\">Using Object Ownership</a>. </p>\n         <p>The following operations are related to\n         <code>DeleteBucketOwnershipControls</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a>GetBucketOwnershipControls</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a>PutBucketOwnershipControls</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Removes <code>OwnershipControls</code> for an Amazon S3 bucket. To use this operation, you\n         must have the <code>s3:PutBucketOwnershipControls</code> permission. For more information\n         about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <p>For information about Amazon S3 Object Ownership, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/about-object-ownership.html\">Using Object Ownership</a>. </p>\n         <p>The following operations are related to\n         <code>DeleteBucketOwnershipControls</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a>GetBucketOwnershipControls</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a>PutBucketOwnershipControls</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "DELETE",
           "uri": "/{Bucket}?ownershipControls",
@@ -20444,7 +20451,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Deletes the\n         policy of a specified bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>If you are using an identity other than the\n                  root user of the Amazon Web Services account that owns the bucket, the calling identity must both have the\n                  <code>DeleteBucketPolicy</code> permissions on the specified bucket and belong to the\n                  bucket owner's account in order to use this operation.</p>\n               <p>If you don't have <code>DeleteBucketPolicy</code> permissions, Amazon S3 returns a <code>403\n                  Access Denied</code> error. If you have the correct permissions, but you're not using an\n                  identity that belongs to the bucket owner's account, Amazon S3 returns a <code>405 Method Not\n                     Allowed</code> error.</p>\n               <important>\n                  <p>To ensure that bucket owners don't inadvertently lock themselves out of their own\n                     buckets, the root principal in a bucket owner's Amazon Web Services account can perform the\n                     <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and\n                     <code>DeleteBucketPolicy</code> API actions, even if their bucket policy explicitly\n                     denies the root principal's access. Bucket owner root principals can only be blocked\n                     from performing these API actions by VPC endpoint policies and Amazon Web Services Organizations\n                     policies.</p>\n               </important>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The <code>s3:DeleteBucketPolicy</code> permission is required in a policy. \n                        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\n                           Policies</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation, you must have the <code>s3express:DeleteBucketPolicy</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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteBucketPolicy</code>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Deletes the policy of a specified bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>If you are using an identity other than the root user of the Amazon Web Services account that\n                  owns the bucket, the calling identity must both have the\n                     <code>DeleteBucketPolicy</code> permissions on the specified bucket and belong\n                  to the bucket owner's account in order to use this operation.</p>\n               <p>If you don't have <code>DeleteBucketPolicy</code> permissions, Amazon S3 returns a\n                     <code>403 Access Denied</code> error. If you have the correct permissions, but\n                  you're not using an identity that belongs to the bucket owner's account, Amazon S3\n                  returns a <code>405 Method Not Allowed</code> error.</p>\n               <important>\n                  <p>To ensure that bucket owners don't inadvertently lock themselves out of\n                     their own buckets, the root principal in a bucket owner's Amazon Web Services account can\n                     perform the <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and\n                        <code>DeleteBucketPolicy</code> API actions, even if their bucket policy\n                     explicitly denies the root principal's access. Bucket owner root principals can\n                     only be blocked from performing these API actions by VPC endpoint policies and\n                     Amazon Web Services Organizations policies.</p>\n               </important>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                           <code>s3:DeleteBucketPolicy</code> permission is required in a policy.\n                        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\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        To grant access to this API operation, you must have the\n                           <code>s3express:DeleteBucketPolicy</code> permission in\n                        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.\n                        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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteBucketPolicy</code>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete bucket policy",
@@ -20501,7 +20508,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p> Deletes the replication configuration from the bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutReplicationConfiguration</code> action. The bucket owner has these\n         permissions by default and can grant it to others. For more information about permissions,\n         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\n            Access Permissions to Your Amazon S3 Resources</a>. </p>\n         <note>\n            <p>It can take a while for the deletion of a replication configuration to fully\n            propagate.</p>\n         </note>\n         <p> For information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>The following operations are related to <code>DeleteBucketReplication</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketReplication.html\">PutBucketReplication</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketReplication.html\">GetBucketReplication</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p> Deletes the replication configuration from the bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutReplicationConfiguration</code> action. The bucket owner has these\n         permissions by default and can grant it to others. For more information about permissions,\n         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\n            Access Permissions to Your Amazon S3 Resources</a>. </p>\n         <note>\n            <p>It can take a while for the deletion of a replication configuration to fully\n            propagate.</p>\n         </note>\n         <p> For information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>The following operations are related to <code>DeleteBucketReplication</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketReplication.html\">PutBucketReplication</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketReplication.html\">GetBucketReplication</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete bucket replication configuration",
@@ -20584,7 +20591,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Deletes the tags from the bucket.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:PutBucketTagging</code> action. By default, the bucket owner has this\n         permission and can grant this permission to others. </p>\n         <p>The following operations are related to <code>DeleteBucketTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketTagging.html\">GetBucketTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketTagging.html\">PutBucketTagging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Deletes the tags from the bucket.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:PutBucketTagging</code> action. By default, the bucket owner has this\n         permission and can grant this permission to others. </p>\n         <p>The following operations are related to <code>DeleteBucketTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketTagging.html\">GetBucketTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketTagging.html\">PutBucketTagging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete bucket tags",
@@ -20641,7 +20648,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>This action removes the website configuration for a bucket. Amazon S3 returns a <code>200\n            OK</code> response upon successfully deleting a website configuration on the specified\n         bucket. You will get a <code>200 OK</code> response if the website configuration you are\n         trying to delete does not exist on the bucket. Amazon S3 returns a <code>404</code> response if\n         the bucket specified in the request does not exist.</p>\n         <p>This DELETE action requires the <code>S3:DeleteBucketWebsite</code> permission. By\n         default, only the bucket owner can delete the website configuration attached to a bucket.\n         However, bucket owners can grant other users permission to delete the website configuration\n         by writing a bucket policy granting them the <code>S3:DeleteBucketWebsite</code>\n         permission. </p>\n         <p>For more information about hosting websites, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a>. </p>\n         <p>The following operations are related to <code>DeleteBucketWebsite</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketWebsite.html\">GetBucketWebsite</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketWebsite.html\">PutBucketWebsite</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>This action removes the website configuration for a bucket. Amazon S3 returns a <code>200\n            OK</code> response upon successfully deleting a website configuration on the specified\n         bucket. You will get a <code>200 OK</code> response if the website configuration you are\n         trying to delete does not exist on the bucket. Amazon S3 returns a <code>404</code> response if\n         the bucket specified in the request does not exist.</p>\n         <p>This DELETE action requires the <code>S3:DeleteBucketWebsite</code> permission. By\n         default, only the bucket owner can delete the website configuration attached to a bucket.\n         However, bucket owners can grant other users permission to delete the website configuration\n         by writing a bucket policy granting them the <code>S3:DeleteBucketWebsite</code>\n         permission. </p>\n         <p>For more information about hosting websites, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a>. </p>\n         <p>The following operations are related to <code>DeleteBucketWebsite</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketWebsite.html\">GetBucketWebsite</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketWebsite.html\">PutBucketWebsite</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete bucket website configuration",
@@ -20812,7 +20819,7 @@
         "DeleteMarker": {
           "target": "com.amazonaws.s3#DeleteMarker",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates whether the specified object version that was permanently deleted was (true) or was\n         not (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or\n         not (false) the current version of the object is a delete marker.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Indicates whether the specified object version that was permanently deleted was (true)\n         or was not (false) a delete marker before deletion. In a simple DELETE, this header\n         indicates whether (true) or not (false) the current version of the object is a delete\n         marker.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-delete-marker"
           }
         },
@@ -20840,7 +20847,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket name of the bucket containing the object. </p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The bucket name of the bucket containing the object. </p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -20892,6 +20899,27 @@
             "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>",
             "smithy.api#httpHeader": "x-amz-expected-bucket-owner"
           }
+        },
+        "IfMatch": {
+          "target": "com.amazonaws.s3#IfMatch",
+          "traits": {
+            "smithy.api#documentation": "<p>The <code>If-Match</code> header field makes the request method conditional on ETags. If the ETag value does not match, the operation returns\n         a <code>412 Precondition Failed</code> error. If the ETag matches or if the object doesn't exist, the operation will return a <code>204 Success (No \n         Content) response</code>.</p>\n         <p>For more information about conditional requests, see <a href=\"https://docs.aws.amazon.com/https:/tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>\n         <note>\n            <p>This functionality is only supported for directory buckets.</p>\n         </note>",
+            "smithy.api#httpHeader": "If-Match"
+          }
+        },
+        "IfMatchLastModifiedTime": {
+          "target": "com.amazonaws.s3#IfMatchLastModifiedTime",
+          "traits": {
+            "smithy.api#documentation": "<p>If present, the object is deleted only if its modification times matches the provided\n            <code>Timestamp</code>. If the <code>Timestamp</code> values do not match, the operation\n         returns a <code>412 Precondition Failed</code> error. If the <code>Timestamp</code> matches\n         or if the object doesn’t exist, the operation returns a <code>204 Success (No\n            Content)</code> response.</p>\n         <note>\n            <p>This functionality is only supported for directory buckets.</p>\n         </note>",
+            "smithy.api#httpHeader": "x-amz-if-match-last-modified-time"
+          }
+        },
+        "IfMatchSize": {
+          "target": "com.amazonaws.s3#IfMatchSize",
+          "traits": {
+            "smithy.api#documentation": "<p>If present, the object is deleted only if its size matches the provided size in bytes. If the <code>Size</code> value does not match, the operation returns a <code>412 Precondition Failed</code> error. If the <code>Size</code> matches or if the object doesn’t exist, \n         the operation returns a <code>204 Success (No Content)</code> response.</p>\n         <note>\n            <p>This functionality is only supported for directory buckets.</p>\n         </note>\n         <important>\n            <p>You can use the <code>If-Match</code>, <code>x-amz-if-match-last-modified-time</code> and <code>x-amz-if-match-size</code> \n         conditional headers in conjunction with each-other or individually.</p>\n         </important>",
+            "smithy.api#httpHeader": "x-amz-if-match-size"
+          }
         }
       },
       "traits": {
@@ -20907,7 +20935,7 @@
         "target": "com.amazonaws.s3#DeleteObjectTaggingOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Removes the entire tag set from the specified object. For more information about\n         managing object tags, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\"> Object Tagging</a>.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:DeleteObjectTagging</code> action.</p>\n         <p>To delete tags of a specific object version, add the <code>versionId</code> query\n         parameter in the request. You will need permission for the\n            <code>s3:DeleteObjectVersionTagging</code> action.</p>\n         <p>The following operations are related to <code>DeleteObjectTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjectTagging.html\">PutObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Removes the entire tag set from the specified object. For more information about\n         managing object tags, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\"> Object Tagging</a>.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:DeleteObjectTagging</code> action.</p>\n         <p>To delete tags of a specific object version, add the <code>versionId</code> query\n         parameter in the request. You will need permission for the\n            <code>s3:DeleteObjectVersionTagging</code> action.</p>\n         <p>The following operations are related to <code>DeleteObjectTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjectTagging.html\">PutObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To remove tag set from an object",
@@ -21009,7 +21037,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<p>This operation enables you to delete multiple objects from a bucket using a single HTTP\n         request. If you know the object keys that you want to delete, then this operation provides a\n         suitable alternative to sending individual delete requests, reducing per-request\n         overhead.</p>\n         <p>The request can contain a list of up to 1000 keys that you want to delete. In the XML, you\n         provide the object key names, and optionally, version IDs if you want to delete a specific\n         version of the object from a versioning-enabled bucket. For each key, Amazon S3 performs a\n         delete operation and returns the result of that delete, success or failure, in the response.\n         Note that if the object specified in the request is not found, Amazon S3 returns the result as\n         deleted.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <p>The operation supports two modes for the response: verbose and quiet. By default, the\n         operation uses verbose mode in which the response includes the result of deletion of each key\n         in your request. In quiet mode the response includes only keys where the delete operation \n         encountered an error. For a successful deletion in a quiet mode, the operation does not return any information\n         about the delete in the response body.</p>\n         <p>When performing this action on an MFA Delete enabled bucket, that attempts to delete any\n         versioned objects, you must include an MFA token. If you do not provide one, the entire\n         request will fail, even if there are non-versioned objects you are trying to delete. If you\n         provide an invalid token, whether there are versioned keys in the request or not, the\n         entire Multi-Object Delete request will fail. For information about MFA Delete, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete\">MFA\n            Delete</a> in the <i>Amazon S3\n               User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - MFA delete is not supported by directory buckets.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The following permissions are required in your policies when your \n                        <code>DeleteObjects</code> request includes specific headers.</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:DeleteObject</code>\n                              </b> - To delete an object from a bucket, you must always specify the <code>s3:DeleteObject</code> permission.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:DeleteObjectVersion</code>\n                              </b> - To delete a specific version of an object from a versioning-enabled bucket, you must specify the <code>s3:DeleteObjectVersion</code> permission.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Content-MD5 request header</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - The Content-MD5 request header is required for all Multi-Object Delete requests. Amazon S3\n                     uses the header value to ensure that your request body has not been altered in\n                     transit.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> - The Content-MD5 request header or a additional checksum request header \n                     (including <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or \n                     <code>x-amz-checksum-sha256</code>) is required for all Multi-Object Delete requests.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteObjects</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>This operation enables you to delete multiple objects from a bucket using a single HTTP\n         request. If you know the object keys that you want to delete, then this operation provides\n         a suitable alternative to sending individual delete requests, reducing per-request\n         overhead.</p>\n         <p>The request can contain a list of up to 1000 keys that you want to delete. In the XML,\n         you provide the object key names, and optionally, version IDs if you want to delete a\n         specific version of the object from a versioning-enabled bucket. For each key, Amazon S3\n         performs a delete operation and returns the result of that delete, success or failure, in\n         the response. Note that if the object specified in the request is not found, Amazon S3 returns\n         the result as deleted.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  S3 Versioning isn't enabled and supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <p>The operation supports two modes for the response: verbose and quiet. By default, the\n         operation uses verbose mode in which the response includes the result of deletion of each\n         key in your request. In quiet mode the response includes only keys where the delete\n         operation encountered an error. For a successful deletion in a quiet mode, the operation\n         does not return any information about the delete in the response body.</p>\n         <p>When performing this action on an MFA Delete enabled bucket, that attempts to delete any\n         versioned objects, you must include an MFA token. If you do not provide one, the entire\n         request will fail, even if there are non-versioned objects you are trying to delete. If you\n         provide an invalid token, whether there are versioned keys in the request or not, the\n         entire Multi-Object Delete request will fail. For information about MFA Delete, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete\">MFA\n            Delete</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            MFA delete is not supported by directory buckets.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                        following permissions are required in your policies when your\n                           <code>DeleteObjects</code> request includes specific headers.</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:DeleteObject</code>\n                              </b>\n                              - To delete an object from a bucket, you must always specify\n                              the <code>s3:DeleteObject</code> permission.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:DeleteObjectVersion</code>\n                              </b> - To delete a specific version of an object from a\n                              versioning-enabled bucket, you must specify the\n                                 <code>s3:DeleteObjectVersion</code> permission.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Content-MD5 request header</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - The Content-MD5\n                        request header is required for all Multi-Object Delete requests. Amazon S3 uses\n                        the header value to ensure that your request body has not been altered in\n                        transit.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> - The\n                        Content-MD5 request header or a additional checksum request header\n                        (including <code>x-amz-checksum-crc32</code>,\n                           <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or\n                           <code>x-amz-checksum-sha256</code>) is required for all Multi-Object\n                        Delete requests.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>DeleteObjects</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To delete multiple object versions from a versioned bucket",
@@ -21119,7 +21147,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket name containing the objects to delete. </p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The bucket name containing the objects to delete. </p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -21139,7 +21167,7 @@
         "MFA": {
           "target": "com.amazonaws.s3#MFA",
           "traits": {
-            "smithy.api#documentation": "<p>The concatenation of the authentication device's serial number, a space, and the value\n         that is displayed on your authentication device. Required to permanently delete a versioned\n         object if versioning is configured with MFA delete enabled.</p>\n         <p>When performing the <code>DeleteObjects</code> operation on an MFA delete enabled bucket, which attempts to delete the specified \n         versioned objects, you must include an MFA token. If you don't provide an MFA token, the entire\n         request will fail, even if there are non-versioned objects that you are trying to delete. If you\n         provide an invalid token, whether there are versioned object keys in the request or not, the\n         entire Multi-Object Delete request will fail. For information about MFA Delete, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete\"> MFA\n            Delete</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The concatenation of the authentication device's serial number, a space, and the value\n         that is displayed on your authentication device. Required to permanently delete a versioned\n         object if versioning is configured with MFA delete enabled.</p>\n         <p>When performing the <code>DeleteObjects</code> operation on an MFA delete enabled\n         bucket, which attempts to delete the specified versioned objects, you must include an MFA\n         token. If you don't provide an MFA token, the entire request will fail, even if there are\n         non-versioned objects that you are trying to delete. If you provide an invalid token,\n         whether there are versioned object keys in the request or not, the entire Multi-Object\n         Delete request will fail. For information about MFA Delete, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete\"> MFA\n            Delete</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-mfa"
           }
         },
@@ -21184,7 +21212,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Removes the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use this\n         operation, you must have the <code>s3:PutBucketPublicAccessBlock</code> permission. For\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>The following operations are related to <code>DeletePublicAccessBlock</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutPublicAccessBlock.html\">PutPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketPolicyStatus.html\">GetBucketPolicyStatus</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Removes the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use this\n         operation, you must have the <code>s3:PutBucketPublicAccessBlock</code> permission. For\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>The following operations are related to <code>DeletePublicAccessBlock</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutPublicAccessBlock.html\">PutPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketPolicyStatus.html\">GetBucketPolicyStatus</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "DELETE",
           "uri": "/{Bucket}?publicAccessBlock",
@@ -21241,7 +21269,7 @@
         "DeleteMarker": {
           "target": "com.amazonaws.s3#DeleteMarker",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates whether the specified object version that was permanently deleted was (true) or was\n         not (false) a delete marker before deletion. In a simple DELETE, this header indicates whether (true) or\n         not (false) the current version of the object is a delete marker.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Indicates whether the specified object version that was permanently deleted was (true)\n         or was not (false) a delete marker before deletion. In a simple DELETE, this header\n         indicates whether (true) or not (false) the current version of the object is a delete\n         marker.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
           }
         },
         "DeleteMarkerVersionId": {
@@ -21350,7 +21378,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Encoding type used by Amazon S3 to encode the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html\">object keys</a> in the response.\n         Responses are encoded only in UTF-8. An object key can contain any Unicode character.\n         However, the XML 1.0 parser can't parse certain characters, such as characters with an\n         ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this\n         parameter to request that Amazon S3 encode the keys in the response. For more information about\n         characters to avoid in object key names, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html#object-key-guidelines\">Object key naming\n            guidelines</a>.</p>\n         <note>\n            <p>When using the URL encoding type, non-ASCII characters that are used in an object's\n            key name will be percent-encoded according to UTF-8 code values. For example, the object\n            <code>test_file(3).png</code> will appear as\n            <code>test_file%283%29.png</code>.</p>\n         </note>"
+        "smithy.api#documentation": "<p>Encoding type used by Amazon S3 to encode the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html\">object keys</a> in the response.\n         Responses are encoded only in UTF-8. An object key can contain any Unicode character.\n         However, the XML 1.0 parser can't parse certain characters, such as characters with an\n         ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this\n         parameter to request that Amazon S3 encode the keys in the response. For more information about\n         characters to avoid in object key names, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html#object-key-guidelines\">Object key naming\n            guidelines</a>.</p>\n         <note>\n            <p>When using the URL encoding type, non-ASCII characters that are used in an object's\n            key name will be percent-encoded according to UTF-8 code values. For example, the object\n               <code>test_file(3).png</code> will appear as\n            <code>test_file%283%29.png</code>.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#Encryption": {
@@ -21391,7 +21419,16 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Specifies encryption-related information for an Amazon S3 bucket that is a destination for\n         replicated objects.</p>\n         <note>\n            <p>If you're specifying a customer managed KMS key, we recommend using a fully qualified\n         KMS key ARN. If you use a KMS key alias instead, then KMS resolves the key within the\n         requester’s account. This behavior can result in data that's encrypted with a KMS key\n         that belongs to the requester, and not the bucket owner.</p>\n         </note>"
+        "smithy.api#documentation": "<p>Specifies encryption-related information for an Amazon S3 bucket that is a destination for\n         replicated objects.</p>\n         <note>\n            <p>If you're specifying a customer managed KMS key, we recommend using a fully\n            qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the\n            key within the requester’s account. This behavior can result in data that's encrypted\n            with a KMS key that belongs to the requester, and not the bucket owner.</p>\n         </note>"
+      }
+    },
+    "com.amazonaws.s3#EncryptionTypeMismatch": {
+      "type": "structure",
+      "members": {},
+      "traits": {
+        "smithy.api#documentation": "<p>\n         The existing object was created with a different encryption type. \n         Subsequent write requests must include the appropriate encryption \n         parameters in the request or while creating the session.\n      </p>",
+        "smithy.api#error": "client",
+        "smithy.api#httpError": 400
       }
     },
     "com.amazonaws.s3#End": {
@@ -21658,7 +21695,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Optional configuration to replicate existing source bucket objects. \n      </p>\n         <note>\n            <p>This parameter is no longer supported. To replicate existing objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html\">Replicating existing objects with S3 Batch Replication</a> in the <i>Amazon S3 User Guide</i>.</p>\n         </note>"
+        "smithy.api#documentation": "<p>Optional configuration to replicate existing source bucket objects. </p>\n         <note>\n            <p>This parameter is no longer supported. To replicate existing objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html\">Replicating existing objects with S3 Batch Replication</a> in the\n               <i>Amazon S3 User Guide</i>.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#ExistingObjectReplicationStatus": {
@@ -21773,7 +21810,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned to an object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of the object key name. A prefix is a specific string of characters at the beginning of an object key name, which you can use to organize objects. For example, you can start the key names of related objects with a prefix, such as <code>2023-</code> or  <code>engineering/</code>. Then, you can use <code>FilterRule</code> to find objects in a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it is at the end of the object key name instead of at the beginning.</p>"
+        "smithy.api#documentation": "<p>Specifies the Amazon S3 object key name to filter on. An object key name is the name assigned\n         to an object in your Amazon S3 bucket. You specify whether to filter on the suffix or prefix of\n         the object key name. A prefix is a specific string of characters at the beginning of an\n         object key name, which you can use to organize objects. For example, you can start the key\n         names of related objects with a prefix, such as <code>2023-</code> or\n            <code>engineering/</code>. Then, you can use <code>FilterRule</code> to find objects in\n         a bucket with key names that have the same prefix. A suffix is similar to a prefix, but it\n         is at the end of the object key name instead of at the beginning.</p>"
       }
     },
     "com.amazonaws.s3#FilterRuleList": {
@@ -21814,7 +21851,7 @@
         "target": "com.amazonaws.s3#GetBucketAccelerateConfigurationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>This implementation of the GET action uses the <code>accelerate</code> subresource to\n         return the Transfer Acceleration state of a bucket, which is either <code>Enabled</code> or\n            <code>Suspended</code>. Amazon S3 Transfer Acceleration is a bucket-level feature that\n         enables you to perform faster data transfers to and from Amazon S3.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:GetAccelerateConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to your Amazon S3 Resources</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>You set the Transfer Acceleration state of an existing bucket to <code>Enabled</code> or\n            <code>Suspended</code> by using the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAccelerateConfiguration.html\">PutBucketAccelerateConfiguration</a> operation. </p>\n         <p>A GET <code>accelerate</code> request does not return a state value for a bucket that\n         has no transfer acceleration state. A bucket has no Transfer Acceleration state if a state\n         has never been set on the bucket. </p>\n         <p>For more information about transfer acceleration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer Acceleration</a> in\n         the Amazon S3 User Guide.</p>\n         <p>The following operations are related to\n         <code>GetBucketAccelerateConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAccelerateConfiguration.html\">PutBucketAccelerateConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>This implementation of the GET action uses the <code>accelerate</code> subresource to\n         return the Transfer Acceleration state of a bucket, which is either <code>Enabled</code> or\n            <code>Suspended</code>. Amazon S3 Transfer Acceleration is a bucket-level feature that\n         enables you to perform faster data transfers to and from Amazon S3.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:GetAccelerateConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to your Amazon S3 Resources</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>You set the Transfer Acceleration state of an existing bucket to <code>Enabled</code> or\n            <code>Suspended</code> by using the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAccelerateConfiguration.html\">PutBucketAccelerateConfiguration</a> operation. </p>\n         <p>A GET <code>accelerate</code> request does not return a state value for a bucket that\n         has no transfer acceleration state. A bucket has no Transfer Acceleration state if a state\n         has never been set on the bucket. </p>\n         <p>For more information about transfer acceleration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer Acceleration</a> in\n         the Amazon S3 User Guide.</p>\n         <p>The following operations are related to\n         <code>GetBucketAccelerateConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAccelerateConfiguration.html\">PutBucketAccelerateConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?accelerate",
@@ -21889,7 +21926,7 @@
         "target": "com.amazonaws.s3#GetBucketAclOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>This implementation of the <code>GET</code> action uses the <code>acl</code> subresource\n         to return the access control list (ACL) of a bucket. To use <code>GET</code> to return the\n         ACL of the bucket, you must have the <code>READ_ACP</code> access to the bucket. If\n            <code>READ_ACP</code> permission is granted to the anonymous user, you can return the\n         ACL of the bucket without using an authorization header.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <note>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership,\n            requests to read ACLs are still supported and return the\n               <code>bucket-owner-full-control</code> ACL with the owner being the account that\n            created the bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\"> Controlling object\n               ownership and disabling ACLs</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>The following operations are related to <code>GetBucketAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html\">ListObjects</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>This implementation of the <code>GET</code> action uses the <code>acl</code> subresource\n         to return the access control list (ACL) of a bucket. To use <code>GET</code> to return the\n         ACL of the bucket, you must have the <code>READ_ACP</code> access to the bucket. If\n            <code>READ_ACP</code> permission is granted to the anonymous user, you can return the\n         ACL of the bucket without using an authorization header.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <note>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership,\n            requests to read ACLs are still supported and return the\n               <code>bucket-owner-full-control</code> ACL with the owner being the account that\n            created the bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\"> Controlling object\n               ownership and disabling ACLs</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>The following operations are related to <code>GetBucketAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html\">ListObjects</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?acl",
@@ -21959,7 +21996,7 @@
         "target": "com.amazonaws.s3#GetBucketAnalyticsConfigurationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>This implementation of the GET action returns an analytics configuration (identified by\n         the analytics configuration ID) from the bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a> in the\n            <i>Amazon S3 User Guide</i>. </p>\n         <p>For information about Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class\n            Analysis</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>The following operations are related to\n         <code>GetBucketAnalyticsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketAnalyticsConfiguration.html\">DeleteBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html\">ListBucketAnalyticsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAnalyticsConfiguration.html\">PutBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>This implementation of the GET action returns an analytics configuration (identified by\n         the analytics configuration ID) from the bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a> in the\n            <i>Amazon S3 User Guide</i>. </p>\n         <p>For information about Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class\n            Analysis</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>The following operations are related to\n         <code>GetBucketAnalyticsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketAnalyticsConfiguration.html\">DeleteBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html\">ListBucketAnalyticsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAnalyticsConfiguration.html\">PutBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?analytics&x-id=GetBucketAnalyticsConfiguration",
@@ -22030,7 +22067,7 @@
         "target": "com.amazonaws.s3#GetBucketCorsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the Cross-Origin Resource Sharing (CORS) configuration information set for the\n         bucket.</p>\n         <p> To use this operation, you must have permission to perform the\n            <code>s3:GetBucketCORS</code> action. By default, the bucket owner has this permission\n         and can grant it to others.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <p> For more information about CORS, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\"> Enabling Cross-Origin Resource\n         Sharing</a>.</p>\n         <p>The following operations are related to <code>GetBucketCors</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketCors.html\">PutBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketCors.html\">DeleteBucketCors</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the Cross-Origin Resource Sharing (CORS) configuration information set for the\n         bucket.</p>\n         <p> To use this operation, you must have permission to perform the\n            <code>s3:GetBucketCORS</code> action. By default, the bucket owner has this permission\n         and can grant it to others.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <p> For more information about CORS, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\"> Enabling Cross-Origin Resource\n         Sharing</a>.</p>\n         <p>The following operations are related to <code>GetBucketCors</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketCors.html\">PutBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketCors.html\">DeleteBucketCors</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get cors configuration set on a bucket",
@@ -22114,7 +22151,7 @@
         "target": "com.amazonaws.s3#GetBucketEncryptionOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Returns the default encryption configuration for an Amazon S3 bucket. By default, all buckets\n         have a default encryption configuration that uses server-side encryption with Amazon S3 managed\n         keys (SSE-S3). </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - 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\n                  Default Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption configuration in directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html\">Setting default server-side encryption behavior \n               for directory buckets</a>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The <code>s3:GetEncryptionConfiguration</code> permission is required in a policy. \n                        The bucket owner has this permission\n                        by default. The bucket owner can grant this permission to others. For more information\n                        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\n                              Access Permissions to Your Amazon S3 Resources</a>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation, you must have the <code>s3express:GetEncryptionConfiguration</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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>GetBucketEncryption</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketEncryption.html\">PutBucketEncryption</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketEncryption.html\">DeleteBucketEncryption</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Returns the default encryption configuration for an Amazon S3 bucket. By default, all buckets\n         have a default encryption configuration that uses server-side encryption with Amazon S3 managed\n         keys (SSE-S3). </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - For information\n                  about the bucket default encryption feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html\">Amazon S3 Bucket Default\n                     Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. For information about the default encryption\n                  configuration in directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-bucket-encryption.html\">Setting\n                     default server-side encryption behavior for directory buckets</a>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                           <code>s3:GetEncryptionConfiguration</code> permission is required in a\n                        policy. The bucket owner has this permission by default. The bucket owner\n                        can grant this permission to others. For more information about permissions,\n                        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\n                           Permissions to Your Amazon S3 Resources</a>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        To grant access to this API operation, you must have the\n                           <code>s3express:GetEncryptionConfiguration</code> permission in\n                        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.\n                        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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>GetBucketEncryption</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketEncryption.html\">PutBucketEncryption</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketEncryption.html\">DeleteBucketEncryption</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?encryption",
@@ -22176,7 +22213,7 @@
         "target": "com.amazonaws.s3#GetBucketIntelligentTieringConfigurationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Gets the S3 Intelligent-Tiering configuration from the specified bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>GetBucketIntelligentTieringConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketIntelligentTieringConfiguration.html\">DeleteBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketIntelligentTieringConfiguration.html\">PutBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketIntelligentTieringConfigurations.html\">ListBucketIntelligentTieringConfigurations</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Gets the S3 Intelligent-Tiering configuration from the specified bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>GetBucketIntelligentTieringConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketIntelligentTieringConfiguration.html\">DeleteBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketIntelligentTieringConfiguration.html\">PutBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketIntelligentTieringConfigurations.html\">ListBucketIntelligentTieringConfigurations</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?intelligent-tiering&x-id=GetBucketIntelligentTieringConfiguration",
@@ -22240,7 +22277,7 @@
         "target": "com.amazonaws.s3#GetBucketInventoryConfigurationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns an inventory configuration (identified by the inventory configuration ID) from\n         the bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetInventoryConfiguration</code> action. The bucket owner has this permission\n         by default and can grant this permission to others. For more information about permissions,\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>.</p>\n         <p>The following operations are related to\n         <code>GetBucketInventoryConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketInventoryConfiguration.html\">DeleteBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketInventoryConfigurations.html\">ListBucketInventoryConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketInventoryConfiguration.html\">PutBucketInventoryConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns an inventory configuration (identified by the inventory configuration ID) from\n         the bucket.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetInventoryConfiguration</code> action. The bucket owner has this permission\n         by default and can grant this permission to others. For more information about permissions,\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>.</p>\n         <p>The following operations are related to\n         <code>GetBucketInventoryConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketInventoryConfiguration.html\">DeleteBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketInventoryConfigurations.html\">ListBucketInventoryConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketInventoryConfiguration.html\">PutBucketInventoryConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?inventory&x-id=GetBucketInventoryConfiguration",
@@ -22311,7 +22348,7 @@
         "target": "com.amazonaws.s3#GetBucketLifecycleConfigurationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <note>\n            <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.\n            For the related API description, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycle.html\">GetBucketLifecycle</a>. Accordingly,\n            this section describes the latest API. The response describes the new filter element\n            that you can use to specify a filter to select a subset of objects to which the rule\n            applies. If you are using a previous version of the lifecycle configuration, it still\n            works. For the earlier action, </p>\n         </note>\n         <p>Returns the lifecycle configuration information set on the bucket. For information about\n         lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle\n         Management</a>.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:GetLifecycleConfiguration</code> action. The bucket owner has this permission,\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>\n            <code>GetBucketLifecycleConfiguration</code> has the following special error:</p>\n         <ul>\n            <li>\n               <p>Error code: <code>NoSuchLifecycleConfiguration</code>\n               </p>\n               <ul>\n                  <li>\n                     <p>Description: The lifecycle configuration does not exist.</p>\n                  </li>\n                  <li>\n                     <p>HTTP Status Code: 404 Not Found</p>\n                  </li>\n                  <li>\n                     <p>SOAP Fault Code Prefix: Client</p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n         <p>The following operations are related to\n         <code>GetBucketLifecycleConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycle.html\">GetBucketLifecycle</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html\">PutBucketLifecycle</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html\">DeleteBucketLifecycle</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Returns the lifecycle configuration information set on the bucket. For information about\n         lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle\n         Management</a>.</p>\n         <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an object\n         key name prefix, one or more object tags, object size, or any combination of these.\n         Accordingly, this section describes the latest API, which is compatible with the new\n         functionality. The previous version of the API supported filtering based only on an object\n         key name prefix, which is supported for general purpose buckets for backward compatibility.\n         For the related API description, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycle.html\">GetBucketLifecycle</a>.</p>\n         <note>\n            <p>Lifecyle configurations for directory buckets only support expiring objects and\n            cancelling multipart uploads. Expiring of versioned objects, transitions and tag filters\n            are not supported.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - By\n                        default, all Amazon S3 resources are private, including buckets, objects, and\n                        related subresources (for example, lifecycle configuration and website\n                        configuration). Only the resource owner (that is, the Amazon Web Services account that\n                        created it) can access the resource. The resource owner can optionally grant\n                        access permissions to others by writing an access policy. For this\n                        operation, a user must have the <code>s3:GetLifecycleConfiguration</code>\n                        permission.</p>\n                     <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing Access\n                           Permissions to Your Amazon S3 Resources</a>.</p>\n                  </li>\n               </ul>\n               <ul>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have the <code>s3express:GetLifecycleConfiguration</code>\n                        permission in an IAM identity-based policy to use this operation.\n                        Cross-account access to this API operation isn't supported. The resource\n                        owner can optionally grant access permissions to others by creating a role\n                        or user for them as long as they are within the same account as the owner\n                        and resource.</p>\n                     <p>For more information about directory bucket policies and permissions, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html\">Authorizing Regional endpoint APIs with IAM</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                     <note>\n                        <p>\n                           <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>\n                           </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host\n                  header syntax is\n                     <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>\n            <code>GetBucketLifecycleConfiguration</code> has the following special error:</p>\n         <ul>\n            <li>\n               <p>Error code: <code>NoSuchLifecycleConfiguration</code>\n               </p>\n               <ul>\n                  <li>\n                     <p>Description: The lifecycle configuration does not exist.</p>\n                  </li>\n                  <li>\n                     <p>HTTP Status Code: 404 Not Found</p>\n                  </li>\n                  <li>\n                     <p>SOAP Fault Code Prefix: Client</p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n         <p>The following operations are related to\n         <code>GetBucketLifecycleConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycle.html\">GetBucketLifecycle</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html\">PutBucketLifecycle</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html\">DeleteBucketLifecycle</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get lifecycle configuration on a bucket",
@@ -22362,7 +22399,7 @@
         "TransitionDefaultMinimumObjectSize": {
           "target": "com.amazonaws.s3#TransitionDefaultMinimumObjectSize",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates which default minimum object size behavior is applied to the lifecycle configuration.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not transition to any storage class by default. </p>\n            </li>\n            <li>\n               <p>\n                  <code>varies_by_storage_class</code> - Objects smaller than 128 KB will transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes will prevent transitions smaller than 128 KB.\n         </p>\n            </li>\n         </ul>\n         <p>To customize the minimum object size for any transition you can add a filter that specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in the body of your transition rule.  Custom filters always take precedence over the default transition behavior.</p>",
+            "smithy.api#documentation": "<p>Indicates which default minimum object size behavior is applied to the lifecycle\n         configuration.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>\n         <ul>\n            <li>\n               <p>\n                  <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not\n               transition to any storage class by default.</p>\n            </li>\n            <li>\n               <p>\n                  <code>varies_by_storage_class</code> - Objects smaller than 128 KB will\n               transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By\n               default, all other storage classes will prevent transitions smaller than 128 KB.\n            </p>\n            </li>\n         </ul>\n         <p>To customize the minimum object size for any transition you can add a filter that\n         specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in\n         the body of your transition rule. Custom filters always take precedence over the default\n         transition behavior.</p>",
             "smithy.api#httpHeader": "x-amz-transition-default-minimum-object-size"
           }
         }
@@ -22389,7 +22426,7 @@
         "ExpectedBucketOwner": {
           "target": "com.amazonaws.s3#AccountId",
           "traits": {
-            "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>",
+            "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-expected-bucket-owner"
           }
         }
@@ -22408,7 +22445,7 @@
       },
       "traits": {
         "aws.customizations#s3UnwrappedXmlOutput": {},
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the Region the bucket resides in. You set the bucket's Region using the\n            <code>LocationConstraint</code> request parameter in a <code>CreateBucket</code>\n         request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <note>\n            <p>We recommend that you use <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html\">HeadBucket</a> to return the Region\n            that a bucket resides in. For backward compatibility, Amazon S3 continues to support\n            GetBucketLocation.</p>\n         </note>\n         <p>The following operations are related to <code>GetBucketLocation</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the Region the bucket resides in. You set the bucket's Region using the\n            <code>LocationConstraint</code> request parameter in a <code>CreateBucket</code>\n         request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <note>\n            <p>We recommend that you use <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html\">HeadBucket</a> to return the Region\n            that a bucket resides in. For backward compatibility, Amazon S3 continues to support\n            GetBucketLocation.</p>\n         </note>\n         <p>The following operations are related to <code>GetBucketLocation</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get bucket location",
@@ -22483,7 +22520,7 @@
         "target": "com.amazonaws.s3#GetBucketLoggingOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the logging status of a bucket and the permissions users have to view and modify\n         that status.</p>\n         <p>The following operations are related to <code>GetBucketLogging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLogging.html\">PutBucketLogging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the logging status of a bucket and the permissions users have to view and modify\n         that status.</p>\n         <p>The following operations are related to <code>GetBucketLogging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLogging.html\">PutBucketLogging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?logging",
@@ -22543,7 +22580,7 @@
         "target": "com.amazonaws.s3#GetBucketMetricsConfigurationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Gets a metrics configuration (specified by the metrics configuration ID) from the\n         bucket. Note that this doesn't include the daily storage metrics.</p>\n         <p> To use this operation, you must have permissions to perform the\n            <code>s3:GetMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <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\n            Metrics with Amazon CloudWatch</a>.</p>\n         <p>The following operations are related to\n         <code>GetBucketMetricsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketMetricsConfiguration.html\">PutBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetricsConfiguration.html\">DeleteBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketMetricsConfigurations.html\">ListBucketMetricsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Gets a metrics configuration (specified by the metrics configuration ID) from the\n         bucket. Note that this doesn't include the daily storage metrics.</p>\n         <p> To use this operation, you must have permissions to perform the\n            <code>s3:GetMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <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\n            Metrics with Amazon CloudWatch</a>.</p>\n         <p>The following operations are related to\n         <code>GetBucketMetricsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketMetricsConfiguration.html\">PutBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetricsConfiguration.html\">DeleteBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketMetricsConfigurations.html\">ListBucketMetricsConfigurations</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?metrics&x-id=GetBucketMetricsConfiguration",
@@ -22614,7 +22651,7 @@
         "target": "com.amazonaws.s3#NotificationConfiguration"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the notification configuration of a bucket.</p>\n         <p>If notifications are not enabled on the bucket, the action returns an empty\n            <code>NotificationConfiguration</code> element.</p>\n         <p>By default, you must be the bucket owner to read the notification configuration of a\n         bucket. However, the bucket owner can use a bucket policy to grant permission to other\n         users to read this configuration with the <code>s3:GetBucketNotification</code>\n         permission.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <p>For more information about setting and reading the notification configuration on a\n         bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Setting Up Notification of Bucket Events</a>. For more information about bucket\n         policies, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies</a>.</p>\n         <p>The following action is related to <code>GetBucketNotification</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketNotification.html\">PutBucketNotification</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the notification configuration of a bucket.</p>\n         <p>If notifications are not enabled on the bucket, the action returns an empty\n            <code>NotificationConfiguration</code> element.</p>\n         <p>By default, you must be the bucket owner to read the notification configuration of a\n         bucket. However, the bucket owner can use a bucket policy to grant permission to other\n         users to read this configuration with the <code>s3:GetBucketNotification</code>\n         permission.</p>\n         <p>When you use this API operation with an access point, provide the alias of the access point in place of the bucket name.</p>\n         <p>When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <p>For more information about setting and reading the notification configuration on a\n         bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Setting Up Notification of Bucket Events</a>. For more information about bucket\n         policies, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies</a>.</p>\n         <p>The following action is related to <code>GetBucketNotification</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketNotification.html\">PutBucketNotification</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?notification",
@@ -22662,7 +22699,7 @@
         "target": "com.amazonaws.s3#GetBucketOwnershipControlsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Retrieves <code>OwnershipControls</code> for an Amazon S3 bucket. To use this operation, you\n         must have the <code>s3:GetBucketOwnershipControls</code> permission. For more information\n         about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html\">Specifying permissions in a\n            policy</a>. </p>\n         <p>For information about Amazon S3 Object Ownership, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Using Object\n            Ownership</a>. </p>\n         <p>The following operations are related to <code>GetBucketOwnershipControls</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a>PutBucketOwnershipControls</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a>DeleteBucketOwnershipControls</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Retrieves <code>OwnershipControls</code> for an Amazon S3 bucket. To use this operation, you\n         must have the <code>s3:GetBucketOwnershipControls</code> permission. For more information\n         about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html\">Specifying permissions in a\n            policy</a>. </p>\n         <p>For information about Amazon S3 Object Ownership, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Using Object\n            Ownership</a>. </p>\n         <p>The following operations are related to <code>GetBucketOwnershipControls</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a>PutBucketOwnershipControls</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a>DeleteBucketOwnershipControls</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?ownershipControls",
@@ -22725,7 +22762,7 @@
         "target": "com.amazonaws.s3#GetBucketPolicyOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Returns the policy of a specified bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>If you are using an identity other than the\n                  root user of the Amazon Web Services account that owns the bucket, the calling identity must both have the\n                  <code>GetBucketPolicy</code> permissions on the specified bucket and belong to the\n                  bucket owner's account in order to use this operation.</p>\n               <p>If you don't have <code>GetBucketPolicy</code> permissions, Amazon S3 returns a <code>403\n                  Access Denied</code> error. If you have the correct permissions, but you're not using an\n                  identity that belongs to the bucket owner's account, Amazon S3 returns a <code>405 Method Not\n                     Allowed</code> error.</p>\n               <important>\n                  <p>To ensure that bucket owners don't inadvertently lock themselves out of their own\n                     buckets, the root principal in a bucket owner's Amazon Web Services account can perform the\n                     <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and\n                     <code>DeleteBucketPolicy</code> API actions, even if their bucket policy explicitly\n                     denies the root principal's access. Bucket owner root principals can only be blocked\n                     from performing these API actions by VPC endpoint policies and Amazon Web Services Organizations\n                     policies.</p>\n               </important>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The <code>s3:GetBucketPolicy</code> permission is required in a policy. \n                        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\n                        Policies</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation, you must have the <code>s3express:GetBucketPolicy</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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Example bucket policies</dt>\n            <dd>\n               <p>\n                  <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>\n               <p>\n                  <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>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following action is related to <code>GetBucketPolicy</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Returns the policy of a specified bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>If you are using an identity other than the root user of the Amazon Web Services account that\n                  owns the bucket, the calling identity must both have the\n                     <code>GetBucketPolicy</code> permissions on the specified bucket and belong to\n                  the bucket owner's account in order to use this operation.</p>\n               <p>If you don't have <code>GetBucketPolicy</code> permissions, Amazon S3 returns a\n                     <code>403 Access Denied</code> error. If you have the correct permissions, but\n                  you're not using an identity that belongs to the bucket owner's account, Amazon S3\n                  returns a <code>405 Method Not Allowed</code> error.</p>\n               <important>\n                  <p>To ensure that bucket owners don't inadvertently lock themselves out of\n                     their own buckets, the root principal in a bucket owner's Amazon Web Services account can\n                     perform the <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and\n                        <code>DeleteBucketPolicy</code> API actions, even if their bucket policy\n                     explicitly denies the root principal's access. Bucket owner root principals can\n                     only be blocked from performing these API actions by VPC endpoint policies and\n                     Amazon Web Services Organizations policies.</p>\n               </important>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                           <code>s3:GetBucketPolicy</code> permission is required in a policy. For\n                        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\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        To grant access to this API operation, you must have the\n                           <code>s3express:GetBucketPolicy</code> permission in\n                        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.\n                        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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Example bucket policies</dt>\n            <dd>\n               <p>\n                  <b>General purpose buckets example bucket policies</b>\n                  - See <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html\">Bucket policy\n                     examples</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <p>\n                  <b>Directory bucket example bucket policies</b>\n                  - 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\n                     <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following action is related to <code>GetBucketPolicy</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get bucket policy",
@@ -22800,7 +22837,7 @@
         "target": "com.amazonaws.s3#GetBucketPolicyStatusOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public.\n         In order to use this operation, you must have the <code>s3:GetBucketPolicyStatus</code>\n         permission. For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <p> For more information about when Amazon S3 considers a bucket public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>. </p>\n         <p>The following operations are related to <code>GetBucketPolicyStatus</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutPublicAccessBlock.html\">PutPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">DeletePublicAccessBlock</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Retrieves the policy status for an Amazon S3 bucket, indicating whether the bucket is public.\n         In order to use this operation, you must have the <code>s3:GetBucketPolicyStatus</code>\n         permission. For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <p> For more information about when Amazon S3 considers a bucket public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>. </p>\n         <p>The following operations are related to <code>GetBucketPolicyStatus</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutPublicAccessBlock.html\">PutPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">DeletePublicAccessBlock</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?policyStatus",
@@ -22863,7 +22900,7 @@
         "target": "com.amazonaws.s3#GetBucketReplicationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the replication configuration of a bucket.</p>\n         <note>\n            <p> It can take a while to propagate the put or delete a replication configuration to\n            all Amazon S3 systems. Therefore, a get request soon after put or delete can return a wrong\n            result. </p>\n         </note>\n         <p> For information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>This action requires permissions for the <code>s3:GetReplicationConfiguration</code>\n         action. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies and User\n            Policies</a>.</p>\n         <p>If you include the <code>Filter</code> element in a replication configuration, you must\n         also include the <code>DeleteMarkerReplication</code> and <code>Priority</code> elements.\n         The response also returns those elements.</p>\n         <p>For information about <code>GetBucketReplication</code> errors, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ReplicationErrorCodeList\">List of\n            replication-related error codes</a>\n         </p>\n         <p>The following operations are related to <code>GetBucketReplication</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketReplication.html\">PutBucketReplication</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketReplication.html\">DeleteBucketReplication</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the replication configuration of a bucket.</p>\n         <note>\n            <p> It can take a while to propagate the put or delete a replication configuration to\n            all Amazon S3 systems. Therefore, a get request soon after put or delete can return a wrong\n            result. </p>\n         </note>\n         <p> For information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>This action requires permissions for the <code>s3:GetReplicationConfiguration</code>\n         action. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-iam-policies.html\">Using Bucket Policies and User\n            Policies</a>.</p>\n         <p>If you include the <code>Filter</code> element in a replication configuration, you must\n         also include the <code>DeleteMarkerReplication</code> and <code>Priority</code> elements.\n         The response also returns those elements.</p>\n         <p>For information about <code>GetBucketReplication</code> errors, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ReplicationErrorCodeList\">List of\n            replication-related error codes</a>\n         </p>\n         <p>The following operations are related to <code>GetBucketReplication</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketReplication.html\">PutBucketReplication</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketReplication.html\">DeleteBucketReplication</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get replication configuration set on a bucket",
@@ -22949,7 +22986,7 @@
         "target": "com.amazonaws.s3#GetBucketRequestPaymentOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the request payment configuration of a bucket. To use this version of the\n         operation, you must be the bucket owner. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html\">Requester Pays\n            Buckets</a>.</p>\n         <p>The following operations are related to <code>GetBucketRequestPayment</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html\">ListObjects</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the request payment configuration of a bucket. To use this version of the\n         operation, you must be the bucket owner. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html\">Requester Pays\n            Buckets</a>.</p>\n         <p>The following operations are related to <code>GetBucketRequestPayment</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html\">ListObjects</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get bucket versioning configuration",
@@ -23024,7 +23061,7 @@
         "target": "com.amazonaws.s3#GetBucketTaggingOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the tag set associated with the bucket.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:GetBucketTagging</code> action. By default, the bucket owner has this\n         permission and can grant this permission to others.</p>\n         <p>\n            <code>GetBucketTagging</code> has the following special error:</p>\n         <ul>\n            <li>\n               <p>Error code: <code>NoSuchTagSet</code>\n               </p>\n               <ul>\n                  <li>\n                     <p>Description: There is no tag set associated with the bucket.</p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n         <p>The following operations are related to <code>GetBucketTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketTagging.html\">PutBucketTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketTagging.html\">DeleteBucketTagging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the tag set associated with the bucket.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:GetBucketTagging</code> action. By default, the bucket owner has this\n         permission and can grant this permission to others.</p>\n         <p>\n            <code>GetBucketTagging</code> has the following special error:</p>\n         <ul>\n            <li>\n               <p>Error code: <code>NoSuchTagSet</code>\n               </p>\n               <ul>\n                  <li>\n                     <p>Description: There is no tag set associated with the bucket.</p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n         <p>The following operations are related to <code>GetBucketTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketTagging.html\">PutBucketTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketTagging.html\">DeleteBucketTagging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get tag set associated with a bucket",
@@ -23109,7 +23146,7 @@
         "target": "com.amazonaws.s3#GetBucketVersioningOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the versioning state of a bucket.</p>\n         <p>To retrieve the versioning state of a bucket, you must be the bucket owner.</p>\n         <p>This implementation also returns the MFA Delete status of the versioning state. If the\n         MFA Delete status is <code>enabled</code>, the bucket owner must use an authentication\n         device to change the versioning state of the bucket.</p>\n         <p>The following operations are related to <code>GetBucketVersioning</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the versioning state of a bucket.</p>\n         <p>To retrieve the versioning state of a bucket, you must be the bucket owner.</p>\n         <p>This implementation also returns the MFA Delete status of the versioning state. If the\n         MFA Delete status is <code>enabled</code>, the bucket owner must use an authentication\n         device to change the versioning state of the bucket.</p>\n         <p>The following operations are related to <code>GetBucketVersioning</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get bucket versioning configuration",
@@ -23192,7 +23229,7 @@
         "target": "com.amazonaws.s3#GetBucketWebsiteOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the website configuration for a bucket. To host website on Amazon S3, you can\n         configure a bucket as website by adding a website configuration. For more information about\n         hosting websites, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a>. </p>\n         <p>This GET action requires the <code>S3:GetBucketWebsite</code> permission. By default,\n         only the bucket owner can read the bucket website configuration. However, bucket owners can\n         allow other users to read the website configuration by writing a bucket policy granting\n         them the <code>S3:GetBucketWebsite</code> permission.</p>\n         <p>The following operations are related to <code>GetBucketWebsite</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketWebsite.html\">DeleteBucketWebsite</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketWebsite.html\">PutBucketWebsite</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the website configuration for a bucket. To host website on Amazon S3, you can\n         configure a bucket as website by adding a website configuration. For more information about\n         hosting websites, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a>. </p>\n         <p>This GET action requires the <code>S3:GetBucketWebsite</code> permission. By default,\n         only the bucket owner can read the bucket website configuration. However, bucket owners can\n         allow other users to read the website configuration by writing a bucket policy granting\n         them the <code>S3:GetBucketWebsite</code> permission.</p>\n         <p>The following operations are related to <code>GetBucketWebsite</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketWebsite.html\">DeleteBucketWebsite</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketWebsite.html\">PutBucketWebsite</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get bucket website configuration",
@@ -23302,7 +23339,7 @@
           "requestValidationModeMember": "ChecksumMode",
           "responseAlgorithms": ["CRC32", "CRC32C", "SHA256", "SHA1"]
         },
-        "smithy.api#documentation": "<p>Retrieves an object from Amazon S3.</p>\n         <p>In the <code>GetObject</code> request, specify the full key name for the object.</p>\n         <p>\n            <b>General purpose buckets</b> - Both the virtual-hosted-style requests and the path-style requests are supported. For a virtual hosted-style request example, if you have\n         the object <code>photos/2006/February/sample.jpg</code>, specify the object key name as\n            <code>/photos/2006/February/sample.jpg</code>. For a path-style request example, if you\n         have the object <code>photos/2006/February/sample.jpg</code> in the bucket named\n            <code>examplebucket</code>, specify the object key name as\n            <code>/examplebucket/photos/2006/February/sample.jpg</code>. For more information about\n         request types, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingSpecifyBucket\">HTTP Host\n            Header Bucket Specification</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Directory buckets</b> - Only virtual-hosted-style requests are supported. For a virtual hosted-style request example, if you have the object <code>photos/2006/February/sample.jpg</code> in the bucket named <code>examplebucket--use1-az5--x-s3</code>, specify the object key name as <code>/photos/2006/February/sample.jpg</code>. Also, when you make requests to this API operation, your requests are sent to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n            </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - You must have the required permissions in a policy. To use <code>GetObject</code>, you must have the <code>READ</code>\n                        access to the object (or version). If you grant <code>READ</code> access to the anonymous user, the <code>GetObject</code> operation \n                        returns the object without using an authorization header. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying permissions in\n                           a policy</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     <p>If you include a <code>versionId</code> in your request header, you must have the\n                        <code>s3:GetObjectVersion</code> permission to access a specific\n                        version of an object. The <code>s3:GetObject</code> permission is not required in this scenario.</p>\n                     <p>If you request the\n                        current version of an object without a specific <code>versionId</code> in the request header, only\n                        the <code>s3:GetObject</code> permission is required. The <code>s3:GetObjectVersion</code> permission is not required in this scenario.\n                     </p>\n                     <p>If the object that you request doesn’t exist, the error that\n                        Amazon S3 returns depends on whether you also have the <code>s3:ListBucket</code>\n                        permission.</p>\n                     <ul>\n                        <li>\n                           <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3\n                              returns an HTTP status code <code>404 Not Found</code> error.</p>\n                        </li>\n                        <li>\n                           <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3 returns an\n                              HTTP status code <code>403 Access Denied</code> error.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted using \n                     SSE-KMS, you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Storage classes</dt>\n            <dd>\n               <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the \n                  S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the \n                  S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a\n                  copy using <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a>. Otherwise, this operation returns an\n                  <code>InvalidObjectState</code> error. For information about restoring archived objects,\n                  see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring\n                     Archived Objects</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <p>\n                  <b>Directory buckets </b> - For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects. \nUnsupported storage class values won't write a destination object and will respond with the HTTP status code <code>400 Bad Request</code>.</p>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>, should not\n                  be sent for the <code>GetObject</code> requests, if your object uses server-side encryption with Amazon S3 managed encryption keys (SSE-S3), server-side encryption with Key Management Service (KMS)\n                  keys (SSE-KMS), or dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). If you include the header in your <code>GetObject</code> requests for the object that uses \n                  these types of keys, you’ll get an HTTP <code>400 Bad Request</code> error.</p>\n               <p>\n                  <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Overriding response header values through the request</dt>\n            <dd>\n               <p>There are times when you want to override certain response header values of a\n                     <code>GetObject</code> response. For example, you might override the\n                     <code>Content-Disposition</code> response header value through your <code>GetObject</code>\n                  request.</p>\n               <p>You can override values for a set of response headers. These modified response header values are included only in a successful response, that is, when the HTTP status code <code>200 OK</code> is returned.                   \n                  The headers you can override using the following query parameters in the request are a subset of the headers that Amazon S3 accepts when you create an object.                  \n               </p>\n               <p>The response headers that you can override for the\n                  <code>GetObject</code> response are <code>Cache-Control</code>, <code>Content-Disposition</code>, \n                  <code>Content-Encoding</code>, <code>Content-Language</code>, <code>Content-Type</code>, and <code>Expires</code>.</p>\n               <p>To override values for a set of response headers in the\n                  <code>GetObject</code> response, you can use the following query\n                  parameters in the request.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>response-cache-control</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-disposition</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-encoding</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-language</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-type</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-expires</code>\n                     </p>\n                  </li>\n               </ul>\n               <note>\n                  <p>When you use these parameters, you must sign the request by using either an Authorization header or a\n                     presigned URL. These parameters cannot be used with an\n                     unsigned (anonymous) request.</p>\n               </note>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>GetObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html\">ListBuckets</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAcl.html\">GetObjectAcl</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Retrieves an object from Amazon S3.</p>\n         <p>In the <code>GetObject</code> request, specify the full key name for the object.</p>\n         <p>\n            <b>General purpose buckets</b> - Both the virtual-hosted-style\n         requests and the path-style requests are supported. For a virtual hosted-style request\n         example, if you have the object <code>photos/2006/February/sample.jpg</code>, specify the\n         object key name as <code>/photos/2006/February/sample.jpg</code>. For a path-style request\n         example, if you have the object <code>photos/2006/February/sample.jpg</code> in the bucket\n         named <code>examplebucket</code>, specify the object key name as\n            <code>/examplebucket/photos/2006/February/sample.jpg</code>. For more information about\n         request types, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingSpecifyBucket\">HTTP Host\n            Header Bucket Specification</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Directory buckets</b> -\n         Only virtual-hosted-style requests are supported. For a virtual hosted-style request example, if you have the object <code>photos/2006/February/sample.jpg</code> in the bucket named <code>examplebucket--use1-az5--x-s3</code>, specify the object key name as <code>/photos/2006/February/sample.jpg</code>. Also, when you make requests to this API operation, your requests are sent to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n            </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - You\n                        must have the required permissions in a policy. To use\n                           <code>GetObject</code>, you must have the <code>READ</code> access to the\n                        object (or version). If you grant <code>READ</code> access to the anonymous\n                        user, the <code>GetObject</code> operation returns the object without using\n                        an authorization header. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying permissions in a policy</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                     <p>If you include a <code>versionId</code> in your request header, you must\n                        have the <code>s3:GetObjectVersion</code> permission to access a specific\n                        version of an object. The <code>s3:GetObject</code> permission is not\n                        required in this scenario.</p>\n                     <p>If you request the current version of an object without a specific\n                           <code>versionId</code> in the request header, only the\n                           <code>s3:GetObject</code> permission is required. The\n                           <code>s3:GetObjectVersion</code> permission is not required in this\n                        scenario. </p>\n                     <p>If the object that you request doesn’t exist, the error that Amazon S3 returns\n                        depends on whether you also have the <code>s3:ListBucket</code>\n                        permission.</p>\n                     <ul>\n                        <li>\n                           <p>If you have the <code>s3:ListBucket</code> permission on the\n                              bucket, Amazon S3 returns an HTTP status code <code>404 Not Found</code>\n                              error.</p>\n                        </li>\n                        <li>\n                           <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3\n                              returns an HTTP status code <code>403 Access Denied</code>\n                              error.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If\n                        the\n                        object is encrypted using SSE-KMS, you must also have the\n                           <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions\n                        in IAM identity-based policies and KMS key policies for the KMS\n                        key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Storage classes</dt>\n            <dd>\n               <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval\n                  storage class, the S3 Glacier Deep Archive storage class, the\n                  S3 Intelligent-Tiering Archive Access tier, or the S3 Intelligent-Tiering Deep Archive Access tier,\n                  before you can retrieve the object you must first restore a copy using <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a>. Otherwise, this operation returns an\n                     <code>InvalidObjectState</code> error. For information about restoring archived\n                  objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring Archived\n                     Objects</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <p>\n                  <b>Directory buckets </b> -\n                  For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects. \nUnsupported storage class values won't write a destination object and will respond with the HTTP status code <code>400 Bad Request</code>.</p>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,\n                  should not be sent for the <code>GetObject</code> requests, if your object uses\n                  server-side encryption with Amazon S3 managed encryption keys (SSE-S3), server-side\n                  encryption with Key Management Service (KMS) keys (SSE-KMS), or dual-layer server-side\n                  encryption with Amazon Web Services KMS keys (DSSE-KMS). If you include the header in your\n                     <code>GetObject</code> requests for the object that uses these types of keys,\n                  you’ll get an HTTP <code>400 Bad Request</code> error.</p>\n               <p>\n                  <b>Directory buckets</b> -\n                  For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Overriding response header values through the request</dt>\n            <dd>\n               <p>There are times when you want to override certain response header values of a\n                     <code>GetObject</code> response. For example, you might override the\n                     <code>Content-Disposition</code> response header value through your\n                     <code>GetObject</code> request.</p>\n               <p>You can override values for a set of response headers. These modified response\n                  header values are included only in a successful response, that is, when the HTTP\n                  status code <code>200 OK</code> is returned. The headers you can override using\n                  the following query parameters in the request are a subset of the headers that\n                  Amazon S3 accepts when you create an object. </p>\n               <p>The response headers that you can override for the <code>GetObject</code>\n                  response are <code>Cache-Control</code>, <code>Content-Disposition</code>,\n                     <code>Content-Encoding</code>, <code>Content-Language</code>,\n                     <code>Content-Type</code>, and <code>Expires</code>.</p>\n               <p>To override values for a set of response headers in the <code>GetObject</code>\n                  response, you can use the following query parameters in the request.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>response-cache-control</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-disposition</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-encoding</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-language</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-content-type</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>response-expires</code>\n                     </p>\n                  </li>\n               </ul>\n               <note>\n                  <p>When you use these parameters, you must sign the request by using either an\n                     Authorization header or a presigned URL. These parameters cannot be used with\n                     an unsigned (anonymous) request.</p>\n               </note>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>GetObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html\">ListBuckets</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAcl.html\">GetObjectAcl</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To retrieve a byte range of an object ",
@@ -23363,7 +23400,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the access control list (ACL) of an object. To use this operation, you must have\n            <code>s3:GetObjectAcl</code> permissions or <code>READ_ACP</code> access to the object.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html#acl-access-policy-permission-mapping\">Mapping of ACL permissions and access policy permissions</a> in the <i>Amazon S3\n            User Guide</i>\n         </p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>By default, GET returns ACL information about the current version of an object. To\n         return ACL information about a different version, use the versionId subresource.</p>\n         <note>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership,\n            requests to read ACLs are still supported and return the\n               <code>bucket-owner-full-control</code> ACL with the owner being the account that\n            created the bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\"> Controlling object\n               ownership and disabling ACLs</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>The following operations are related to <code>GetObjectAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the access control list (ACL) of an object. To use this operation, you must have\n            <code>s3:GetObjectAcl</code> permissions or <code>READ_ACP</code> access to the object.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html#acl-access-policy-permission-mapping\">Mapping of ACL permissions and access policy permissions</a> in the <i>Amazon S3\n            User Guide</i>\n         </p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>By default, GET returns ACL information about the current version of an object. To\n         return ACL information about a different version, use the versionId subresource.</p>\n         <note>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership,\n            requests to read ACLs are still supported and return the\n               <code>bucket-owner-full-control</code> ACL with the owner being the account that\n            created the bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\"> Controlling object\n               ownership and disabling ACLs</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>The following operations are related to <code>GetObjectAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To retrieve object ACL",
@@ -23513,7 +23550,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>Retrieves all the metadata from an object without returning the object itself. This\n         operation is useful if you're interested only in an object's metadata. </p>\n         <p>\n            <code>GetObjectAttributes</code> combines the functionality of <code>HeadObject</code>\n         and <code>ListParts</code>. All of the data returned with each of those individual calls\n         can be returned with a single call to <code>GetObjectAttributes</code>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To use\n                        <code>GetObjectAttributes</code>, you must have READ access to the object. The permissions that you need to use this operation depend on whether the\n                        bucket is versioned. If the bucket is versioned, you need both the\n                        <code>s3:GetObjectVersion</code> and <code>s3:GetObjectVersionAttributes</code>\n                        permissions for this operation. If the bucket is not versioned, you need the\n                        <code>s3:GetObject</code> and <code>s3:GetObjectAttributes</code> permissions.\n                        For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in\n                           a Policy</a> in the <i>Amazon S3 User Guide</i>. If the object\n                        that you request does not exist, the error Amazon S3 returns depends on whether you\n                        also have the <code>s3:ListBucket</code> permission.</p>\n                     <ul>\n                        <li>\n                           <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3\n                              returns an HTTP status code <code>404 Not Found</code> (\"no such key\")\n                              error.</p>\n                        </li>\n                        <li>\n                           <p>If you don't have the <code>s3:ListBucket</code> permission, Amazon S3 returns\n                              an HTTP status code <code>403 Forbidden</code> (\"access denied\")\n                              error.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted with\n                     SSE-KMS, you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <note>\n                  <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,\n                  should not be sent for <code>HEAD</code> requests if your object uses server-side\n                  encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer server-side\n                  encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side encryption with Amazon S3\n                  managed encryption keys (SSE-S3). The <code>x-amz-server-side-encryption</code> header is used when you <code>PUT</code> an object to S3 and want to specify the encryption method. \n                  If you include this header in a <code>GET</code> request for an object that uses these types of keys, \n                  you’ll get an HTTP <code>400 Bad Request</code> error. It's because the encryption method can't be changed when you retrieve the object.</p>\n               </note>\n               <p>If you encrypt an object by using server-side encryption with customer-provided\n                  encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the\n                  metadata from the object, you must use the following headers to provide the encryption key for the server to be able to retrieve the object's metadata. The headers are: </p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-algorithm</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key-MD5</code>\n                     </p>\n                  </li>\n               </ul>\n               <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n                  (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3\n                     User Guide</i>.</p>\n               <note>\n                  <p>\n                     <b>Directory bucket permissions</b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n               </note>\n            </dd>\n            <dt>Versioning</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> \n                        to the <code>versionId</code> query parameter in the request.</p>\n            </dd>\n            <dt>Conditional request headers</dt>\n            <dd>\n               <p>Consider the following when using request headers:</p>\n               <ul>\n                  <li>\n                     <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers\n                        are present in the request as follows, then Amazon S3 returns the HTTP status code\n                        <code>200 OK</code> and the data requested:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>If-Match</code> condition evaluates to <code>true</code>.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>If-Unmodified-Since</code> condition evaluates to\n                              <code>false</code>.</p>\n                        </li>\n                     </ul>\n                     <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>\n                  </li>\n                  <li>\n                     <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code>\n                        headers are present in the request as follows, then Amazon S3 returns the HTTP status code\n                        <code>304 Not Modified</code>:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>If-None-Match</code> condition evaluates to <code>false</code>.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>If-Modified-Since</code> condition evaluates to\n                              <code>true</code>.</p>\n                        </li>\n                     </ul>\n                     <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following actions are related to <code>GetObjectAttributes</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAcl.html\">GetObjectAcl</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectLegalHold.html\">GetObjectLegalHold</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectLockConfiguration.html\">GetObjectLockConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectRetention.html\">GetObjectRetention</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html\">HeadObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Retrieves all the metadata from an object without returning the object itself. This\n         operation is useful if you're interested only in an object's metadata. </p>\n         <p>\n            <code>GetObjectAttributes</code> combines the functionality of <code>HeadObject</code>\n         and <code>ListParts</code>. All of the data returned with each of those individual calls\n         can be returned with a single call to <code>GetObjectAttributes</code>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        use <code>GetObjectAttributes</code>, you must have READ access to the\n                        object. The permissions that you need to use this operation depend on\n                        whether the bucket is versioned. If the bucket is versioned, you need both\n                        the <code>s3:GetObjectVersion</code> and\n                           <code>s3:GetObjectVersionAttributes</code> permissions for this\n                        operation. If the bucket is not versioned, you need the\n                           <code>s3:GetObject</code> and <code>s3:GetObjectAttributes</code>\n                        permissions. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying\n                           Permissions in a Policy</a> in the\n                           <i>Amazon S3 User Guide</i>. If the object that you request does\n                        not exist, the error Amazon S3 returns depends on whether you also have the\n                           <code>s3:ListBucket</code> permission.</p>\n                     <ul>\n                        <li>\n                           <p>If you have the <code>s3:ListBucket</code> permission on the\n                              bucket, Amazon S3 returns an HTTP status code <code>404 Not Found</code>\n                              (\"no such key\") error.</p>\n                        </li>\n                        <li>\n                           <p>If you don't have the <code>s3:ListBucket</code> permission, Amazon S3\n                              returns an HTTP status code <code>403 Forbidden</code> (\"access\n                              denied\") error.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If\n                        the\n                        object is encrypted with SSE-KMS, you must also have the\n                           <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions\n                        in IAM identity-based policies and KMS key policies for the KMS\n                        key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <note>\n                  <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,\n                     should not be sent for <code>HEAD</code> requests if your object uses\n                     server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer\n                     server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side\n                     encryption with Amazon S3 managed encryption keys (SSE-S3). The\n                        <code>x-amz-server-side-encryption</code> header is used when you\n                        <code>PUT</code> an object to S3 and want to specify the encryption method.\n                     If you include this header in a <code>GET</code> request for an object that\n                     uses these types of keys, you’ll get an HTTP <code>400 Bad Request</code>\n                     error. It's because the encryption method can't be changed when you retrieve\n                     the object.</p>\n               </note>\n               <p>If you encrypt an object by using server-side encryption with customer-provided\n                  encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve\n                  the metadata from the object, you must use the following headers to provide the\n                  encryption key for the server to be able to retrieve the object's metadata. The\n                  headers are: </p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-algorithm</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key-MD5</code>\n                     </p>\n                  </li>\n               </ul>\n               <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side\n                     Encryption (Using Customer-Provided Encryption Keys)</a> in the\n                     <i>Amazon S3 User Guide</i>.</p>\n               <note>\n                  <p>\n                     <b>Directory bucket permissions</b> -\n                     For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n               </note>\n            </dd>\n            <dt>Versioning</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets</b> -\n                  S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> to the\n                     <code>versionId</code> query parameter in the request.</p>\n            </dd>\n            <dt>Conditional request headers</dt>\n            <dd>\n               <p>Consider the following when using request headers:</p>\n               <ul>\n                  <li>\n                     <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code>\n                        headers are present in the request as follows, then Amazon S3 returns the HTTP\n                        status code <code>200 OK</code> and the data requested:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>If-Match</code> condition evaluates to\n                              <code>true</code>.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>If-Unmodified-Since</code> condition evaluates to\n                                 <code>false</code>.</p>\n                        </li>\n                     </ul>\n                     <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>\n                  </li>\n                  <li>\n                     <p>If both of the <code>If-None-Match</code> and\n                           <code>If-Modified-Since</code> headers are present in the request as\n                        follows, then Amazon S3 returns the HTTP status code <code>304 Not\n                           Modified</code>:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>If-None-Match</code> condition evaluates to\n                                 <code>false</code>.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>If-Modified-Since</code> condition evaluates to\n                                 <code>true</code>.</p>\n                        </li>\n                     </ul>\n                     <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following actions are related to <code>GetObjectAttributes</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAcl.html\">GetObjectAcl</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectLegalHold.html\">GetObjectLegalHold</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectLockConfiguration.html\">GetObjectLockConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectRetention.html\">GetObjectRetention</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html\">HeadObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}/{Key+}?attributes",
@@ -23534,7 +23571,7 @@
         "LastModified": {
           "target": "com.amazonaws.s3#LastModified",
           "traits": {
-            "smithy.api#documentation": "<p>The creation date of the object.</p>",
+            "smithy.api#documentation": "<p>Date and time when the object was last modified.</p>",
             "smithy.api#httpHeader": "Last-Modified"
           }
         },
@@ -23572,7 +23609,7 @@
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>Provides the storage class information of the object. Amazon S3 returns this header for all\n         objects except for S3 Standard storage class objects.</p>\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Provides the storage class information of the object. Amazon S3 returns this header for all\n         objects except for S3 Standard storage class objects.</p>\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
           }
         },
         "ObjectSize": {
@@ -23624,7 +23661,7 @@
         "Parts": {
           "target": "com.amazonaws.s3#PartsList",
           "traits": {
-            "smithy.api#documentation": "<p>A container for elements related to a particular part. A response can contain zero or\n         more <code>Parts</code> elements.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - For <code>GetObjectAttributes</code>, if a additional checksum (including <code>x-amz-checksum-crc32</code>, \n               <code>x-amz-checksum-crc32c</code>, <code>x-amz-checksum-sha1</code>, or \n               <code>x-amz-checksum-sha256</code>) isn't applied to the object specified in the request, the response doesn't return <code>Part</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For <code>GetObjectAttributes</code>, no matter whether a additional checksum is applied to the object specified in the request, the response returns <code>Part</code>.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>A container for elements related to a particular part. A response can contain zero or\n         more <code>Parts</code> elements.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - For\n                     <code>GetObjectAttributes</code>, if a additional checksum (including\n                     <code>x-amz-checksum-crc32</code>, <code>x-amz-checksum-crc32c</code>,\n                     <code>x-amz-checksum-sha1</code>, or <code>x-amz-checksum-sha256</code>) isn't\n                  applied to the object specified in the request, the response doesn't return\n                     <code>Part</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For\n                     <code>GetObjectAttributes</code>, no matter whether a additional checksum is\n                  applied to the object specified in the request, the response returns\n                     <code>Part</code>.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#xmlFlattened": {},
             "smithy.api#xmlName": "Part"
           }
@@ -23640,7 +23677,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the bucket that contains the object.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the bucket that contains the object.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -23659,7 +23696,7 @@
         "VersionId": {
           "target": "com.amazonaws.s3#ObjectVersionId",
           "traits": {
-            "smithy.api#documentation": "<p>The version ID used to reference a specific version of the object.</p>\n         <note>\n            <p>S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> \n         to the <code>versionId</code> query parameter in the request.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The version ID used to reference a specific version of the object.</p>\n         <note>\n            <p>S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> to the\n               <code>versionId</code> query parameter in the request.</p>\n         </note>",
             "smithy.api#httpQuery": "versionId"
           }
         },
@@ -23733,7 +23770,7 @@
         "target": "com.amazonaws.s3#GetObjectLegalHoldOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Gets an object's current legal hold status. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking\n         Objects</a>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>The following action is related to <code>GetObjectLegalHold</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Gets an object's current legal hold status. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking\n         Objects</a>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>The following action is related to <code>GetObjectLegalHold</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}/{Key+}?legal-hold",
@@ -23813,7 +23850,7 @@
         "target": "com.amazonaws.s3#GetObjectLockConfigurationOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock\n         configuration will be applied by default to every new object placed in the specified\n         bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>.</p>\n         <p>The following action is related to <code>GetObjectLockConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock\n         configuration will be applied by default to every new object placed in the specified\n         bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>.</p>\n         <p>The following action is related to <code>GetObjectLockConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?object-lock",
@@ -23876,7 +23913,7 @@
         "DeleteMarker": {
           "target": "com.amazonaws.s3#DeleteMarker",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates whether the object retrieved was (true) or was not (false) a Delete Marker. If\n         false, this response header does not appear in the response.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes <code>x-amz-delete-marker: true</code> in the response.</p>\n               </li>\n               <li>\n                  <p>If the specified version in the request is a delete marker, the response returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified: timestamp</code> response header.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>Indicates whether the object retrieved was (true) or was not (false) a Delete Marker. If\n         false, this response header does not appear in the response.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>If the current version of the object is a delete marker, Amazon S3 behaves as if the\n                  object was deleted and includes <code>x-amz-delete-marker: true</code> in the\n                  response.</p>\n               </li>\n               <li>\n                  <p>If the specified version in the request is a delete marker, the response\n                  returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified:\n                     timestamp</code> response header.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-delete-marker"
           }
         },
@@ -23890,21 +23927,21 @@
         "Expiration": {
           "target": "com.amazonaws.s3#Expiration",
           "traits": {
-            "smithy.api#documentation": "<p>If the object expiration is configured (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">\n               <code>PutBucketLifecycleConfiguration</code>\n            </a>), the response includes\n         this header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value\n         pairs providing object expiration information. The value of the <code>rule-id</code> is\n         URL-encoded.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If the object expiration is configured (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">\n               <code>PutBucketLifecycleConfiguration</code>\n            </a>), the response includes this\n         header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value pairs\n         providing object expiration information. The value of the <code>rule-id</code> is\n         URL-encoded.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-expiration"
           }
         },
         "Restore": {
           "target": "com.amazonaws.s3#Restore",
           "traits": {
-            "smithy.api#documentation": "<p>Provides information about object restoration action and expiration time of the restored\n         object copy.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Provides information about object restoration action and expiration time of the restored\n         object copy.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-restore"
           }
         },
         "LastModified": {
           "target": "com.amazonaws.s3#LastModified",
           "traits": {
-            "smithy.api#documentation": "<p>Date and time when the object was last modified.</p>\n         <p>\n            <b>General purpose buckets </b> - When you specify a <code>versionId</code> of the object in your request, if the specified version in the request is a delete marker, the response returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified: timestamp</code> response header.</p>",
+            "smithy.api#documentation": "<p>Date and time when the object was last modified.</p>\n         <p>\n            <b>General purpose buckets </b> - When you specify a\n            <code>versionId</code> of the object in your request, if the specified version in the\n         request is a delete marker, the response returns a <code>405 Method Not Allowed</code>\n         error and the <code>Last-Modified: timestamp</code> response header.</p>",
             "smithy.api#httpHeader": "Last-Modified"
           }
         },
@@ -23953,7 +23990,7 @@
         "MissingMeta": {
           "target": "com.amazonaws.s3#MissingMeta",
           "traits": {
-            "smithy.api#documentation": "<p>This is set to the number of metadata entries not returned in the headers that are prefixed with <code>x-amz-meta-</code>. This can happen if you create metadata using an API like SOAP that supports more\n         flexible metadata than the REST API. For example, using SOAP, you can create metadata whose\n         values are not legal HTTP headers.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>This is set to the number of metadata entries not returned in the headers that are\n         prefixed with <code>x-amz-meta-</code>. This can happen if you create metadata using an API\n         like SOAP that supports more flexible metadata than the REST API. For example, using SOAP,\n         you can create metadata whose values are not legal HTTP headers.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-missing-meta"
           }
         },
@@ -24044,7 +24081,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification of\n         the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification\n         of the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -24058,14 +24095,14 @@
         "BucketKeyEnabled": {
           "target": "com.amazonaws.s3#BucketKeyEnabled",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates whether the object uses an S3 Bucket Key for server-side encryption\n         with Key Management Service (KMS) keys (SSE-KMS).</p>",
+            "smithy.api#documentation": "<p>Indicates whether the object uses an S3 Bucket Key for server-side encryption with\n         Key Management Service (KMS) keys (SSE-KMS).</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled"
           }
         },
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>Provides storage class information of the object. Amazon S3 returns this header for all\n         objects except for S3 Standard storage class objects.</p>\n         <note>\n            <p>\n               <b>Directory buckets </b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Provides storage class information of the object. Amazon S3 returns this header for all\n         objects except for S3 Standard storage class objects.</p>\n         <note>\n            <p>\n               <b>Directory buckets </b> -\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-storage-class"
           }
         },
@@ -24092,7 +24129,7 @@
         "TagCount": {
           "target": "com.amazonaws.s3#TagCount",
           "traits": {
-            "smithy.api#documentation": "<p>The number of tags, if any, on the object, when you have the relevant permission to read object tags.</p>\n         <p>You can use <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a> to retrieve\n         the tag set associated with an object.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The number of tags, if any, on the object, when you have the relevant permission to read\n         object tags.</p>\n         <p>You can use <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a> to retrieve\n         the tag set associated with an object.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-tagging-count"
           }
         },
@@ -24128,7 +24165,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket name containing the object. </p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Object Lambda access points</b> - When you use this action with an Object Lambda access point, you must direct requests to the Object Lambda access point hostname. The Object Lambda access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-object-lambda.<i>Region</i>.amazonaws.com.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The bucket name containing the object. </p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Object Lambda access points</b> - When you use this action with an Object Lambda access point, you must direct requests to the Object Lambda access point hostname. The Object Lambda access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-object-lambda.<i>Region</i>.amazonaws.com.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -24139,28 +24176,28 @@
         "IfMatch": {
           "target": "com.amazonaws.s3#IfMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is the same as the one specified in this header;\n         otherwise, return a <code>412 Precondition Failed</code> error.</p>\n         <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are present in the request as follows: <code>If-Match</code> condition \n         evaluates to <code>true</code>, and; <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is the same as the one specified in this\n         header; otherwise, return a <code>412 Precondition Failed</code> error.</p>\n         <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are\n         present in the request as follows: <code>If-Match</code> condition evaluates to\n            <code>true</code>, and; <code>If-Unmodified-Since</code> condition evaluates to\n            <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-Match"
           }
         },
         "IfModifiedSince": {
           "target": "com.amazonaws.s3#IfModifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if it has been modified since the specified time; otherwise,\n         return a <code>304 Not Modified</code> error.</p>\n         <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are present in the request as follows:<code> If-None-Match</code> \n         condition evaluates to <code>false</code>, and; <code>If-Modified-Since</code> condition evaluates to <code>true</code>; then, S3 returns <code>304 Not Modified</code> \n                  status code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if it has been modified since the specified time; otherwise,\n         return a <code>304 Not Modified</code> error.</p>\n         <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are\n         present in the request as follows:<code> If-None-Match</code> condition evaluates to\n            <code>false</code>, and; <code>If-Modified-Since</code> condition evaluates to\n            <code>true</code>; then, S3 returns <code>304 Not Modified</code> status code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-Modified-Since"
           }
         },
         "IfNoneMatch": {
           "target": "com.amazonaws.s3#IfNoneMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is different from the one specified in this header;\n         otherwise, return a <code>304 Not Modified</code> error.</p>\n         <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> \n         headers are present in the request as follows:<code> If-None-Match</code> \n         condition evaluates to <code>false</code>, and; <code>If-Modified-Since</code> \n         condition evaluates to <code>true</code>; then, S3 returns <code>304 Not Modified</code> HTTP status code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is different from the one specified in\n         this header; otherwise, return a <code>304 Not Modified</code> error.</p>\n         <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are\n         present in the request as follows:<code> If-None-Match</code> condition evaluates to\n            <code>false</code>, and; <code>If-Modified-Since</code> condition evaluates to\n            <code>true</code>; then, S3 returns <code>304 Not Modified</code> HTTP status\n         code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-None-Match"
           }
         },
         "IfUnmodifiedSince": {
           "target": "com.amazonaws.s3#IfUnmodifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if it has not been modified since the specified time; otherwise,\n         return a <code>412 Precondition Failed</code> error.</p>\n         <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code>\n                  headers are present in the request as follows: <code>If-Match</code> condition\n                  evaluates to <code>true</code>, and; <code>If-Unmodified-Since</code> condition\n                  evaluates to <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if it has not been modified since the specified time; otherwise,\n         return a <code>412 Precondition Failed</code> error.</p>\n         <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are\n         present in the request as follows: <code>If-Match</code> condition evaluates to\n            <code>true</code>, and; <code>If-Unmodified-Since</code> condition evaluates to\n            <code>false</code>; then, S3 returns <code>200 OK</code> and the data requested. </p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-Unmodified-Since"
           }
         },
@@ -24227,28 +24264,28 @@
         "VersionId": {
           "target": "com.amazonaws.s3#ObjectVersionId",
           "traits": {
-            "smithy.api#documentation": "<p>Version ID used to reference a specific version of the object.</p>\n         <p>By default, the <code>GetObject</code> operation returns the current version of an object. To return a different version, use the <code>versionId</code> subresource.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>If you include a <code>versionId</code> in your request header, you must have the <code>s3:GetObjectVersion</code> permission to access a specific version of an object. The <code>s3:GetObject</code> permission is not required in this scenario.</p>\n               </li>\n               <li>\n                  <p>If you request the current version of an object without a specific <code>versionId</code> in the request header, only the <code>s3:GetObject</code> permission is required. The <code>s3:GetObjectVersion</code> permission is not required in this scenario.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> \n                  to the <code>versionId</code> query parameter in the request.</p>\n               </li>\n            </ul>\n         </note>\n         <p>For more information about versioning, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketVersioning.html\">PutBucketVersioning</a>.</p>",
+            "smithy.api#documentation": "<p>Version ID used to reference a specific version of the object.</p>\n         <p>By default, the <code>GetObject</code> operation returns the current version of an\n         object. To return a different version, use the <code>versionId</code> subresource.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>If you include a <code>versionId</code> in your request header, you must have\n                  the <code>s3:GetObjectVersion</code> permission to access a specific version of an\n                  object. The <code>s3:GetObject</code> permission is not required in this\n                  scenario.</p>\n               </li>\n               <li>\n                  <p>If you request the current version of an object without a specific\n                     <code>versionId</code> in the request header, only the\n                     <code>s3:GetObject</code> permission is required. The\n                     <code>s3:GetObjectVersion</code> permission is not required in this\n                  scenario.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> to the\n                     <code>versionId</code> query parameter in the request.</p>\n               </li>\n            </ul>\n         </note>\n         <p>For more information about versioning, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketVersioning.html\">PutBucketVersioning</a>.</p>",
             "smithy.api#httpQuery": "versionId"
           }
         },
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when decrypting the object (for example,\n         <code>AES256</code>).</p>\n         <p>If you encrypt an object by using server-side encryption with customer-provided\n         encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,\n         you must use the following headers:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-algorithm</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key-MD5</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n         (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when decrypting the object (for example,\n            <code>AES256</code>).</p>\n         <p>If you encrypt an object by using server-side encryption with customer-provided\n         encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,\n         you must use the following headers:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-algorithm</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key-MD5</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n            (Using Customer-Provided Encryption Keys)</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
         "SSECustomerKey": {
           "target": "com.amazonaws.s3#SSECustomerKey",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the customer-provided encryption key that you originally provided for Amazon S3 to encrypt the data before storing it. This\n         value is used to decrypt the object when recovering it and must match the one used when\n         storing the data. The key must be appropriate for use with the algorithm specified in the\n            <code>x-amz-server-side-encryption-customer-algorithm</code> header.</p>\n         <p>If you encrypt an object by using server-side encryption with customer-provided\n         encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,\n         you must use the following headers:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-algorithm</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key-MD5</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n         (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the customer-provided encryption key that you originally provided for Amazon S3 to\n         encrypt the data before storing it. This value is used to decrypt the object when\n         recovering it and must match the one used when storing the data. The key must be\n         appropriate for use with the algorithm specified in the\n            <code>x-amz-server-side-encryption-customer-algorithm</code> header.</p>\n         <p>If you encrypt an object by using server-side encryption with customer-provided\n         encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,\n         you must use the following headers:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-algorithm</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key-MD5</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n            (Using Customer-Provided Encryption Keys)</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key"
           }
         },
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to RFC 1321. Amazon S3 uses\n         this header for a message integrity check to ensure that the encryption key was transmitted\n         without error.</p>\n         <p>If you encrypt an object by using server-side encryption with customer-provided\n         encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,\n         you must use the following headers:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-algorithm</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key-MD5</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n         (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the 128-bit MD5 digest of the customer-provided encryption key according to\n         RFC 1321. Amazon S3 uses this header for a message integrity check to ensure that the encryption\n         key was transmitted without error.</p>\n         <p>If you encrypt an object by using server-side encryption with customer-provided\n         encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object,\n         you must use the following headers:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-algorithm</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>x-amz-server-side-encryption-customer-key-MD5</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n            (Using Customer-Provided Encryption Keys)</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -24275,7 +24312,7 @@
         "ChecksumMode": {
           "target": "com.amazonaws.s3#ChecksumMode",
           "traits": {
-            "smithy.api#documentation": "<p>To retrieve the checksum, this mode must be enabled.</p>\n         <p>\n            <b>General purpose buckets</b> - In addition, if you enable checksum mode and the object is uploaded with a \n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html\">checksum</a> \n         and encrypted with an Key Management Service (KMS) key, you must have permission to use the \n         <code>kms:Decrypt</code> action to retrieve the checksum.</p>",
+            "smithy.api#documentation": "<p>To retrieve the checksum, this mode must be enabled.</p>\n         <p>\n            <b>General purpose buckets</b> - In addition, if you enable\n         checksum mode and the object is uploaded with a <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html\">checksum</a> and encrypted with an\n         Key Management Service (KMS) key, you must have permission to use the <code>kms:Decrypt</code> action\n         to retrieve the checksum.</p>",
             "smithy.api#httpHeader": "x-amz-checksum-mode"
           }
         }
@@ -24296,7 +24333,7 @@
         "target": "com.amazonaws.s3#GetObjectRetentionOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Retrieves an object's retention settings. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking\n         Objects</a>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>The following action is related to <code>GetObjectRetention</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Retrieves an object's retention settings. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking\n         Objects</a>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>The following action is related to <code>GetObjectRetention</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}/{Key+}?retention",
@@ -24376,7 +24413,7 @@
         "target": "com.amazonaws.s3#GetObjectTaggingOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns the tag-set of an object. You send the GET request against the tagging\n         subresource associated with the object.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:GetObjectTagging</code> action. By default, the GET action returns information\n         about current version of an object. For a versioned bucket, you can have multiple versions\n         of an object in your bucket. To retrieve tags of any other version, use the versionId query\n         parameter. You also need permission for the <code>s3:GetObjectVersionTagging</code>\n         action.</p>\n         <p> By default, the bucket owner has this permission and can grant this permission to\n         others.</p>\n         <p> For information about the Amazon S3 object tagging feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\">Object Tagging</a>.</p>\n         <p>The following actions are related to <code>GetObjectTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjectTagging.html\">DeleteObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjectTagging.html\">PutObjectTagging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns the tag-set of an object. You send the GET request against the tagging\n         subresource associated with the object.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:GetObjectTagging</code> action. By default, the GET action returns information\n         about current version of an object. For a versioned bucket, you can have multiple versions\n         of an object in your bucket. To retrieve tags of any other version, use the versionId query\n         parameter. You also need permission for the <code>s3:GetObjectVersionTagging</code>\n         action.</p>\n         <p> By default, the bucket owner has this permission and can grant this permission to\n         others.</p>\n         <p> For information about the Amazon S3 object tagging feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-tagging.html\">Object Tagging</a>.</p>\n         <p>The following actions are related to <code>GetObjectTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjectTagging.html\">DeleteObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObjectTagging.html\">PutObjectTagging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To retrieve tag set of a specific object version",
@@ -24504,7 +24541,7 @@
         "target": "com.amazonaws.s3#GetObjectTorrentOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns torrent files from a bucket. BitTorrent can save you bandwidth when you're\n         distributing large files.</p>\n         <note>\n            <p>You can get torrent only for objects that are less than 5 GB in size, and that are\n            not encrypted using server-side encryption with a customer-provided encryption\n            key.</p>\n         </note>\n         <p>To use GET, you must have READ access to the object.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>The following action is related to <code>GetObjectTorrent</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns torrent files from a bucket. BitTorrent can save you bandwidth when you're\n         distributing large files.</p>\n         <note>\n            <p>You can get torrent only for objects that are less than 5 GB in size, and that are\n            not encrypted using server-side encryption with a customer-provided encryption\n            key.</p>\n         </note>\n         <p>To use GET, you must have READ access to the object.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>The following action is related to <code>GetObjectTorrent</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To retrieve torrent files for an object",
@@ -24594,7 +24631,7 @@
         "target": "com.amazonaws.s3#GetPublicAccessBlockOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Retrieves the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use\n         this operation, you must have the <code>s3:GetBucketPublicAccessBlock</code> permission.\n         For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <important>\n            <p>When Amazon S3 evaluates the <code>PublicAccessBlock</code> configuration for a bucket or\n            an object, it checks the <code>PublicAccessBlock</code> configuration for both the\n            bucket (or the bucket that contains the object) and the bucket owner's account. If the\n               <code>PublicAccessBlock</code> settings are different between the bucket and the\n            account, Amazon S3 uses the most restrictive combination of the bucket-level and\n            account-level settings.</p>\n         </important>\n         <p>For more information about when Amazon S3 considers a bucket or an object public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>.</p>\n         <p>The following operations are related to <code>GetPublicAccessBlock</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutPublicAccessBlock.html\">PutPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">DeletePublicAccessBlock</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Retrieves the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket. To use\n         this operation, you must have the <code>s3:GetBucketPublicAccessBlock</code> permission.\n         For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <important>\n            <p>When Amazon S3 evaluates the <code>PublicAccessBlock</code> configuration for a bucket or\n            an object, it checks the <code>PublicAccessBlock</code> configuration for both the\n            bucket (or the bucket that contains the object) and the bucket owner's account. If the\n               <code>PublicAccessBlock</code> settings are different between the bucket and the\n            account, Amazon S3 uses the most restrictive combination of the bucket-level and\n            account-level settings.</p>\n         </important>\n         <p>For more information about when Amazon S3 considers a bucket or an object public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>.</p>\n         <p>The following operations are related to <code>GetPublicAccessBlock</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutPublicAccessBlock.html\">PutPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">DeletePublicAccessBlock</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?publicAccessBlock",
@@ -24766,7 +24803,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>You can use this operation to determine if a bucket exists and if you have permission to access it. The action returns a <code>200 OK</code> if the bucket exists and you have permission\n         to access it.</p>\n         <note>\n            <p>If the bucket does not exist or you do not have permission to access it, the\n            <code>HEAD</code> request returns a generic <code>400 Bad Request</code>, <code>403\n            Forbidden</code> or <code>404 Not Found</code> code. A message body is not included, so\n         you cannot determine the exception beyond these HTTP response codes.</p>\n         </note>\n         <dl>\n            <dt>Authentication and authorization</dt>\n            <dd>\n               <p>\n                  <b>General purpose buckets</b> - Request to public buckets that grant the s3:ListBucket permission publicly do not need to be signed. All other <code>HeadBucket</code> requests must be authenticated and signed by using IAM credentials (access key ID and secret access key for the IAM identities). All headers with the <code>x-amz-</code> prefix, including\n                        <code>x-amz-copy-source</code>, must be signed. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n               <p>\n                  <b>Directory buckets</b> - You must use IAM credentials to authenticate and authorize your access to the <code>HeadBucket</code> API operation, instead of using the \n                  temporary security credentials through the <code>CreateSession</code> API operation.</p>\n               <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p></p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To use this operation, you must have permissions to perform the\n                        <code>s3:ListBucket</code> action. The bucket owner has this permission by default and\n                        can grant this permission to others. For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing\n                           access permissions to your Amazon S3 resources</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have the <b>\n                           <code>s3express:CreateSession</code>\n                        </b> permission in the\n                           <code>Action</code> element of a policy. By default, the session is in the <code>ReadWrite</code> mode. If you want to restrict the access, you can explicitly set the <code>s3express:SessionMode</code> condition key to <code>ReadOnly</code> on the bucket.</p>\n                     <p>For more information about example bucket policies, 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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n               <note>\n                  <p>You must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </note>\n            </dd>\n         </dl>",
+        "smithy.api#documentation": "<p>You can use this operation to determine if a bucket exists and if you have permission to\n         access it. The action returns a <code>200 OK</code> if the bucket exists and you have\n         permission to access it.</p>\n         <note>\n            <p>If the bucket does not exist or you do not have permission to access it, the\n               <code>HEAD</code> request returns a generic <code>400 Bad Request</code>, <code>403\n               Forbidden</code> or <code>404 Not Found</code> code. A message body is not included,\n            so you cannot determine the exception beyond these HTTP response codes.</p>\n         </note>\n         <dl>\n            <dt>Authentication and authorization</dt>\n            <dd>\n               <p>\n                  <b>General purpose buckets</b> - Request to public\n                  buckets that grant the s3:ListBucket permission publicly do not need to be signed.\n                  All other <code>HeadBucket</code> requests must be authenticated and signed by\n                  using IAM credentials (access key ID and secret access key for the IAM\n                  identities). All headers with the <code>x-amz-</code> prefix, including\n                     <code>x-amz-copy-source</code>, must be signed. For more information, see\n                     <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n               <p>\n                  <b>Directory buckets</b> - You must use IAM\n                  credentials to authenticate and authorize your access to the\n                     <code>HeadBucket</code> API operation, instead of using the temporary security\n                  credentials through the <code>CreateSession</code> API operation.</p>\n               <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your\n                  behalf.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p></p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        use this operation, you must have permissions to perform the\n                           <code>s3:ListBucket</code> action. The bucket owner has this permission\n                        by default and can grant this permission to others. For more information\n                        about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing access\n                           permissions to your Amazon S3 resources</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have the <b>\n                           <code>s3express:CreateSession</code>\n                        </b> permission in the\n                           <code>Action</code> element of a policy. By default, the session is in\n                        the <code>ReadWrite</code> mode. If you want to restrict the access, you can\n                        explicitly set the <code>s3express:SessionMode</code> condition key to\n                           <code>ReadOnly</code> on the bucket.</p>\n                     <p>For more information about example bucket policies, 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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for\n                           S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n               <note>\n                  <p>You must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </note>\n            </dd>\n         </dl>",
         "smithy.api#examples": [
           {
             "title": "To determine if bucket exists",
@@ -24826,7 +24863,7 @@
         "BucketLocationName": {
           "target": "com.amazonaws.s3#BucketLocationName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the location where the bucket will be created.</p>\n         <p>For directory buckets, the AZ ID of the Availability Zone where the bucket is created. An example AZ ID value is <code>usw2-az1</code>.</p>\n         <note>\n            <p>This functionality is only supported by directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The name of the location where the bucket will be created.</p>\n         <p>For directory buckets, the AZ ID of the Availability Zone where the bucket is created. An example\n         AZ ID value is <code>usw2-az1</code>.</p>\n         <note>\n            <p>This functionality is only supported by directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-bucket-location-name"
           }
         },
@@ -24855,7 +24892,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket name.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Object Lambda access points</b> - When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The bucket name.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Object Lambda access points</b> - When you use this API operation with an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. \nIf the Object Lambda access point alias in a request is not valid, the error code <code>InvalidAccessPointAliasError</code> is returned. \nFor more information about <code>InvalidAccessPointAliasError</code>, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ErrorCodeList\">List of\n            Error Codes</a>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -24889,7 +24926,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>The <code>HEAD</code> operation retrieves metadata from an object without returning the\n         object itself. This operation is useful if you're interested only in an object's metadata.</p>\n         <note>\n            <p>A <code>HEAD</code> request has the same options as a <code>GET</code> operation on an\n         object. The response is identical to the <code>GET</code> response except that there is no\n         response body. Because of this, if the <code>HEAD</code> request generates an error, it\n         returns a generic code, such as <code>400 Bad Request</code>, <code>403 Forbidden</code>, <code>404 Not\n            Found</code>, <code>405 Method Not Allowed</code>, <code>412 Precondition Failed</code>, or <code>304 Not Modified</code>. \n         It's not possible to retrieve the exact exception of these error codes.</p>\n         </note>\n         <p>Request headers are limited to 8 KB in size. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonRequestHeaders.html\">Common\n         Request Headers</a>.</p>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p></p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        use <code>HEAD</code>, you must have the <code>s3:GetObject</code> permission. You need the relevant read object (or version) permission for this operation.\n                        For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/list_amazons3.html\">Actions, resources, and condition\n                           keys for Amazon S3</a> in the <i>Amazon S3\n                              User Guide</i>. For more information about the permissions to S3 API operations by S3 resource types, see <a href=\"/AmazonS3/latest/userguide/using-with-s3-policy-actions.html\">Required permissions for Amazon S3 API operations</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     <p>If the object you request doesn't exist, the error that\n                        Amazon S3 returns depends on whether you also have the <code>s3:ListBucket</code> permission.</p>\n                     <ul>\n                        <li>\n                           <p>If you have the <code>s3:ListBucket</code> permission on the bucket, Amazon S3\n                              returns an HTTP status code <code>404 Not Found</code> error.</p>\n                        </li>\n                        <li>\n                           <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3 returns\n                              an HTTP status code <code>403 Forbidden</code> error.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If you enable <code>x-amz-checksum-mode</code> in the request and the object is encrypted with\n                        Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key to retrieve the checksum of the object.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <note>\n                  <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,\n                  should not be sent for <code>HEAD</code> requests if your object uses server-side\n                  encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer server-side\n                  encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side encryption with Amazon S3\n                  managed encryption keys (SSE-S3). The <code>x-amz-server-side-encryption</code> header is used when you <code>PUT</code> an object to S3 and want to specify the encryption method. \n                  If you include this header in a <code>HEAD</code> request for an object that uses these types of keys, \n                  you’ll get an HTTP <code>400 Bad Request</code> error. It's because the encryption method can't be changed when you retrieve the object.</p>\n               </note>\n               <p>If you encrypt an object by using server-side encryption with customer-provided\n               encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the\n               metadata from the object, you must use the following headers to provide the encryption key for the server to be able to retrieve the object's metadata. The headers are: </p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-algorithm</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key-MD5</code>\n                     </p>\n                  </li>\n               </ul>\n               <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption\n               (Using Customer-Provided Encryption Keys)</a> in the <i>Amazon S3\n                  User Guide</i>.</p>\n               <note>\n                  <p>\n                     <b>Directory bucket </b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. </p>\n               </note>\n            </dd>\n            <dt>Versioning</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes <code>x-amz-delete-marker: true</code> in the response.</p>\n                  </li>\n                  <li>\n                     <p>If the specified version is a delete marker, the response returns a <code>405 Method Not Allowed</code> error and the <code>Last-Modified: timestamp</code> response header.</p>\n                  </li>\n               </ul>\n               <note>\n                  <ul>\n                     <li>\n                        <p>\n                           <b>Directory buckets</b> - Delete marker is not supported by directory buckets.</p>\n                     </li>\n                     <li>\n                        <p>\n                           <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code> \n                        to the <code>versionId</code> query parameter in the request.</p>\n                     </li>\n                  </ul>\n               </note>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n               <note>\n                  <p>For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </note>\n            </dd>\n         </dl>\n         <p>The following actions are related to <code>HeadObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>The <code>HEAD</code> operation retrieves metadata from an object without returning the\n         object itself. This operation is useful if you're interested only in an object's\n         metadata.</p>\n         <note>\n            <p>A <code>HEAD</code> request has the same options as a <code>GET</code> operation on\n            an object. The response is identical to the <code>GET</code> response except that there\n            is no response body. Because of this, if the <code>HEAD</code> request generates an\n            error, it returns a generic code, such as <code>400 Bad Request</code>, <code>403\n               Forbidden</code>, <code>404 Not Found</code>, <code>405 Method Not Allowed</code>,\n               <code>412 Precondition Failed</code>, or <code>304 Not Modified</code>. It's not\n            possible to retrieve the exact exception of these error codes.</p>\n         </note>\n         <p>Request headers are limited to 8 KB in size. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTCommonRequestHeaders.html\">Common\n            Request Headers</a>.</p>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p></p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        use <code>HEAD</code>, you must have the <code>s3:GetObject</code>\n                        permission. You need the relevant read object (or version) permission for\n                        this operation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/list_amazons3.html\">Actions, resources, and\n                           condition keys for Amazon S3</a> in the <i>Amazon S3 User\n                           Guide</i>. For more information about the permissions to S3 API\n                        operations by S3 resource types, see <a href=\"/AmazonS3/latest/userguide/using-with-s3-policy-actions.html\">Required permissions for Amazon S3 API operations</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                     <p>If the object you request doesn't exist, the error that Amazon S3 returns\n                        depends on whether you also have the <code>s3:ListBucket</code>\n                        permission.</p>\n                     <ul>\n                        <li>\n                           <p>If you have the <code>s3:ListBucket</code> permission on the\n                              bucket, Amazon S3 returns an HTTP status code <code>404 Not Found</code>\n                              error.</p>\n                        </li>\n                        <li>\n                           <p>If you don’t have the <code>s3:ListBucket</code> permission, Amazon S3\n                              returns an HTTP status code <code>403 Forbidden</code> error.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If you enable <code>x-amz-checksum-mode</code> in the request and the\n                        object is encrypted with Amazon Web Services Key Management Service (Amazon Web Services KMS), you must\n                        also have the <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code>\n                        permissions in IAM identity-based policies and KMS key policies for the\n                        KMS key to retrieve the checksum of the object.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <note>\n                  <p>Encryption request headers, like <code>x-amz-server-side-encryption</code>,\n                     should not be sent for <code>HEAD</code> requests if your object uses\n                     server-side encryption with Key Management Service (KMS) keys (SSE-KMS), dual-layer\n                     server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), or server-side\n                     encryption with Amazon S3 managed encryption keys (SSE-S3). The\n                        <code>x-amz-server-side-encryption</code> header is used when you\n                        <code>PUT</code> an object to S3 and want to specify the encryption method.\n                     If you include this header in a <code>HEAD</code> request for an object that\n                     uses these types of keys, you’ll get an HTTP <code>400 Bad Request</code>\n                     error. It's because the encryption method can't be changed when you retrieve\n                     the object.</p>\n               </note>\n               <p>If you encrypt an object by using server-side encryption with customer-provided\n                  encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve\n                  the metadata from the object, you must use the following headers to provide the\n                  encryption key for the server to be able to retrieve the object's metadata. The\n                  headers are: </p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-algorithm</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>x-amz-server-side-encryption-customer-key-MD5</code>\n                     </p>\n                  </li>\n               </ul>\n               <p>For more information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side\n                     Encryption (Using Customer-Provided Encryption Keys)</a> in the\n                     <i>Amazon S3 User Guide</i>.</p>\n               <note>\n                  <p>\n                     <b>Directory bucket </b> -\n                     For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS. SSE-C isn't supported. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. </p>\n               </note>\n            </dd>\n            <dt>Versioning</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>If the current version of the object is a delete marker, Amazon S3 behaves as\n                        if the object was deleted and includes <code>x-amz-delete-marker:\n                           true</code> in the response.</p>\n                  </li>\n                  <li>\n                     <p>If the specified version is a delete marker, the response returns a\n                           <code>405 Method Not Allowed</code> error and the <code>Last-Modified:\n                           timestamp</code> response header.</p>\n                  </li>\n               </ul>\n               <note>\n                  <ul>\n                     <li>\n                        <p>\n                           <b>Directory buckets</b> -\n                           Delete marker is not supported for directory buckets.</p>\n                     </li>\n                     <li>\n                        <p>\n                           <b>Directory buckets</b> -\n                           S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the <code>null</code> value of the version ID is supported by directory buckets. You can only specify <code>null</code>\n                           to the <code>versionId</code> query parameter in the request.</p>\n                     </li>\n                  </ul>\n               </note>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n               <note>\n                  <p>For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </note>\n            </dd>\n         </dl>\n         <p>The following actions are related to <code>HeadObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To retrieve metadata of an object without returning the object itself",
@@ -24966,14 +25003,14 @@
         "Expiration": {
           "target": "com.amazonaws.s3#Expiration",
           "traits": {
-            "smithy.api#documentation": "<p>If the object expiration is configured (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">\n               <code>PutBucketLifecycleConfiguration</code>\n            </a>), the response includes\n         this header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value\n         pairs providing object expiration information. The value of the <code>rule-id</code> is\n         URL-encoded.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If the object expiration is configured (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">\n               <code>PutBucketLifecycleConfiguration</code>\n            </a>), the response includes this\n         header. It includes the <code>expiry-date</code> and <code>rule-id</code> key-value pairs\n         providing object expiration information. The value of the <code>rule-id</code> is\n         URL-encoded.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-expiration"
           }
         },
         "Restore": {
           "target": "com.amazonaws.s3#Restore",
           "traits": {
-            "smithy.api#documentation": "<p>If the object is an archived object (an object whose storage class is GLACIER), the\n         response includes this header if either the archive restoration is in progress (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a> or an archive copy is already restored.</p>\n         <p> If an archive copy is already restored, the header value indicates when Amazon S3 is\n         scheduled to delete the object copy. For example:</p>\n         <p>\n            <code>x-amz-restore: ongoing-request=\"false\", expiry-date=\"Fri, 21 Dec 2012 00:00:00\n            GMT\"</code>\n         </p>\n         <p>If the object restoration is in progress, the header returns the value\n            <code>ongoing-request=\"true\"</code>.</p>\n         <p>For more information about archiving objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html#lifecycle-transition-general-considerations\">Transitioning Objects: General Considerations</a>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If the object is an archived object (an object whose storage class is GLACIER), the\n         response includes this header if either the archive restoration is in progress (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a> or an archive copy is already restored.</p>\n         <p> If an archive copy is already restored, the header value indicates when Amazon S3 is\n         scheduled to delete the object copy. For example:</p>\n         <p>\n            <code>x-amz-restore: ongoing-request=\"false\", expiry-date=\"Fri, 21 Dec 2012 00:00:00\n            GMT\"</code>\n         </p>\n         <p>If the object restoration is in progress, the header returns the value\n            <code>ongoing-request=\"true\"</code>.</p>\n         <p>For more information about archiving objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html#lifecycle-transition-general-considerations\">Transitioning Objects: General Considerations</a>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-restore"
           }
         },
@@ -25099,7 +25136,7 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,\n            <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for\n         example, <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
@@ -25120,7 +25157,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification of\n         the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification\n         of the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -25134,14 +25171,14 @@
         "BucketKeyEnabled": {
           "target": "com.amazonaws.s3#BucketKeyEnabled",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates whether the object uses an S3 Bucket Key for server-side encryption\n         with Key Management Service (KMS) keys (SSE-KMS).</p>",
+            "smithy.api#documentation": "<p>Indicates whether the object uses an S3 Bucket Key for server-side encryption with\n         Key Management Service (KMS) keys (SSE-KMS).</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled"
           }
         },
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>Provides storage class information of the object. Amazon S3 returns this header for all\n         objects except for S3 Standard storage class objects.</p>\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a>.</p>\n         <note>\n            <p>\n               <b>Directory buckets </b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Provides storage class information of the object. Amazon S3 returns this header for all\n         objects except for S3 Standard storage class objects.</p>\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a>.</p>\n         <note>\n            <p>\n               <b>Directory buckets </b> -\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-storage-class"
           }
         },
@@ -25197,7 +25234,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the bucket that contains the object.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the bucket that contains the object.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -25208,28 +25245,28 @@
         "IfMatch": {
           "target": "com.amazonaws.s3#IfMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is the same as the one specified;\n         otherwise, return a 412 (precondition failed) error.</p>\n         <p>If both of the <code>If-Match</code> and\n         <code>If-Unmodified-Since</code> headers are present in the request as\n         follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-Match</code> condition evaluates to <code>true</code>, and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Unmodified-Since</code> condition evaluates to\n               <code>false</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns <code>200 OK</code> and the data requested.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is the same as the one specified;\n         otherwise, return a 412 (precondition failed) error.</p>\n         <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are\n         present in the request as follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-Match</code> condition evaluates to <code>true</code>, and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns <code>200 OK</code> and the data requested.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-Match"
           }
         },
         "IfModifiedSince": {
           "target": "com.amazonaws.s3#IfModifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if it has been modified since the specified time; otherwise,\n         return a 304 (not modified) error.</p>\n         <p>If both of the <code>If-None-Match</code> and\n         <code>If-Modified-Since</code> headers are present in the request as\n         follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-None-Match</code> condition evaluates to <code>false</code>,\n               and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Modified-Since</code> condition evaluates to\n               <code>true</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns the <code>304 Not Modified</code> response code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if it has been modified since the specified time; otherwise,\n         return a 304 (not modified) error.</p>\n         <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are\n         present in the request as follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-None-Match</code> condition evaluates to <code>false</code>, and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Modified-Since</code> condition evaluates to <code>true</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns the <code>304 Not Modified</code> response code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-Modified-Since"
           }
         },
         "IfNoneMatch": {
           "target": "com.amazonaws.s3#IfNoneMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is different from the one specified;\n         otherwise, return a 304 (not modified) error.</p>\n         <p>If both of the <code>If-None-Match</code> and\n         <code>If-Modified-Since</code> headers are present in the request as\n         follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-None-Match</code> condition evaluates to <code>false</code>,\n               and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Modified-Since</code> condition evaluates to\n               <code>true</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns the <code>304 Not Modified</code> response code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if its entity tag (ETag) is different from the one specified;\n         otherwise, return a 304 (not modified) error.</p>\n         <p>If both of the <code>If-None-Match</code> and <code>If-Modified-Since</code> headers are\n         present in the request as follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-None-Match</code> condition evaluates to <code>false</code>, and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Modified-Since</code> condition evaluates to <code>true</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns the <code>304 Not Modified</code> response code.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-None-Match"
           }
         },
         "IfUnmodifiedSince": {
           "target": "com.amazonaws.s3#IfUnmodifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Return the object only if it has not been modified since the specified time; otherwise,\n         return a 412 (precondition failed) error.</p>\n         <p>If both of the <code>If-Match</code> and\n         <code>If-Unmodified-Since</code> headers are present in the request as\n         follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-Match</code> condition evaluates to <code>true</code>, and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Unmodified-Since</code> condition evaluates to\n               <code>false</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns <code>200 OK</code> and the data requested.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
+            "smithy.api#documentation": "<p>Return the object only if it has not been modified since the specified time; otherwise,\n         return a 412 (precondition failed) error.</p>\n         <p>If both of the <code>If-Match</code> and <code>If-Unmodified-Since</code> headers are\n         present in the request as follows:</p>\n         <ul>\n            <li>\n               <p>\n                  <code>If-Match</code> condition evaluates to <code>true</code>, and;</p>\n            </li>\n            <li>\n               <p>\n                  <code>If-Unmodified-Since</code> condition evaluates to <code>false</code>;</p>\n            </li>\n         </ul>\n         <p>Then Amazon S3 returns <code>200 OK</code> and the data requested.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>.</p>",
             "smithy.api#httpHeader": "If-Unmodified-Since"
           }
         },
@@ -25303,7 +25340,7 @@
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n         AES256).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
@@ -25344,7 +25381,7 @@
         "ChecksumMode": {
           "target": "com.amazonaws.s3#ChecksumMode",
           "traits": {
-            "smithy.api#documentation": "<p>To retrieve the checksum, this parameter must be enabled.</p>\n         <p>\n            <b>General purpose buckets</b> - If you enable checksum mode and the object is uploaded with a \n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html\">checksum</a> \n         and encrypted with an Key Management Service (KMS) key, you must have permission to use the \n         <code>kms:Decrypt</code> action to retrieve the checksum.</p>\n         <p>\n            <b>Directory buckets</b> - If you enable <code>ChecksumMode</code> and the object is encrypted with\n         Amazon Web Services Key Management Service (Amazon Web Services KMS), you must also have the\n         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key to retrieve the checksum of the object.</p>",
+            "smithy.api#documentation": "<p>To retrieve the checksum, this parameter must be enabled.</p>\n         <p>\n            <b>General purpose buckets</b> -\n         If you enable checksum mode and the object is uploaded with a\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_Checksum.html\">checksum</a>\n         and encrypted with an Key Management Service (KMS) key, you must have permission to use the\n            <code>kms:Decrypt</code> action to retrieve the checksum.</p>\n         <p>\n            <b>Directory buckets</b> - If you enable\n            <code>ChecksumMode</code> and the object is encrypted with Amazon Web Services Key Management Service\n         (Amazon Web Services KMS), you must also have the <code>kms:GenerateDataKey</code> and\n            <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key\n         policies for the KMS key to retrieve the checksum of the object.</p>",
             "smithy.api#httpHeader": "x-amz-checksum-mode"
           }
         }
@@ -25368,6 +25405,21 @@
     "com.amazonaws.s3#IfMatch": {
       "type": "string"
     },
+    "com.amazonaws.s3#IfMatchInitiatedTime": {
+      "type": "timestamp",
+      "traits": {
+        "smithy.api#timestampFormat": "http-date"
+      }
+    },
+    "com.amazonaws.s3#IfMatchLastModifiedTime": {
+      "type": "timestamp",
+      "traits": {
+        "smithy.api#timestampFormat": "http-date"
+      }
+    },
+    "com.amazonaws.s3#IfMatchSize": {
+      "type": "long"
+    },
     "com.amazonaws.s3#IfModifiedSince": {
       "type": "timestamp"
     },
@@ -25401,7 +25453,7 @@
         "ID": {
           "target": "com.amazonaws.s3#ID",
           "traits": {
-            "smithy.api#documentation": "<p>If the principal is an Amazon Web Services account, it provides the Canonical User ID. If the\n         principal is an IAM User, it provides a user ARN value.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - If the principal is an Amazon Web Services account, it provides the Amazon Web Services account ID. If the\n         principal is an IAM User, it provides a user ARN value.</p>\n         </note>"
+            "smithy.api#documentation": "<p>If the principal is an Amazon Web Services account, it provides the Canonical User ID. If the\n         principal is an IAM User, it provides a user ARN value.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - If the principal is an\n            Amazon Web Services account, it provides the Amazon Web Services account ID. If the principal is an IAM User, it\n            provides a user ARN value.</p>\n         </note>"
           }
         },
         "DisplayName": {
@@ -25586,11 +25638,29 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Object is archived and inaccessible until restored.</p>\n         <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage class, the \n         S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access tier, or the \n         S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you must first restore a\n         copy using <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a>. Otherwise, this operation returns an\n         <code>InvalidObjectState</code> error. For information about restoring archived objects,\n         see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring\n            Archived Objects</a> in the <i>Amazon S3 User Guide</i>.</p>",
+        "smithy.api#documentation": "<p>Object is archived and inaccessible until restored.</p>\n         <p>If the object you are retrieving is stored in the S3 Glacier Flexible Retrieval storage\n         class, the S3 Glacier Deep Archive storage class, the S3 Intelligent-Tiering Archive Access\n         tier, or the S3 Intelligent-Tiering Deep Archive Access tier, before you can retrieve the object you\n         must first restore a copy using <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html\">RestoreObject</a>. Otherwise, this\n         operation returns an <code>InvalidObjectState</code> error. For information about restoring\n         archived objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring Archived Objects</a> in\n         the <i>Amazon S3 User Guide</i>.</p>",
         "smithy.api#error": "client",
         "smithy.api#httpError": 403
       }
     },
+    "com.amazonaws.s3#InvalidRequest": {
+      "type": "structure",
+      "members": {},
+      "traits": {
+        "smithy.api#documentation": "<p>You may receive this error in multiple cases. Depending on the reason for the error, you may receive one of the messages below:</p>\n         <ul>\n            <li>\n               <p>Cannot specify both a write offset value and user-defined object metadata for existing objects.</p>\n            </li>\n            <li>\n               <p>Checksum Type mismatch occurred, expected checksum Type: sha1, actual checksum Type: crc32c.</p>\n            </li>\n            <li>\n               <p>Request body cannot be empty when 'write offset' is specified.</p>\n            </li>\n         </ul>",
+        "smithy.api#error": "client",
+        "smithy.api#httpError": 400
+      }
+    },
+    "com.amazonaws.s3#InvalidWriteOffset": {
+      "type": "structure",
+      "members": {},
+      "traits": {
+        "smithy.api#documentation": "<p>\n         The write offset value that you specified does not match the current object size.\n      </p>",
+        "smithy.api#error": "client",
+        "smithy.api#httpError": 400
+      }
+    },
     "com.amazonaws.s3#InventoryConfiguration": {
       "type": "structure",
       "members": {
@@ -26038,13 +26108,19 @@
     "com.amazonaws.s3#LastModified": {
       "type": "timestamp"
     },
+    "com.amazonaws.s3#LastModifiedTime": {
+      "type": "timestamp",
+      "traits": {
+        "smithy.api#timestampFormat": "http-date"
+      }
+    },
     "com.amazonaws.s3#LifecycleExpiration": {
       "type": "structure",
       "members": {
         "Date": {
           "target": "com.amazonaws.s3#Date",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates at what date the object is to be moved or deleted. The date value must conform\n         to the ISO 8601 format. The time is always midnight UTC.</p>"
+            "smithy.api#documentation": "<p>Indicates at what date the object is to be moved or deleted. The date value must conform\n         to the ISO 8601 format. The time is always midnight UTC.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>"
           }
         },
         "Days": {
@@ -26056,7 +26132,7 @@
         "ExpiredObjectDeleteMarker": {
           "target": "com.amazonaws.s3#ExpiredObjectDeleteMarker",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates whether Amazon S3 will remove a delete marker with no noncurrent versions. If set\n         to true, the delete marker will be expired; if set to false the policy takes no action.\n         This cannot be specified with Days or Date in a Lifecycle Expiration Policy.</p>"
+            "smithy.api#documentation": "<p>Indicates whether Amazon S3 will remove a delete marker with no noncurrent versions. If set\n         to true, the delete marker will be expired; if set to false the policy takes no action.\n         This cannot be specified with Days or Date in a Lifecycle Expiration Policy.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>"
           }
         }
       },
@@ -26089,7 +26165,7 @@
         "Filter": {
           "target": "com.amazonaws.s3#LifecycleRuleFilter",
           "traits": {
-            "smithy.api#documentation": "<p>The <code>Filter</code> is used to identify objects that a Lifecycle Rule applies to. A\n            <code>Filter</code> must have exactly one of <code>Prefix</code>, <code>Tag</code>, or\n            <code>And</code> specified. <code>Filter</code> is required if the\n            <code>LifecycleRule</code> does not contain a <code>Prefix</code> element.</p>"
+            "smithy.api#documentation": "<p>The <code>Filter</code> is used to identify objects that a Lifecycle Rule applies to. A\n            <code>Filter</code> must have exactly one of <code>Prefix</code>, <code>Tag</code>, or\n            <code>And</code> specified. <code>Filter</code> is required if the\n            <code>LifecycleRule</code> does not contain a <code>Prefix</code> element.</p>\n         <note>\n            <p>\n               <code>Tag</code> filters are not supported for directory buckets.</p>\n         </note>"
           }
         },
         "Status": {
@@ -26102,7 +26178,7 @@
         "Transitions": {
           "target": "com.amazonaws.s3#TransitionList",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies when an Amazon S3 object transitions to a specified storage class.</p>",
+            "smithy.api#documentation": "<p>Specifies when an Amazon S3 object transitions to a specified storage class.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>",
             "smithy.api#xmlFlattened": {},
             "smithy.api#xmlName": "Transition"
           }
@@ -26110,7 +26186,7 @@
         "NoncurrentVersionTransitions": {
           "target": "com.amazonaws.s3#NoncurrentVersionTransitionList",
           "traits": {
-            "smithy.api#documentation": "<p> Specifies the transition rule for the lifecycle rule that describes when noncurrent\n         objects transition to a specific storage class. If your bucket is versioning-enabled (or\n         versioning is suspended), you can set this action to request that Amazon S3 transition\n         noncurrent object versions to a specific storage class at a set period in the object's\n         lifetime. </p>",
+            "smithy.api#documentation": "<p>Specifies the transition rule for the lifecycle rule that describes when noncurrent\n         objects transition to a specific storage class. If your bucket is versioning-enabled (or\n         versioning is suspended), you can set this action to request that Amazon S3 transition\n         noncurrent object versions to a specific storage class at a set period in the object's\n         lifetime.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>",
             "smithy.api#xmlFlattened": {},
             "smithy.api#xmlName": "NoncurrentVersionTransition"
           }
@@ -26172,7 +26248,7 @@
         "Tag": {
           "target": "com.amazonaws.s3#Tag",
           "traits": {
-            "smithy.api#documentation": "<p>This tag must exist in the object's tag set in order for the rule to apply.</p>"
+            "smithy.api#documentation": "<p>This tag must exist in the object's tag set in order for the rule to apply.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>"
           }
         },
         "ObjectSizeGreaterThan": {
@@ -26192,7 +26268,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>The <code>Filter</code> is used to identify objects that a Lifecycle Rule applies to. A\n         <code>Filter</code> can have exactly one of <code>Prefix</code>, <code>Tag</code>, <code>ObjectSizeGreaterThan</code>, <code>ObjectSizeLessThan</code>, or\n         <code>And</code> specified. If the <code>Filter</code> element is left empty, the Lifecycle Rule applies to all objects in the bucket.</p>"
+        "smithy.api#documentation": "<p>The <code>Filter</code> is used to identify objects that a Lifecycle Rule applies to. A\n            <code>Filter</code> can have exactly one of <code>Prefix</code>, <code>Tag</code>,\n            <code>ObjectSizeGreaterThan</code>, <code>ObjectSizeLessThan</code>, or <code>And</code>\n         specified. If the <code>Filter</code> element is left empty, the Lifecycle Rule applies to\n         all objects in the bucket.</p>"
       }
     },
     "com.amazonaws.s3#LifecycleRules": {
@@ -26210,7 +26286,7 @@
         "target": "com.amazonaws.s3#ListBucketAnalyticsConfigurationsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Lists the analytics configurations for the bucket. You can have up to 1,000 analytics\n         configurations per bucket.</p>\n         <p>This action supports list pagination and does not return more than 100 configurations at\n         a time. You should always check the <code>IsTruncated</code> element in the response. If\n         there are no more configurations to list, <code>IsTruncated</code> is set to false. If\n         there are more configurations to list, <code>IsTruncated</code> is set to true, and there\n         will be a value in <code>NextContinuationToken</code>. You use the\n            <code>NextContinuationToken</code> value to continue the pagination of the list by\n         passing the value in continuation-token in the request to <code>GET</code> the next\n         page.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class\n            Analysis</a>. </p>\n         <p>The following operations are related to\n         <code>ListBucketAnalyticsConfigurations</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAnalyticsConfiguration.html\">GetBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketAnalyticsConfiguration.html\">DeleteBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAnalyticsConfiguration.html\">PutBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Lists the analytics configurations for the bucket. You can have up to 1,000 analytics\n         configurations per bucket.</p>\n         <p>This action supports list pagination and does not return more than 100 configurations at\n         a time. You should always check the <code>IsTruncated</code> element in the response. If\n         there are no more configurations to list, <code>IsTruncated</code> is set to false. If\n         there are more configurations to list, <code>IsTruncated</code> is set to true, and there\n         will be a value in <code>NextContinuationToken</code>. You use the\n            <code>NextContinuationToken</code> value to continue the pagination of the list by\n         passing the value in continuation-token in the request to <code>GET</code> the next\n         page.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about Amazon S3 analytics feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3 Analytics – Storage Class\n            Analysis</a>. </p>\n         <p>The following operations are related to\n         <code>ListBucketAnalyticsConfigurations</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAnalyticsConfiguration.html\">GetBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketAnalyticsConfiguration.html\">DeleteBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketAnalyticsConfiguration.html\">PutBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?analytics&x-id=ListBucketAnalyticsConfigurations",
@@ -26300,7 +26376,7 @@
         "target": "com.amazonaws.s3#ListBucketIntelligentTieringConfigurationsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Lists the S3 Intelligent-Tiering configuration from the specified bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>ListBucketIntelligentTieringConfigurations</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketIntelligentTieringConfiguration.html\">DeleteBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketIntelligentTieringConfiguration.html\">PutBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketIntelligentTieringConfiguration.html\">GetBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Lists the S3 Intelligent-Tiering configuration from the specified bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>ListBucketIntelligentTieringConfigurations</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketIntelligentTieringConfiguration.html\">DeleteBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketIntelligentTieringConfiguration.html\">PutBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketIntelligentTieringConfiguration.html\">GetBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?intelligent-tiering&x-id=ListBucketIntelligentTieringConfigurations",
@@ -26382,7 +26458,7 @@
         "target": "com.amazonaws.s3#ListBucketInventoryConfigurationsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns a list of inventory configurations for the bucket. You can have up to 1,000\n         analytics configurations per bucket.</p>\n         <p>This action supports list pagination and does not return more than 100 configurations at\n         a time. Always check the <code>IsTruncated</code> element in the response. If there are no\n         more configurations to list, <code>IsTruncated</code> is set to false. If there are more\n         configurations to list, <code>IsTruncated</code> is set to true, and there is a value in\n            <code>NextContinuationToken</code>. You use the <code>NextContinuationToken</code> value\n         to continue the pagination of the list by passing the value in continuation-token in the\n         request to <code>GET</code> the next page.</p>\n         <p> To use this operation, you must have permissions to perform the\n            <code>s3:GetInventoryConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>\n         </p>\n         <p>The following operations are related to\n         <code>ListBucketInventoryConfigurations</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketInventoryConfiguration.html\">GetBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketInventoryConfiguration.html\">DeleteBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketInventoryConfiguration.html\">PutBucketInventoryConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns a list of inventory configurations for the bucket. You can have up to 1,000\n         analytics configurations per bucket.</p>\n         <p>This action supports list pagination and does not return more than 100 configurations at\n         a time. Always check the <code>IsTruncated</code> element in the response. If there are no\n         more configurations to list, <code>IsTruncated</code> is set to false. If there are more\n         configurations to list, <code>IsTruncated</code> is set to true, and there is a value in\n            <code>NextContinuationToken</code>. You use the <code>NextContinuationToken</code> value\n         to continue the pagination of the list by passing the value in continuation-token in the\n         request to <code>GET</code> the next page.</p>\n         <p> To use this operation, you must have permissions to perform the\n            <code>s3:GetInventoryConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For information about the Amazon S3 inventory feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a>\n         </p>\n         <p>The following operations are related to\n         <code>ListBucketInventoryConfigurations</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketInventoryConfiguration.html\">GetBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketInventoryConfiguration.html\">DeleteBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketInventoryConfiguration.html\">PutBucketInventoryConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?inventory&x-id=ListBucketInventoryConfigurations",
@@ -26472,7 +26548,7 @@
         "target": "com.amazonaws.s3#ListBucketMetricsConfigurationsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Lists the metrics configurations for the bucket. The metrics configurations are only for\n         the request metrics of the bucket and do not provide information on daily storage metrics.\n         You can have up to 1,000 configurations per bucket.</p>\n         <p>This action supports list pagination and does not return more than 100 configurations at\n         a time. Always check the <code>IsTruncated</code> element in the response. If there are no\n         more configurations to list, <code>IsTruncated</code> is set to false. If there are more\n         configurations to list, <code>IsTruncated</code> is set to true, and there is a value in\n            <code>NextContinuationToken</code>. You use the <code>NextContinuationToken</code> value\n         to continue the pagination of the list by passing the value in\n            <code>continuation-token</code> in the request to <code>GET</code> the next page.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For more information about metrics configurations and CloudWatch request metrics, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>.</p>\n         <p>The following operations are related to\n         <code>ListBucketMetricsConfigurations</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketMetricsConfiguration.html\">PutBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetricsConfiguration.html\">GetBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetricsConfiguration.html\">DeleteBucketMetricsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Lists the metrics configurations for the bucket. The metrics configurations are only for\n         the request metrics of the bucket and do not provide information on daily storage metrics.\n         You can have up to 1,000 configurations per bucket.</p>\n         <p>This action supports list pagination and does not return more than 100 configurations at\n         a time. Always check the <code>IsTruncated</code> element in the response. If there are no\n         more configurations to list, <code>IsTruncated</code> is set to false. If there are more\n         configurations to list, <code>IsTruncated</code> is set to true, and there is a value in\n            <code>NextContinuationToken</code>. You use the <code>NextContinuationToken</code> value\n         to continue the pagination of the list by passing the value in\n            <code>continuation-token</code> in the request to <code>GET</code> the next page.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:GetMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>For more information about metrics configurations and CloudWatch request metrics, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html\">Monitoring Metrics with Amazon CloudWatch</a>.</p>\n         <p>The following operations are related to\n         <code>ListBucketMetricsConfigurations</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketMetricsConfiguration.html\">PutBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetricsConfiguration.html\">GetBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetricsConfiguration.html\">DeleteBucketMetricsConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/{Bucket}?metrics&x-id=ListBucketMetricsConfigurations",
@@ -26557,7 +26633,7 @@
         "target": "com.amazonaws.s3#ListBucketsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns a list of all buckets owned by the authenticated sender of the request. To use\n         this operation, you must have the <code>s3:ListAllMyBuckets</code> permission. </p>\n         <p>For information about Amazon S3 buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html\">Creating, configuring, and\n            working with Amazon S3 buckets</a>.</p>\n         <important>\n            <p>We strongly recommend using only paginated requests. Unpaginated requests are only supported for \n            Amazon Web Services accounts set to the default general purpose bucket quota of 10,000. If you have an approved \n            general purpose bucket quota above 10,000, you must send paginated requests to list your account’s buckets. \n            All unpaginated ListBuckets requests will be rejected for Amazon Web Services accounts with a general purpose bucket quota \n            greater than 10,000. </p>\n         </important>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns a list of all buckets owned by the authenticated sender of the request. To grant IAM permission to use\n         this operation, you must add the <code>s3:ListAllMyBuckets</code> policy action. </p>\n         <p>For information about Amazon S3 buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html\">Creating, configuring, and\n            working with Amazon S3 buckets</a>.</p>\n         <important>\n            <p>We strongly recommend using only paginated <code>ListBuckets</code> requests. Unpaginated <code>ListBuckets</code> requests are only supported for \n            Amazon Web Services accounts set to the default general purpose bucket quota of 10,000. If you have an approved \n            general purpose bucket quota above 10,000, you must send paginated <code>ListBuckets</code> requests to list your account’s buckets. \n            All unpaginated <code>ListBuckets</code> requests will be rejected for Amazon Web Services accounts with a general purpose bucket quota \n            greater than 10,000. </p>\n         </important>",
         "smithy.api#examples": [
           {
             "title": "To list all buckets",
@@ -26615,7 +26691,7 @@
         "ContinuationToken": {
           "target": "com.amazonaws.s3#NextToken",
           "traits": {
-            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> is included in the\n         response when there are more buckets that can be listed with pagination. The next <code>ListBuckets</code> request to Amazon S3 can be continued with this <code>ContinuationToken</code>. <code>ContinuationToken</code> is obfuscated and is not a real bucket.</p>"
+            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> is included in the response when there are more buckets\n         that can be listed with pagination. The next <code>ListBuckets</code> request to Amazon S3 can\n         be continued with this <code>ContinuationToken</code>. <code>ContinuationToken</code> is\n         obfuscated and is not a real bucket.</p>"
           }
         },
         "Prefix": {
@@ -26636,28 +26712,28 @@
         "MaxBuckets": {
           "target": "com.amazonaws.s3#MaxBuckets",
           "traits": {
-            "smithy.api#documentation": "<p>Maximum number of buckets to be returned in response. When the number is more than the count of buckets that are owned by an Amazon Web Services account, return all the buckets in response.</p>",
+            "smithy.api#documentation": "<p>Maximum number of buckets to be returned in response. When the number is more than the\n         count of buckets that are owned by an Amazon Web Services account, return all the buckets in\n         response.</p>",
             "smithy.api#httpQuery": "max-buckets"
           }
         },
         "ContinuationToken": {
           "target": "com.amazonaws.s3#Token",
           "traits": {
-            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on\n         this bucket with a token. <code>ContinuationToken</code> is obfuscated and is not a real\n         key. You can use this <code>ContinuationToken</code> for pagination of the list results.  </p>\n         <p>Length Constraints: Minimum length of 0. Maximum length of 1024.</p>\n         <p>Required: No.</p>\n         <note>\n            <p>If you specify the <code>bucket-region</code>, <code>prefix</code>, or <code>continuation-token</code> \n            query parameters without using <code>max-buckets</code> to set the maximum number of buckets returned in the response, \n            Amazon S3 applies a default page size of 10,000 and provides a continuation token if there are more buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on\n         this bucket with a token. <code>ContinuationToken</code> is obfuscated and is not a real\n         key. You can use this <code>ContinuationToken</code> for pagination of the list results. </p>\n         <p>Length Constraints: Minimum length of 0. Maximum length of 1024.</p>\n         <p>Required: No.</p>\n         <note>\n            <p>If you specify the <code>bucket-region</code>, <code>prefix</code>, or <code>continuation-token</code> \n            query parameters without using <code>max-buckets</code> to set the maximum number of buckets returned in the response, \n            Amazon S3 applies a default page size of 10,000 and provides a continuation token if there are more buckets.</p>\n         </note>",
             "smithy.api#httpQuery": "continuation-token"
           }
         },
         "Prefix": {
           "target": "com.amazonaws.s3#Prefix",
           "traits": {
-            "smithy.api#documentation": "<p>Limits the response to bucket names that begin with the specified bucket name prefix.</p>",
+            "smithy.api#documentation": "<p>Limits the response to bucket names that begin with the specified bucket name\n         prefix.</p>",
             "smithy.api#httpQuery": "prefix"
           }
         },
         "BucketRegion": {
           "target": "com.amazonaws.s3#BucketRegion",
           "traits": {
-            "smithy.api#documentation": "<p>Limits the response to buckets that are located in the specified Amazon Web Services Region. The Amazon Web Services Region must be expressed according to the Amazon Web Services Region code, such as <code>us-west-2</code> for the US West (Oregon) Region. For a list of the valid values for all of the Amazon Web Services Regions, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a>.</p>\n         <note>\n            <p>Requests made to a Regional endpoint that is different from the <code>bucket-region</code> parameter are not supported. For example, if you want to limit the response to your buckets in Region <code>us-west-2</code>, the request must be made to an endpoint in Region <code>us-west-2</code>.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Limits the response to buckets that are located in the specified Amazon Web Services Region. The Amazon Web Services\n         Region must be expressed according to the Amazon Web Services Region code, such as <code>us-west-2</code>\n         for the US West (Oregon) Region. For a list of the valid values for all of the Amazon Web Services\n         Regions, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a>.</p>\n         <note>\n            <p>Requests made to a Regional endpoint that is different from the\n               <code>bucket-region</code> parameter are not supported. For example, if you want to\n            limit the response to your buckets in Region <code>us-west-2</code>, the request must be\n            made to an endpoint in Region <code>us-west-2</code>.</p>\n         </note>",
             "smithy.api#httpQuery": "bucket-region"
           }
         }
@@ -26675,7 +26751,7 @@
         "target": "com.amazonaws.s3#ListDirectoryBucketsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Returns a list of all Amazon S3 directory buckets owned by the authenticated sender of the request. For more information about directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have the <code>s3express:ListAllMyDirectoryBuckets</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>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <note>\n            <p> The <code>BucketRegion</code> response element is not part of the <code>ListDirectoryBuckets</code> Response Syntax.</p>\n         </note>",
+        "smithy.api#documentation": "<p>Returns a list of all Amazon S3 directory buckets owned by the authenticated sender of the\n         request. For more information about directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have the <code>s3express:ListAllMyDirectoryBuckets</code> permission\n                  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.\n                  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>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host\n                  header syntax is\n                     <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <note>\n            <p> The <code>BucketRegion</code> response element is not part of the\n               <code>ListDirectoryBuckets</code> Response Syntax.</p>\n         </note>",
         "smithy.api#http": {
           "method": "GET",
           "uri": "/?x-id=ListDirectoryBuckets",
@@ -26706,7 +26782,7 @@
         "ContinuationToken": {
           "target": "com.amazonaws.s3#DirectoryBucketToken",
           "traits": {
-            "smithy.api#documentation": "<p>If <code>ContinuationToken</code> was sent with the request, it is included in the\n         response. You can use the returned <code>ContinuationToken</code> for pagination of the list response.</p>"
+            "smithy.api#documentation": "<p>If <code>ContinuationToken</code> was sent with the request, it is included in the\n         response. You can use the returned <code>ContinuationToken</code> for pagination of the\n         list response.</p>"
           }
         }
       },
@@ -26721,14 +26797,14 @@
         "ContinuationToken": {
           "target": "com.amazonaws.s3#DirectoryBucketToken",
           "traits": {
-            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on buckets in this account with a token. <code>ContinuationToken</code> is obfuscated and is not a real\n         bucket name. You can use this <code>ContinuationToken</code> for the pagination of the list results.  </p>",
+            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on\n         buckets in this account with a token. <code>ContinuationToken</code> is obfuscated and is\n         not a real bucket name. You can use this <code>ContinuationToken</code> for the pagination\n         of the list results. </p>",
             "smithy.api#httpQuery": "continuation-token"
           }
         },
         "MaxDirectoryBuckets": {
           "target": "com.amazonaws.s3#MaxDirectoryBuckets",
           "traits": {
-            "smithy.api#documentation": "<p>Maximum number of buckets to be returned in response. When the number is more than the count of buckets that are owned by an Amazon Web Services account, return all the buckets in response.</p>",
+            "smithy.api#documentation": "<p>Maximum number of buckets to be returned in response. When the number is more than the\n         count of buckets that are owned by an Amazon Web Services account, return all the buckets in\n         response.</p>",
             "smithy.api#httpQuery": "max-directory-buckets"
           }
         }
@@ -26746,7 +26822,7 @@
         "target": "com.amazonaws.s3#ListMultipartUploadsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>This operation lists in-progress multipart uploads in a bucket. An in-progress multipart upload is a\n         multipart upload that has been initiated by the <code>CreateMultipartUpload</code> request, but\n         has not yet been completed or aborted.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - \n            If multipart uploads in a directory bucket are in progress, you can't delete the bucket until all the in-progress multipart uploads are aborted or completed. \n            To delete these in-progress multipart uploads, use the <code>ListMultipartUploads</code> operation to list the in-progress multipart\n            uploads in the bucket and use the <code>AbortMultipartUpload</code> operation to abort all the in-progress multipart uploads.\n            </p>\n         </note>\n         <p>The <code>ListMultipartUploads</code> operation returns a maximum of 1,000 multipart uploads in the response. The limit of 1,000 multipart\n         uploads is also the default\n         value. You can further limit the number of uploads in a response by specifying the\n         <code>max-uploads</code> request parameter. If there are more than 1,000 multipart uploads that \n         satisfy your <code>ListMultipartUploads</code> request, the response returns an <code>IsTruncated</code> element\n         with the value of <code>true</code>, a <code>NextKeyMarker</code> element, and a <code>NextUploadIdMarker</code> element. \n         To list the remaining multipart uploads, you need to make subsequent <code>ListMultipartUploads</code> requests. \n         In these requests, include two query parameters: <code>key-marker</code> and <code>upload-id-marker</code>. \n         Set the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous response. \n         Similarly, set the value of <code>upload-id-marker</code> to the <code>NextUploadIdMarker</code> value from the previous response.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The <code>upload-id-marker</code> element and \n         the <code>NextUploadIdMarker</code> element aren't supported by directory buckets. \n         To list the additional multipart uploads, you only need to set the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous response. </p>\n         </note>\n         <p>For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n         Upload</a> in the <i>Amazon S3\n            User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For information about permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload\n                        and Permissions</a> in the <i>Amazon S3\n                           User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Sorting of multipart uploads in response</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - In the <code>ListMultipartUploads</code> response, the multipart uploads are sorted based on two criteria:</p>\n                     <ul>\n                        <li>\n                           <p>Key-based sorting - Multipart uploads are initially sorted in ascending order based on their object keys.</p>\n                        </li>\n                        <li>\n                           <p>Time-based sorting - For uploads that share the same object key, \n                              they are further sorted in ascending order based on the upload initiation time. Among uploads with the same key, the one that was initiated first will appear before the ones that were initiated later.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> - In the <code>ListMultipartUploads</code> response, the multipart uploads aren't sorted lexicographically based on the object keys. \n                        \n                        </p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>ListMultipartUploads</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>This operation lists in-progress multipart uploads in a bucket. An in-progress multipart\n         upload is a multipart upload that has been initiated by the\n            <code>CreateMultipartUpload</code> request, but has not yet been completed or\n         aborted.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - If multipart uploads in\n            a directory bucket are in progress, you can't delete the bucket until all the\n            in-progress multipart uploads are aborted or completed. To delete these in-progress\n            multipart uploads, use the <code>ListMultipartUploads</code> operation to list the\n            in-progress multipart uploads in the bucket and use the\n               <code>AbortMultipartUpload</code> operation to abort all the in-progress multipart\n            uploads. </p>\n         </note>\n         <p>The <code>ListMultipartUploads</code> operation returns a maximum of 1,000 multipart\n         uploads in the response. The limit of 1,000 multipart uploads is also the default value.\n         You can further limit the number of uploads in a response by specifying the\n            <code>max-uploads</code> request parameter. If there are more than 1,000 multipart\n         uploads that satisfy your <code>ListMultipartUploads</code> request, the response returns\n         an <code>IsTruncated</code> element with the value of <code>true</code>, a\n            <code>NextKeyMarker</code> element, and a <code>NextUploadIdMarker</code> element. To\n         list the remaining multipart uploads, you need to make subsequent\n            <code>ListMultipartUploads</code> requests. In these requests, include two query\n         parameters: <code>key-marker</code> and <code>upload-id-marker</code>. Set the value of\n            <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous\n         response. Similarly, set the value of <code>upload-id-marker</code> to the\n            <code>NextUploadIdMarker</code> value from the previous response.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The\n               <code>upload-id-marker</code> element and the <code>NextUploadIdMarker</code> element\n            aren't supported by directory buckets. To list the additional multipart uploads, you\n            only need to set the value of <code>key-marker</code> to the <code>NextKeyMarker</code>\n            value from the previous response. </p>\n         </note>\n         <p>For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n            Upload</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For\n                        information about permissions required to use the multipart upload API, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload and\n                           Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Sorting of multipart uploads in response</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - In the\n                           <code>ListMultipartUploads</code> response, the multipart uploads are\n                        sorted based on two criteria:</p>\n                     <ul>\n                        <li>\n                           <p>Key-based sorting - Multipart uploads are initially sorted\n                              in ascending order based on their object keys.</p>\n                        </li>\n                        <li>\n                           <p>Time-based sorting - For uploads that share the same object\n                              key, they are further sorted in ascending order based on the upload\n                              initiation time. Among uploads with the same key, the one that was\n                              initiated first will appear before the ones that were initiated\n                              later.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> - In the\n                           <code>ListMultipartUploads</code> response, the multipart uploads aren't\n                        sorted lexicographically based on the object keys.\n                        \n                     </p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>ListMultipartUploads</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "List next set of multipart uploads when previous result is truncated",
@@ -26862,7 +26938,7 @@
         "UploadIdMarker": {
           "target": "com.amazonaws.s3#UploadIdMarker",
           "traits": {
-            "smithy.api#documentation": "<p>Together with key-marker, specifies the multipart upload after which listing should\n         begin. If key-marker is not specified, the upload-id-marker parameter is ignored.\n         Otherwise, any multipart uploads for a key equal to the key-marker might be included in the\n         list only if they have an upload ID lexicographically greater than the specified\n         <code>upload-id-marker</code>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Together with key-marker, specifies the multipart upload after which listing should\n         begin. If key-marker is not specified, the upload-id-marker parameter is ignored.\n         Otherwise, any multipart uploads for a key equal to the key-marker might be included in the\n         list only if they have an upload ID lexicographically greater than the specified\n            <code>upload-id-marker</code>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
           }
         },
         "NextKeyMarker": {
@@ -26940,7 +27016,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the bucket to which the multipart upload was initiated. </p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the bucket to which the multipart upload was initiated. </p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -26964,7 +27040,7 @@
         "KeyMarker": {
           "target": "com.amazonaws.s3#KeyMarker",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the multipart upload after which listing should begin.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - For general purpose buckets, <code>key-marker</code>  \n               is an object key. Together with <code>upload-id-marker</code>, this parameter specifies the multipart\n               upload after which listing should begin.</p>\n                  <p>If <code>upload-id-marker</code> is not specified, only the keys lexicographically\n                  greater than the specified <code>key-marker</code> will be included in the list.</p>\n                  <p>If <code>upload-id-marker</code> is specified, any multipart uploads for a key equal to\n                  the <code>key-marker</code> might also be included, provided those multipart uploads have\n                  upload IDs lexicographically greater than the specified\n                  <code>upload-id-marker</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, <code>key-marker</code> \n               is obfuscated and isn't a real object key. \n               The <code>upload-id-marker</code> parameter isn't supported by directory buckets. \n               To list the additional multipart uploads, you only need to set the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from the previous response. \n            </p>\n                  <p>In the <code>ListMultipartUploads</code> response, the multipart uploads aren't sorted lexicographically based on the object keys. \n                  \n                  </p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the multipart upload after which listing should begin.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - For\n                  general purpose buckets, <code>key-marker</code> is an object key. Together with\n                     <code>upload-id-marker</code>, this parameter specifies the multipart upload\n                  after which listing should begin.</p>\n                  <p>If <code>upload-id-marker</code> is not specified, only the keys\n                  lexicographically greater than the specified <code>key-marker</code> will be\n                  included in the list.</p>\n                  <p>If <code>upload-id-marker</code> is specified, any multipart uploads for a key\n                  equal to the <code>key-marker</code> might also be included, provided those\n                  multipart uploads have upload IDs lexicographically greater than the specified\n                     <code>upload-id-marker</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For\n                  directory buckets, <code>key-marker</code> is obfuscated and isn't a real object\n                  key. The <code>upload-id-marker</code> parameter isn't supported by\n                  directory buckets. To list the additional multipart uploads, you only need to set\n                  the value of <code>key-marker</code> to the <code>NextKeyMarker</code> value from\n                  the previous response. </p>\n                  <p>In the <code>ListMultipartUploads</code> response, the multipart uploads aren't\n                  sorted lexicographically based on the object keys.\n                  \n               </p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpQuery": "key-marker"
           }
         },
@@ -27019,7 +27095,7 @@
         "target": "com.amazonaws.s3#ListObjectVersionsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns metadata about all versions of the objects in a bucket. You can also use request\n         parameters as selection criteria to return metadata about a subset of all the object\n         versions.</p>\n         <important>\n            <p> To use this operation, you must have permission to perform the\n               <code>s3:ListBucketVersions</code> action. Be aware of the name difference. </p>\n         </important>\n         <note>\n            <p> A <code>200 OK</code> response can contain valid or invalid XML. Make sure to design\n            your application to parse the contents of the response and handle it\n            appropriately.</p>\n         </note>\n         <p>To use this operation, you must have READ access to the bucket.</p>\n         <p>The following operations are related to <code>ListObjectVersions</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html\">ListObjectsV2</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns metadata about all versions of the objects in a bucket. You can also use request\n         parameters as selection criteria to return metadata about a subset of all the object\n         versions.</p>\n         <important>\n            <p> To use this operation, you must have permission to perform the\n               <code>s3:ListBucketVersions</code> action. Be aware of the name difference. </p>\n         </important>\n         <note>\n            <p> A <code>200 OK</code> response can contain valid or invalid XML. Make sure to design\n            your application to parse the contents of the response and handle it\n            appropriately.</p>\n         </note>\n         <p>To use this operation, you must have READ access to the bucket.</p>\n         <p>The following operations are related to <code>ListObjectVersions</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html\">ListObjectsV2</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To list object versions",
@@ -27262,7 +27338,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Returns some or all (up to 1,000) of the objects in a bucket. You can use the request\n         parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK\n         response can contain valid or invalid XML. Be sure to design your application to parse the\n         contents of the response and handle it appropriately.</p>\n         <important>\n            <p>This action has been revised. We recommend that you use the newer version, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html\">ListObjectsV2</a>, when developing applications. For backward compatibility,\n            Amazon S3 continues to support <code>ListObjects</code>.</p>\n         </important>\n         <p>The following operations are related to <code>ListObjects</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html\">ListObjectsV2</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html\">ListBuckets</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Returns some or all (up to 1,000) of the objects in a bucket. You can use the request\n         parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK\n         response can contain valid or invalid XML. Be sure to design your application to parse the\n         contents of the response and handle it appropriately.</p>\n         <important>\n            <p>This action has been revised. We recommend that you use the newer version, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html\">ListObjectsV2</a>, when developing applications. For backward compatibility,\n            Amazon S3 continues to support <code>ListObjects</code>.</p>\n         </important>\n         <p>The following operations are related to <code>ListObjects</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectsV2.html\">ListObjectsV2</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html\">ListBuckets</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To list objects in a bucket",
@@ -27390,7 +27466,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the bucket containing the objects.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the bucket containing the objects.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -27475,7 +27551,7 @@
         }
       ],
       "traits": {
-        "smithy.api#documentation": "<p>Returns some or all (up to 1,000) of the objects in a bucket with each request. You can\n         use the request parameters as selection criteria to return a subset of the objects in a\n         bucket. A <code>200 OK</code> response can contain valid or invalid XML. Make sure to\n         design your application to parse the contents of the response and handle it appropriately.\n         \n         For more information about listing objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/ListingKeysUsingAPIs.html\">Listing object keys\n            programmatically</a> in the <i>Amazon S3 User Guide</i>. To get a list of your buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html\">ListBuckets</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose bucket</b> - For general purpose buckets, <code>ListObjectsV2</code> doesn't return prefixes that are related only to in-progress multipart uploads.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - \n               For directory buckets, <code>ListObjectsV2</code> response includes the prefixes that are related only to in-progress multipart uploads.\n              </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To use this operation, you must have READ access to the bucket. You must have permission to perform\n                        the <code>s3:ListBucket</code> action. The bucket owner has this permission by default and\n                        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\n                              Access Permissions to Your Amazon S3 Resources</a> in the\n                        <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Sorting order of returned objects</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - For general purpose buckets, <code>ListObjectsV2</code> returns objects in lexicographical order based on their key names.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> - For directory buckets, <code>ListObjectsV2</code> does not return objects in lexicographical order.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <important>\n            <p>This section describes the latest revision of this action. We recommend that you use\n            this revised API operation for application development. For backward compatibility, Amazon S3\n            continues to support the prior version of this API operation, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html\">ListObjects</a>.</p>\n         </important>\n         <p>The following operations are related to <code>ListObjectsV2</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Returns some or all (up to 1,000) of the objects in a bucket with each request. You can\n         use the request parameters as selection criteria to return a subset of the objects in a\n         bucket. A <code>200 OK</code> response can contain valid or invalid XML. Make sure to\n         design your application to parse the contents of the response and handle it appropriately.\n         For more information about listing objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/ListingKeysUsingAPIs.html\">Listing object keys\n            programmatically</a> in the <i>Amazon S3 User Guide</i>. To get a list of\n         your buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html\">ListBuckets</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose bucket</b> - For general purpose buckets,\n                     <code>ListObjectsV2</code> doesn't return prefixes that are related only to\n                  in-progress multipart uploads.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For\n                  directory buckets, <code>ListObjectsV2</code> response includes the prefixes that\n                  are related only to in-progress multipart uploads. </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        use this operation, you must have READ access to the bucket. You must have\n                        permission to perform the <code>s3:ListBucket</code> action. The bucket\n                        owner has this permission by default and can grant this permission to\n                        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\n                           Permissions to Your Amazon S3 Resources</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Sorting order of returned objects</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - For\n                        general purpose buckets, <code>ListObjectsV2</code> returns objects in\n                        lexicographical order based on their key names.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> - For\n                        directory buckets, <code>ListObjectsV2</code> does not return objects in\n                        lexicographical order.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <important>\n            <p>This section describes the latest revision of this action. We recommend that you use\n            this revised API operation for application development. For backward compatibility, Amazon S3\n            continues to support the prior version of this API operation, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html\">ListObjects</a>.</p>\n         </important>\n         <p>The following operations are related to <code>ListObjectsV2</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To get object list",
@@ -27565,7 +27641,7 @@
         "CommonPrefixes": {
           "target": "com.amazonaws.s3#CommonPrefixList",
           "traits": {
-            "smithy.api#documentation": "<p>All of the keys (up to 1,000) that share the same prefix are grouped together. When counting the total numbers of returns by this API operation, \n         this group of keys is considered as one item.</p>\n         <p>A response can contain <code>CommonPrefixes</code> only if you specify a\n         delimiter.</p>\n         <p>\n            <code>CommonPrefixes</code> contains all (if there are any) keys between\n            <code>Prefix</code> and the next occurrence of the string specified by a\n         delimiter.</p>\n         <p>\n            <code>CommonPrefixes</code> lists keys that act like subdirectories in the directory\n         specified by <code>Prefix</code>.</p>\n         <p>For example, if the prefix is <code>notes/</code> and the delimiter is a slash\n            (<code>/</code>) as in <code>notes/summer/july</code>, the common prefix is\n            <code>notes/summer/</code>. All of the keys that roll up into a common prefix count as a\n         single return when calculating the number of returns. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, only prefixes that end in a delimiter (<code>/</code>) are supported.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - When you query <code>ListObjectsV2</code> with a delimiter during in-progress multipart uploads, the \n               <code>CommonPrefixes</code> response parameter contains the prefixes that are associated with the in-progress multipart uploads. \n               For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>All of the keys (up to 1,000) that share the same prefix are grouped together. When\n         counting the total numbers of returns by this API operation, this group of keys is\n         considered as one item.</p>\n         <p>A response can contain <code>CommonPrefixes</code> only if you specify a\n         delimiter.</p>\n         <p>\n            <code>CommonPrefixes</code> contains all (if there are any) keys between\n            <code>Prefix</code> and the next occurrence of the string specified by a\n         delimiter.</p>\n         <p>\n            <code>CommonPrefixes</code> lists keys that act like subdirectories in the directory\n         specified by <code>Prefix</code>.</p>\n         <p>For example, if the prefix is <code>notes/</code> and the delimiter is a slash\n            (<code>/</code>) as in <code>notes/summer/july</code>, the common prefix is\n            <code>notes/summer/</code>. All of the keys that roll up into a common prefix count as a\n         single return when calculating the number of returns. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, only prefixes that end in a delimiter (<code>/</code>) are supported.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - When you query\n                     <code>ListObjectsV2</code> with a delimiter during in-progress multipart\n                  uploads, the <code>CommonPrefixes</code> response parameter contains the prefixes\n                  that are associated with the in-progress multipart uploads. For more information\n                  about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in\n                  the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#xmlFlattened": {}
           }
         },
@@ -27584,7 +27660,7 @@
         "ContinuationToken": {
           "target": "com.amazonaws.s3#Token",
           "traits": {
-            "smithy.api#documentation": "<p> If <code>ContinuationToken</code> was sent with the request, it is included in the\n         response. You can use the returned <code>ContinuationToken</code> for pagination of the list response. You can use this <code>ContinuationToken</code> for pagination of the list results. </p>"
+            "smithy.api#documentation": "<p> If <code>ContinuationToken</code> was sent with the request, it is included in the\n         response. You can use the returned <code>ContinuationToken</code> for pagination of the\n         list response. You can use this <code>ContinuationToken</code> for pagination of the list\n         results. </p>"
           }
         },
         "NextContinuationToken": {
@@ -27617,7 +27693,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -27628,14 +27704,14 @@
         "Delimiter": {
           "target": "com.amazonaws.s3#Delimiter",
           "traits": {
-            "smithy.api#documentation": "<p>A delimiter is a character that you use to group keys.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, <code>/</code> is the only supported delimiter.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - When you query <code>ListObjectsV2</code> with a delimiter during in-progress multipart uploads, the \n            <code>CommonPrefixes</code> response parameter contains the prefixes that are associated with the in-progress multipart uploads. \n               For more information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>A delimiter is a character that you use to group keys.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, <code>/</code> is the only supported delimiter.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - When you query\n                     <code>ListObjectsV2</code> with a delimiter during in-progress multipart\n                  uploads, the <code>CommonPrefixes</code> response parameter contains the prefixes\n                  that are associated with the in-progress multipart uploads. For more information\n                  about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in\n                  the <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpQuery": "delimiter"
           }
         },
         "EncodingType": {
           "target": "com.amazonaws.s3#EncodingType",
           "traits": {
-            "smithy.api#documentation": "<p>Encoding type used by Amazon S3 to encode the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html\">object keys</a> in the response.\n         Responses are encoded only in UTF-8. An object key can contain any Unicode character.\n         However, the XML 1.0 parser can't parse certain characters, such as characters with an\n         ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this\n         parameter to request that Amazon S3 encode the keys in the response. For more information about\n         characters to avoid in object key names, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html#object-key-guidelines\">Object key naming\n            guidelines</a>.</p>\n         <note>\n            <p>When using the URL encoding type, non-ASCII characters that are used in an object's\n            key name will be percent-encoded according to UTF-8 code values. For example, the object\n            <code>test_file(3).png</code> will appear as\n            <code>test_file%283%29.png</code>.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Encoding type used by Amazon S3 to encode the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html\">object keys</a> in the response.\n         Responses are encoded only in UTF-8. An object key can contain any Unicode character.\n         However, the XML 1.0 parser can't parse certain characters, such as characters with an\n         ASCII value from 0 to 10. For characters that aren't supported in XML 1.0, you can add this\n         parameter to request that Amazon S3 encode the keys in the response. For more information about\n         characters to avoid in object key names, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html#object-key-guidelines\">Object key naming\n            guidelines</a>.</p>\n         <note>\n            <p>When using the URL encoding type, non-ASCII characters that are used in an object's\n            key name will be percent-encoded according to UTF-8 code values. For example, the object\n               <code>test_file(3).png</code> will appear as\n            <code>test_file%283%29.png</code>.</p>\n         </note>",
             "smithy.api#httpQuery": "encoding-type"
           }
         },
@@ -27659,14 +27735,14 @@
         "ContinuationToken": {
           "target": "com.amazonaws.s3#Token",
           "traits": {
-            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on\n         this bucket with a token. <code>ContinuationToken</code> is obfuscated and is not a real\n         key. You can use this <code>ContinuationToken</code> for pagination of the list results.  </p>",
+            "smithy.api#documentation": "<p>\n            <code>ContinuationToken</code> indicates to Amazon S3 that the list is being continued on\n         this bucket with a token. <code>ContinuationToken</code> is obfuscated and is not a real\n         key. You can use this <code>ContinuationToken</code> for pagination of the list results.\n      </p>",
             "smithy.api#httpQuery": "continuation-token"
           }
         },
         "FetchOwner": {
           "target": "com.amazonaws.s3#FetchOwner",
           "traits": {
-            "smithy.api#documentation": "<p>The owner field is not present in <code>ListObjectsV2</code> by default. If you want to\n         return the owner field with each key in the result, then set the <code>FetchOwner</code>\n         field to <code>true</code>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets, the bucket owner is returned as the object owner for all objects.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The owner field is not present in <code>ListObjectsV2</code> by default. If you want to\n         return the owner field with each key in the result, then set the <code>FetchOwner</code>\n         field to <code>true</code>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets,\n            the bucket owner is returned as the object owner for all objects.</p>\n         </note>",
             "smithy.api#httpQuery": "fetch-owner"
           }
         },
@@ -27712,7 +27788,7 @@
         "target": "com.amazonaws.s3#ListPartsOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Lists the parts that have been uploaded for a specific multipart upload.</p>\n         <p>To use this operation, you must provide the <code>upload ID</code> in the request. You obtain this uploadID by sending the initiate multipart upload\n         request through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>.</p>\n         <p>The <code>ListParts</code> request returns a maximum of 1,000 uploaded parts. The limit of 1,000 parts is also the default value. You can restrict the number of parts in a response by specifying the\n            <code>max-parts</code> request parameter. If your multipart upload consists of more than\n         1,000 parts, the response returns an <code>IsTruncated</code> field with the value of <code>true</code>,\n         and a <code>NextPartNumberMarker</code> element. To list remaining uploaded parts, in subsequent <code>ListParts</code>\n         requests, include the <code>part-number-marker</code> query string parameter and set its value to\n         the <code>NextPartNumberMarker</code> field value from the previous response.</p>\n         <p>For more information on multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n         Upload</a> in the <i>Amazon S3\n            User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For information about permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload\n                        and Permissions</a> in the <i>Amazon S3\n                           User Guide</i>.</p>\n                     <p>If the upload was created using server-side encryption with Key Management Service (KMS) keys\n                        (SSE-KMS) or dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS), you must have permission\n                        to the <code>kms:Decrypt</code> action for the <code>ListParts</code> request to succeed.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>ListParts</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Lists the parts that have been uploaded for a specific multipart upload.</p>\n         <p>To use this operation, you must provide the <code>upload ID</code> in the request. You\n         obtain this uploadID by sending the initiate multipart upload request through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>.</p>\n         <p>The <code>ListParts</code> request returns a maximum of 1,000 uploaded parts. The limit\n         of 1,000 parts is also the default value. You can restrict the number of parts in a\n         response by specifying the <code>max-parts</code> request parameter. If your multipart\n         upload consists of more than 1,000 parts, the response returns an <code>IsTruncated</code>\n         field with the value of <code>true</code>, and a <code>NextPartNumberMarker</code> element.\n         To list remaining uploaded parts, in subsequent <code>ListParts</code> requests, include\n         the <code>part-number-marker</code> query string parameter and set its value to the\n            <code>NextPartNumberMarker</code> field value from the previous response.</p>\n         <p>For more information on multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n            Upload</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - For\n                        information about permissions required to use the multipart upload API, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload and\n                           Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     <p>If the upload was created using server-side encryption with Key Management Service\n                        (KMS) keys (SSE-KMS) or dual-layer server-side encryption with\n                        Amazon Web Services KMS keys (DSSE-KMS), you must have permission to the\n                           <code>kms:Decrypt</code> action for the <code>ListParts</code> request to\n                        succeed.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>ListParts</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAttributes.html\">GetObjectAttributes</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To list parts of a multipart upload.",
@@ -27824,7 +27900,7 @@
         "Parts": {
           "target": "com.amazonaws.s3#Parts",
           "traits": {
-            "smithy.api#documentation": "<p>Container for elements related to a particular part. A response can contain zero or\n         more <code>Part</code> elements.</p>",
+            "smithy.api#documentation": "<p>Container for elements related to a particular part. A response can contain zero or more\n            <code>Part</code> elements.</p>",
             "smithy.api#xmlFlattened": {},
             "smithy.api#xmlName": "Part"
           }
@@ -27838,13 +27914,13 @@
         "Owner": {
           "target": "com.amazonaws.s3#Owner",
           "traits": {
-            "smithy.api#documentation": "<p>Container element that identifies the object owner, after the object is created. If\n         multipart upload is initiated by an IAM user, this element provides the parent account ID\n         and display name.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The bucket owner is returned as the object owner for all the parts.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Container element that identifies the object owner, after the object is created. If\n         multipart upload is initiated by an IAM user, this element provides the parent account ID\n         and display name.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The bucket owner is\n            returned as the object owner for all the parts.</p>\n         </note>"
           }
         },
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>The class of storage used to store the uploaded\n         object.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
+            "smithy.api#documentation": "<p>The class of storage used to store the uploaded object.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
           }
         },
         "RequestCharged": {
@@ -27871,7 +27947,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the bucket to which the parts are being uploaded. </p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the bucket to which the parts are being uploaded. </p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -27966,12 +28042,12 @@
         "Name": {
           "target": "com.amazonaws.s3#LocationNameAsString",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the location where the bucket will be created.</p>\n         <p>For directory buckets, the name of the location is the AZ ID of the Availability Zone where the bucket will be created. An example AZ ID value is <code>usw2-az1</code>.</p>"
+            "smithy.api#documentation": "<p>The name of the location where the bucket will be created.</p>\n         <p>For directory buckets, the name of the location is the AZ ID of the Availability Zone where the\n         bucket will be created. An example AZ ID value is <code>usw2-az1</code>.</p>"
           }
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Specifies the location where the bucket will be created.</p>\n         <p>For directory buckets, the location type is Availability Zone. For more information about directory buckets, see \n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is only supported by directory buckets.</p>\n         </note>"
+        "smithy.api#documentation": "<p>Specifies the location where the bucket will be created.</p>\n         <p>For directory buckets, the location type is Availability Zone. For more information about\n         directory buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html\">Directory buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is only supported by directory buckets.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#LocationNameAsString": {
@@ -28308,13 +28384,13 @@
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>The class of storage used to store the object.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
+            "smithy.api#documentation": "<p>The class of storage used to store the object.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
           }
         },
         "Owner": {
           "target": "com.amazonaws.s3#Owner",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the owner of the object that is part of the multipart upload. </p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The bucket owner is returned as the object owner for all the objects.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Specifies the owner of the object that is part of the multipart upload. </p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The bucket owner is\n            returned as the object owner for all the objects.</p>\n         </note>"
           }
         },
         "Initiator": {
@@ -28394,18 +28470,18 @@
         "NoncurrentDays": {
           "target": "com.amazonaws.s3#Days",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the number of days an object is noncurrent before Amazon S3 can perform the\n         associated action. The value must be a non-zero positive integer. For information about the\n         noncurrent days calculations, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#non-current-days-calculations\">How\n            Amazon S3 Calculates When an Object Became Noncurrent</a> in the\n            <i>Amazon S3 User Guide</i>.</p>"
+            "smithy.api#documentation": "<p>Specifies the number of days an object is noncurrent before Amazon S3 can perform the\n         associated action. The value must be a non-zero positive integer. For information about the\n         noncurrent days calculations, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#non-current-days-calculations\">How\n            Amazon S3 Calculates When an Object Became Noncurrent</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>"
           }
         },
         "NewerNoncurrentVersions": {
           "target": "com.amazonaws.s3#VersionCount",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies how many noncurrent versions Amazon S3 will retain. You can specify up to 100\n         noncurrent versions to retain. Amazon S3 will permanently delete any additional noncurrent\n         versions beyond the specified number to retain. For more information about noncurrent\n         versions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html\">Lifecycle configuration\n            elements</a> in the <i>Amazon S3 User Guide</i>.</p>"
+            "smithy.api#documentation": "<p>Specifies how many noncurrent versions Amazon S3 will retain. You can specify up to 100\n         noncurrent versions to retain. Amazon S3 will permanently delete any additional noncurrent\n         versions beyond the specified number to retain. For more information about noncurrent\n         versions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html\">Lifecycle configuration\n            elements</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>"
           }
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Specifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently\n         deletes the noncurrent object versions. You set this lifecycle configuration action on a\n         bucket that has versioning enabled (or suspended) to request that Amazon S3 delete noncurrent\n         object versions at a specific period in the object's lifetime.</p>"
+        "smithy.api#documentation": "<p>Specifies when noncurrent object versions expire. Upon expiration, Amazon S3 permanently\n         deletes the noncurrent object versions. You set this lifecycle configuration action on a\n         bucket that has versioning enabled (or suspended) to request that Amazon S3 delete noncurrent\n         object versions at a specific period in the object's lifetime.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#NoncurrentVersionTransition": {
@@ -28543,19 +28619,19 @@
         "StorageClass": {
           "target": "com.amazonaws.s3#ObjectStorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>The class of storage used to store the object.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
+            "smithy.api#documentation": "<p>The class of storage used to store the object.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
           }
         },
         "Owner": {
           "target": "com.amazonaws.s3#Owner",
           "traits": {
-            "smithy.api#documentation": "<p>The owner of the object</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The bucket owner is returned as the object owner.</p>\n         </note>"
+            "smithy.api#documentation": "<p>The owner of the object</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - The bucket owner is\n            returned as the object owner.</p>\n         </note>"
           }
         },
         "RestoreStatus": {
           "target": "com.amazonaws.s3#RestoreStatus",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the restoration status of an object. Objects in certain storage classes must\n         be restored before they can be retrieved. For more information about these storage classes\n         and how to work with archived objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/archived-objects.html\"> Working with archived\n            objects</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Specifies the restoration status of an object. Objects in certain storage classes must\n         be restored before they can be retrieved. For more information about these storage classes\n         and how to work with archived objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/archived-objects.html\"> Working with archived\n            objects</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
           }
         }
       },
@@ -28675,6 +28751,24 @@
           "traits": {
             "smithy.api#documentation": "<p>Version ID for the specific version of the object to delete.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
           }
+        },
+        "ETag": {
+          "target": "com.amazonaws.s3#ETag",
+          "traits": {
+            "smithy.api#documentation": "<p>An entity tag (ETag) is an identifier assigned by a web server to a specific version of a resource found at a URL.\n         This header field makes the request method conditional on <code>ETags</code>. </p>\n         <note>\n            <p>Entity tags (ETags) for S3 Express One Zone are random alphanumeric strings unique to the object. </p>\n         </note>"
+          }
+        },
+        "LastModifiedTime": {
+          "target": "com.amazonaws.s3#LastModifiedTime",
+          "traits": {
+            "smithy.api#documentation": "<p>If present, the objects are deleted only if its modification times matches the provided <code>Timestamp</code>. \n      </p>\n         <note>\n            <p>This functionality is only supported for directory buckets.</p>\n         </note>"
+          }
+        },
+        "Size": {
+          "target": "com.amazonaws.s3#Size",
+          "traits": {
+            "smithy.api#documentation": "<p>If present, the objects are deleted only if its size matches the provided size in bytes. </p>\n         <note>\n            <p>This functionality is only supported for directory buckets.</p>\n         </note>"
+          }
         }
       },
       "traits": {
@@ -28875,7 +28969,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>The container element for object ownership for a bucket's ownership controls.</p>\n         <p>\n            <code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to the bucket\n         owner if the objects are uploaded with the <code>bucket-owner-full-control</code> canned\n         ACL.</p>\n         <p>\n            <code>ObjectWriter</code> - The uploading account will own the object if the object is uploaded with\n         the <code>bucket-owner-full-control</code> canned ACL.</p>\n         <p>\n            <code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no longer affect\n         permissions. The bucket owner automatically owns and has full control over every object in\n         the bucket. The bucket only accepts PUT requests that don't specify an ACL or specify bucket owner\n         full control ACLs (such as the predefined <code>bucket-owner-full-control</code> canned ACL or a custom ACL \n         in XML format that grants the same permissions).</p>\n         <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and ACLs are disabled. We recommend\n      keeping ACLs disabled, except in uncommon use cases where you must control access for each object individually. For more information about S3 Object Ownership, see\n      <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling ownership of objects and disabling ACLs for your bucket</a> in the <i>Amazon S3 User Guide</i>.\n      </p>\n         <note>\n            <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>\n         </note>"
+        "smithy.api#documentation": "<p>The container element for object ownership for a bucket's ownership controls.</p>\n         <p>\n            <code>BucketOwnerPreferred</code> - Objects uploaded to the bucket change ownership to\n         the bucket owner if the objects are uploaded with the\n            <code>bucket-owner-full-control</code> canned ACL.</p>\n         <p>\n            <code>ObjectWriter</code> - The uploading account will own the object if the object is\n         uploaded with the <code>bucket-owner-full-control</code> canned ACL.</p>\n         <p>\n            <code>BucketOwnerEnforced</code> - Access control lists (ACLs) are disabled and no\n         longer affect permissions. The bucket owner automatically owns and has full control over\n         every object in the bucket. The bucket only accepts PUT requests that don't specify an ACL\n         or specify bucket owner full control ACLs (such as the predefined\n            <code>bucket-owner-full-control</code> canned ACL or a custom ACL in XML format that\n         grants the same permissions).</p>\n         <p>By default, <code>ObjectOwnership</code> is set to <code>BucketOwnerEnforced</code> and\n         ACLs are disabled. We recommend keeping ACLs disabled, except in uncommon use cases where\n         you must control access for each object individually. For more information about S3 Object\n         Ownership, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling ownership of\n            objects and disabling ACLs for your bucket</a> in the\n            <i>Amazon S3 User Guide</i>. </p>\n         <note>\n            <p>This functionality is not supported for directory buckets. Directory buckets use the bucket owner enforced setting for S3 Object Ownership.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#ObjectPart": {
@@ -29302,12 +29396,12 @@
         "PartitionDateSource": {
           "target": "com.amazonaws.s3#PartitionDateSource",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the partition date source for the partitioned prefix.\n         <code>PartitionDateSource</code> can be <code>EventTime</code> or\n         <code>DeliveryTime</code>.</p>\n         <p>For <code>DeliveryTime</code>, the time in the log file names corresponds to the\n         delivery time for the log files. </p>\n         <p> For <code>EventTime</code>, The logs delivered are for a specific day only. The year,\n         month, and day correspond to the day on which the event occurred, and the hour, minutes and\n         seconds are set to 00 in the key.</p>"
+            "smithy.api#documentation": "<p>Specifies the partition date source for the partitioned prefix.\n            <code>PartitionDateSource</code> can be <code>EventTime</code> or\n            <code>DeliveryTime</code>.</p>\n         <p>For <code>DeliveryTime</code>, the time in the log file names corresponds to the\n         delivery time for the log files. </p>\n         <p> For <code>EventTime</code>, The logs delivered are for a specific day only. The year,\n         month, and day correspond to the day on which the event occurred, and the hour, minutes and\n         seconds are set to 00 in the key.</p>"
           }
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Amazon S3 keys for log objects are partitioned in the following format:</p>\n         <p>\n            <code>[DestinationPrefix][SourceAccountId]/[SourceRegion]/[SourceBucket]/[YYYY]/[MM]/[DD]/[YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]</code>\n         </p>\n         <p>PartitionedPrefix defaults to EventTime delivery when server access logs are delivered.</p>",
+        "smithy.api#documentation": "<p>Amazon S3 keys for log objects are partitioned in the following format:</p>\n         <p>\n            <code>[DestinationPrefix][SourceAccountId]/[SourceRegion]/[SourceBucket]/[YYYY]/[MM]/[DD]/[YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]</code>\n         </p>\n         <p>PartitionedPrefix defaults to EventTime delivery when server access logs are\n         delivered.</p>",
         "smithy.api#xmlName": "PartitionedPrefix"
       }
     },
@@ -29508,7 +29602,7 @@
         "aws.protocols#httpChecksum": {
           "requestAlgorithmMember": "ChecksumAlgorithm"
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a\n         bucket-level feature that enables you to perform faster data transfers to Amazon S3.</p>\n         <p> To use this operation, you must have permission to perform the\n            <code>s3:PutAccelerateConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p> The Transfer Acceleration state of a bucket can be set to one of the following two\n         values:</p>\n         <ul>\n            <li>\n               <p> Enabled – Enables accelerated data transfers to the bucket.</p>\n            </li>\n            <li>\n               <p> Suspended – Disables accelerated data transfers to the bucket.</p>\n            </li>\n         </ul>\n         <p>The <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAccelerateConfiguration.html\">GetBucketAccelerateConfiguration</a> action returns the transfer acceleration state\n         of a bucket.</p>\n         <p>After setting the Transfer Acceleration state of a bucket to Enabled, it might take up\n         to thirty minutes before the data transfer rates to the bucket increase.</p>\n         <p> The name of the bucket used for Transfer Acceleration must be DNS-compliant and must\n         not contain periods (\".\").</p>\n         <p> For more information about transfer acceleration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer\n         Acceleration</a>.</p>\n         <p>The following operations are related to\n         <code>PutBucketAccelerateConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAccelerateConfiguration.html\">GetBucketAccelerateConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a\n         bucket-level feature that enables you to perform faster data transfers to Amazon S3.</p>\n         <p> To use this operation, you must have permission to perform the\n            <code>s3:PutAccelerateConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p> The Transfer Acceleration state of a bucket can be set to one of the following two\n         values:</p>\n         <ul>\n            <li>\n               <p> Enabled – Enables accelerated data transfers to the bucket.</p>\n            </li>\n            <li>\n               <p> Suspended – Disables accelerated data transfers to the bucket.</p>\n            </li>\n         </ul>\n         <p>The <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAccelerateConfiguration.html\">GetBucketAccelerateConfiguration</a> action returns the transfer acceleration state\n         of a bucket.</p>\n         <p>After setting the Transfer Acceleration state of a bucket to Enabled, it might take up\n         to thirty minutes before the data transfer rates to the bucket increase.</p>\n         <p> The name of the bucket used for Transfer Acceleration must be DNS-compliant and must\n         not contain periods (\".\").</p>\n         <p> For more information about transfer acceleration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html\">Transfer\n         Acceleration</a>.</p>\n         <p>The following operations are related to\n         <code>PutBucketAccelerateConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAccelerateConfiguration.html\">GetBucketAccelerateConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?accelerate",
@@ -29576,7 +29670,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets the permissions on an existing bucket using access control lists (ACL). For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. To set the ACL of a\n         bucket, you must have the <code>WRITE_ACP</code> permission.</p>\n         <p>You can use one of the following two ways to set a bucket's permissions:</p>\n         <ul>\n            <li>\n               <p>Specify the ACL in the request body</p>\n            </li>\n            <li>\n               <p>Specify permissions using request headers</p>\n            </li>\n         </ul>\n         <note>\n            <p>You cannot specify access permission using both the body and the request\n            headers.</p>\n         </note>\n         <p>Depending on your application needs, you may choose to set the ACL on a bucket using\n         either the request body or the headers. For example, if you have an existing application\n         that updates a bucket ACL using the request body, then you can continue to use that\n         approach.</p>\n         <important>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs\n            are disabled and no longer affect permissions. You must use policies to grant access to\n            your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return\n            the <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are\n            still supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling object\n               ownership</a> in the <i>Amazon S3 User Guide</i>.</p>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You can set access permissions by using one of the following methods:</p>\n               <ul>\n                  <li>\n                     <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. Amazon S3\n                        supports a set of predefined ACLs, known as <i>canned\n                        ACLs</i>. Each canned ACL has a predefined set of grantees and\n                        permissions. Specify the canned ACL name as the value of\n                           <code>x-amz-acl</code>. If you use this header, you cannot use other\n                        access control-specific headers in your request. For more information, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned\n                        ACL</a>.</p>\n                  </li>\n                  <li>\n                     <p>Specify access permissions explicitly with the\n                           <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>,\n                           <code>x-amz-grant-write-acp</code>, and\n                           <code>x-amz-grant-full-control</code> headers. When using these headers,\n                        you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3\n                        groups) who will receive the permission. If you use these ACL-specific\n                        headers, you cannot use the <code>x-amz-acl</code> header to set a canned\n                        ACL. These parameters map to the set of permissions that Amazon S3 supports in an\n                        ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n                           Overview</a>.</p>\n                     <p>You specify each grantee as a type=value pair, where the type is one of\n                        the following:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>id</code> – if the value specified is the canonical user ID\n                              of an Amazon Web Services account</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>uri</code> – if you are granting permissions to a predefined\n                              group</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>emailAddress</code> – if the value specified is the email\n                              address of an Amazon Web Services account</p>\n                           <note>\n                              <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                              <ul>\n                                 <li>\n                                    <p>US East (N. Virginia)</p>\n                                 </li>\n                                 <li>\n                                    <p>US West (N. California)</p>\n                                 </li>\n                                 <li>\n                                    <p> US West (Oregon)</p>\n                                 </li>\n                                 <li>\n                                    <p> Asia Pacific (Singapore)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Sydney)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Tokyo)</p>\n                                 </li>\n                                 <li>\n                                    <p>Europe (Ireland)</p>\n                                 </li>\n                                 <li>\n                                    <p>South America (São Paulo)</p>\n                                 </li>\n                              </ul>\n                              <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                           </note>\n                        </li>\n                     </ul>\n                     <p>For example, the following <code>x-amz-grant-write</code> header grants\n                        create, overwrite, and delete objects permission to LogDelivery group\n                        predefined by Amazon S3 and two Amazon Web Services accounts identified by their email\n                        addresses.</p>\n                     <p>\n                        <code>x-amz-grant-write:\n                           uri=\"http://acs.amazonaws.com/groups/s3/LogDelivery\", id=\"111122223333\",\n                           id=\"555566667777\" </code>\n                     </p>\n                  </li>\n               </ul>\n               <p>You can use either a canned ACL or specify access permissions explicitly. You\n                  cannot do both.</p>\n            </dd>\n            <dt>Grantee Values</dt>\n            <dd>\n               <p>You can specify the person (grantee) to whom you're assigning access rights\n                  (using request elements) in the following ways:</p>\n               <ul>\n                  <li>\n                     <p>By the person's ID:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"CanonicalUser\"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>\n                           </Grantee></code>\n                     </p>\n                     <p>DisplayName is optional and ignored in the request</p>\n                  </li>\n                  <li>\n                     <p>By URI:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"Group\"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>By Email address:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"AmazonCustomerByEmail\"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee></code>\n                     </p>\n                     <p>The grantee is resolved to the CanonicalUser and, in a response to a GET\n                        Object acl request, appears as the CanonicalUser. </p>\n                     <note>\n                        <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                        <ul>\n                           <li>\n                              <p>US East (N. Virginia)</p>\n                           </li>\n                           <li>\n                              <p>US West (N. California)</p>\n                           </li>\n                           <li>\n                              <p> US West (Oregon)</p>\n                           </li>\n                           <li>\n                              <p> Asia Pacific (Singapore)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Sydney)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Tokyo)</p>\n                           </li>\n                           <li>\n                              <p>Europe (Ireland)</p>\n                           </li>\n                           <li>\n                              <p>South America (São Paulo)</p>\n                           </li>\n                        </ul>\n                        <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAcl.html\">GetObjectAcl</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets the permissions on an existing bucket using access control lists (ACL). For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Using ACLs</a>. To set the ACL of a\n         bucket, you must have the <code>WRITE_ACP</code> permission.</p>\n         <p>You can use one of the following two ways to set a bucket's permissions:</p>\n         <ul>\n            <li>\n               <p>Specify the ACL in the request body</p>\n            </li>\n            <li>\n               <p>Specify permissions using request headers</p>\n            </li>\n         </ul>\n         <note>\n            <p>You cannot specify access permission using both the body and the request\n            headers.</p>\n         </note>\n         <p>Depending on your application needs, you may choose to set the ACL on a bucket using\n         either the request body or the headers. For example, if you have an existing application\n         that updates a bucket ACL using the request body, then you can continue to use that\n         approach.</p>\n         <important>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs\n            are disabled and no longer affect permissions. You must use policies to grant access to\n            your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return\n            the <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are\n            still supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling object\n               ownership</a> in the <i>Amazon S3 User Guide</i>.</p>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You can set access permissions by using one of the following methods:</p>\n               <ul>\n                  <li>\n                     <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. Amazon S3\n                        supports a set of predefined ACLs, known as <i>canned\n                        ACLs</i>. Each canned ACL has a predefined set of grantees and\n                        permissions. Specify the canned ACL name as the value of\n                           <code>x-amz-acl</code>. If you use this header, you cannot use other\n                        access control-specific headers in your request. For more information, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned\n                        ACL</a>.</p>\n                  </li>\n                  <li>\n                     <p>Specify access permissions explicitly with the\n                           <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>,\n                           <code>x-amz-grant-write-acp</code>, and\n                           <code>x-amz-grant-full-control</code> headers. When using these headers,\n                        you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3\n                        groups) who will receive the permission. If you use these ACL-specific\n                        headers, you cannot use the <code>x-amz-acl</code> header to set a canned\n                        ACL. These parameters map to the set of permissions that Amazon S3 supports in an\n                        ACL. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n                           Overview</a>.</p>\n                     <p>You specify each grantee as a type=value pair, where the type is one of\n                        the following:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>id</code> – if the value specified is the canonical user ID\n                              of an Amazon Web Services account</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>uri</code> – if you are granting permissions to a predefined\n                              group</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>emailAddress</code> – if the value specified is the email\n                              address of an Amazon Web Services account</p>\n                           <note>\n                              <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                              <ul>\n                                 <li>\n                                    <p>US East (N. Virginia)</p>\n                                 </li>\n                                 <li>\n                                    <p>US West (N. California)</p>\n                                 </li>\n                                 <li>\n                                    <p> US West (Oregon)</p>\n                                 </li>\n                                 <li>\n                                    <p> Asia Pacific (Singapore)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Sydney)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Tokyo)</p>\n                                 </li>\n                                 <li>\n                                    <p>Europe (Ireland)</p>\n                                 </li>\n                                 <li>\n                                    <p>South America (São Paulo)</p>\n                                 </li>\n                              </ul>\n                              <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                           </note>\n                        </li>\n                     </ul>\n                     <p>For example, the following <code>x-amz-grant-write</code> header grants\n                        create, overwrite, and delete objects permission to LogDelivery group\n                        predefined by Amazon S3 and two Amazon Web Services accounts identified by their email\n                        addresses.</p>\n                     <p>\n                        <code>x-amz-grant-write:\n                           uri=\"http://acs.amazonaws.com/groups/s3/LogDelivery\", id=\"111122223333\",\n                           id=\"555566667777\" </code>\n                     </p>\n                  </li>\n               </ul>\n               <p>You can use either a canned ACL or specify access permissions explicitly. You\n                  cannot do both.</p>\n            </dd>\n            <dt>Grantee Values</dt>\n            <dd>\n               <p>You can specify the person (grantee) to whom you're assigning access rights\n                  (using request elements) in the following ways:</p>\n               <ul>\n                  <li>\n                     <p>By the person's ID:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"CanonicalUser\"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>\n                           </Grantee></code>\n                     </p>\n                     <p>DisplayName is optional and ignored in the request</p>\n                  </li>\n                  <li>\n                     <p>By URI:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"Group\"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>By Email address:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"AmazonCustomerByEmail\"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee></code>\n                     </p>\n                     <p>The grantee is resolved to the CanonicalUser and, in a response to a GET\n                        Object acl request, appears as the CanonicalUser. </p>\n                     <note>\n                        <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                        <ul>\n                           <li>\n                              <p>US East (N. Virginia)</p>\n                           </li>\n                           <li>\n                              <p>US West (N. California)</p>\n                           </li>\n                           <li>\n                              <p> US West (Oregon)</p>\n                           </li>\n                           <li>\n                              <p> Asia Pacific (Singapore)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Sydney)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Tokyo)</p>\n                           </li>\n                           <li>\n                              <p>Europe (Ireland)</p>\n                           </li>\n                           <li>\n                              <p>South America (São Paulo)</p>\n                           </li>\n                        </ul>\n                        <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectAcl.html\">GetObjectAcl</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Put bucket acl",
@@ -29699,7 +29793,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets an analytics configuration for the bucket (specified by the analytics configuration\n         ID). You can have up to 1,000 analytics configurations per bucket.</p>\n         <p>You can choose to have storage class analysis export analysis reports sent to a\n         comma-separated values (CSV) flat file. See the <code>DataExport</code> request element.\n         Reports are updated daily and are based on the object filters that you configure. When\n         selecting data export, you specify a destination bucket and an optional destination prefix\n         where the file is written. You can export the data to a destination bucket in a different\n         account. However, the destination bucket must be in the same Region as the bucket that you\n         are making the PUT analytics configuration to. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3\n            Analytics – Storage Class Analysis</a>. </p>\n         <important>\n            <p>You must create a bucket policy on the destination bucket where the exported file is\n            written to grant permissions to Amazon S3 to write objects to the bucket. For an example\n            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>\n         </important>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>\n            <code>PutBucketAnalyticsConfiguration</code> has the following special errors:</p>\n         <ul>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>HTTP Error: HTTP 400 Bad Request</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Code: InvalidArgument</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: Invalid argument.</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>HTTP Error: HTTP 400 Bad Request</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Code: TooManyConfigurations</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: You are attempting to create a new configuration but have\n                        already reached the 1,000-configuration limit.</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>HTTP Error: HTTP 403 Forbidden</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Code: AccessDenied</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: You are not the owner of the specified bucket, or you do\n                        not have the s3:PutAnalyticsConfiguration bucket permission to set the\n                        configuration on the bucket.</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n         <p>The following operations are related to\n         <code>PutBucketAnalyticsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAnalyticsConfiguration.html\">GetBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketAnalyticsConfiguration.html\">DeleteBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html\">ListBucketAnalyticsConfigurations</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets an analytics configuration for the bucket (specified by the analytics configuration\n         ID). You can have up to 1,000 analytics configurations per bucket.</p>\n         <p>You can choose to have storage class analysis export analysis reports sent to a\n         comma-separated values (CSV) flat file. See the <code>DataExport</code> request element.\n         Reports are updated daily and are based on the object filters that you configure. When\n         selecting data export, you specify a destination bucket and an optional destination prefix\n         where the file is written. You can export the data to a destination bucket in a different\n         account. However, the destination bucket must be in the same Region as the bucket that you\n         are making the PUT analytics configuration to. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html\">Amazon S3\n            Analytics – Storage Class Analysis</a>. </p>\n         <important>\n            <p>You must create a bucket policy on the destination bucket where the exported file is\n            written to grant permissions to Amazon S3 to write objects to the bucket. For an example\n            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>\n         </important>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission\n         by default. The bucket owner can grant this permission to others. For more information\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>\n            <code>PutBucketAnalyticsConfiguration</code> has the following special errors:</p>\n         <ul>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>HTTP Error: HTTP 400 Bad Request</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Code: InvalidArgument</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: Invalid argument.</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>HTTP Error: HTTP 400 Bad Request</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Code: TooManyConfigurations</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: You are attempting to create a new configuration but have\n                        already reached the 1,000-configuration limit.</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>HTTP Error: HTTP 403 Forbidden</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Code: AccessDenied</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: You are not the owner of the specified bucket, or you do\n                        not have the s3:PutAnalyticsConfiguration bucket permission to set the\n                        configuration on the bucket.</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n         <p>The following operations are related to\n         <code>PutBucketAnalyticsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAnalyticsConfiguration.html\">GetBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketAnalyticsConfiguration.html\">DeleteBucketAnalyticsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketAnalyticsConfigurations.html\">ListBucketAnalyticsConfigurations</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?analytics",
@@ -29768,7 +29862,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists,\n         Amazon S3 replaces it.</p>\n         <p>To use this operation, you must be allowed to perform the <code>s3:PutBucketCORS</code>\n         action. By default, the bucket owner has this permission and can grant it to others.</p>\n         <p>You set this configuration on a bucket so that the bucket can service cross-origin\n         requests. For example, you might want to enable a request whose origin is\n            <code>http://www.example.com</code> to access your Amazon S3 bucket at\n            <code>my.example.bucket.com</code> by using the browser's <code>XMLHttpRequest</code>\n         capability.</p>\n         <p>To enable cross-origin resource sharing (CORS) on a bucket, you add the\n            <code>cors</code> subresource to the bucket. The <code>cors</code> subresource is an XML\n         document in which you configure rules that identify origins and the HTTP methods that can\n         be executed on your bucket. The document is limited to 64 KB in size. </p>\n         <p>When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a\n         bucket, it evaluates the <code>cors</code> configuration on the bucket and uses the first\n            <code>CORSRule</code> rule that matches the incoming browser request to enable a\n         cross-origin request. For a rule to match, the following conditions must be met:</p>\n         <ul>\n            <li>\n               <p>The request's <code>Origin</code> header must match <code>AllowedOrigin</code>\n               elements.</p>\n            </li>\n            <li>\n               <p>The request method (for example, GET, PUT, HEAD, and so on) or the\n                  <code>Access-Control-Request-Method</code> header in case of a pre-flight\n                  <code>OPTIONS</code> request must be one of the <code>AllowedMethod</code>\n               elements. </p>\n            </li>\n            <li>\n               <p>Every header specified in the <code>Access-Control-Request-Headers</code> request\n               header of a pre-flight request must match an <code>AllowedHeader</code> element.\n            </p>\n            </li>\n         </ul>\n         <p> For more information about CORS, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\">Enabling Cross-Origin Resource Sharing</a> in\n         the <i>Amazon S3 User Guide</i>.</p>\n         <p>The following operations are related to <code>PutBucketCors</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketCors.html\">GetBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketCors.html\">DeleteBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTOPTIONSobject.html\">RESTOPTIONSobject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists,\n         Amazon S3 replaces it.</p>\n         <p>To use this operation, you must be allowed to perform the <code>s3:PutBucketCORS</code>\n         action. By default, the bucket owner has this permission and can grant it to others.</p>\n         <p>You set this configuration on a bucket so that the bucket can service cross-origin\n         requests. For example, you might want to enable a request whose origin is\n            <code>http://www.example.com</code> to access your Amazon S3 bucket at\n            <code>my.example.bucket.com</code> by using the browser's <code>XMLHttpRequest</code>\n         capability.</p>\n         <p>To enable cross-origin resource sharing (CORS) on a bucket, you add the\n            <code>cors</code> subresource to the bucket. The <code>cors</code> subresource is an XML\n         document in which you configure rules that identify origins and the HTTP methods that can\n         be executed on your bucket. The document is limited to 64 KB in size. </p>\n         <p>When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a\n         bucket, it evaluates the <code>cors</code> configuration on the bucket and uses the first\n            <code>CORSRule</code> rule that matches the incoming browser request to enable a\n         cross-origin request. For a rule to match, the following conditions must be met:</p>\n         <ul>\n            <li>\n               <p>The request's <code>Origin</code> header must match <code>AllowedOrigin</code>\n               elements.</p>\n            </li>\n            <li>\n               <p>The request method (for example, GET, PUT, HEAD, and so on) or the\n                  <code>Access-Control-Request-Method</code> header in case of a pre-flight\n                  <code>OPTIONS</code> request must be one of the <code>AllowedMethod</code>\n               elements. </p>\n            </li>\n            <li>\n               <p>Every header specified in the <code>Access-Control-Request-Headers</code> request\n               header of a pre-flight request must match an <code>AllowedHeader</code> element.\n            </p>\n            </li>\n         </ul>\n         <p> For more information about CORS, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html\">Enabling Cross-Origin Resource Sharing</a> in\n         the <i>Amazon S3 User Guide</i>.</p>\n         <p>The following operations are related to <code>PutBucketCors</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketCors.html\">GetBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketCors.html\">DeleteBucketCors</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTOPTIONSobject.html\">RESTOPTIONSobject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To set cors configuration on a bucket.",
@@ -29870,7 +29964,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<p>This operation configures default encryption \n         and Amazon S3 Bucket Keys for an existing bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>By default, all buckets have a default encryption configuration that uses server-side\n         encryption with Amazon S3 managed keys (SSE-S3).</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b>\n                  </p>\n                  <ul>\n                     <li>\n                        <p>You can optionally configure default encryption\n                     for a bucket by using server-side encryption with Key Management Service (KMS) keys (SSE-KMS) or\n                     dual-layer server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). \n                     If you specify default encryption by using\n                     SSE-KMS, you can also configure <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html\">Amazon S3 Bucket\n                        Keys</a>. For information about the bucket default\n                     encryption feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html\">Amazon S3 Bucket Default Encryption</a>\n                     in the <i>Amazon S3 User Guide</i>.\n                  </p>\n                     </li>\n                     <li>\n                        <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>\n                     </li>\n                  </ul>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - You can optionally configure default encryption\n               for a bucket by using server-side encryption with Key Management Service (KMS) keys (SSE-KMS).</p>\n                  <ul>\n                     <li>\n                        <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 \n                     <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n                     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>\n                     </li>\n                     <li>\n                        <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 for the lifetime of the bucket. \nThe <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n</p>\n                     </li>\n                     <li>\n                        <p>S3 Bucket Keys are always enabled for <code>GET</code> and <code>PUT</code> operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-objects-Batch-Ops\">the Copy operation in Batch Operations</a>, or \n                            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-import-job\">the import jobs</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n                     </li>\n                     <li>\n                        <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>\n                     </li>\n                     <li>\n                        <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>\n                     </li>\n                  </ul>\n               </li>\n            </ul>\n         </note>\n         <important>\n            <p>If you're specifying a customer managed KMS key, we recommend using a fully qualified\n            KMS key ARN. If you use a KMS key alias instead, then KMS resolves the key within the\n            requester’s account. This behavior can result in data that's encrypted with a KMS key\n            that belongs to the requester, and not the bucket owner.</p>\n            <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\">\n               Authenticating Requests (Amazon Web Services Signature Version 4)</a>. </p>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The <code>s3:PutEncryptionConfiguration</code> permission is required in a policy. \n                        The bucket owner has this permission\n                        by default. The bucket owner can grant this permission to others. For more information\n                        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\n                              Access Permissions to Your Amazon S3 Resources</a> in the\n                        <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <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>\n                     <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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketEncryption</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketEncryption.html\">GetBucketEncryption</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketEncryption.html\">DeleteBucketEncryption</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>This operation configures default encryption and Amazon S3 Bucket Keys for an existing\n         bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>By default, all buckets have a default encryption configuration that uses server-side\n         encryption with Amazon S3 managed keys (SSE-S3).</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b>\n                  </p>\n                  <ul>\n                     <li>\n                        <p>You can optionally configure default encryption for a bucket by using\n                        server-side encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer\n                        server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). If you specify\n                        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\n                           Bucket Keys</a>. For information about the bucket default encryption\n                        feature, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html\">Amazon S3 Bucket Default\n                           Encryption</a> in the <i>Amazon S3 User Guide</i>. </p>\n                     </li>\n                     <li>\n                        <p>If you use PutBucketEncryption to set your <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html\">default bucket\n                           encryption</a> to SSE-KMS, you should verify that your KMS key ID\n                        is correct. Amazon S3 doesn't validate the KMS key ID provided in\n                        PutBucketEncryption requests.</p>\n                     </li>\n                  </ul>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets </b> - You can\n                  optionally configure default encryption for a bucket by using server-side\n                  encryption with Key Management Service (KMS) keys (SSE-KMS).</p>\n                  <ul>\n                     <li>\n                        <p>We recommend that the bucket's default encryption uses the desired\n                        encryption configuration and you don't override the bucket default\n                        encryption in your <code>CreateSession</code> requests or <code>PUT</code>\n                        object requests. Then, new objects are automatically encrypted with the\n                        desired encryption settings.\n                        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>\n                     </li>\n                     <li>\n                        <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 for the lifetime of the bucket. \nThe <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n</p>\n                     </li>\n                     <li>\n                        <p>S3 Bucket Keys are always enabled for <code>GET</code> and <code>PUT</code> operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-objects-Batch-Ops\">the Copy operation in Batch Operations</a>, or \n                            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-import-job\">the import jobs</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n                     </li>\n                     <li>\n                        <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>\n                     </li>\n                     <li>\n                        <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\n                        KMS key ID provided in PutBucketEncryption requests.</p>\n                     </li>\n                  </ul>\n               </li>\n            </ul>\n         </note>\n         <important>\n            <p>If you're specifying a customer managed KMS key, we recommend using a fully\n            qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the\n            key within the requester’s account. This behavior can result in data that's encrypted\n            with a KMS key that belongs to the requester, and not the bucket owner.</p>\n            <p>Also, this action requires Amazon Web Services Signature Version 4. For more information, see\n               <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html\"> Authenticating\n               Requests (Amazon Web Services Signature Version 4)</a>. </p>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                           <code>s3:PutEncryptionConfiguration</code> permission is required in a\n                        policy. The bucket owner has this permission by default. The bucket owner\n                        can grant this permission to others. For more information about permissions,\n                        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\n                           Permissions to Your Amazon S3 Resources</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        To grant access to this API operation, you must have the\n                           <code>s3express:PutEncryptionConfiguration</code> permission in\n                        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.\n                        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>\n                     <p>To set a directory bucket default encryption with SSE-KMS, you must also\n                        have the <code>kms:GenerateDataKey</code> and the <code>kms:Decrypt</code>\n                        permissions in IAM identity-based policies and KMS key policies for the\n                        target KMS key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketEncryption</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketEncryption.html\">GetBucketEncryption</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketEncryption.html\">DeleteBucketEncryption</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?encryption",
@@ -29940,7 +30034,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to\n         1,000 S3 Intelligent-Tiering configurations per bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>PutBucketIntelligentTieringConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketIntelligentTieringConfiguration.html\">DeleteBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketIntelligentTieringConfiguration.html\">GetBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketIntelligentTieringConfigurations.html\">ListBucketIntelligentTieringConfigurations</a>\n               </p>\n            </li>\n         </ul>\n         <note>\n            <p>You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically\n            move objects stored in the S3 Intelligent-Tiering storage class to the Archive Access\n            or Deep Archive Access tier.</p>\n         </note>\n         <p>\n            <code>PutBucketIntelligentTieringConfiguration</code> has the following special\n         errors:</p>\n         <dl>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> InvalidArgument</p>\n               <p>\n                  <i>Cause:</i> Invalid Argument</p>\n            </dd>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> TooManyConfigurations</p>\n               <p>\n                  <i>Cause:</i> You are attempting to create a new configuration\n                  but have already reached the 1,000-configuration limit. </p>\n            </dd>\n            <dt>HTTP 403 Forbidden Error</dt>\n            <dd>\n               <p>\n                  <i>Cause:</i> You are not the owner of the specified bucket, or\n                  you do not have the <code>s3:PutIntelligentTieringConfiguration</code> bucket\n                  permission to set the configuration on the bucket. </p>\n            </dd>\n         </dl>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to\n         1,000 S3 Intelligent-Tiering configurations per bucket.</p>\n         <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>\n         <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>\n         <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>\n         <p>Operations related to <code>PutBucketIntelligentTieringConfiguration</code> include: </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketIntelligentTieringConfiguration.html\">DeleteBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketIntelligentTieringConfiguration.html\">GetBucketIntelligentTieringConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketIntelligentTieringConfigurations.html\">ListBucketIntelligentTieringConfigurations</a>\n               </p>\n            </li>\n         </ul>\n         <note>\n            <p>You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically\n            move objects stored in the S3 Intelligent-Tiering storage class to the Archive Access\n            or Deep Archive Access tier.</p>\n         </note>\n         <p>\n            <code>PutBucketIntelligentTieringConfiguration</code> has the following special\n         errors:</p>\n         <dl>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> InvalidArgument</p>\n               <p>\n                  <i>Cause:</i> Invalid Argument</p>\n            </dd>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> TooManyConfigurations</p>\n               <p>\n                  <i>Cause:</i> You are attempting to create a new configuration\n                  but have already reached the 1,000-configuration limit. </p>\n            </dd>\n            <dt>HTTP 403 Forbidden Error</dt>\n            <dd>\n               <p>\n                  <i>Cause:</i> You are not the owner of the specified bucket, or\n                  you do not have the <code>s3:PutIntelligentTieringConfiguration</code> bucket\n                  permission to set the configuration on the bucket. </p>\n            </dd>\n         </dl>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?intelligent-tiering",
@@ -29998,7 +30092,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>This implementation of the <code>PUT</code> action adds an inventory configuration\n         (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory\n         configurations per bucket. </p>\n         <p>Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly\n         basis, and the results are published to a flat file. The bucket that is inventoried is\n         called the <i>source</i> bucket, and the bucket where the inventory flat file\n         is stored is called the <i>destination</i> bucket. The\n            <i>destination</i> bucket must be in the same Amazon Web Services Region as the\n            <i>source</i> bucket. </p>\n         <p>When you configure an inventory for a <i>source</i> bucket, you specify\n         the <i>destination</i> bucket where you want the inventory to be stored, and\n         whether to generate the inventory daily or weekly. You can also configure what object\n         metadata to include and whether to inventory all object versions or only current versions.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a> in the\n         Amazon S3 User Guide.</p>\n         <important>\n            <p>You must create a bucket policy on the <i>destination</i> bucket to\n            grant permissions to Amazon S3 to write objects to the bucket in the defined location. For an\n            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>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To use this operation, you must have permission to perform the\n                     <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this\n                  permission by default and can grant this permission to others. </p>\n               <p>The <code>s3:PutInventoryConfiguration</code> permission allows a user to\n                  create an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html\">S3 Inventory</a>\n                  report that includes all object metadata fields available and to specify the\n                  destination bucket to store the inventory. A user with read access to objects in\n                  the destination bucket can also access all object metadata fields that are\n                  available in the inventory report. </p>\n               <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\n                     <i>Amazon S3 User Guide</i>. For more information about the metadata\n                  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\n                  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\n                     <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n         </dl>\n         <p>\n            <code>PutBucketInventoryConfiguration</code> has the following special errors:</p>\n         <dl>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> InvalidArgument</p>\n               <p>\n                  <i>Cause:</i> Invalid Argument</p>\n            </dd>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> TooManyConfigurations</p>\n               <p>\n                  <i>Cause:</i> You are attempting to create a new configuration\n                  but have already reached the 1,000-configuration limit. </p>\n            </dd>\n            <dt>HTTP 403 Forbidden Error</dt>\n            <dd>\n               <p>\n                  <i>Cause:</i> You are not the owner of the specified bucket, or\n                  you do not have the <code>s3:PutInventoryConfiguration</code> bucket permission to\n                  set the configuration on the bucket. </p>\n            </dd>\n         </dl>\n         <p>The following operations are related to\n         <code>PutBucketInventoryConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketInventoryConfiguration.html\">GetBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketInventoryConfiguration.html\">DeleteBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketInventoryConfigurations.html\">ListBucketInventoryConfigurations</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>This implementation of the <code>PUT</code> action adds an inventory configuration\n         (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory\n         configurations per bucket. </p>\n         <p>Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly\n         basis, and the results are published to a flat file. The bucket that is inventoried is\n         called the <i>source</i> bucket, and the bucket where the inventory flat file\n         is stored is called the <i>destination</i> bucket. The\n            <i>destination</i> bucket must be in the same Amazon Web Services Region as the\n            <i>source</i> bucket. </p>\n         <p>When you configure an inventory for a <i>source</i> bucket, you specify\n         the <i>destination</i> bucket where you want the inventory to be stored, and\n         whether to generate the inventory daily or weekly. You can also configure what object\n         metadata to include and whether to inventory all object versions or only current versions.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html\">Amazon S3 Inventory</a> in the\n         Amazon S3 User Guide.</p>\n         <important>\n            <p>You must create a bucket policy on the <i>destination</i> bucket to\n            grant permissions to Amazon S3 to write objects to the bucket in the defined location. For an\n            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>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To use this operation, you must have permission to perform the\n                     <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this\n                  permission by default and can grant this permission to others. </p>\n               <p>The <code>s3:PutInventoryConfiguration</code> permission allows a user to\n                  create an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html\">S3 Inventory</a>\n                  report that includes all object metadata fields available and to specify the\n                  destination bucket to store the inventory. A user with read access to objects in\n                  the destination bucket can also access all object metadata fields that are\n                  available in the inventory report. </p>\n               <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\n                     <i>Amazon S3 User Guide</i>. For more information about the metadata\n                  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\n                  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\n                     <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n         </dl>\n         <p>\n            <code>PutBucketInventoryConfiguration</code> has the following special errors:</p>\n         <dl>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> InvalidArgument</p>\n               <p>\n                  <i>Cause:</i> Invalid Argument</p>\n            </dd>\n            <dt>HTTP 400 Bad Request Error</dt>\n            <dd>\n               <p>\n                  <i>Code:</i> TooManyConfigurations</p>\n               <p>\n                  <i>Cause:</i> You are attempting to create a new configuration\n                  but have already reached the 1,000-configuration limit. </p>\n            </dd>\n            <dt>HTTP 403 Forbidden Error</dt>\n            <dd>\n               <p>\n                  <i>Cause:</i> You are not the owner of the specified bucket, or\n                  you do not have the <code>s3:PutInventoryConfiguration</code> bucket permission to\n                  set the configuration on the bucket. </p>\n            </dd>\n         </dl>\n         <p>The following operations are related to\n         <code>PutBucketInventoryConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketInventoryConfiguration.html\">GetBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketInventoryConfiguration.html\">DeleteBucketInventoryConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketInventoryConfigurations.html\">ListBucketInventoryConfigurations</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?inventory",
@@ -30067,7 +30161,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle\n         configuration. Keep in mind that this will overwrite an existing lifecycle configuration,\n         so if you want to retain any configuration details, they must be included in the new\n         lifecycle configuration. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\">Managing\n            your storage lifecycle</a>.</p>\n         <dl>\n            <dt>Rules</dt>\n            <dd>\n               <p>You specify the lifecycle configuration in your request body. The lifecycle\n                  configuration is specified as XML consisting of one or more rules. An Amazon S3\n                  Lifecycle configuration can have up to 1,000 rules. This limit is not adjustable.</p>\n               <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.\n                     For the related API description, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html\">PutBucketLifecycle</a>.</p>\n               <p>A lifecycle rule consists of the following:</p>\n               <ul>\n                  <li>\n                     <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>\n                  </li>\n                  <li>\n                     <p>A status indicating whether the rule is in effect.</p>\n                  </li>\n                  <li>\n                     <p>One or more lifecycle transition and expiration actions that you want\n                        Amazon S3 to perform on the objects identified by the filter. If the state of\n                        your bucket is versioning-enabled or versioning-suspended, you can have many\n                        versions of the same object (one current version and zero or more noncurrent\n                        versions). Amazon S3 provides predefined actions that you can specify for current\n                        and noncurrent object versions.</p>\n                  </li>\n               </ul>\n               <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle\n                     Management</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html\">Lifecycle Configuration\n                     Elements</a>.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p>By default, all Amazon S3 resources are private, including buckets, objects, and\n                  related subresources (for example, lifecycle configuration and website\n                  configuration). Only the resource owner (that is, the Amazon Web Services account that created\n                  it) can access the resource. The resource owner can optionally grant access\n                  permissions to others by writing an access policy. For this operation, a user must\n                  get the <code>s3:PutLifecycleConfiguration</code> permission.</p>\n               <p>You can also explicitly deny permissions. An explicit deny also supersedes any\n                  other permissions. If you want to block users or accounts from removing or\n                  deleting objects from your bucket, you must deny them permissions for the\n                  following actions:</p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>s3:DeleteObject</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>s3:DeleteObjectVersion</code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>s3:PutLifecycleConfiguration</code>\n                     </p>\n                  </li>\n               </ul>\n               <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing Access\n                     Permissions to Your Amazon S3 Resources</a>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to\n         <code>PutBucketLifecycleConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html\">Examples of\n                  Lifecycle Configuration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html\">DeleteBucketLifecycle</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle\n         configuration. Keep in mind that this will overwrite an existing lifecycle configuration,\n         so if you want to retain any configuration details, they must be included in the new\n         lifecycle configuration. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\">Managing\n            your storage lifecycle</a>.</p>\n         <dl>\n            <dt>Rules</dt>\n            <dt>Permissions</dt>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>You specify the lifecycle configuration in your request body. The lifecycle\n                  configuration is specified as XML consisting of one or more rules. An Amazon S3\n                  Lifecycle configuration can have up to 1,000 rules. This limit is not\n                  adjustable.</p>\n               <p>Bucket lifecycle configuration supports specifying a lifecycle rule using an\n                  object key name prefix, one or more object tags, object size, or any combination\n                  of these. Accordingly, this section describes the latest API. The previous version\n                  of the API supported filtering based only on an object key name prefix, which is\n                  supported for backward compatibility for general purpose buckets. For the related\n                  API description, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html\">PutBucketLifecycle</a>. </p>\n               <note>\n                  <p>Lifecyle configurations for directory buckets only support expiring objects and\n                     cancelling multipart uploads. Expiring of versioned objects,transitions and tag\n                     filters are not supported.</p>\n               </note>\n               <p>A lifecycle rule consists of the following:</p>\n               <ul>\n                  <li>\n                     <p>A filter identifying a subset of objects to which the rule applies. The\n                        filter can be based on a key name prefix, object tags, object size, or any\n                        combination of these.</p>\n                  </li>\n                  <li>\n                     <p>A status indicating whether the rule is in effect.</p>\n                  </li>\n                  <li>\n                     <p>One or more lifecycle transition and expiration actions that you want\n                        Amazon S3 to perform on the objects identified by the filter. If the state of\n                        your bucket is versioning-enabled or versioning-suspended, you can have many\n                        versions of the same object (one current version and zero or more noncurrent\n                        versions). Amazon S3 provides predefined actions that you can specify for current\n                        and noncurrent object versions.</p>\n                  </li>\n               </ul>\n               <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle\n                     Management</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html\">Lifecycle Configuration\n                     Elements</a>.</p>\n            </dd>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - By\n                        default, all Amazon S3 resources are private, including buckets, objects, and\n                        related subresources (for example, lifecycle configuration and website\n                        configuration). Only the resource owner (that is, the Amazon Web Services account that\n                        created it) can access the resource. The resource owner can optionally grant\n                        access permissions to others by writing an access policy. For this\n                        operation, a user must have the <code>s3:PutLifecycleConfiguration</code>\n                        permission.</p>\n                     <p>You can also explicitly deny permissions. An explicit deny also\n                        supersedes any other permissions. If you want to block users or accounts\n                        from removing or deleting objects from your bucket, you must deny them\n                        permissions for the following actions:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>s3:DeleteObject</code>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>s3:DeleteObjectVersion</code>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>s3:PutLifecycleConfiguration</code>\n                           </p>\n                           <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing\n                                 Access Permissions to Your Amazon S3 Resources</a>.</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n               <ul>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have the <code>s3express:PutLifecycleConfiguration</code>\n                        permission in an IAM identity-based policy to use this operation.\n                        Cross-account access to this API operation isn't supported. The resource\n                        owner can optionally grant access permissions to others by creating a role\n                        or user for them as long as they are within the same account as the owner\n                        and resource.</p>\n                     <p>For more information about directory bucket policies and permissions, see\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html\">Authorizing Regional endpoint APIs with IAM</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                     <note>\n                        <p>\n                           <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>\n                           </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host\n                  header syntax is\n                     <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n               <p>The following operations are related to\n                     <code>PutBucketLifecycleConfiguration</code>:</p>\n               <ul>\n                  <li>\n                     <p>\n                        <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html\">DeleteBucketLifecycle</a>\n                     </p>\n                  </li>\n               </ul>\n            </dd>\n         </dl>",
         "smithy.api#examples": [
           {
             "title": "Put bucket lifecycle",
@@ -30115,7 +30209,7 @@
         "TransitionDefaultMinimumObjectSize": {
           "target": "com.amazonaws.s3#TransitionDefaultMinimumObjectSize",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates which default minimum object size behavior is applied to the lifecycle configuration.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not transition to any storage class by default. </p>\n            </li>\n            <li>\n               <p>\n                  <code>varies_by_storage_class</code> - Objects smaller than 128 KB will transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes will prevent transitions smaller than 128 KB.\n         </p>\n            </li>\n         </ul>\n         <p>To customize the minimum object size for any transition you can add a filter that specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in the body of your transition rule.  Custom filters always take precedence over the default transition behavior.</p>",
+            "smithy.api#documentation": "<p>Indicates which default minimum object size behavior is applied to the lifecycle\n         configuration.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>\n         <ul>\n            <li>\n               <p>\n                  <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not\n               transition to any storage class by default. </p>\n            </li>\n            <li>\n               <p>\n                  <code>varies_by_storage_class</code> - Objects smaller than 128 KB will\n               transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By\n               default, all other storage classes will prevent transitions smaller than 128 KB.\n            </p>\n            </li>\n         </ul>\n         <p>To customize the minimum object size for any transition you can add a filter that\n         specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in\n         the body of your transition rule. Custom filters always take precedence over the default\n         transition behavior.</p>",
             "smithy.api#httpHeader": "x-amz-transition-default-minimum-object-size"
           }
         }
@@ -30156,14 +30250,14 @@
         "ExpectedBucketOwner": {
           "target": "com.amazonaws.s3#AccountId",
           "traits": {
-            "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>",
+            "smithy.api#documentation": "<p>The account ID of the expected bucket owner. If the account ID that you provide does not match the actual owner of the bucket, the request fails with the HTTP status code <code>403 Forbidden</code> (access denied).</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-expected-bucket-owner"
           }
         },
         "TransitionDefaultMinimumObjectSize": {
           "target": "com.amazonaws.s3#TransitionDefaultMinimumObjectSize",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates which default minimum object size behavior is applied to the lifecycle configuration.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not transition to any storage class by default. </p>\n            </li>\n            <li>\n               <p>\n                  <code>varies_by_storage_class</code> - Objects smaller than 128 KB will transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By default, all other storage classes will prevent transitions smaller than 128 KB.\n         </p>\n            </li>\n         </ul>\n         <p>To customize the minimum object size for any transition you can add a filter that specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in the body of your transition rule.  Custom filters always take precedence over the default transition behavior.</p>",
+            "smithy.api#documentation": "<p>Indicates which default minimum object size behavior is applied to the lifecycle\n         configuration.</p>\n         <note>\n            <p>This parameter applies to general purpose buckets only. It is not supported for\n            directory bucket lifecycle configurations.</p>\n         </note>\n         <ul>\n            <li>\n               <p>\n                  <code>all_storage_classes_128K</code> - Objects smaller than 128 KB will not\n               transition to any storage class by default. </p>\n            </li>\n            <li>\n               <p>\n                  <code>varies_by_storage_class</code> - Objects smaller than 128 KB will\n               transition to Glacier Flexible Retrieval or Glacier Deep Archive storage classes. By\n               default, all other storage classes will prevent transitions smaller than 128 KB.\n            </p>\n            </li>\n         </ul>\n         <p>To customize the minimum object size for any transition you can add a filter that\n         specifies a custom <code>ObjectSizeGreaterThan</code> or <code>ObjectSizeLessThan</code> in\n         the body of your transition rule. Custom filters always take precedence over the default\n         transition behavior.</p>",
             "smithy.api#httpHeader": "x-amz-transition-default-minimum-object-size"
           }
         }
@@ -30185,7 +30279,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Set the logging parameters for a bucket and to specify permissions for who can view and\n         modify the logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as\n         the source bucket. To set the logging status of a bucket, you must be the bucket\n         owner.</p>\n         <p>The bucket owner is automatically granted FULL_CONTROL to all logs. You use the\n            <code>Grantee</code> request element to grant access to other people. The\n            <code>Permissions</code> request element specifies the kind of access the grantee has to\n         the logs.</p>\n         <important>\n            <p>If the target bucket for log delivery uses the bucket owner enforced setting for S3\n            Object Ownership, you can't use the <code>Grantee</code> request element to grant access\n            to others. Permissions can only be granted using policies. For more information, see\n               <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\n               <i>Amazon S3 User Guide</i>.</p>\n         </important>\n         <dl>\n            <dt>Grantee Values</dt>\n            <dd>\n               <p>You can specify the person (grantee) to whom you're assigning access rights (by\n                  using request elements) in the following ways:</p>\n               <ul>\n                  <li>\n                     <p>By the person's ID:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"CanonicalUser\"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>\n                           </Grantee></code>\n                     </p>\n                     <p>\n                        <code>DisplayName</code> is optional and ignored in the request.</p>\n                  </li>\n                  <li>\n                     <p>By Email address:</p>\n                     <p>\n                        <code> <Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"AmazonCustomerByEmail\"><EmailAddress><>Grantees@email.com<></EmailAddress></Grantee></code>\n                     </p>\n                     <p>The grantee is resolved to the <code>CanonicalUser</code> and, in a\n                        response to a <code>GETObjectAcl</code> request, appears as the\n                        CanonicalUser.</p>\n                  </li>\n                  <li>\n                     <p>By URI:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"Group\"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>\n                     </p>\n                  </li>\n               </ul>\n            </dd>\n         </dl>\n         <p>To enable logging, you use <code>LoggingEnabled</code> and its children request\n         elements. To disable logging, you use an empty <code>BucketLoggingStatus</code> request\n         element:</p>\n         <p>\n            <code><BucketLoggingStatus xmlns=\"http://doc.s3.amazonaws.com/2006-03-01\"\n            /></code>\n         </p>\n         <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\n            <i>Amazon S3 User Guide</i>. </p>\n         <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\n         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>\n         <p>The following operations are related to <code>PutBucketLogging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLogging.html\">GetBucketLogging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Set the logging parameters for a bucket and to specify permissions for who can view and\n         modify the logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as\n         the source bucket. To set the logging status of a bucket, you must be the bucket\n         owner.</p>\n         <p>The bucket owner is automatically granted FULL_CONTROL to all logs. You use the\n            <code>Grantee</code> request element to grant access to other people. The\n            <code>Permissions</code> request element specifies the kind of access the grantee has to\n         the logs.</p>\n         <important>\n            <p>If the target bucket for log delivery uses the bucket owner enforced setting for S3\n            Object Ownership, you can't use the <code>Grantee</code> request element to grant access\n            to others. Permissions can only be granted using policies. For more information, see\n               <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\n               <i>Amazon S3 User Guide</i>.</p>\n         </important>\n         <dl>\n            <dt>Grantee Values</dt>\n            <dd>\n               <p>You can specify the person (grantee) to whom you're assigning access rights (by\n                  using request elements) in the following ways:</p>\n               <ul>\n                  <li>\n                     <p>By the person's ID:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"CanonicalUser\"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>\n                           </Grantee></code>\n                     </p>\n                     <p>\n                        <code>DisplayName</code> is optional and ignored in the request.</p>\n                  </li>\n                  <li>\n                     <p>By Email address:</p>\n                     <p>\n                        <code> <Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"AmazonCustomerByEmail\"><EmailAddress><>Grantees@email.com<></EmailAddress></Grantee></code>\n                     </p>\n                     <p>The grantee is resolved to the <code>CanonicalUser</code> and, in a\n                        response to a <code>GETObjectAcl</code> request, appears as the\n                        CanonicalUser.</p>\n                  </li>\n                  <li>\n                     <p>By URI:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"Group\"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>\n                     </p>\n                  </li>\n               </ul>\n            </dd>\n         </dl>\n         <p>To enable logging, you use <code>LoggingEnabled</code> and its children request\n         elements. To disable logging, you use an empty <code>BucketLoggingStatus</code> request\n         element:</p>\n         <p>\n            <code><BucketLoggingStatus xmlns=\"http://doc.s3.amazonaws.com/2006-03-01\"\n            /></code>\n         </p>\n         <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\n            <i>Amazon S3 User Guide</i>. </p>\n         <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\n         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>\n         <p>The following operations are related to <code>PutBucketLogging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLogging.html\">GetBucketLogging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Set logging configuration for a bucket",
@@ -30280,7 +30374,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets a metrics configuration (specified by the metrics configuration ID) for the bucket.\n         You can have up to 1,000 metrics configurations per bucket. If you're updating an existing\n         metrics configuration, note that this is a full replacement of the existing metrics\n         configuration. If you don't include the elements you want to keep, they are erased.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <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\n            Metrics with Amazon CloudWatch</a>.</p>\n         <p>The following operations are related to\n         <code>PutBucketMetricsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetricsConfiguration.html\">DeleteBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetricsConfiguration.html\">GetBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketMetricsConfigurations.html\">ListBucketMetricsConfigurations</a>\n               </p>\n            </li>\n         </ul>\n         <p>\n            <code>PutBucketMetricsConfiguration</code> has the following special error:</p>\n         <ul>\n            <li>\n               <p>Error code: <code>TooManyConfigurations</code>\n               </p>\n               <ul>\n                  <li>\n                     <p>Description: You are attempting to create a new configuration but have\n                     already reached the 1,000-configuration limit.</p>\n                  </li>\n                  <li>\n                     <p>HTTP Status Code: HTTP 400 Bad Request</p>\n                  </li>\n               </ul>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets a metrics configuration (specified by the metrics configuration ID) for the bucket.\n         You can have up to 1,000 metrics configurations per bucket. If you're updating an existing\n         metrics configuration, note that this is a full replacement of the existing metrics\n         configuration. If you don't include the elements you want to keep, they are erased.</p>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutMetricsConfiguration</code> action. The bucket owner has this permission by\n         default. The bucket owner can grant this permission to others. For more information about\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <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\n            Metrics with Amazon CloudWatch</a>.</p>\n         <p>The following operations are related to\n         <code>PutBucketMetricsConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetricsConfiguration.html\">DeleteBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetricsConfiguration.html\">GetBucketMetricsConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBucketMetricsConfigurations.html\">ListBucketMetricsConfigurations</a>\n               </p>\n            </li>\n         </ul>\n         <p>\n            <code>PutBucketMetricsConfiguration</code> has the following special error:</p>\n         <ul>\n            <li>\n               <p>Error code: <code>TooManyConfigurations</code>\n               </p>\n               <ul>\n                  <li>\n                     <p>Description: You are attempting to create a new configuration but have\n                     already reached the 1,000-configuration limit.</p>\n                  </li>\n                  <li>\n                     <p>HTTP Status Code: HTTP 400 Bad Request</p>\n                  </li>\n               </ul>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?metrics",
@@ -30345,7 +30439,7 @@
         "target": "smithy.api#Unit"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Enables notifications of specified events for a bucket. For more information about event\n         notifications, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Event\n         Notifications</a>.</p>\n         <p>Using this API, you can replace an existing notification configuration. The\n         configuration is an XML file that defines the event types that you want Amazon S3 to publish and\n         the destination where you want Amazon S3 to publish an event notification when it detects an\n         event of the specified type.</p>\n         <p>By default, your bucket has no event notifications configured. That is, the notification\n         configuration will be an empty <code>NotificationConfiguration</code>.</p>\n         <p>\n            <code><NotificationConfiguration></code>\n         </p>\n         <p>\n            <code></NotificationConfiguration></code>\n         </p>\n         <p>This action replaces the existing notification configuration with the configuration you\n         include in the request body.</p>\n         <p>After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification\n         Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and\n         that the bucket owner has permission to publish to it by sending a test notification. In\n         the case of Lambda destinations, Amazon S3 verifies that the Lambda function permissions\n         grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information,\n         see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Notifications for Amazon S3 Events</a>.</p>\n         <p>You can disable notifications by adding the empty NotificationConfiguration\n         element.</p>\n         <p>For more information about the number of event notification configurations that you can\n         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\n            General Reference</i>.</p>\n         <p>By default, only the bucket owner can configure notifications on a bucket. However,\n         bucket owners can use a bucket policy to grant permission to other users to set this\n         configuration with the required <code>s3:PutBucketNotification</code> permission.</p>\n         <note>\n            <p>The PUT notification is an atomic operation. For example, suppose your notification\n            configuration includes SNS topic, SQS queue, and Lambda function configurations. When\n            you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS\n            topic. If the message fails, the entire PUT action will fail, and Amazon S3 will not add the\n            configuration to your bucket.</p>\n         </note>\n         <p>If the configuration in the request body includes only one\n            <code>TopicConfiguration</code> specifying only the\n            <code>s3:ReducedRedundancyLostObject</code> event type, the response will also include\n         the <code>x-amz-sns-test-message-id</code> header containing the message ID of the test\n         notification sent to the topic.</p>\n         <p>The following action is related to\n         <code>PutBucketNotificationConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketNotificationConfiguration.html\">GetBucketNotificationConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Enables notifications of specified events for a bucket. For more information about event\n         notifications, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Event\n         Notifications</a>.</p>\n         <p>Using this API, you can replace an existing notification configuration. The\n         configuration is an XML file that defines the event types that you want Amazon S3 to publish and\n         the destination where you want Amazon S3 to publish an event notification when it detects an\n         event of the specified type.</p>\n         <p>By default, your bucket has no event notifications configured. That is, the notification\n         configuration will be an empty <code>NotificationConfiguration</code>.</p>\n         <p>\n            <code><NotificationConfiguration></code>\n         </p>\n         <p>\n            <code></NotificationConfiguration></code>\n         </p>\n         <p>This action replaces the existing notification configuration with the configuration you\n         include in the request body.</p>\n         <p>After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification\n         Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and\n         that the bucket owner has permission to publish to it by sending a test notification. In\n         the case of Lambda destinations, Amazon S3 verifies that the Lambda function permissions\n         grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information,\n         see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Notifications for Amazon S3 Events</a>.</p>\n         <p>You can disable notifications by adding the empty NotificationConfiguration\n         element.</p>\n         <p>For more information about the number of event notification configurations that you can\n         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\n            General Reference</i>.</p>\n         <p>By default, only the bucket owner can configure notifications on a bucket. However,\n         bucket owners can use a bucket policy to grant permission to other users to set this\n         configuration with the required <code>s3:PutBucketNotification</code> permission.</p>\n         <note>\n            <p>The PUT notification is an atomic operation. For example, suppose your notification\n            configuration includes SNS topic, SQS queue, and Lambda function configurations. When\n            you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS\n            topic. If the message fails, the entire PUT action will fail, and Amazon S3 will not add the\n            configuration to your bucket.</p>\n         </note>\n         <p>If the configuration in the request body includes only one\n            <code>TopicConfiguration</code> specifying only the\n            <code>s3:ReducedRedundancyLostObject</code> event type, the response will also include\n         the <code>x-amz-sns-test-message-id</code> header containing the message ID of the test\n         notification sent to the topic.</p>\n         <p>The following action is related to\n         <code>PutBucketNotificationConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketNotificationConfiguration.html\">GetBucketNotificationConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Set notification configuration for a bucket",
@@ -30428,7 +30522,7 @@
         "aws.protocols#httpChecksum": {
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Creates or modifies <code>OwnershipControls</code> for an Amazon S3 bucket. To use this\n         operation, you must have the <code>s3:PutBucketOwnershipControls</code> permission. For\n         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\n            policy</a>. </p>\n         <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\n            ownership</a>. </p>\n         <p>The following operations are related to <code>PutBucketOwnershipControls</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a>GetBucketOwnershipControls</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a>DeleteBucketOwnershipControls</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Creates or modifies <code>OwnershipControls</code> for an Amazon S3 bucket. To use this\n         operation, you must have the <code>s3:PutBucketOwnershipControls</code> permission. For\n         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\n            policy</a>. </p>\n         <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\n            ownership</a>. </p>\n         <p>The following operations are related to <code>PutBucketOwnershipControls</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a>GetBucketOwnershipControls</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a>DeleteBucketOwnershipControls</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?ownershipControls",
@@ -30496,7 +30590,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<p>Applies an Amazon S3 bucket policy to an Amazon S3 bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>If you are using an identity other than the\n                  root user of the Amazon Web Services account that owns the bucket, the calling identity must both have the\n                  <code>PutBucketPolicy</code> permissions on the specified bucket and belong to the\n                  bucket owner's account in order to use this operation.</p>\n               <p>If you don't have <code>PutBucketPolicy</code> permissions, Amazon S3 returns a <code>403\n                  Access Denied</code> error. If you have the correct permissions, but you're not using an\n                  identity that belongs to the bucket owner's account, Amazon S3 returns a <code>405 Method Not\n                     Allowed</code> error.</p>\n               <important>\n                  <p>To ensure that bucket owners don't inadvertently lock themselves out of their own\n                     buckets, the root principal in a bucket owner's Amazon Web Services account can perform the\n                     <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and\n                     <code>DeleteBucketPolicy</code> API actions, even if their bucket policy explicitly\n                     denies the root principal's access. Bucket owner root principals can only be blocked\n                     from performing these API actions by VPC endpoint policies and Amazon Web Services Organizations\n                     policies.</p>\n               </important>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The <code>s3:PutBucketPolicy</code> permission is required in a policy. \n                        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\n                           Policies</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Example bucket policies</dt>\n            <dd>\n               <p>\n                  <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>\n               <p>\n                  <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>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketPolicy</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Applies an Amazon S3 bucket policy to an Amazon S3 bucket.</p>\n         <note>\n            <p>\n               <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>\n               </code>. Virtual-hosted-style requests aren't supported. \nFor more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>If you are using an identity other than the root user of the Amazon Web Services account that\n                  owns the bucket, the calling identity must both have the\n                     <code>PutBucketPolicy</code> permissions on the specified bucket and belong to\n                  the bucket owner's account in order to use this operation.</p>\n               <p>If you don't have <code>PutBucketPolicy</code> permissions, Amazon S3 returns a\n                     <code>403 Access Denied</code> error. If you have the correct permissions, but\n                  you're not using an identity that belongs to the bucket owner's account, Amazon S3\n                  returns a <code>405 Method Not Allowed</code> error.</p>\n               <important>\n                  <p>To ensure that bucket owners don't inadvertently lock themselves out of\n                     their own buckets, the root principal in a bucket owner's Amazon Web Services account can\n                     perform the <code>GetBucketPolicy</code>, <code>PutBucketPolicy</code>, and\n                        <code>DeleteBucketPolicy</code> API actions, even if their bucket policy\n                     explicitly denies the root principal's access. Bucket owner root principals can\n                     only be blocked from performing these API actions by VPC endpoint policies and\n                     Amazon Web Services Organizations policies.</p>\n               </important>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                           <code>s3:PutBucketPolicy</code> permission is required in a policy. For\n                        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\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        To grant access to this API operation, you must have the\n                           <code>s3express:PutBucketPolicy</code> permission in\n                        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.\n                        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>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Example bucket policies</dt>\n            <dd>\n               <p>\n                  <b>General purpose buckets example bucket policies</b>\n                  - See <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html\">Bucket policy\n                     examples</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <p>\n                  <b>Directory bucket example bucket policies</b>\n                  - 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\n                     <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketPolicy</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Set bucket policy",
@@ -30557,7 +30651,7 @@
         "Policy": {
           "target": "com.amazonaws.s3#Policy",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket policy as a JSON document.</p>\n         <p>For directory buckets, the only IAM action supported in the bucket policy is <code>s3express:CreateSession</code>.</p>",
+            "smithy.api#documentation": "<p>The bucket policy as a JSON document.</p>\n         <p>For directory buckets, the only IAM action supported in the bucket policy is\n            <code>s3express:CreateSession</code>.</p>",
             "smithy.api#httpPayload": {},
             "smithy.api#required": {}
           }
@@ -30587,7 +30681,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p> Creates a replication configuration or replaces an existing one. For more information,\n         see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the <i>Amazon S3 User Guide</i>. </p>\n         <p>Specify the replication configuration in the request body. In the replication\n         configuration, you provide the name of the destination bucket or buckets where you want\n         Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your\n         behalf, and other relevant information. You can invoke this request for a specific\n         Amazon Web Services Region by using the \n         <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-requestedregion\">\n               <code>aws:RequestedRegion</code>\n            </a> condition key.</p>\n         <p>A replication configuration must include at least one rule, and can contain a maximum of\n         1,000. Each rule identifies a subset of objects to replicate by filtering the objects in\n         the source bucket. To choose additional subsets of objects to replicate, add a rule for\n         each subset.</p>\n         <p>To specify a subset of the objects in the source bucket to apply a replication rule to,\n         add the Filter element as a child of the Rule element. You can filter objects based on an\n         object key prefix, one or more object tags, or both. When you add the Filter element in the\n         configuration, you must also add the following elements:\n            <code>DeleteMarkerReplication</code>, <code>Status</code>, and\n         <code>Priority</code>.</p>\n         <note>\n            <p>If you are using an earlier version of the replication configuration, Amazon S3 handles\n            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>\n         </note>\n         <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>\n         <dl>\n            <dt>Handling Replication of Encrypted Objects</dt>\n            <dd>\n               <p>By default, Amazon S3 doesn't replicate objects that are stored at rest using\n                  server-side encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects,\n                  add the following: <code>SourceSelectionCriteria</code>,\n                     <code>SseKmsEncryptedObjects</code>, <code>Status</code>,\n                     <code>EncryptionConfiguration</code>, and <code>ReplicaKmsKeyID</code>. For\n                  information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-config-for-kms-objects.html\">Replicating\n                     Objects Created with SSE Using KMS keys</a>.</p>\n               <p>For information on <code>PutBucketReplication</code> errors, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ReplicationErrorCodeList\">List of\n                     replication-related error codes</a>\n               </p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To create a <code>PutBucketReplication</code> request, you must have\n                     <code>s3:PutReplicationConfiguration</code> permissions for the bucket.\n                  \n               </p>\n               <p>By default, a resource owner, in this case the Amazon Web Services account that created the\n                  bucket, can perform this operation. The resource owner can also grant others\n                  permissions to perform the operation. For more information about permissions, see\n                     <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in\n                     a Policy</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing Access\n                     Permissions to Your Amazon S3 Resources</a>.</p>\n               <note>\n                  <p>To perform this operation, the user or role performing the action must have\n                     the <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_passrole.html\">iam:PassRole</a>\n                     permission.</p>\n               </note>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketReplication</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketReplication.html\">GetBucketReplication</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketReplication.html\">DeleteBucketReplication</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p> Creates a replication configuration or replaces an existing one. For more information,\n         see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html\">Replication</a> in the <i>Amazon S3 User Guide</i>. </p>\n         <p>Specify the replication configuration in the request body. In the replication\n         configuration, you provide the name of the destination bucket or buckets where you want\n         Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your\n         behalf, and other relevant information. You can invoke this request for a specific Amazon Web Services\n         Region by using the <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html#condition-keys-requestedregion\">\n               <code>aws:RequestedRegion</code>\n            </a> condition key.</p>\n         <p>A replication configuration must include at least one rule, and can contain a maximum of\n         1,000. Each rule identifies a subset of objects to replicate by filtering the objects in\n         the source bucket. To choose additional subsets of objects to replicate, add a rule for\n         each subset.</p>\n         <p>To specify a subset of the objects in the source bucket to apply a replication rule to,\n         add the Filter element as a child of the Rule element. You can filter objects based on an\n         object key prefix, one or more object tags, or both. When you add the Filter element in the\n         configuration, you must also add the following elements:\n            <code>DeleteMarkerReplication</code>, <code>Status</code>, and\n         <code>Priority</code>.</p>\n         <note>\n            <p>If you are using an earlier version of the replication configuration, Amazon S3 handles\n            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>\n         </note>\n         <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>\n         <dl>\n            <dt>Handling Replication of Encrypted Objects</dt>\n            <dd>\n               <p>By default, Amazon S3 doesn't replicate objects that are stored at rest using\n                  server-side encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects,\n                  add the following: <code>SourceSelectionCriteria</code>,\n                     <code>SseKmsEncryptedObjects</code>, <code>Status</code>,\n                     <code>EncryptionConfiguration</code>, and <code>ReplicaKmsKeyID</code>. For\n                  information about replication configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/replication-config-for-kms-objects.html\">Replicating\n                     Objects Created with SSE Using KMS keys</a>.</p>\n               <p>For information on <code>PutBucketReplication</code> errors, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#ReplicationErrorCodeList\">List of\n                     replication-related error codes</a>\n               </p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To create a <code>PutBucketReplication</code> request, you must have\n                     <code>s3:PutReplicationConfiguration</code> permissions for the bucket.\n                  \n               </p>\n               <p>By default, a resource owner, in this case the Amazon Web Services account that created the\n                  bucket, can perform this operation. The resource owner can also grant others\n                  permissions to perform the operation. For more information about permissions, see\n                     <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in\n                     a Policy</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing Access\n                     Permissions to Your Amazon S3 Resources</a>.</p>\n               <note>\n                  <p>To perform this operation, the user or role performing the action must have\n                     the <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_passrole.html\">iam:PassRole</a>\n                     permission.</p>\n               </note>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutBucketReplication</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketReplication.html\">GetBucketReplication</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketReplication.html\">DeleteBucketReplication</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Set replication configuration on a bucket",
@@ -30690,7 +30784,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets the request payment configuration for a bucket. By default, the bucket owner pays\n         for downloads from the bucket. This configuration parameter enables the bucket owner (only)\n         to specify that the person requesting the download will be charged for the download. For\n         more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html\">Requester Pays\n         Buckets</a>.</p>\n         <p>The following operations are related to <code>PutBucketRequestPayment</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketRequestPayment.html\">GetBucketRequestPayment</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets the request payment configuration for a bucket. By default, the bucket owner pays\n         for downloads from the bucket. This configuration parameter enables the bucket owner (only)\n         to specify that the person requesting the download will be charged for the download. For\n         more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html\">Requester Pays\n         Buckets</a>.</p>\n         <p>The following operations are related to <code>PutBucketRequestPayment</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketRequestPayment.html\">GetBucketRequestPayment</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Set request payment configuration on a bucket.",
@@ -30777,7 +30871,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets the tags for a bucket.</p>\n         <p>Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this,\n         sign up to get your Amazon Web Services account bill with tag key values included. Then, to see the cost\n         of combined resources, organize your billing information according to resources with the\n         same tag key values. For example, you can tag several resources with a specific application\n         name, and then organize your billing information to see the total cost of that application\n         across several services. For more information, see <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html\">Cost Allocation and\n            Tagging</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/CostAllocTagging.html\">Using Cost Allocation in Amazon S3\n            Bucket Tags</a>.</p>\n         <note>\n            <p> When this operation sets the tags for a bucket, it will overwrite any current tags\n            the bucket already has. You cannot use this operation to add tags to an existing list of\n            tags.</p>\n         </note>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutBucketTagging</code> action. The bucket owner has this permission by default\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>\n            <code>PutBucketTagging</code> has the following special errors. For more Amazon S3 errors\n         see, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html\">Error\n            Responses</a>.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>InvalidTag</code> - The tag provided was not a valid tag. This error\n               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\n                  Cost Allocation in Amazon S3 Bucket Tags</a>.</p>\n            </li>\n            <li>\n               <p>\n                  <code>MalformedXML</code> - The XML provided does not match the\n               schema.</p>\n            </li>\n            <li>\n               <p>\n                  <code>OperationAborted</code> - A conflicting conditional action is\n               currently in progress against this resource. Please try again.</p>\n            </li>\n            <li>\n               <p>\n                  <code>InternalError</code> - The service was unable to apply the provided\n               tag to the bucket.</p>\n            </li>\n         </ul>\n         <p>The following operations are related to <code>PutBucketTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketTagging.html\">GetBucketTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketTagging.html\">DeleteBucketTagging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets the tags for a bucket.</p>\n         <p>Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this,\n         sign up to get your Amazon Web Services account bill with tag key values included. Then, to see the cost\n         of combined resources, organize your billing information according to resources with the\n         same tag key values. For example, you can tag several resources with a specific application\n         name, and then organize your billing information to see the total cost of that application\n         across several services. For more information, see <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html\">Cost Allocation and\n            Tagging</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/CostAllocTagging.html\">Using Cost Allocation in Amazon S3\n            Bucket Tags</a>.</p>\n         <note>\n            <p> When this operation sets the tags for a bucket, it will overwrite any current tags\n            the bucket already has. You cannot use this operation to add tags to an existing list of\n            tags.</p>\n         </note>\n         <p>To use this operation, you must have permissions to perform the\n            <code>s3:PutBucketTagging</code> action. The bucket owner has this permission by default\n         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\n            Access Permissions to Your Amazon S3 Resources</a>.</p>\n         <p>\n            <code>PutBucketTagging</code> has the following special errors. For more Amazon S3 errors\n         see, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html\">Error\n            Responses</a>.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>InvalidTag</code> - The tag provided was not a valid tag. This error\n               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\n                  Cost Allocation in Amazon S3 Bucket Tags</a>.</p>\n            </li>\n            <li>\n               <p>\n                  <code>MalformedXML</code> - The XML provided does not match the\n               schema.</p>\n            </li>\n            <li>\n               <p>\n                  <code>OperationAborted</code> - A conflicting conditional action is\n               currently in progress against this resource. Please try again.</p>\n            </li>\n            <li>\n               <p>\n                  <code>InternalError</code> - The service was unable to apply the provided\n               tag to the bucket.</p>\n            </li>\n         </ul>\n         <p>The following operations are related to <code>PutBucketTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketTagging.html\">GetBucketTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketTagging.html\">DeleteBucketTagging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Set tags on a bucket",
@@ -30873,7 +30967,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <note>\n            <p>When you enable versioning on a bucket for the first time, it might take a short\n            amount of time for the change to be fully propagated. We recommend that you wait for 15\n            minutes after enabling versioning before issuing write operations\n            (<code>PUT</code>\n            or\n            <code>DELETE</code>)\n            on objects in the bucket. </p>\n         </note>\n         <p>Sets the versioning state of an existing bucket.</p>\n         <p>You can set the versioning state with one of the following values:</p>\n         <p>\n            <b>Enabled</b>—Enables versioning for the objects in the\n         bucket. All objects added to the bucket receive a unique version ID.</p>\n         <p>\n            <b>Suspended</b>—Disables versioning for the objects in the\n         bucket. All objects added to the bucket receive the version ID null.</p>\n         <p>If the versioning state has never been set on a bucket, it has no versioning state; a\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a> request does not return a versioning state value.</p>\n         <p>In order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner\n         and want to enable MFA Delete in the bucket versioning configuration, you must include the\n            <code>x-amz-mfa request</code> header and the <code>Status</code> and the\n            <code>MfaDelete</code> request elements in a request to set the versioning state of the\n         bucket.</p>\n         <important>\n            <p>If you have an object expiration lifecycle configuration in your non-versioned bucket\n            and you want to maintain the same permanent delete behavior when you enable versioning,\n            you must add a noncurrent expiration policy. The noncurrent expiration lifecycle\n            configuration will manage the deletes of the noncurrent object versions in the\n            version-enabled bucket. (A version-enabled bucket maintains one current and zero or more\n            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>\n         </important>\n         <p>The following operations are related to <code>PutBucketVersioning</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <note>\n            <p>When you enable versioning on a bucket for the first time, it might take a short\n            amount of time for the change to be fully propagated. We recommend that you wait for 15\n            minutes after enabling versioning before issuing write operations (<code>PUT</code> or\n               <code>DELETE</code>) on objects in the bucket. </p>\n         </note>\n         <p>Sets the versioning state of an existing bucket.</p>\n         <p>You can set the versioning state with one of the following values:</p>\n         <p>\n            <b>Enabled</b>—Enables versioning for the objects in the\n         bucket. All objects added to the bucket receive a unique version ID.</p>\n         <p>\n            <b>Suspended</b>—Disables versioning for the objects in the\n         bucket. All objects added to the bucket receive the version ID null.</p>\n         <p>If the versioning state has never been set on a bucket, it has no versioning state; a\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a> request does not return a versioning state value.</p>\n         <p>In order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner\n         and want to enable MFA Delete in the bucket versioning configuration, you must include the\n            <code>x-amz-mfa request</code> header and the <code>Status</code> and the\n            <code>MfaDelete</code> request elements in a request to set the versioning state of the\n         bucket.</p>\n         <important>\n            <p>If you have an object expiration lifecycle configuration in your non-versioned bucket\n            and you want to maintain the same permanent delete behavior when you enable versioning,\n            you must add a noncurrent expiration policy. The noncurrent expiration lifecycle\n            configuration will manage the deletes of the noncurrent object versions in the\n            version-enabled bucket. (A version-enabled bucket maintains one current and zero or more\n            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>\n         </important>\n         <p>The following operations are related to <code>PutBucketVersioning</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html\">CreateBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucket.html\">DeleteBucket</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "Set versioning configuration on a bucket",
@@ -30968,7 +31062,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets the configuration of the website that is specified in the <code>website</code>\n         subresource. To configure a bucket as a website, you can add this subresource on the bucket\n         with website configuration information such as the file name of the index document and any\n         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>\n         <p>This PUT action requires the <code>S3:PutBucketWebsite</code> permission. By default,\n         only the bucket owner can configure the website attached to a bucket; however, bucket\n         owners can allow other users to set the website configuration by writing a bucket policy\n         that grants them the <code>S3:PutBucketWebsite</code> permission.</p>\n         <p>To redirect all website requests sent to the bucket's website endpoint, you add a\n         website configuration with the following elements. Because all requests are sent to another\n         website, you don't need to provide index document name for the bucket.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>WebsiteConfiguration</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>RedirectAllRequestsTo</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HostName</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Protocol</code>\n               </p>\n            </li>\n         </ul>\n         <p>If you want granular control over redirects, you can use the following elements to add\n         routing rules that describe conditions for redirecting requests and information about the\n         redirect destination. In this case, the website configuration must provide an index\n         document for the bucket, because some requests might not be redirected. </p>\n         <ul>\n            <li>\n               <p>\n                  <code>WebsiteConfiguration</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>IndexDocument</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Suffix</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>ErrorDocument</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>RoutingRules</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>RoutingRule</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Condition</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HttpErrorCodeReturnedEquals</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>KeyPrefixEquals</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Redirect</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Protocol</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HostName</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>ReplaceKeyPrefixWith</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>ReplaceKeyWith</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HttpRedirectCode</code>\n               </p>\n            </li>\n         </ul>\n         <p>Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more\n         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\n            Object Redirect</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>The maximum request length is limited to 128 KB.</p>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets the configuration of the website that is specified in the <code>website</code>\n         subresource. To configure a bucket as a website, you can add this subresource on the bucket\n         with website configuration information such as the file name of the index document and any\n         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>\n         <p>This PUT action requires the <code>S3:PutBucketWebsite</code> permission. By default,\n         only the bucket owner can configure the website attached to a bucket; however, bucket\n         owners can allow other users to set the website configuration by writing a bucket policy\n         that grants them the <code>S3:PutBucketWebsite</code> permission.</p>\n         <p>To redirect all website requests sent to the bucket's website endpoint, you add a\n         website configuration with the following elements. Because all requests are sent to another\n         website, you don't need to provide index document name for the bucket.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>WebsiteConfiguration</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>RedirectAllRequestsTo</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HostName</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Protocol</code>\n               </p>\n            </li>\n         </ul>\n         <p>If you want granular control over redirects, you can use the following elements to add\n         routing rules that describe conditions for redirecting requests and information about the\n         redirect destination. In this case, the website configuration must provide an index\n         document for the bucket, because some requests might not be redirected. </p>\n         <ul>\n            <li>\n               <p>\n                  <code>WebsiteConfiguration</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>IndexDocument</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Suffix</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>ErrorDocument</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Key</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>RoutingRules</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>RoutingRule</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Condition</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HttpErrorCodeReturnedEquals</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>KeyPrefixEquals</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Redirect</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>Protocol</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HostName</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>ReplaceKeyPrefixWith</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>ReplaceKeyWith</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>HttpRedirectCode</code>\n               </p>\n            </li>\n         </ul>\n         <p>Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more\n         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\n            Object Redirect</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>The maximum request length is limited to 128 KB.</p>",
         "smithy.api#examples": [
           {
             "title": "Set website configuration on a bucket",
@@ -31056,11 +31150,25 @@
       "output": {
         "target": "com.amazonaws.s3#PutObjectOutput"
       },
+      "errors": [
+        {
+          "target": "com.amazonaws.s3#EncryptionTypeMismatch"
+        },
+        {
+          "target": "com.amazonaws.s3#InvalidRequest"
+        },
+        {
+          "target": "com.amazonaws.s3#InvalidWriteOffset"
+        },
+        {
+          "target": "com.amazonaws.s3#TooManyParts"
+        }
+      ],
       "traits": {
         "aws.protocols#httpChecksum": {
           "requestAlgorithmMember": "ChecksumAlgorithm"
         },
-        "smithy.api#documentation": "<p>Adds an object to a bucket.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the\n               entire object to the bucket. You cannot use <code>PutObject</code> to only update a\n               single piece of metadata for an existing object. You must put the entire object with\n               updated metadata if you want to update some values.</p>\n               </li>\n               <li>\n                  <p>If your bucket uses the bucket owner enforced setting for Object Ownership, ACLs are disabled and no longer affect permissions. All\n                  objects written to the bucket by any account will be owned by the bucket owner.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <p>Amazon S3 is a distributed system. If it receives multiple write requests for the same object\n         simultaneously, it overwrites all but the last object written. However, Amazon S3 provides features that can modify this behavior:</p>\n         <ul>\n            <li>\n               <p>\n                  <b>S3 Object Lock</b> - To prevent objects from\n            being deleted or overwritten, you can use <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html\">Amazon S3 Object\n               Lock</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <note>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </note>\n            </li>\n            <li>\n               <p>\n                  <b>S3 Versioning</b> - When you enable\n            versioning for a bucket, if Amazon S3 receives multiple write requests for the same object\n            simultaneously, it stores all versions of the objects. For each write request that is made to the same object, Amazon S3 automatically generates a unique version ID\n            of that object being stored in Amazon S3. \n           You can retrieve, replace, or delete any version of the object. For more information about versioning, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html\">Adding Objects to\n               Versioning-Enabled Buckets</a> in the <i>Amazon S3\n                  User Guide</i>. For information about returning the versioning state\n            of a bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a>. </p>\n               <note>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </note>\n            </li>\n         </ul>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The following permissions are required in your policies when your \n                        <code>PutObject</code> request includes specific headers.</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:PutObject</code>\n                              </b> - To successfully complete the <code>PutObject</code> request, you must always have the <code>s3:PutObject</code> permission on a bucket to add an object\n                                 to it.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:PutObjectAcl</code>\n                              </b> - To successfully change the objects ACL of your <code>PutObject</code> request, you must have the <code>s3:PutObjectAcl</code>.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:PutObjectTagging</code>\n                              </b> - To successfully set the tag-set with your <code>PutObject</code> request, you\n                                 must have the <code>s3:PutObjectTagging</code>.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted with\n                        SSE-KMS, you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Data integrity with Content-MD5</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - To ensure that data is not corrupted traversing the network, use the\n                    <code>Content-MD5</code> header. When you use this header, Amazon S3 checks the object\n                    against the provided MD5 value and, if they do not match, Amazon S3 returns an error. Alternatively, when the object's ETag is its MD5 digest, \n                    you can calculate the MD5 while putting the object to Amazon S3 and compare the returned ETag to\n                    the calculated MD5 value.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> - This functionality is not supported for directory buckets.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>For more information about related Amazon S3 APIs, see the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Adds an object to a bucket.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added\n                  the entire object to the bucket. You cannot use <code>PutObject</code> to only\n                  update a single piece of metadata for an existing object. You must put the entire\n                  object with updated metadata if you want to update some values.</p>\n               </li>\n               <li>\n                  <p>If your bucket uses the bucket owner enforced setting for Object Ownership,\n                  ACLs are disabled and no longer affect permissions. All objects written to the\n                  bucket by any account will be owned by the bucket owner.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n                     </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n               </li>\n            </ul>\n         </note>\n         <p>Amazon S3 is a distributed system. If it receives multiple write requests for the same object\n         simultaneously, it overwrites all but the last object written. However, Amazon S3 provides\n         features that can modify this behavior:</p>\n         <ul>\n            <li>\n               <p>\n                  <b>S3 Object Lock</b> - To prevent objects from\n               being deleted or overwritten, you can use <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html\">Amazon S3 Object\n                  Lock</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <note>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </note>\n            </li>\n            <li>\n               <p>\n                  <b>S3 Versioning</b> - When you enable versioning\n               for a bucket, if Amazon S3 receives multiple write requests for the same object\n               simultaneously, it stores all versions of the objects. For each write request that is\n               made to the same object, Amazon S3 automatically generates a unique version ID of that\n               object being stored in Amazon S3. You can retrieve, replace, or delete any version of the\n               object. For more information about versioning, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html\">Adding\n                  Objects to Versioning-Enabled Buckets</a> in the <i>Amazon S3 User\n                  Guide</i>. For information about returning the versioning state of a\n               bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a>. </p>\n               <note>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </note>\n            </li>\n         </ul>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - The\n                        following permissions are required in your policies when your\n                           <code>PutObject</code> request includes specific headers.</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:PutObject</code>\n                              </b> -\n                              To successfully complete the <code>PutObject</code> request, you must\n                              always have the <code>s3:PutObject</code> permission on a bucket to\n                              add an object to it.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:PutObjectAcl</code>\n                              </b> - To successfully change the objects ACL of your\n                                 <code>PutObject</code> request, you must have the\n                                 <code>s3:PutObjectAcl</code>.</p>\n                        </li>\n                        <li>\n                           <p>\n                              <b>\n                                 <code>s3:PutObjectTagging</code>\n                              </b> - To successfully set the tag-set with your\n                                 <code>PutObject</code> request, you must have the\n                                 <code>s3:PutObjectTagging</code>.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted with SSE-KMS, you must also have the\n                           <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions\n                        in IAM identity-based policies and KMS key policies for the KMS\n                        key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Data integrity with Content-MD5</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - To ensure that\n                        data is not corrupted traversing the network, use the\n                           <code>Content-MD5</code> header. When you use this header, Amazon S3 checks\n                        the object against the provided MD5 value and, if they do not match, Amazon S3\n                        returns an error. Alternatively, when the object's ETag is its MD5 digest,\n                        you can calculate the MD5 while putting the object to Amazon S3 and compare the\n                        returned ETag to the calculated MD5 value.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket</b> -\n                        This functionality is not supported for directory buckets.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>For more information about related Amazon S3 APIs, see the following:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObject.html\">DeleteObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To create an object.",
@@ -31191,7 +31299,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Uses the <code>acl</code> subresource to set the access control list (ACL) permissions\n         for a new or existing object in an S3 bucket. You must have the <code>WRITE_ACP</code>\n         permission to set the ACL of an object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#permissions\">What\n            permissions can I grant?</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>Depending on your application needs, you can choose to set the ACL on an object using\n         either the request body or the headers. For example, if you have an existing application\n         that updates a bucket ACL using the request body, you can continue to use that approach.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         in the <i>Amazon S3 User Guide</i>.</p>\n         <important>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs\n            are disabled and no longer affect permissions. You must use policies to grant access to\n            your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return\n            the <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are\n            still supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling object\n               ownership</a> in the <i>Amazon S3 User Guide</i>.</p>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You can set access permissions using one of the following methods:</p>\n               <ul>\n                  <li>\n                     <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. Amazon S3\n                        supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has\n                        a predefined set of grantees and permissions. Specify the canned ACL name as\n                        the value of <code>x-amz-ac</code>l. If you use this header, you cannot use\n                        other access control-specific headers in your request. For more information,\n                        see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned\n                        ACL</a>.</p>\n                  </li>\n                  <li>\n                     <p>Specify access permissions explicitly with the\n                           <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>,\n                           <code>x-amz-grant-write-acp</code>, and\n                           <code>x-amz-grant-full-control</code> headers. When using these headers,\n                        you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3\n                        groups) who will receive the permission. If you use these ACL-specific\n                        headers, you cannot use <code>x-amz-acl</code> header to set a canned ACL.\n                        These parameters map to the set of permissions that Amazon S3 supports in an ACL.\n                        For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n                           Overview</a>.</p>\n                     <p>You specify each grantee as a type=value pair, where the type is one of\n                        the following:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>id</code> – if the value specified is the canonical user ID\n                              of an Amazon Web Services account</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>uri</code> – if you are granting permissions to a predefined\n                              group</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>emailAddress</code> – if the value specified is the email\n                              address of an Amazon Web Services account</p>\n                           <note>\n                              <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                              <ul>\n                                 <li>\n                                    <p>US East (N. Virginia)</p>\n                                 </li>\n                                 <li>\n                                    <p>US West (N. California)</p>\n                                 </li>\n                                 <li>\n                                    <p> US West (Oregon)</p>\n                                 </li>\n                                 <li>\n                                    <p> Asia Pacific (Singapore)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Sydney)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Tokyo)</p>\n                                 </li>\n                                 <li>\n                                    <p>Europe (Ireland)</p>\n                                 </li>\n                                 <li>\n                                    <p>South America (São Paulo)</p>\n                                 </li>\n                              </ul>\n                              <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                           </note>\n                        </li>\n                     </ul>\n                     <p>For example, the following <code>x-amz-grant-read</code> header grants\n                        list objects permission to the two Amazon Web Services accounts identified by their email\n                        addresses.</p>\n                     <p>\n                        <code>x-amz-grant-read: emailAddress=\"xyz@amazon.com\",\n                           emailAddress=\"abc@amazon.com\" </code>\n                     </p>\n                  </li>\n               </ul>\n               <p>You can use either a canned ACL or specify access permissions explicitly. You\n                  cannot do both.</p>\n            </dd>\n            <dt>Grantee Values</dt>\n            <dd>\n               <p>You can specify the person (grantee) to whom you're assigning access rights\n                  (using request elements) in the following ways:</p>\n               <ul>\n                  <li>\n                     <p>By the person's ID:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"CanonicalUser\"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>\n                           </Grantee></code>\n                     </p>\n                     <p>DisplayName is optional and ignored in the request.</p>\n                  </li>\n                  <li>\n                     <p>By URI:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"Group\"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>By Email address:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"AmazonCustomerByEmail\"><EmailAddress><>Grantees@email.com<></EmailAddress>lt;/Grantee></code>\n                     </p>\n                     <p>The grantee is resolved to the CanonicalUser and, in a response to a GET\n                        Object acl request, appears as the CanonicalUser.</p>\n                     <note>\n                        <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                        <ul>\n                           <li>\n                              <p>US East (N. Virginia)</p>\n                           </li>\n                           <li>\n                              <p>US West (N. California)</p>\n                           </li>\n                           <li>\n                              <p> US West (Oregon)</p>\n                           </li>\n                           <li>\n                              <p> Asia Pacific (Singapore)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Sydney)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Tokyo)</p>\n                           </li>\n                           <li>\n                              <p>Europe (Ireland)</p>\n                           </li>\n                           <li>\n                              <p>South America (São Paulo)</p>\n                           </li>\n                        </ul>\n                        <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Versioning</dt>\n            <dd>\n               <p>The ACL of an object is set at the object version level. By default, PUT sets\n                  the ACL of the current version of an object. To set the ACL of a different\n                  version, use the <code>versionId</code> subresource.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutObjectAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Uses the <code>acl</code> subresource to set the access control list (ACL) permissions\n         for a new or existing object in an S3 bucket. You must have the <code>WRITE_ACP</code>\n         permission to set the ACL of an object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#permissions\">What\n            permissions can I grant?</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>Depending on your application needs, you can choose to set the ACL on an object using\n         either the request body or the headers. For example, if you have an existing application\n         that updates a bucket ACL using the request body, you can continue to use that approach.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         in the <i>Amazon S3 User Guide</i>.</p>\n         <important>\n            <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs\n            are disabled and no longer affect permissions. You must use policies to grant access to\n            your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return\n            the <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are\n            still supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\">Controlling object\n               ownership</a> in the <i>Amazon S3 User Guide</i>.</p>\n         </important>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You can set access permissions using one of the following methods:</p>\n               <ul>\n                  <li>\n                     <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. Amazon S3\n                        supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has\n                        a predefined set of grantees and permissions. Specify the canned ACL name as\n                        the value of <code>x-amz-ac</code>l. If you use this header, you cannot use\n                        other access control-specific headers in your request. For more information,\n                        see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned\n                        ACL</a>.</p>\n                  </li>\n                  <li>\n                     <p>Specify access permissions explicitly with the\n                           <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>,\n                           <code>x-amz-grant-write-acp</code>, and\n                           <code>x-amz-grant-full-control</code> headers. When using these headers,\n                        you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3\n                        groups) who will receive the permission. If you use these ACL-specific\n                        headers, you cannot use <code>x-amz-acl</code> header to set a canned ACL.\n                        These parameters map to the set of permissions that Amazon S3 supports in an ACL.\n                        For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL)\n                           Overview</a>.</p>\n                     <p>You specify each grantee as a type=value pair, where the type is one of\n                        the following:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <code>id</code> – if the value specified is the canonical user ID\n                              of an Amazon Web Services account</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>uri</code> – if you are granting permissions to a predefined\n                              group</p>\n                        </li>\n                        <li>\n                           <p>\n                              <code>emailAddress</code> – if the value specified is the email\n                              address of an Amazon Web Services account</p>\n                           <note>\n                              <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                              <ul>\n                                 <li>\n                                    <p>US East (N. Virginia)</p>\n                                 </li>\n                                 <li>\n                                    <p>US West (N. California)</p>\n                                 </li>\n                                 <li>\n                                    <p> US West (Oregon)</p>\n                                 </li>\n                                 <li>\n                                    <p> Asia Pacific (Singapore)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Sydney)</p>\n                                 </li>\n                                 <li>\n                                    <p>Asia Pacific (Tokyo)</p>\n                                 </li>\n                                 <li>\n                                    <p>Europe (Ireland)</p>\n                                 </li>\n                                 <li>\n                                    <p>South America (São Paulo)</p>\n                                 </li>\n                              </ul>\n                              <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                           </note>\n                        </li>\n                     </ul>\n                     <p>For example, the following <code>x-amz-grant-read</code> header grants\n                        list objects permission to the two Amazon Web Services accounts identified by their email\n                        addresses.</p>\n                     <p>\n                        <code>x-amz-grant-read: emailAddress=\"xyz@amazon.com\",\n                           emailAddress=\"abc@amazon.com\" </code>\n                     </p>\n                  </li>\n               </ul>\n               <p>You can use either a canned ACL or specify access permissions explicitly. You\n                  cannot do both.</p>\n            </dd>\n            <dt>Grantee Values</dt>\n            <dd>\n               <p>You can specify the person (grantee) to whom you're assigning access rights\n                  (using request elements) in the following ways:</p>\n               <ul>\n                  <li>\n                     <p>By the person's ID:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"CanonicalUser\"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>\n                           </Grantee></code>\n                     </p>\n                     <p>DisplayName is optional and ignored in the request.</p>\n                  </li>\n                  <li>\n                     <p>By URI:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"Group\"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>\n                     </p>\n                  </li>\n                  <li>\n                     <p>By Email address:</p>\n                     <p>\n                        <code><Grantee xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n                           xsi:type=\"AmazonCustomerByEmail\"><EmailAddress><>Grantees@email.com<></EmailAddress>lt;/Grantee></code>\n                     </p>\n                     <p>The grantee is resolved to the CanonicalUser and, in a response to a GET\n                        Object acl request, appears as the CanonicalUser.</p>\n                     <note>\n                        <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>\n                        <ul>\n                           <li>\n                              <p>US East (N. Virginia)</p>\n                           </li>\n                           <li>\n                              <p>US West (N. California)</p>\n                           </li>\n                           <li>\n                              <p> US West (Oregon)</p>\n                           </li>\n                           <li>\n                              <p> Asia Pacific (Singapore)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Sydney)</p>\n                           </li>\n                           <li>\n                              <p>Asia Pacific (Tokyo)</p>\n                           </li>\n                           <li>\n                              <p>Europe (Ireland)</p>\n                           </li>\n                           <li>\n                              <p>South America (São Paulo)</p>\n                           </li>\n                        </ul>\n                        <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href=\"https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region\">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>\n                     </note>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Versioning</dt>\n            <dd>\n               <p>The ACL of an object is set at the object version level. By default, PUT sets\n                  the ACL of the current version of an object. To set the ACL of a different\n                  version, use the <code>versionId</code> subresource.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>PutObjectAcl</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To grant permissions using object ACL",
@@ -31354,7 +31462,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Applies a legal hold configuration to the specified object. For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking\n            Objects</a>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Applies a legal hold configuration to the specified object. For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking\n            Objects</a>.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}/{Key+}?legal-hold",
@@ -31458,7 +31566,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Places an Object Lock configuration on the specified bucket. The rule specified in the\n         Object Lock configuration will be applied by default to every new object placed in the\n         specified bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>The <code>DefaultRetention</code> settings require both a mode and a\n                  period.</p>\n               </li>\n               <li>\n                  <p>The <code>DefaultRetention</code> period can be either <code>Days</code> or\n                     <code>Years</code> but you must select one. You cannot specify\n                     <code>Days</code> and <code>Years</code> at the same time.</p>\n               </li>\n               <li>\n                  <p>You can enable Object Lock for new or existing buckets. For more\n                  information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-configure.html\">Configuring Object\n                     Lock</a>.</p>\n               </li>\n            </ul>\n         </note>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Places an Object Lock configuration on the specified bucket. The rule specified in the\n         Object Lock configuration will be applied by default to every new object placed in the\n         specified bucket. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>The <code>DefaultRetention</code> settings require both a mode and a\n                  period.</p>\n               </li>\n               <li>\n                  <p>The <code>DefaultRetention</code> period can be either <code>Days</code> or\n                     <code>Years</code> but you must select one. You cannot specify\n                     <code>Days</code> and <code>Years</code> at the same time.</p>\n               </li>\n               <li>\n                  <p>You can enable Object Lock for new or existing buckets. For more information,\n                  see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-configure.html\">Configuring Object\n                     Lock</a>.</p>\n               </li>\n            </ul>\n         </note>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?object-lock",
@@ -31547,14 +31655,14 @@
         "Expiration": {
           "target": "com.amazonaws.s3#Expiration",
           "traits": {
-            "smithy.api#documentation": "<p>If the expiration is configured for the object (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>) in the <i>Amazon S3 User Guide</i>, the response includes this header. It\n         includes the <code>expiry-date</code> and <code>rule-id</code> key-value pairs that provide\n         information about object expiration. The value of the <code>rule-id</code> is\n         URL-encoded.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If the expiration is configured for the object (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>) in the <i>Amazon S3 User Guide</i>,\n         the response includes this header. It includes the <code>expiry-date</code> and\n            <code>rule-id</code> key-value pairs that provide information about object expiration.\n         The value of the <code>rule-id</code> is URL-encoded.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-expiration"
           }
         },
         "ETag": {
           "target": "com.amazonaws.s3#ETag",
           "traits": {
-            "smithy.api#documentation": "<p>Entity tag for the uploaded object.</p>\n         <p>\n            <b>General purpose buckets </b> - To ensure that data is not corrupted traversing the network, \n         for objects where the \n         ETag is the MD5 digest of the object, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to\n      the calculated MD5 value.</p>\n         <p>\n            <b>Directory buckets </b> - The ETag for the object in a directory bucket isn't the MD5 digest of the object.</p>",
+            "smithy.api#documentation": "<p>Entity tag for the uploaded object.</p>\n         <p>\n            <b>General purpose buckets </b> - To ensure that data is not\n         corrupted traversing the network, for objects where the ETag is the MD5 digest of the\n         object, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned\n         ETag to the calculated MD5 value.</p>\n         <p>\n            <b>Directory buckets </b> - The ETag for the object in\n         a directory bucket isn't the MD5 digest of the object.</p>",
             "smithy.api#httpHeader": "ETag"
           }
         },
@@ -31596,7 +31704,7 @@
         "VersionId": {
           "target": "com.amazonaws.s3#ObjectVersionId",
           "traits": {
-            "smithy.api#documentation": "<p>Version ID of the object.</p>\n         <p>If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID\n         for the object being stored. Amazon S3 returns this ID in the response. When you enable\n         versioning for a bucket, if Amazon S3 receives multiple write requests for the same object\n         simultaneously, it stores all of the objects. For more information about versioning, see\n         <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html\">Adding Objects to\n            Versioning-Enabled Buckets</a> in the <i>Amazon S3\n               User Guide</i>. For information about returning the versioning state\n         of a bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a>. </p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Version ID of the object.</p>\n         <p>If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID\n         for the object being stored. Amazon S3 returns this ID in the response. When you enable\n         versioning for a bucket, if Amazon S3 receives multiple write requests for the same object\n         simultaneously, it stores all of the objects. For more information about versioning, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html\">Adding Objects to\n            Versioning-Enabled Buckets</a> in the <i>Amazon S3 User Guide</i>. For\n         information about returning the versioning state of a bucket, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html\">GetBucketVersioning</a>. </p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-version-id"
           }
         },
@@ -31610,7 +31718,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification of\n         the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification\n         of the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -31635,6 +31743,13 @@
             "smithy.api#httpHeader": "x-amz-server-side-encryption-bucket-key-enabled"
           }
         },
+        "Size": {
+          "target": "com.amazonaws.s3#Size",
+          "traits": {
+            "smithy.api#documentation": "<p>\n         The size of the object in bytes. This will only be present if you append to an object.\n      </p>\n         <note>\n            <p>This functionality is only supported for objects in the Amazon S3 Express One Zone storage class in directory buckets.</p>\n         </note>",
+            "smithy.api#httpHeader": "x-amz-object-size"
+          }
+        },
         "RequestCharged": {
           "target": "com.amazonaws.s3#RequestCharged",
           "traits": {
@@ -31652,7 +31767,7 @@
         "ACL": {
           "target": "com.amazonaws.s3#ObjectCannedACL",
           "traits": {
-            "smithy.api#documentation": "<p>The canned ACL to apply to the object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned\n         ACL</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>When adding a new object, you can use headers to grant ACL-based permissions to\n         individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are\n         then added to the ACL on the object. By default, all objects are private. Only the owner\n         has full access control. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-using-rest-api.html\">Managing\n            ACLs Using the REST API</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>If the bucket that you're uploading objects to uses the bucket owner enforced setting\n         for S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that\n         use this setting only accept PUT requests that don't specify an ACL or PUT requests that\n         specify bucket owner full control ACLs, such as the <code>bucket-owner-full-control</code>\n         canned ACL or an equivalent form of this ACL expressed in the XML format. PUT requests that\n         contain other ACLs (for example, custom grants to certain Amazon Web Services accounts) fail and return a\n         <code>400</code> error with the error code <code>AccessControlListNotSupported</code>.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\"> Controlling ownership of\n            objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>The canned ACL to apply to the object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL\">Canned\n            ACL</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>When adding a new object, you can use headers to grant ACL-based permissions to\n         individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are\n         then added to the ACL on the object. By default, all objects are private. Only the owner\n         has full access control. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html\">Access Control List (ACL) Overview</a>\n         and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-using-rest-api.html\">Managing\n            ACLs Using the REST API</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>If the bucket that you're uploading objects to uses the bucket owner enforced setting\n         for S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that\n         use this setting only accept PUT requests that don't specify an ACL or PUT requests that\n         specify bucket owner full control ACLs, such as the <code>bucket-owner-full-control</code>\n         canned ACL or an equivalent form of this ACL expressed in the XML format. PUT requests that\n         contain other ACLs (for example, custom grants to certain Amazon Web Services accounts) fail and return a\n            <code>400</code> error with the error code <code>AccessControlListNotSupported</code>.\n         For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html\"> Controlling ownership of\n            objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>This functionality is not supported for directory buckets.</p>\n               </li>\n               <li>\n                  <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-acl"
           }
         },
@@ -31667,7 +31782,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket name to which the PUT action was initiated. </p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The bucket name to which the PUT action was initiated. </p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -31713,7 +31828,7 @@
         "ContentMD5": {
           "target": "com.amazonaws.s3#ContentMD5",
           "traits": {
-            "smithy.api#documentation": "<p>The base64-encoded 128-bit MD5 digest of the message (without the headers) according to\n         RFC 1864. This header can be used as a message integrity check to verify that the data is\n         the same data that was originally sent. Although it is optional, we recommend using the\n         Content-MD5 mechanism as an end-to-end integrity check. For more information about REST\n         request authentication, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n         <note>\n            <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is required for any request to upload an\n         object with a retention period configured using Amazon S3 Object Lock. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object\">Uploading objects to an Object Lock enabled bucket\n         </a> in the <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>The base64-encoded 128-bit MD5 digest of the message (without the headers) according to\n         RFC 1864. This header can be used as a message integrity check to verify that the data is\n         the same data that was originally sent. Although it is optional, we recommend using the\n         Content-MD5 mechanism as an end-to-end integrity check. For more information about REST\n         request authentication, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n         <note>\n            <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is\n            required for any request to upload an object with a retention period configured using\n            Amazon S3 Object Lock. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object\">Uploading objects to an Object Lock enabled bucket </a> in the\n               <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "Content-MD5"
           }
         },
@@ -31727,7 +31842,7 @@
         "ChecksumAlgorithm": {
           "target": "com.amazonaws.s3#ChecksumAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n    additional functionality if you don't use the SDK. When you send this header, there must be a corresponding <code>x-amz-checksum-<i>algorithm</i>\n            </code> or\n    <code>x-amz-trailer</code> header sent. Otherwise, Amazon S3 fails the request with the HTTP status code <code>400 Bad Request</code>.</p>\n         <p>For the <code>x-amz-checksum-<i>algorithm</i>\n            </code> header, replace <code>\n               <i>algorithm</i>\n            </code> with the supported algorithm from the following list: </p>\n         <ul>\n            <li>\n               <p>\n                  <code>CRC32</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>CRC32C</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>SHA1</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>SHA256</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more\n    information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html\">Checking object integrity</a> in\n    the <i>Amazon S3 User Guide</i>.</p>\n         <p>If the individual checksum value you provide through <code>x-amz-checksum-<i>algorithm</i>\n            </code> doesn't match the checksum algorithm you set through <code>x-amz-sdk-checksum-algorithm</code>,  Amazon S3 ignores any provided\n            <code>ChecksumAlgorithm</code> parameter and uses the checksum algorithm that matches the provided value in <code>x-amz-checksum-<i>algorithm</i>\n            </code>.</p>\n         <note>\n            <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is required for any request to upload an\n         object with a retention period configured using Amazon S3 Object Lock. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object\">Uploading objects to an Object Lock enabled bucket\n         </a> in the <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>For directory buckets, when you use Amazon Web Services SDKs, <code>CRC32</code> is the default checksum algorithm that's used for performance.</p>",
+            "smithy.api#documentation": "<p>Indicates the algorithm used to create the checksum for the object when you use the SDK. This header will not provide any\n    additional functionality if you don't use the SDK. When you send this header, there must be a corresponding <code>x-amz-checksum-<i>algorithm</i>\n            </code> or\n    <code>x-amz-trailer</code> header sent. Otherwise, Amazon S3 fails the request with the HTTP status code <code>400 Bad Request</code>.</p>\n         <p>For the <code>x-amz-checksum-<i>algorithm</i>\n            </code> header, replace <code>\n               <i>algorithm</i>\n            </code> with the supported algorithm from the following list: </p>\n         <ul>\n            <li>\n               <p>\n                  <code>CRC32</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>CRC32C</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>SHA1</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>SHA256</code>\n               </p>\n            </li>\n         </ul>\n         <p>For more\n    information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html\">Checking object integrity</a> in\n    the <i>Amazon S3 User Guide</i>.</p>\n         <p>If the individual checksum value you provide through <code>x-amz-checksum-<i>algorithm</i>\n            </code> doesn't match the checksum algorithm you set through <code>x-amz-sdk-checksum-algorithm</code>,  Amazon S3 ignores any provided\n            <code>ChecksumAlgorithm</code> parameter and uses the checksum algorithm that matches the provided value in <code>x-amz-checksum-<i>algorithm</i>\n            </code>.</p>\n         <note>\n            <p>The <code>Content-MD5</code> or <code>x-amz-sdk-checksum-algorithm</code> header is\n            required for any request to upload an object with a retention period configured using\n            Amazon S3 Object Lock. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-managing.html#object-lock-put-object\">Uploading objects to an Object Lock enabled bucket </a> in the\n               <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <p>For directory buckets, when you use Amazon Web Services SDKs, <code>CRC32</code> is the default checksum algorithm that's used for performance.</p>",
             "smithy.api#httpHeader": "x-amz-sdk-checksum-algorithm"
           }
         },
@@ -31769,7 +31884,7 @@
         "IfNoneMatch": {
           "target": "com.amazonaws.s3#IfNoneMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Uploads the object only if the object key name does not already exist in the bucket specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>\n         <p>If a conflicting operation occurs during the upload S3 returns a <code>409 ConditionalRequestConflict</code> response. On a 409 failure you should retry the upload.</p>\n         <p>Expects the '*' (asterisk) character.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>, or <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html\">Conditional requests</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>Uploads the object only if the object key name does not already exist in the bucket\n         specified. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error.</p>\n         <p>If a conflicting operation occurs during the upload S3 returns a <code>409\n            ConditionalRequestConflict</code> response. On a 409 failure you should retry the\n         upload.</p>\n         <p>Expects the '*' (asterisk) character.</p>\n         <p>For more information about conditional requests, see <a href=\"https://tools.ietf.org/html/rfc7232\">RFC 7232</a>, or <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html\">Conditional requests</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpHeader": "If-None-Match"
           }
         },
@@ -31812,6 +31927,13 @@
             }
           }
         },
+        "WriteOffsetBytes": {
+          "target": "com.amazonaws.s3#WriteOffsetBytes",
+          "traits": {
+            "smithy.api#documentation": "<p>\n         Specifies the offset for appending data to existing objects in bytes. \n         The offset must be equal to the size of the existing object being appended to. \n         If no object exists, setting this header to 0 will create a new object.\n      </p>\n         <note>\n            <p>This functionality is only supported for objects in the Amazon S3 Express One Zone storage class in directory buckets.</p>\n         </note>",
+            "smithy.api#httpHeader": "x-amz-write-offset-bytes"
+          }
+        },
         "Metadata": {
           "target": "com.amazonaws.s3#Metadata",
           "traits": {
@@ -31822,28 +31944,28 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm that was used when you store this object in Amazon S3 (for example,\n            <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>\n         <ul>\n            <li>\n               <p>\n                  <b>General purpose buckets </b> - You have four mutually exclusive options to protect data using server-side encryption in\n            Amazon S3, depending on how you choose to manage the encryption keys. Specifically, the\n            encryption key options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS or\n            DSSE-KMS), and customer-provided keys (SSE-C). Amazon S3 encrypts data with server-side\n            encryption by using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to\n            encrypt data at rest by using server-side encryption with other key options. For more\n            information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Using Server-Side\n               Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>\n                  <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>.         \n         </p>\n               <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request. \n                            You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n               <note>\n                  <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            So in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          the encryption request headers must match the default encryption configuration of the directory bucket.\n\n</p>\n               </note>\n            </li>\n         </ul>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm that was used when you store this object in Amazon S3\n         (for example, <code>AES256</code>, <code>aws:kms</code>, <code>aws:kms:dsse</code>).</p>\n         <ul>\n            <li>\n               <p>\n                  <b>General purpose buckets </b> - You have four mutually\n               exclusive options to protect data using server-side encryption in Amazon S3, depending on\n               how you choose to manage the encryption keys. Specifically, the encryption key\n               options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS or DSSE-KMS), and\n               customer-provided keys (SSE-C). Amazon S3 encrypts data with server-side encryption by\n               using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt\n               data at rest by using server-side encryption with other key options. For more\n               information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Using Server-Side\n                  Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>\n                  <b>Directory buckets </b> -\n               For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your \n            <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects \n are automatically encrypted with the desired encryption settings. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. 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>\n               <p>In the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>) using the REST API, the encryption request headers must match the encryption settings that are specified in the <code>CreateSession</code> request. \n                            You can't override the values of the encryption settings (<code>x-amz-server-side-encryption</code>, <code>x-amz-server-side-encryption-aws-kms-key-id</code>, <code>x-amz-server-side-encryption-context</code>, and <code>x-amz-server-side-encryption-bucket-key-enabled</code>) that are specified in the <code>CreateSession</code> request. \n                            You don't need to explicitly specify these encryption settings values in Zonal endpoint API calls, and   \n                            Amazon S3 will use the encryption settings values from the <code>CreateSession</code> request to protect new objects in the directory bucket. \n                           </p>\n               <note>\n                  <p>When you use the CLI or the Amazon Web Services SDKs, for <code>CreateSession</code>, the session token refreshes automatically to avoid service interruptions when a session expires. The CLI or the Amazon Web Services SDKs use the bucket's default encryption configuration for the \n                            <code>CreateSession</code> request. It's not supported to override the encryption settings values in the <code>CreateSession</code> request. \n                            So in the Zonal endpoint API calls (except <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>), \n          the encryption request headers must match the default encryption configuration of the directory bucket.\n\n</p>\n               </note>\n            </li>\n         </ul>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
         "StorageClass": {
           "target": "com.amazonaws.s3#StorageClass",
           "traits": {
-            "smithy.api#documentation": "<p>By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The\n         STANDARD storage class provides high durability and high availability. Depending on\n         performance needs, you can specify a different Storage Class. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage Classes</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>For directory buckets, only the S3 Express One Zone storage class is supported to store newly created objects.</p>\n               </li>\n               <li>\n                  <p>Amazon S3 on Outposts only uses\n               the OUTPOSTS Storage Class.</p>\n               </li>\n            </ul>\n         </note>",
+            "smithy.api#documentation": "<p>By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The\n         STANDARD storage class provides high durability and high availability. Depending on\n         performance needs, you can specify a different Storage Class. For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html\">Storage\n            Classes</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>For directory buckets, only the S3 Express One Zone storage class is supported to store\n                  newly created objects.</p>\n               </li>\n               <li>\n                  <p>Amazon S3 on Outposts only uses the OUTPOSTS Storage Class.</p>\n               </li>\n            </ul>\n         </note>",
             "smithy.api#httpHeader": "x-amz-storage-class"
           }
         },
         "WebsiteRedirectLocation": {
           "target": "com.amazonaws.s3#WebsiteRedirectLocation",
           "traits": {
-            "smithy.api#documentation": "<p>If the bucket is configured as a website, redirects requests for this object to another\n         object in the same bucket or to an external URL. Amazon S3 stores the value of this header in\n         the object metadata. For information about object metadata, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html\">Object Key and Metadata</a> in the <i>Amazon S3\n               User Guide</i>.</p>\n         <p>In the following example, the request header sets the redirect to an object\n         (anotherPage.html) in the same bucket:</p>\n         <p>\n            <code>x-amz-website-redirect-location: /anotherPage.html</code>\n         </p>\n         <p>In the following example, the request header sets the object redirect to another\n         website:</p>\n         <p>\n            <code>x-amz-website-redirect-location: http://www.example.com/</code>\n         </p>\n         <p>For more information about website hosting in Amazon S3, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a> and\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html\">How to\n               Configure Website Page Redirects</a> in the <i>Amazon S3\n                  User Guide</i>. </p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If the bucket is configured as a website, redirects requests for this object to another\n         object in the same bucket or to an external URL. Amazon S3 stores the value of this header in\n         the object metadata. For information about object metadata, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html\">Object Key and Metadata</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <p>In the following example, the request header sets the redirect to an object\n         (anotherPage.html) in the same bucket:</p>\n         <p>\n            <code>x-amz-website-redirect-location: /anotherPage.html</code>\n         </p>\n         <p>In the following example, the request header sets the object redirect to another\n         website:</p>\n         <p>\n            <code>x-amz-website-redirect-location: http://www.example.com/</code>\n         </p>\n         <p>For more information about website hosting in Amazon S3, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html\">Hosting Websites on Amazon S3</a> and\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html\">How to\n            Configure Website Page Redirects</a> in the <i>Amazon S3 User Guide</i>. </p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-website-redirect-location"
           }
         },
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n         <code>AES256</code>).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n            <code>AES256</code>).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
@@ -31912,7 +32034,7 @@
         "ObjectLockLegalHoldStatus": {
           "target": "com.amazonaws.s3#ObjectLockLegalHoldStatus",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies whether a legal hold will be applied to this object. For more information\n         about S3 Object Lock, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Object Lock</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies whether a legal hold will be applied to this object. For more information\n         about S3 Object Lock, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Object Lock</a> in the\n            <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-object-lock-legal-hold"
           }
         },
@@ -31941,7 +32063,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Places an Object Retention configuration on an object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>.\n         Users or accounts require the <code>s3:PutObjectRetention</code> permission in order to\n         place an Object Retention configuration on objects. Bypassing a Governance Retention\n         configuration requires the <code>s3:BypassGovernanceRetention</code> permission. </p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Places an Object Retention configuration on an object. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock.html\">Locking Objects</a>.\n         Users or accounts require the <code>s3:PutObjectRetention</code> permission in order to\n         place an Object Retention configuration on objects. Bypassing a Governance Retention\n         configuration requires the <code>s3:BypassGovernanceRetention</code> permission. </p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}/{Key+}?retention",
@@ -32052,7 +32174,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Sets the supplied tag-set to an object that already exists in a bucket. A tag is a\n         key-value pair. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html\">Object Tagging</a>.</p>\n         <p>You can associate tags with an object by sending a PUT request against the tagging\n         subresource that is associated with the object. You can retrieve tags by sending a GET\n         request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>.</p>\n         <p>For tagging-related restrictions related to characters and encodings, see <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/allocation-tag-restrictions.html\">Tag\n            Restrictions</a>. Note that Amazon S3 limits the maximum number of tags to 10 tags per\n         object.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:PutObjectTagging</code> action. By default, the bucket owner has this\n         permission and can grant this permission to others.</p>\n         <p>To put tags of any other version, use the <code>versionId</code> query parameter. You\n         also need permission for the <code>s3:PutObjectVersionTagging</code> action.</p>\n         <p>\n            <code>PutObjectTagging</code> has the following special errors. For more Amazon S3 errors\n         see, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html\">Error\n            Responses</a>.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>InvalidTag</code> - The tag provided was not a valid tag. This error\n               can occur if the tag did not pass input validation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html\">Object\n                  Tagging</a>.</p>\n            </li>\n            <li>\n               <p>\n                  <code>MalformedXML</code> - The XML provided does not match the\n               schema.</p>\n            </li>\n            <li>\n               <p>\n                  <code>OperationAborted</code> - A conflicting conditional action is\n               currently in progress against this resource. Please try again.</p>\n            </li>\n            <li>\n               <p>\n                  <code>InternalError</code> - The service was unable to apply the provided\n               tag to the object.</p>\n            </li>\n         </ul>\n         <p>The following operations are related to <code>PutObjectTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjectTagging.html\">DeleteObjectTagging</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Sets the supplied tag-set to an object that already exists in a bucket. A tag is a\n         key-value pair. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html\">Object Tagging</a>.</p>\n         <p>You can associate tags with an object by sending a PUT request against the tagging\n         subresource that is associated with the object. You can retrieve tags by sending a GET\n         request. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>.</p>\n         <p>For tagging-related restrictions related to characters and encodings, see <a href=\"https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/allocation-tag-restrictions.html\">Tag\n            Restrictions</a>. Note that Amazon S3 limits the maximum number of tags to 10 tags per\n         object.</p>\n         <p>To use this operation, you must have permission to perform the\n            <code>s3:PutObjectTagging</code> action. By default, the bucket owner has this\n         permission and can grant this permission to others.</p>\n         <p>To put tags of any other version, use the <code>versionId</code> query parameter. You\n         also need permission for the <code>s3:PutObjectVersionTagging</code> action.</p>\n         <p>\n            <code>PutObjectTagging</code> has the following special errors. For more Amazon S3 errors\n         see, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html\">Error\n            Responses</a>.</p>\n         <ul>\n            <li>\n               <p>\n                  <code>InvalidTag</code> - The tag provided was not a valid tag. This error\n               can occur if the tag did not pass input validation. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html\">Object\n                  Tagging</a>.</p>\n            </li>\n            <li>\n               <p>\n                  <code>MalformedXML</code> - The XML provided does not match the\n               schema.</p>\n            </li>\n            <li>\n               <p>\n                  <code>OperationAborted</code> - A conflicting conditional action is\n               currently in progress against this resource. Please try again.</p>\n            </li>\n            <li>\n               <p>\n                  <code>InternalError</code> - The service was unable to apply the provided\n               tag to the object.</p>\n            </li>\n         </ul>\n         <p>The following operations are related to <code>PutObjectTagging</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html\">GetObjectTagging</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjectTagging.html\">DeleteObjectTagging</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To add tags to an existing object",
@@ -32183,7 +32305,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Creates or modifies the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket.\n         To use this operation, you must have the <code>s3:PutBucketPublicAccessBlock</code>\n         permission. For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <important>\n            <p>When Amazon S3 evaluates the <code>PublicAccessBlock</code> configuration for a bucket or\n            an object, it checks the <code>PublicAccessBlock</code> configuration for both the\n            bucket (or the bucket that contains the object) and the bucket owner's account. If the\n               <code>PublicAccessBlock</code> configurations are different between the bucket and\n            the account, Amazon S3 uses the most restrictive combination of the bucket-level and\n            account-level settings.</p>\n         </important>\n         <p>For more information about when Amazon S3 considers a bucket or an object public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>.</p>\n         <p>The following operations are related to <code>PutPublicAccessBlock</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">DeletePublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketPolicyStatus.html\">GetBucketPolicyStatus</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Creates or modifies the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket.\n         To use this operation, you must have the <code>s3:PutBucketPublicAccessBlock</code>\n         permission. For more information about Amazon S3 permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in a\n            Policy</a>.</p>\n         <important>\n            <p>When Amazon S3 evaluates the <code>PublicAccessBlock</code> configuration for a bucket or\n            an object, it checks the <code>PublicAccessBlock</code> configuration for both the\n            bucket (or the bucket that contains the object) and the bucket owner's account. If the\n               <code>PublicAccessBlock</code> configurations are different between the bucket and\n            the account, Amazon S3 uses the most restrictive combination of the bucket-level and\n            account-level settings.</p>\n         </important>\n         <p>For more information about when Amazon S3 considers a bucket or an object public, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status\">The Meaning of \"Public\"</a>.</p>\n         <p>The following operations are related to <code>PutPublicAccessBlock</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetPublicAccessBlock.html\">GetPublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeletePublicAccessBlock.html\">DeletePublicAccessBlock</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketPolicyStatus.html\">GetBucketPolicyStatus</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html\">Using Amazon S3 Block\n                  Public Access</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?publicAccessBlock",
@@ -32506,7 +32628,7 @@
         "ExistingObjectReplication": {
           "target": "com.amazonaws.s3#ExistingObjectReplication",
           "traits": {
-            "smithy.api#documentation": "<p>Optional configuration to replicate existing source bucket objects.\n      </p>\n         <note>\n            <p>This parameter is no longer supported. To replicate existing objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html\">Replicating existing objects with S3 Batch Replication</a> in the <i>Amazon S3 User Guide</i>.</p>\n         </note>"
+            "smithy.api#documentation": "<p>Optional configuration to replicate existing source bucket objects. </p>\n         <note>\n            <p>This parameter is no longer supported. To replicate existing objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-batch-replication-batch.html\">Replicating existing objects with S3 Batch Replication</a> in the\n               <i>Amazon S3 User Guide</i>.</p>\n         </note>"
           }
         },
         "Destination": {
@@ -32708,7 +32830,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Confirms that the requester knows that they will be charged for the request. Bucket\n         owners need not specify this parameter in their requests. If either the source or\n         destination S3 bucket has Requester Pays enabled, the requester will pay for\n         corresponding charges to copy the object. For information about downloading objects from\n         Requester Pays buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html\">Downloading Objects in\n            Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
+        "smithy.api#documentation": "<p>Confirms that the requester knows that they will be charged for the request. Bucket\n         owners need not specify this parameter in their requests. If either the source or\n         destination S3 bucket has Requester Pays enabled, the requester will pay for corresponding\n         charges to copy the object. For information about downloading objects from Requester Pays\n         buckets, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectsinRequesterPaysBuckets.html\">Downloading Objects in\n            Requester Pays Buckets</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#RequestPaymentConfiguration": {
@@ -32790,7 +32912,7 @@
         "aws.protocols#httpChecksum": {
           "requestAlgorithmMember": "ChecksumAlgorithm"
         },
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Restores an archived copy of an object back into Amazon S3</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>This action performs the following types of requests: </p>\n         <ul>\n            <li>\n               <p>\n                  <code>restore an archive</code> - Restore an archived object</p>\n            </li>\n         </ul>\n         <p>For more information about the <code>S3</code> structure in the request body, see the\n         following:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Managing Access with ACLs</a> in the\n               <i>Amazon S3 User Guide</i>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Protecting Data Using Server-Side Encryption</a> in the\n                  <i>Amazon S3 User Guide</i>\n               </p>\n            </li>\n         </ul>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To use this operation, you must have permissions to perform the\n                     <code>s3:RestoreObject</code> action. The bucket owner has this permission by\n                  default and can grant this permission to others. For more information about\n                  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> in the\n                     <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Restoring objects</dt>\n            <dd>\n               <p>Objects that you archive to the S3 Glacier Flexible Retrieval Flexible Retrieval\n                  or S3 Glacier Deep Archive storage class, and S3 Intelligent-Tiering Archive or\n                  S3 Intelligent-Tiering Deep Archive tiers, are not accessible in real time. For objects in the\n                  S3 Glacier Flexible Retrieval Flexible Retrieval or S3 Glacier Deep Archive\n                  storage classes, you must first initiate a restore request, and then wait until a\n                  temporary copy of the object is available. If you want a permanent copy of the\n                  object, create a copy of it in the Amazon S3 Standard storage class in your S3 bucket.\n                  To access an archived object, you must restore the object for the duration (number\n                  of days) that you specify. For objects in the Archive Access or Deep Archive\n                  Access tiers of S3 Intelligent-Tiering, you must first initiate a restore request,\n                  and then wait until the object is moved into the Frequent Access tier.</p>\n               <p>To restore a specific object version, you can provide a version ID. If you\n                  don't provide a version ID, Amazon S3 restores the current version.</p>\n               <p>When restoring an archived object, you can specify one of the following data\n                  access tier options in the <code>Tier</code> element of the request body: </p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>Expedited</code> - Expedited retrievals allow you to quickly access\n                        your data stored in the S3 Glacier Flexible Retrieval Flexible Retrieval\n                        storage class or S3 Intelligent-Tiering Archive tier when occasional urgent requests\n                        for restoring archives are required. For all but the largest archived\n                        objects (250 MB+), data accessed using Expedited retrievals is typically\n                        made available within 1–5 minutes. Provisioned capacity ensures that\n                        retrieval capacity for Expedited retrievals is available when you need it.\n                        Expedited retrievals and provisioned capacity are not available for objects\n                        stored in the S3 Glacier Deep Archive storage class or\n                        S3 Intelligent-Tiering Deep Archive tier.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>Standard</code> - Standard retrievals allow you to access any of\n                        your archived objects within several hours. This is the default option for\n                        retrieval requests that do not specify the retrieval option. Standard\n                        retrievals typically finish within 3–5 hours for objects stored in the\n                        S3 Glacier Flexible Retrieval Flexible Retrieval storage class or\n                        S3 Intelligent-Tiering Archive tier. They typically finish within 12 hours for\n                        objects stored in the S3 Glacier Deep Archive storage class or\n                        S3 Intelligent-Tiering Deep Archive tier. Standard retrievals are free for objects stored\n                        in S3 Intelligent-Tiering.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>Bulk</code> - Bulk retrievals free for objects stored in the\n                        S3 Glacier Flexible Retrieval and S3 Intelligent-Tiering storage classes,\n                        enabling you to retrieve large amounts, even petabytes, of data at no cost.\n                        Bulk retrievals typically finish within 5–12 hours for objects stored in the\n                        S3 Glacier Flexible Retrieval Flexible Retrieval storage class or\n                        S3 Intelligent-Tiering Archive tier. Bulk retrievals are also the lowest-cost\n                        retrieval option when restoring objects from\n                        S3 Glacier Deep Archive. They typically finish within 48 hours for\n                        objects stored in the S3 Glacier Deep Archive storage class or\n                        S3 Intelligent-Tiering Deep Archive tier. </p>\n                  </li>\n               </ul>\n               <p>For more information about archive retrieval options and provisioned capacity\n                  for <code>Expedited</code> data access, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring Archived\n                     Objects</a> in the <i>Amazon S3 User Guide</i>. </p>\n               <p>You can use Amazon S3 restore speed upgrade to change the restore speed to a faster\n                  speed while it is in progress. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html#restoring-objects-upgrade-tier.title.html\"> Upgrading the speed of an in-progress restore</a> in the\n                     <i>Amazon S3 User Guide</i>. </p>\n               <p>To get the status of object restoration, you can send a <code>HEAD</code>\n                  request. Operations return the <code>x-amz-restore</code> header, which provides\n                  information about the restoration status, in the response. You can use Amazon S3 event\n                  notifications to notify you when a restore is initiated or completed. For more\n                  information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Amazon S3 Event\n                     Notifications</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <p>After restoring an archived object, you can update the restoration period by\n                  reissuing the request with a new period. Amazon S3 updates the restoration period\n                  relative to the current time and charges only for the request-there are no\n                  data transfer charges. You cannot update the restoration period when Amazon S3 is\n                  actively processing your current restore request for the object.</p>\n               <p>If your bucket has a lifecycle configuration with a rule that includes an\n                  expiration action, the object expiration overrides the life span that you specify\n                  in a restore request. For example, if you restore an object copy for 10 days, but\n                  the object is scheduled to expire in 3 days, Amazon S3 deletes the object in 3 days.\n                  For more information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle\n                     Management</a> in <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Responses</dt>\n            <dd>\n               <p>A successful action returns either the <code>200 OK</code> or <code>202\n                     Accepted</code> status code. </p>\n               <ul>\n                  <li>\n                     <p>If the object is not previously restored, then Amazon S3 returns <code>202\n                           Accepted</code> in the response. </p>\n                  </li>\n                  <li>\n                     <p>If the object is previously restored, Amazon S3 returns <code>200 OK</code> in\n                        the response. </p>\n                  </li>\n               </ul>\n               <ul>\n                  <li>\n                     <p>Special errors:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <i>Code: RestoreAlreadyInProgress</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>Cause: Object restore is already in progress.</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>HTTP Status Code: 409 Conflict</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>SOAP Fault Code Prefix: Client</i>\n                           </p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <ul>\n                        <li>\n                           <p>\n                              <i>Code: GlacierExpeditedRetrievalNotAvailable</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>Cause: expedited retrievals are currently not available.\n                                 Try again later. (Returned if there is insufficient capacity to\n                                 process the Expedited request. This error applies only to Expedited\n                                 retrievals and not to S3 Standard or Bulk retrievals.)</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>HTTP Status Code: 503</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>SOAP Fault Code Prefix: N/A</i>\n                           </p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>RestoreObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketNotificationConfiguration.html\">GetBucketNotificationConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Restores an archived copy of an object back into Amazon S3</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>This action performs the following types of requests: </p>\n         <ul>\n            <li>\n               <p>\n                  <code>restore an archive</code> - Restore an archived object</p>\n            </li>\n         </ul>\n         <p>For more information about the <code>S3</code> structure in the request body, see the\n         following:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html\">PutObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html\">Managing Access with ACLs</a> in the\n               <i>Amazon S3 User Guide</i>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Protecting Data Using Server-Side Encryption</a> in the\n                  <i>Amazon S3 User Guide</i>\n               </p>\n            </li>\n         </ul>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>To use this operation, you must have permissions to perform the\n                     <code>s3:RestoreObject</code> action. The bucket owner has this permission by\n                  default and can grant this permission to others. For more information about\n                  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> in the\n                     <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Restoring objects</dt>\n            <dd>\n               <p>Objects that you archive to the S3 Glacier Flexible Retrieval Flexible Retrieval\n                  or S3 Glacier Deep Archive storage class, and S3 Intelligent-Tiering Archive or\n                  S3 Intelligent-Tiering Deep Archive tiers, are not accessible in real time. For objects in the\n                  S3 Glacier Flexible Retrieval Flexible Retrieval or S3 Glacier Deep Archive\n                  storage classes, you must first initiate a restore request, and then wait until a\n                  temporary copy of the object is available. If you want a permanent copy of the\n                  object, create a copy of it in the Amazon S3 Standard storage class in your S3 bucket.\n                  To access an archived object, you must restore the object for the duration (number\n                  of days) that you specify. For objects in the Archive Access or Deep Archive\n                  Access tiers of S3 Intelligent-Tiering, you must first initiate a restore request,\n                  and then wait until the object is moved into the Frequent Access tier.</p>\n               <p>To restore a specific object version, you can provide a version ID. If you\n                  don't provide a version ID, Amazon S3 restores the current version.</p>\n               <p>When restoring an archived object, you can specify one of the following data\n                  access tier options in the <code>Tier</code> element of the request body: </p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>Expedited</code> - Expedited retrievals allow you to quickly access\n                        your data stored in the S3 Glacier Flexible Retrieval Flexible Retrieval\n                        storage class or S3 Intelligent-Tiering Archive tier when occasional urgent requests\n                        for restoring archives are required. For all but the largest archived\n                        objects (250 MB+), data accessed using Expedited retrievals is typically\n                        made available within 1–5 minutes. Provisioned capacity ensures that\n                        retrieval capacity for Expedited retrievals is available when you need it.\n                        Expedited retrievals and provisioned capacity are not available for objects\n                        stored in the S3 Glacier Deep Archive storage class or\n                        S3 Intelligent-Tiering Deep Archive tier.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>Standard</code> - Standard retrievals allow you to access any of\n                        your archived objects within several hours. This is the default option for\n                        retrieval requests that do not specify the retrieval option. Standard\n                        retrievals typically finish within 3–5 hours for objects stored in the\n                        S3 Glacier Flexible Retrieval Flexible Retrieval storage class or\n                        S3 Intelligent-Tiering Archive tier. They typically finish within 12 hours for\n                        objects stored in the S3 Glacier Deep Archive storage class or\n                        S3 Intelligent-Tiering Deep Archive tier. Standard retrievals are free for objects stored\n                        in S3 Intelligent-Tiering.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <code>Bulk</code> - Bulk retrievals free for objects stored in the\n                        S3 Glacier Flexible Retrieval and S3 Intelligent-Tiering storage classes,\n                        enabling you to retrieve large amounts, even petabytes, of data at no cost.\n                        Bulk retrievals typically finish within 5–12 hours for objects stored in the\n                        S3 Glacier Flexible Retrieval Flexible Retrieval storage class or\n                        S3 Intelligent-Tiering Archive tier. Bulk retrievals are also the lowest-cost\n                        retrieval option when restoring objects from\n                        S3 Glacier Deep Archive. They typically finish within 48 hours for\n                        objects stored in the S3 Glacier Deep Archive storage class or\n                        S3 Intelligent-Tiering Deep Archive tier. </p>\n                  </li>\n               </ul>\n               <p>For more information about archive retrieval options and provisioned capacity\n                  for <code>Expedited</code> data access, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html\">Restoring Archived\n                     Objects</a> in the <i>Amazon S3 User Guide</i>. </p>\n               <p>You can use Amazon S3 restore speed upgrade to change the restore speed to a faster\n                  speed while it is in progress. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/restoring-objects.html#restoring-objects-upgrade-tier.title.html\"> Upgrading the speed of an in-progress restore</a> in the\n                     <i>Amazon S3 User Guide</i>. </p>\n               <p>To get the status of object restoration, you can send a <code>HEAD</code>\n                  request. Operations return the <code>x-amz-restore</code> header, which provides\n                  information about the restoration status, in the response. You can use Amazon S3 event\n                  notifications to notify you when a restore is initiated or completed. For more\n                  information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html\">Configuring Amazon S3 Event\n                     Notifications</a> in the <i>Amazon S3 User Guide</i>.</p>\n               <p>After restoring an archived object, you can update the restoration period by\n                  reissuing the request with a new period. Amazon S3 updates the restoration period\n                  relative to the current time and charges only for the request-there are no\n                  data transfer charges. You cannot update the restoration period when Amazon S3 is\n                  actively processing your current restore request for the object.</p>\n               <p>If your bucket has a lifecycle configuration with a rule that includes an\n                  expiration action, the object expiration overrides the life span that you specify\n                  in a restore request. For example, if you restore an object copy for 10 days, but\n                  the object is scheduled to expire in 3 days, Amazon S3 deletes the object in 3 days.\n                  For more information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object Lifecycle\n                     Management</a> in <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Responses</dt>\n            <dd>\n               <p>A successful action returns either the <code>200 OK</code> or <code>202\n                     Accepted</code> status code. </p>\n               <ul>\n                  <li>\n                     <p>If the object is not previously restored, then Amazon S3 returns <code>202\n                           Accepted</code> in the response. </p>\n                  </li>\n                  <li>\n                     <p>If the object is previously restored, Amazon S3 returns <code>200 OK</code> in\n                        the response. </p>\n                  </li>\n               </ul>\n               <ul>\n                  <li>\n                     <p>Special errors:</p>\n                     <ul>\n                        <li>\n                           <p>\n                              <i>Code: RestoreAlreadyInProgress</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>Cause: Object restore is already in progress.</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>HTTP Status Code: 409 Conflict</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>SOAP Fault Code Prefix: Client</i>\n                           </p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <ul>\n                        <li>\n                           <p>\n                              <i>Code: GlacierExpeditedRetrievalNotAvailable</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>Cause: expedited retrievals are currently not available.\n                                 Try again later. (Returned if there is insufficient capacity to\n                                 process the Expedited request. This error applies only to Expedited\n                                 retrievals and not to S3 Standard or Bulk retrievals.)</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>HTTP Status Code: 503</i>\n                           </p>\n                        </li>\n                        <li>\n                           <p>\n                              <i>SOAP Fault Code Prefix: N/A</i>\n                           </p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>RestoreObject</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketNotificationConfiguration.html\">GetBucketNotificationConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To restore an archived object",
@@ -32978,7 +33100,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Specifies the restoration status of an object. Objects in certain storage classes must\n         be restored before they can be retrieved. For more information about these storage classes\n         and how to work with archived objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/archived-objects.html\"> Working with archived\n            objects</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets. Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
+        "smithy.api#documentation": "<p>Specifies the restoration status of an object. Objects in certain storage classes must\n         be restored before they can be retrieved. For more information about these storage classes\n         and how to work with archived objects, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/archived-objects.html\"> Working with archived\n            objects</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.\n            Only the S3 Express One Zone storage class is supported by directory buckets to store objects.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#Role": {
@@ -33161,7 +33283,7 @@
         "target": "com.amazonaws.s3#SelectObjectContentOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>This action filters the contents of an Amazon S3 object based on a simple structured query\n         language (SQL) statement. In the request, along with the SQL expression, you must also\n         specify a data serialization format (JSON, CSV, or Apache Parquet) of the object. Amazon S3 uses\n         this format to parse object data into records, and returns only records that match the\n         specified SQL expression. You must also specify the data serialization format for the\n         response.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>For more information about Amazon S3 Select, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/selecting-content-from-objects.html\">Selecting Content from\n            Objects</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-glacier-select-sql-reference-select.html\">SELECT\n            Command</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p></p>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have the <code>s3:GetObject</code> permission for this operation. Amazon S3\n                  Select does not support anonymous access. For more information about permissions,\n                  see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in\n                     a Policy</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Object Data Formats</dt>\n            <dd>\n               <p>You can use Amazon S3 Select to query objects that have the following format\n                  properties:</p>\n               <ul>\n                  <li>\n                     <p>\n                        <i>CSV, JSON, and Parquet</i> - Objects must be in CSV,\n                        JSON, or Parquet format.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>UTF-8</i> - UTF-8 is the only encoding type Amazon S3 Select\n                        supports.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>GZIP or BZIP2</i> - CSV and JSON files can be compressed\n                        using GZIP or BZIP2. GZIP and BZIP2 are the only compression formats that\n                        Amazon S3 Select supports for CSV and JSON files. Amazon S3 Select supports columnar\n                        compression for Parquet using GZIP or Snappy. Amazon S3 Select does not support\n                        whole-object compression for Parquet objects.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Server-side encryption</i> - Amazon S3 Select supports\n                        querying objects that are protected with server-side encryption.</p>\n                     <p>For objects that are encrypted with customer-provided encryption keys\n                        (SSE-C), you must use HTTPS, and you must use the headers that are\n                        documented in the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>. For more\n                        information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption (Using Customer-Provided Encryption Keys)</a>\n                        in the <i>Amazon S3 User Guide</i>.</p>\n                     <p>For objects that are encrypted with Amazon S3 managed keys (SSE-S3) and\n                        Amazon Web Services KMS keys (SSE-KMS), server-side encryption is handled transparently,\n                        so you don't need to specify anything. For more information about\n                        server-side encryption, including SSE-S3 and SSE-KMS, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Protecting Data Using Server-Side Encryption</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Working with the Response Body</dt>\n            <dd>\n               <p>Given the response size is unknown, Amazon S3 Select streams the response as a\n                  series of messages and includes a <code>Transfer-Encoding</code> header with\n                     <code>chunked</code> as its value in the response. For more information, see\n                     <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTSelectObjectAppendix.html\">Appendix:\n                     SelectObjectContent\n                  Response</a>.</p>\n            </dd>\n            <dt>GetObject Support</dt>\n            <dd>\n               <p>The <code>SelectObjectContent</code> action does not support the following\n                     <code>GetObject</code> functionality. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>Range</code>: Although you can specify a scan range for an Amazon S3 Select\n                        request (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_SelectObjectContent.html#AmazonS3-SelectObjectContent-request-ScanRange\">SelectObjectContentRequest - ScanRange</a> in the request\n                        parameters), you cannot specify the range of bytes of an object to return.\n                     </p>\n                  </li>\n                  <li>\n                     <p>The <code>GLACIER</code>, <code>DEEP_ARCHIVE</code>, and\n                           <code>REDUCED_REDUNDANCY</code> storage classes, or the\n                           <code>ARCHIVE_ACCESS</code> and <code>DEEP_ARCHIVE_ACCESS</code> access\n                        tiers of the <code>INTELLIGENT_TIERING</code> storage class: You cannot\n                        query objects in the <code>GLACIER</code>, <code>DEEP_ARCHIVE</code>, or\n                           <code>REDUCED_REDUNDANCY</code> storage classes, nor objects in the\n                           <code>ARCHIVE_ACCESS</code> or <code>DEEP_ARCHIVE_ACCESS</code> access\n                        tiers of the <code>INTELLIGENT_TIERING</code> storage class. For more\n                        information about storage classes, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html\">Using Amazon S3\n                           storage classes</a> in the\n                        <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special Errors</dt>\n            <dd>\n               <p>For a list of special errors for this operation, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#SelectObjectContentErrorCodeList\">List of SELECT Object Content Error Codes</a>\n               </p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>SelectObjectContent</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>This action filters the contents of an Amazon S3 object based on a simple structured query\n         language (SQL) statement. In the request, along with the SQL expression, you must also\n         specify a data serialization format (JSON, CSV, or Apache Parquet) of the object. Amazon S3 uses\n         this format to parse object data into records, and returns only records that match the\n         specified SQL expression. You must also specify the data serialization format for the\n         response.</p>\n         <p>This functionality is not supported for Amazon S3 on Outposts.</p>\n         <p>For more information about Amazon S3 Select, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/selecting-content-from-objects.html\">Selecting Content from\n            Objects</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-glacier-select-sql-reference-select.html\">SELECT\n            Command</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p></p>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have the <code>s3:GetObject</code> permission for this operation. Amazon S3\n                  Select does not support anonymous access. For more information about permissions,\n                  see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html\">Specifying Permissions in\n                     a Policy</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </dd>\n            <dt>Object Data Formats</dt>\n            <dd>\n               <p>You can use Amazon S3 Select to query objects that have the following format\n                  properties:</p>\n               <ul>\n                  <li>\n                     <p>\n                        <i>CSV, JSON, and Parquet</i> - Objects must be in CSV,\n                        JSON, or Parquet format.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>UTF-8</i> - UTF-8 is the only encoding type Amazon S3 Select\n                        supports.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>GZIP or BZIP2</i> - CSV and JSON files can be compressed\n                        using GZIP or BZIP2. GZIP and BZIP2 are the only compression formats that\n                        Amazon S3 Select supports for CSV and JSON files. Amazon S3 Select supports columnar\n                        compression for Parquet using GZIP or Snappy. Amazon S3 Select does not support\n                        whole-object compression for Parquet objects.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Server-side encryption</i> - Amazon S3 Select supports\n                        querying objects that are protected with server-side encryption.</p>\n                     <p>For objects that are encrypted with customer-provided encryption keys\n                        (SSE-C), you must use HTTPS, and you must use the headers that are\n                        documented in the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>. For more\n                        information about SSE-C, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html\">Server-Side Encryption (Using Customer-Provided Encryption Keys)</a>\n                        in the <i>Amazon S3 User Guide</i>.</p>\n                     <p>For objects that are encrypted with Amazon S3 managed keys (SSE-S3) and\n                        Amazon Web Services KMS keys (SSE-KMS), server-side encryption is handled transparently,\n                        so you don't need to specify anything. For more information about\n                        server-side encryption, including SSE-S3 and SSE-KMS, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html\">Protecting Data Using Server-Side Encryption</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Working with the Response Body</dt>\n            <dd>\n               <p>Given the response size is unknown, Amazon S3 Select streams the response as a\n                  series of messages and includes a <code>Transfer-Encoding</code> header with\n                     <code>chunked</code> as its value in the response. For more information, see\n                     <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTSelectObjectAppendix.html\">Appendix:\n                     SelectObjectContent\n                  Response</a>.</p>\n            </dd>\n            <dt>GetObject Support</dt>\n            <dd>\n               <p>The <code>SelectObjectContent</code> action does not support the following\n                     <code>GetObject</code> functionality. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <code>Range</code>: Although you can specify a scan range for an Amazon S3 Select\n                        request (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_SelectObjectContent.html#AmazonS3-SelectObjectContent-request-ScanRange\">SelectObjectContentRequest - ScanRange</a> in the request\n                        parameters), you cannot specify the range of bytes of an object to return.\n                     </p>\n                  </li>\n                  <li>\n                     <p>The <code>GLACIER</code>, <code>DEEP_ARCHIVE</code>, and\n                           <code>REDUCED_REDUNDANCY</code> storage classes, or the\n                           <code>ARCHIVE_ACCESS</code> and <code>DEEP_ARCHIVE_ACCESS</code> access\n                        tiers of the <code>INTELLIGENT_TIERING</code> storage class: You cannot\n                        query objects in the <code>GLACIER</code>, <code>DEEP_ARCHIVE</code>, or\n                           <code>REDUCED_REDUNDANCY</code> storage classes, nor objects in the\n                           <code>ARCHIVE_ACCESS</code> or <code>DEEP_ARCHIVE_ACCESS</code> access\n                        tiers of the <code>INTELLIGENT_TIERING</code> storage class. For more\n                        information about storage classes, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html\">Using Amazon S3\n                           storage classes</a> in the\n                        <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special Errors</dt>\n            <dd>\n               <p>For a list of special errors for this operation, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html#SelectObjectContentErrorCodeList\">List of SELECT Object Content Error Codes</a>\n               </p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>SelectObjectContent</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycleConfiguration.html\">PutBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "POST",
           "uri": "/{Bucket}/{Key+}?select&select-type=2",
@@ -33391,12 +33513,12 @@
         "KMSMasterKeyID": {
           "target": "com.amazonaws.s3#SSEKMSKeyId",
           "traits": {
-            "smithy.api#documentation": "<p>Amazon Web Services Key Management Service (KMS) customer managed key ID to use for the default\n         encryption. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - This parameter is allowed if and only if <code>SSEAlgorithm</code> is set to\n                  <code>aws:kms</code> or <code>aws:kms:dsse</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - This parameter is allowed if and only if <code>SSEAlgorithm</code> is set to\n                  <code>aws:kms</code>.</p>\n               </li>\n            </ul>\n         </note>\n         <p>You can specify the key ID, key alias, or the Amazon Resource Name (ARN) of the KMS\n         key.</p>\n         <ul>\n            <li>\n               <p>Key ID: <code>1234abcd-12ab-34cd-56ef-1234567890ab</code>\n               </p>\n            </li>\n            <li>\n               <p>Key ARN: <code>arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab</code>\n               </p>\n            </li>\n            <li>\n               <p>Key Alias: <code>alias/alias-name</code>\n               </p>\n            </li>\n         </ul>\n         <p>If you are using encryption with cross-account or Amazon Web Services service operations, you must use\n         a fully qualified KMS key ARN. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html#bucket-encryption-update-bucket-policy\">Using encryption for cross-account operations</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you're specifying a customer managed KMS key, we recommend using a fully qualified\n                  KMS key ARN. If you use a KMS key alias instead, then KMS resolves the key within the\n                  requester’s account. This behavior can result in data that's encrypted with a KMS key\n                  that belongs to the requester, and not the bucket owner. Also, if you use a key ID, you can run into a LogDestination undeliverable error when creating\n                  a VPC flow log. \n               </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - 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>\n               </li>\n            </ul>\n         </note>\n         <important>\n            <p>Amazon S3 only supports symmetric encryption KMS keys. For more information, see <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html\">Asymmetric keys in Amazon Web Services KMS</a> in the <i>Amazon Web Services Key Management Service\n               Developer Guide</i>.</p>\n         </important>"
+            "smithy.api#documentation": "<p>Amazon Web Services Key Management Service (KMS) customer managed key ID to use for the default\n         encryption. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - This parameter is\n                  allowed if and only if <code>SSEAlgorithm</code> is set to <code>aws:kms</code> or\n                     <code>aws:kms:dsse</code>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - This parameter is\n                  allowed if and only if <code>SSEAlgorithm</code> is set to\n                  <code>aws:kms</code>.</p>\n               </li>\n            </ul>\n         </note>\n         <p>You can specify the key ID, key alias, or the Amazon Resource Name (ARN) of the KMS\n         key.</p>\n         <ul>\n            <li>\n               <p>Key ID: <code>1234abcd-12ab-34cd-56ef-1234567890ab</code>\n               </p>\n            </li>\n            <li>\n               <p>Key ARN:\n                  <code>arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab</code>\n               </p>\n            </li>\n            <li>\n               <p>Key Alias: <code>alias/alias-name</code>\n               </p>\n            </li>\n         </ul>\n         <p>If you are using encryption with cross-account or Amazon Web Services service operations, you must use\n         a fully qualified KMS key ARN. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html#bucket-encryption-update-bucket-policy\">Using encryption for cross-account operations</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you're specifying\n                  a customer managed KMS key, we recommend using a fully qualified KMS key ARN.\n                  If you use a KMS key alias instead, then KMS resolves the key within the\n                  requester’s account. This behavior can result in data that's encrypted with a\n                  KMS key that belongs to the requester, and not the bucket owner. Also, if you\n                  use a key ID, you can run into a LogDestination undeliverable error when creating\n                  a VPC flow log. </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  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>\n               </li>\n            </ul>\n         </note>\n         <important>\n            <p>Amazon S3 only supports symmetric encryption KMS keys. For more information, see <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html\">Asymmetric keys in Amazon Web Services KMS</a> in the <i>Amazon Web Services Key Management Service\n               Developer Guide</i>.</p>\n         </important>"
           }
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Describes the default server-side encryption to apply to new objects in the bucket. If a\n         PUT Object request doesn't specify any server-side encryption, this default encryption will\n         be applied. For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTencryption.html\">PutBucketEncryption</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you don't specify a customer managed key at configuration, Amazon S3 automatically creates\n                  an Amazon Web Services KMS key (<code>aws/s3</code>) in your Amazon Web Services account the first time that you add an object encrypted\n                  with SSE-KMS to a bucket. By default, Amazon S3 uses this KMS key for SSE-KMS. </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - 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 for the lifetime of the bucket. \nThe <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.</p>\n               </li>\n            </ul>\n         </note>"
+        "smithy.api#documentation": "<p>Describes the default server-side encryption to apply to new objects in the bucket. If a\n         PUT Object request doesn't specify any server-side encryption, this default encryption will\n         be applied. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTencryption.html\">PutBucketEncryption</a>.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you don't specify\n                  a customer managed key at configuration, Amazon S3 automatically creates an Amazon Web Services KMS key\n                     (<code>aws/s3</code>) in your Amazon Web Services account the first time that you add an\n                  object encrypted with SSE-KMS to a bucket. By default, Amazon S3 uses this KMS key\n                  for SSE-KMS. </p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  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 for the lifetime of the bucket. \nThe <a href=\"https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk\">Amazon Web Services managed key</a> (<code>aws/s3</code>) isn't supported. \n</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  For directory buckets, there are only two supported options for server-side encryption: SSE-S3 and SSE-KMS.</p>\n               </li>\n            </ul>\n         </note>"
       }
     },
     "com.amazonaws.s3#ServerSideEncryptionConfiguration": {
@@ -33428,12 +33550,12 @@
         "BucketKeyEnabled": {
           "target": "com.amazonaws.s3#BucketKeyEnabled",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies whether Amazon S3 should use an S3 Bucket Key with server-side encryption using KMS\n         (SSE-KMS) for new objects in the bucket. Existing objects are not affected. Setting the\n            <code>BucketKeyEnabled</code> element to <code>true</code> causes Amazon S3 to use an S3\n         Bucket Key. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - By default, S3 Bucket Key is not enabled. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html\">Amazon S3 Bucket Keys</a> in the\n               <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - S3 Bucket Keys are always enabled for <code>GET</code> and <code>PUT</code> operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-objects-Batch-Ops\">the Copy operation in Batch Operations</a>, or \n                            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-import-job\">the import jobs</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n               </li>\n            </ul>\n         </note>"
+            "smithy.api#documentation": "<p>Specifies whether Amazon S3 should use an S3 Bucket Key with server-side encryption using KMS\n         (SSE-KMS) for new objects in the bucket. Existing objects are not affected. Setting the\n            <code>BucketKeyEnabled</code> element to <code>true</code> causes Amazon S3 to use an S3\n         Bucket Key. </p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - By default, S3\n                  Bucket Key is not enabled. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html\">Amazon S3 Bucket Keys</a> in the\n                     <i>Amazon S3 User Guide</i>.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  S3 Bucket Keys are always enabled for <code>GET</code> and <code>PUT</code> operations in a directory bucket and can’t be disabled. S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>, <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-objects-Batch-Ops\">the Copy operation in Batch Operations</a>, or \n                            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-import-job\">the import jobs</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n               </li>\n            </ul>\n         </note>"
           }
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Specifies the default server-side encryption configuration.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you're specifying a customer managed KMS key, we recommend using a fully qualified\n                     KMS key ARN. If you use a KMS key alias instead, then KMS resolves the key within the\n                     requester’s account. This behavior can result in data that's encrypted with a KMS key\n                     that belongs to the requester, and not the bucket owner.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> - 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>\n               </li>\n            </ul>\n         </note>"
+        "smithy.api#documentation": "<p>Specifies the default server-side encryption configuration.</p>\n         <note>\n            <ul>\n               <li>\n                  <p>\n                     <b>General purpose buckets</b> - If you're specifying\n                  a customer managed KMS key, we recommend using a fully qualified KMS key ARN.\n                  If you use a KMS key alias instead, then KMS resolves the key within the\n                  requester’s account. This behavior can result in data that's encrypted with a\n                  KMS key that belongs to the requester, and not the bucket owner.</p>\n               </li>\n               <li>\n                  <p>\n                     <b>Directory buckets</b> -\n                  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>\n               </li>\n            </ul>\n         </note>"
       }
     },
     "com.amazonaws.s3#ServerSideEncryptionRules": {
@@ -33454,7 +33576,7 @@
         "AccessKeyId": {
           "target": "com.amazonaws.s3#AccessKeyIdValue",
           "traits": {
-            "smithy.api#documentation": "<p>A unique identifier that's associated with a secret access key. The access key ID and the secret access key are used together to sign programmatic Amazon Web Services requests cryptographically. </p>",
+            "smithy.api#documentation": "<p>A unique identifier that's associated with a secret access key. The access key ID and\n         the secret access key are used together to sign programmatic Amazon Web Services requests\n         cryptographically. </p>",
             "smithy.api#required": {},
             "smithy.api#xmlName": "AccessKeyId"
           }
@@ -33462,7 +33584,7 @@
         "SecretAccessKey": {
           "target": "com.amazonaws.s3#SessionCredentialValue",
           "traits": {
-            "smithy.api#documentation": "<p>A key that's used with the access key ID to cryptographically sign programmatic Amazon Web Services requests. Signing a request identifies the sender and prevents the request from being altered. </p>",
+            "smithy.api#documentation": "<p>A key that's used with the access key ID to cryptographically sign programmatic Amazon Web Services\n         requests. Signing a request identifies the sender and prevents the request from being\n         altered. </p>",
             "smithy.api#required": {},
             "smithy.api#xmlName": "SecretAccessKey"
           }
@@ -33470,7 +33592,7 @@
         "SessionToken": {
           "target": "com.amazonaws.s3#SessionCredentialValue",
           "traits": {
-            "smithy.api#documentation": "<p>A part of the temporary security credentials. The session token is used to validate the temporary security credentials.  \n         \n      </p>",
+            "smithy.api#documentation": "<p>A part of the temporary security credentials. The session token is used to validate the\n         temporary security credentials.\n         \n      </p>",
             "smithy.api#required": {},
             "smithy.api#xmlName": "SessionToken"
           }
@@ -33478,14 +33600,14 @@
         "Expiration": {
           "target": "com.amazonaws.s3#SessionExpiration",
           "traits": {
-            "smithy.api#documentation": "<p>Temporary security credentials expire after a specified interval. After temporary credentials expire, any calls that you make with those credentials will fail. So you must generate a new set of temporary credentials. \n         Temporary credentials cannot be extended or refreshed beyond the original specified interval.</p>",
+            "smithy.api#documentation": "<p>Temporary security credentials expire after a specified interval. After temporary\n         credentials expire, any calls that you make with those credentials will fail. So you must\n         generate a new set of temporary credentials. Temporary credentials cannot be extended or\n         refreshed beyond the original specified interval.</p>",
             "smithy.api#required": {},
             "smithy.api#xmlName": "Expiration"
           }
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>The established temporary security credentials of the session.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - These session credentials are only supported for the authentication and authorization of Zonal endpoint API operations on directory buckets.</p>\n         </note>"
+        "smithy.api#documentation": "<p>The established temporary security credentials of the session.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - These session\n            credentials are only supported for the authentication and authorization of Zonal endpoint API operations\n            on directory buckets.</p>\n         </note>"
       }
     },
     "com.amazonaws.s3#SessionExpiration": {
@@ -33515,7 +33637,7 @@
       "type": "structure",
       "members": {},
       "traits": {
-        "smithy.api#documentation": "<p>To use simple format for S3 keys for log objects, set SimplePrefix to an empty object.</p>\n         <p>\n            <code>[DestinationPrefix][YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]</code>\n         </p>",
+        "smithy.api#documentation": "<p>To use simple format for S3 keys for log objects, set SimplePrefix to an empty\n         object.</p>\n         <p>\n            <code>[DestinationPrefix][YYYY]-[MM]-[DD]-[hh]-[mm]-[ss]-[UniqueString]</code>\n         </p>",
         "smithy.api#xmlName": "SimplePrefix"
       }
     },
@@ -33862,7 +33984,7 @@
         "SimplePrefix": {
           "target": "com.amazonaws.s3#SimplePrefix",
           "traits": {
-            "smithy.api#documentation": "<p>To use the simple format for S3 keys for log objects. To specify SimplePrefix format, set SimplePrefix to {}.</p>",
+            "smithy.api#documentation": "<p>To use the simple format for S3 keys for log objects. To specify SimplePrefix format,\n         set SimplePrefix to {}.</p>",
             "smithy.api#xmlName": "SimplePrefix"
           }
         },
@@ -33875,7 +33997,7 @@
         }
       },
       "traits": {
-        "smithy.api#documentation": "<p>Amazon S3 key format for log objects. Only one format, PartitionedPrefix or SimplePrefix, is allowed.</p>"
+        "smithy.api#documentation": "<p>Amazon S3 key format for log objects. Only one format, PartitionedPrefix or\n         SimplePrefix, is allowed.</p>"
       }
     },
     "com.amazonaws.s3#TargetPrefix": {
@@ -33935,6 +34057,15 @@
     "com.amazonaws.s3#Token": {
       "type": "string"
     },
+    "com.amazonaws.s3#TooManyParts": {
+      "type": "structure",
+      "members": {},
+      "traits": {
+        "smithy.api#documentation": "<p>\n         You have attempted to add more parts than the maximum of 10000 \n         that are allowed for this object. You can use the CopyObject operation \n         to copy this object to another and then add more data to the newly copied object.\n      </p>",
+        "smithy.api#error": "client",
+        "smithy.api#httpError": 400
+      }
+    },
     "com.amazonaws.s3#TopicArn": {
       "type": "string"
     },
@@ -34106,7 +34237,7 @@
         "aws.protocols#httpChecksum": {
           "requestAlgorithmMember": "ChecksumAlgorithm"
         },
-        "smithy.api#documentation": "<p>Uploads a part in a multipart upload.</p>\n         <note>\n            <p>In this operation, you provide new data as a part of an object in your request. However, you have an option\n            to specify your existing Amazon S3 object as a data source for the part you are uploading. To\n            upload a part from an existing object, you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a> operation.\n         </p>\n         </note>\n         <p>You must initiate a multipart upload (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>)\n         before you can upload any part. In response to your initiate request, Amazon S3 returns an\n         upload ID, a unique identifier that you must include in your upload part request.</p>\n         <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely\n         identifies a part and also defines its position within the object being created. If you\n         upload a new part using the same part number that was used with a previous part, the\n         previously uploaded part is overwritten.</p>\n         <p>For information about maximum and minimum part sizes and other multipart upload\n         specifications, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html\">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>After you initiate multipart upload and upload\n         one or more parts, you must either complete or abort multipart upload in order to stop\n         getting charged for storage of the uploaded parts. Only after you either complete or abort\n         multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts\n         storage.</p>\n         </note>\n         <p>For more information on multipart uploads, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in the\n         <i>Amazon S3 User Guide </i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        perform a multipart upload with encryption using an Key Management Service key, the\n                        requester must have permission to the <code>kms:Decrypt</code> and\n                           <code>kms:GenerateDataKey</code> actions on the key. The requester must\n                        also have permissions for the <code>kms:GenerateDataKey</code> action for\n                        the <code>CreateMultipartUpload</code> API. Then, the requester needs\n                        permissions for the <code>kms:Decrypt</code> action on the\n                           <code>UploadPart</code> and <code>UploadPartCopy</code> APIs.</p>\n                     <p>These permissions are required because Amazon S3 must decrypt and read data\n                        from the encrypted file parts before it completes the multipart upload. For\n                        more information about KMS permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting data\n                           using server-side encryption with KMS</a> in the\n                           <i>Amazon S3 User Guide</i>. For information about the\n                        permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart upload and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API and permissions</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted with\n                        SSE-KMS, you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Data integrity</dt>\n            <dd>\n               <p>\n                  <b>General purpose bucket</b> - To ensure that data is not corrupted traversing the network, specify the\n                     <code>Content-MD5</code> header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error. If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the\n                        <code>x-amz-content-sha256</code> header as a checksum instead of\n                        <code>Content-MD5</code>. For more information see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html\">Authenticating\n                           Requests: Using the Authorization Header (Amazon Web Services Signature Version 4)</a>. </p>\n               <note>\n                  <p>\n                     <b>Directory buckets</b> - MD5 is not supported by directory buckets. You can use checksum algorithms to check object integrity.</p>\n               </note>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it\n                        writes it to disks in its data centers and decrypts it when you access it. You have \n                        mutually exclusive options to protect data using server-side encryption in Amazon S3, depending\n                        on how you choose to manage the encryption keys. Specifically, the encryption key options\n                        are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and Customer-Provided Keys\n                        (SSE-C). Amazon S3 encrypts data with server-side encryption using Amazon S3 managed keys (SSE-S3) by\n                        default. You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption\n                        with other key options. The option you use depends on whether you want to use KMS keys\n                        (SSE-KMS) or provide your own encryption key (SSE-C).</p>\n                     <p>Server-side encryption is supported by the S3 Multipart Upload operations. Unless you are\n                        using a customer-provided encryption key (SSE-C), you don't need to specify the encryption\n                        parameters in each UploadPart request. Instead, you only need to specify the server-side\n                        encryption parameters in the initial Initiate Multipart request. For more information, see\n                        <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>.</p>\n                     <p>If you request server-side encryption using a customer-provided encryption key (SSE-C)\n                        in your initiate multipart upload request, you must provide identical encryption\n                        information in each part upload using the following request headers.</p>\n                     <ul>\n                        <li>\n                           <p>x-amz-server-side-encryption-customer-algorithm</p>\n                        </li>\n                        <li>\n                           <p>x-amz-server-side-encryption-customer-key</p>\n                        </li>\n                        <li>\n                           <p>x-amz-server-side-encryption-customer-key-MD5</p>\n                        </li>\n                     </ul>\n                     <p>\n                        For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Using Server-Side\n                           Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>).</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special errors</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>Error Code: <code>NoSuchUpload</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 404 Not Found </p>\n                        </li>\n                        <li>\n                           <p>SOAP Fault Code Prefix: Client</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>UploadPart</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Uploads a part in a multipart upload.</p>\n         <note>\n            <p>In this operation, you provide new data as a part of an object in your request.\n            However, you have an option to specify your existing Amazon S3 object as a data source for\n            the part you are uploading. To upload a part from an existing object, you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a> operation. </p>\n         </note>\n         <p>You must initiate a multipart upload (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>)\n         before you can upload any part. In response to your initiate request, Amazon S3 returns an\n         upload ID, a unique identifier that you must include in your upload part request.</p>\n         <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely\n         identifies a part and also defines its position within the object being created. If you\n         upload a new part using the same part number that was used with a previous part, the\n         previously uploaded part is overwritten.</p>\n         <p>For information about maximum and minimum part sizes and other multipart upload\n         specifications, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html\">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>After you initiate multipart upload and upload one or more parts, you must either\n            complete or abort multipart upload in order to stop getting charged for storage of the\n            uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up\n            the parts storage and stops charging you for the parts storage.</p>\n         </note>\n         <p>For more information on multipart uploads, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html\">Multipart Upload Overview</a> in the\n            <i>Amazon S3 User Guide </i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Permissions</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - To\n                        perform a multipart upload with encryption using an Key Management Service key, the\n                        requester must have permission to the <code>kms:Decrypt</code> and\n                           <code>kms:GenerateDataKey</code> actions on the key. The requester must\n                        also have permissions for the <code>kms:GenerateDataKey</code> action for\n                        the <code>CreateMultipartUpload</code> API. Then, the requester needs\n                        permissions for the <code>kms:Decrypt</code> action on the\n                           <code>UploadPart</code> and <code>UploadPartCopy</code> APIs.</p>\n                     <p>These permissions are required because Amazon S3 must decrypt and read data\n                        from the encrypted file parts before it completes the multipart upload. For\n                        more information about KMS permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting data\n                           using server-side encryption with KMS</a> in the\n                           <i>Amazon S3 User Guide</i>. For information about the\n                        permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart upload and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API and permissions</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use. \nAmazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html\">\n                           <code>CreateSession</code>\n                        </a>.</p>\n                     <p>If the object is encrypted with SSE-KMS, you must also have the\n                           <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions\n                        in IAM identity-based policies and KMS key policies for the KMS\n                        key.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Data integrity</dt>\n            <dd>\n               <p>\n                  <b>General purpose bucket</b> - To ensure that data\n                  is not corrupted traversing the network, specify the <code>Content-MD5</code>\n                  header in the upload part request. Amazon S3 checks the part data against the provided\n                  MD5 value. If they do not match, Amazon S3 returns an error. If the upload request is\n                  signed with Signature Version 4, then Amazon Web Services S3 uses the\n                     <code>x-amz-content-sha256</code> header as a checksum instead of\n                     <code>Content-MD5</code>. For more information see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html\">Authenticating Requests: Using the Authorization Header (Amazon Web Services Signature\n                     Version 4)</a>. </p>\n               <note>\n                  <p>\n                     <b>Directory buckets</b> - MD5 is not supported by directory buckets. You can use checksum algorithms to check object integrity.</p>\n               </note>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket</b> - Server-side\n                        encryption is for data encryption at rest. Amazon S3 encrypts your data as it\n                        writes it to disks in its data centers and decrypts it when you access it.\n                        You have mutually exclusive options to protect data using server-side\n                        encryption in Amazon S3, depending on how you choose to manage the encryption\n                        keys. Specifically, the encryption key options are Amazon S3 managed keys\n                        (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and Customer-Provided Keys (SSE-C).\n                        Amazon S3 encrypts data with server-side encryption using Amazon S3 managed keys\n                        (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt data at rest\n                        using server-side encryption with other key options. The option you use\n                        depends on whether you want to use KMS keys (SSE-KMS) or provide your own\n                        encryption key (SSE-C).</p>\n                     <p>Server-side encryption is supported by the S3 Multipart Upload\n                        operations. Unless you are using a customer-provided encryption key (SSE-C),\n                        you don't need to specify the encryption parameters in each UploadPart\n                        request. Instead, you only need to specify the server-side encryption\n                        parameters in the initial Initiate Multipart request. For more information,\n                        see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>.</p>\n                     <p>If you request server-side encryption using a customer-provided\n                        encryption key (SSE-C) in your initiate multipart upload request, you must\n                        provide identical encryption information in each part upload using the\n                        following request headers.</p>\n                     <ul>\n                        <li>\n                           <p>x-amz-server-side-encryption-customer-algorithm</p>\n                        </li>\n                        <li>\n                           <p>x-amz-server-side-encryption-customer-key</p>\n                        </li>\n                        <li>\n                           <p>x-amz-server-side-encryption-customer-key-MD5</p>\n                        </li>\n                     </ul>\n                     <p> For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Using\n                           Server-Side Encryption</a> in the\n                           <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory buckets </b> -\n                        For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>).</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special errors</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>Error Code: <code>NoSuchUpload</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified multipart upload does not exist. The\n                              upload ID might be invalid, or the multipart upload might have been\n                              aborted or completed.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 404 Not Found </p>\n                        </li>\n                        <li>\n                           <p>SOAP Fault Code Prefix: Client</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>UploadPart</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To upload a part",
@@ -34139,7 +34270,7 @@
         "target": "com.amazonaws.s3#UploadPartCopyOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Uploads a part by copying data from an existing object as data source. To specify the\n         data source, you add the request header <code>x-amz-copy-source</code> in your request. To specify \n         a byte range, you add the request header <code>x-amz-copy-source-range</code> in your\n         request. </p>\n         <p>For information about maximum and minimum part sizes and other multipart upload\n         specifications, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html\">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>. </p>\n         <note>\n            <p>Instead of copying data from an existing object as part data, you might use the <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n            action to upload new data as a part of an object in your request.</p>\n         </note>\n         <p>You must initiate a multipart upload before you can upload any part. In response to your\n         initiate request, Amazon S3 returns the upload ID, a unique identifier that you must include in\n         your upload part request.</p>\n         <p>For conceptual information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading\n         Objects Using Multipart Upload</a> in the\n         <i>Amazon S3 User Guide</i>. For information about copying objects using a single atomic action vs. a multipart\n         upload, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html\">Operations on Objects</a> in\n         the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Authentication and authorization</dt>\n            <dd>\n               <p>All <code>UploadPartCopy</code> requests must be authenticated and signed by using IAM credentials (access key ID and secret access key for the IAM identities). All headers with the <code>x-amz-</code> prefix, including\n                        <code>x-amz-copy-source</code>, must be signed. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n               <p>\n                  <b>Directory buckets</b> - You must use IAM credentials to authenticate and authorize your access to the <code>UploadPartCopy</code> API operation, instead of using the \n                  temporary security credentials through the <code>CreateSession</code> API operation.</p>\n               <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have <code>READ</code> access to the source object and <code>WRITE</code>\n                  access to the destination bucket.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - You\n                        must have the permissions in a policy based on the bucket types of your\n                        source bucket and destination bucket in an <code>UploadPartCopy</code>\n                        operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object is in a general purpose bucket, you must have the\n                                 <b>\n                                 <code>s3:GetObject</code>\n                              </b>\n                              permission to read the source object that is being copied. </p>\n                        </li>\n                        <li>\n                           <p>If the destination bucket is a general purpose bucket, you must have the\n                                 <b>\n                                 <code>s3:PutObject</code>\n                              </b>\n                              permission to write the object copy to the destination bucket. </p>\n                        </li>\n                        <li>\n                           <p>To perform a multipart upload with encryption using an Key Management Service\n                              key, the requester must have permission to the\n                                 <code>kms:Decrypt</code> and <code>kms:GenerateDataKey</code>\n                              actions on the key. The requester must also have permissions for the\n                                 <code>kms:GenerateDataKey</code> action for the\n                                 <code>CreateMultipartUpload</code> API. Then, the requester needs\n                              permissions for the <code>kms:Decrypt</code> action on the\n                                 <code>UploadPart</code> and <code>UploadPartCopy</code> APIs. These\n                              permissions are required because Amazon S3 must decrypt and read data from\n                              the encrypted file parts before it completes the multipart upload. For\n                              more information about KMS permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting\n                                 data using server-side encryption with KMS</a> in the\n                                 <i>Amazon S3 User Guide</i>. For information about the\n                              permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart upload\n                                 and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API and permissions</a> in the\n                                 <i>Amazon S3 User Guide</i>.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have permissions in a bucket policy or an IAM identity-based policy based on the source and destination\n                        bucket types in an <code>UploadPartCopy</code> operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object that you want to copy is in a\n                              directory bucket, you must have the <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in\n                              the <code>Action</code> element of a policy to read the object. By\n                              default, the session is in the <code>ReadWrite</code> mode. If you\n                              want to restrict the access, you can explicitly set the\n                                 <code>s3express:SessionMode</code> condition key to\n                                 <code>ReadOnly</code> on the copy source bucket.</p>\n                        </li>\n                        <li>\n                           <p>If the copy destination is a directory bucket, you must have the \n                              <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in the\n                              <code>Action</code> element of a policy to write the object\n                              to the destination. The <code>s3express:SessionMode</code> condition\n                              key cannot be set to <code>ReadOnly</code> on the copy destination. </p>\n                        </li>\n                     </ul>\n                     <p>If the object is encrypted with\n                        SSE-KMS, you must also have the\n                        <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>\n                     <p>For example policies, 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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the\n                        <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose buckets </b> - \n                     \n                     For information about using server-side encryption with customer-provided\n                           encryption keys with the <code>UploadPartCopy</code> operation, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>.\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     <note>\n                        <p>For directory buckets, when you perform a <code>CreateMultipartUpload</code> operation and an <code>UploadPartCopy</code> operation,  \n                        the request headers you provide in the <code>CreateMultipartUpload</code> request must match the default encryption configuration of the destination bucket. </p>\n                     </note>\n                     <p>S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special errors</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>Error Code: <code>NoSuchUpload</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified multipart upload does not exist. The\n                                 upload ID might be invalid, or the multipart upload might have been\n                                 aborted or completed.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 404 Not Found</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>InvalidRequest</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified copy source is not supported as a\n                                    byte-range copy source.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>UploadPartCopy</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Uploads a part by copying data from an existing object as data source. To specify the\n         data source, you add the request header <code>x-amz-copy-source</code> in your request. To\n         specify a byte range, you add the request header <code>x-amz-copy-source-range</code> in\n         your request. </p>\n         <p>For information about maximum and minimum part sizes and other multipart upload\n         specifications, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html\">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>. </p>\n         <note>\n            <p>Instead of copying data from an existing object as part data, you might use the\n               <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a> action to upload new data as a part of an object in your\n            request.</p>\n         </note>\n         <p>You must initiate a multipart upload before you can upload any part. In response to your\n         initiate request, Amazon S3 returns the upload ID, a unique identifier that you must include in\n         your upload part request.</p>\n         <p>For conceptual information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n            Upload</a> in the <i>Amazon S3 User Guide</i>. For information about\n         copying objects using a single atomic action vs. a multipart upload, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html\">Operations on\n            Objects</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>\n               </code>. Path-style requests are not supported. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html\">Regional and Zonal endpoints</a> in the\n    <i>Amazon S3 User Guide</i>.</p>\n         </note>\n         <dl>\n            <dt>Authentication and authorization</dt>\n            <dd>\n               <p>All <code>UploadPartCopy</code> requests must be authenticated and signed by\n                  using IAM credentials (access key ID and secret access key for the IAM\n                  identities). All headers with the <code>x-amz-</code> prefix, including\n                     <code>x-amz-copy-source</code>, must be signed. For more information, see\n                     <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html\">REST Authentication</a>.</p>\n               <p>\n                  <b>Directory buckets</b> - You must use IAM\n                  credentials to authenticate and authorize your access to the\n                     <code>UploadPartCopy</code> API operation, instead of using the temporary\n                  security credentials through the <code>CreateSession</code> API operation.</p>\n               <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your\n                  behalf.</p>\n            </dd>\n            <dt>Permissions</dt>\n            <dd>\n               <p>You must have <code>READ</code> access to the source object and\n                     <code>WRITE</code> access to the destination bucket.</p>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose bucket permissions</b> - You\n                        must have the permissions in a policy based on the bucket types of your\n                        source bucket and destination bucket in an <code>UploadPartCopy</code>\n                        operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object is in a general purpose bucket, you must have the\n                                 <b>\n                                 <code>s3:GetObject</code>\n                              </b>\n                              permission to read the source object that is being copied. </p>\n                        </li>\n                        <li>\n                           <p>If the destination bucket is a general purpose bucket, you must have the\n                                 <b>\n                                 <code>s3:PutObject</code>\n                              </b>\n                              permission to write the object copy to the destination bucket. </p>\n                        </li>\n                        <li>\n                           <p>To perform a multipart upload with encryption using an Key Management Service\n                              key, the requester must have permission to the\n                                 <code>kms:Decrypt</code> and <code>kms:GenerateDataKey</code>\n                              actions on the key. The requester must also have permissions for the\n                                 <code>kms:GenerateDataKey</code> action for the\n                                 <code>CreateMultipartUpload</code> API. Then, the requester needs\n                              permissions for the <code>kms:Decrypt</code> action on the\n                                 <code>UploadPart</code> and <code>UploadPartCopy</code> APIs. These\n                              permissions are required because Amazon S3 must decrypt and read data from\n                              the encrypted file parts before it completes the multipart upload. For\n                              more information about KMS permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html\">Protecting\n                                 data using server-side encryption with KMS</a> in the\n                                 <i>Amazon S3 User Guide</i>. For information about the\n                              permissions required to use the multipart upload API, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart upload\n                                 and permissions</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions\">Multipart upload API and permissions</a> in the\n                                 <i>Amazon S3 User Guide</i>.</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory bucket permissions</b> -\n                        You must have permissions in a bucket policy or an IAM identity-based policy based on the\n                        source and destination bucket types in an <code>UploadPartCopy</code>\n                        operation.</p>\n                     <ul>\n                        <li>\n                           <p>If the source object that you want to copy is in a\n                              directory bucket, you must have the <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in\n                              the <code>Action</code> element of a policy to read the object. By\n                              default, the session is in the <code>ReadWrite</code> mode. If you\n                              want to restrict the access, you can explicitly set the\n                                 <code>s3express:SessionMode</code> condition key to\n                                 <code>ReadOnly</code> on the copy source bucket.</p>\n                        </li>\n                        <li>\n                           <p>If the copy destination is a directory bucket, you must have the\n                                 <b>\n                                 <code>s3express:CreateSession</code>\n                              </b> permission in the\n                                 <code>Action</code> element of a policy to write the object to the\n                              destination. The <code>s3express:SessionMode</code> condition key\n                              cannot be set to <code>ReadOnly</code> on the copy destination.\n                           </p>\n                        </li>\n                     </ul>\n                     <p>If the object is encrypted with SSE-KMS, you must also have the\n                           <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions\n                        in IAM identity-based policies and KMS key policies for the KMS\n                        key.</p>\n                     <p>For example policies, 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> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html\">Amazon Web Services Identity and Access Management (IAM) identity-based policies for\n                           S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Encryption</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>\n                        <b>General purpose buckets </b> -\n                         For information about using\n                        server-side encryption with customer-provided encryption keys with the\n                           <code>UploadPartCopy</code> operation, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html\">CopyObject</a> and\n                           <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>. </p>\n                  </li>\n                  <li>\n                     <p>\n                        <b>Directory buckets </b> -\n                        For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). For more\n         information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html\">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>.</p>\n                     <note>\n                        <p>For directory buckets, when you perform a\n                              <code>CreateMultipartUpload</code> operation and an\n                              <code>UploadPartCopy</code> operation, the request headers you provide\n                           in the <code>CreateMultipartUpload</code> request must match the default\n                           encryption configuration of the destination bucket. </p>\n                     </note>\n                     <p>S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets  \nto directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html\">UploadPartCopy</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>\n                  </li>\n               </ul>\n            </dd>\n            <dt>Special errors</dt>\n            <dd>\n               <ul>\n                  <li>\n                     <p>Error Code: <code>NoSuchUpload</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified multipart upload does not exist. The\n                              upload ID might be invalid, or the multipart upload might have been\n                              aborted or completed.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 404 Not Found</p>\n                        </li>\n                     </ul>\n                  </li>\n                  <li>\n                     <p>Error Code: <code>InvalidRequest</code>\n                     </p>\n                     <ul>\n                        <li>\n                           <p>Description: The specified copy source is not supported as a\n                              byte-range copy source.</p>\n                        </li>\n                        <li>\n                           <p>HTTP Status Code: 400 Bad Request</p>\n                        </li>\n                     </ul>\n                  </li>\n               </ul>\n            </dd>\n            <dt>HTTP Host header syntax</dt>\n            <dd>\n               <p>\n                  <b>Directory buckets </b> - The HTTP Host header syntax is <code>\n                     <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>\n            </dd>\n         </dl>\n         <p>The following operations are related to <code>UploadPartCopy</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#examples": [
           {
             "title": "To upload a part by copying byte range from an existing object as data source",
@@ -34209,7 +34340,7 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,\n            <code>AES256</code>, <code>aws:kms</code>).</p>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for\n         example, <code>AES256</code>, <code>aws:kms</code>).</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
@@ -34223,7 +34354,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification of\n         the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification\n         of the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -34258,7 +34389,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The bucket name.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The bucket name.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -34269,7 +34400,7 @@
         "CopySource": {
           "target": "com.amazonaws.s3#CopySource",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the source object for the copy operation. You specify the value in one of two\n         formats, depending on whether you want to access the source object through an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-points.html\">access point</a>:</p>\n         <ul>\n            <li>\n               <p>For objects not accessed through an access point, specify the name of the source bucket\n               and key of the source object, separated by a slash (/). For example, to copy the\n               object <code>reports/january.pdf</code> from the bucket\n               <code>awsexamplebucket</code>, use <code>awsexamplebucket/reports/january.pdf</code>.\n               The value must be URL-encoded.</p>\n            </li>\n            <li>\n               <p>For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format <code>arn:aws:s3:<Region>:<account-id>:accesspoint/<access-point-name>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through access point <code>my-access-point</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf</code>. The value must be URL encoded.</p>\n               <note>\n                  <ul>\n                     <li>\n                        <p>Amazon S3 supports copy operations using Access points only when the source and destination buckets are in the same Amazon Web Services Region.</p>\n                     </li>\n                     <li>\n                        <p>Access points are not supported by directory buckets.</p>\n                     </li>\n                  </ul>\n               </note>\n               <p>Alternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format <code>arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through outpost <code>my-outpost</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf</code>. The value must be URL-encoded.  </p>\n            </li>\n         </ul>\n         <p>If your bucket has versioning enabled, you could have multiple versions of the\n         same object. By default, <code>x-amz-copy-source</code> identifies the current\n         version of the source object to copy. \n         To copy a specific version of the source object to copy, append <code>?versionId=<version-id></code>\n         to the <code>x-amz-copy-source</code> request header (for example, \n         <code>x-amz-copy-source: /awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>).\n         </p>\n         <p>If the current version is a delete marker and you\n         don't specify a versionId in the <code>x-amz-copy-source</code> request header, Amazon S3 returns a\n         <code>404 Not Found</code> error, because the object does not exist. If you specify versionId in the\n         <code>x-amz-copy-source</code> and the versionId is a delete marker, Amazon S3\n         returns an HTTP <code>400 Bad Request</code> error, because you are not allowed to specify a delete marker\n         as a version for the <code>x-amz-copy-source</code>. </p>\n         <note>\n            <p>\n               <b>Directory buckets</b> - S3 Versioning isn't enabled and supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the source object for the copy operation. You specify the value in one of two\n         formats, depending on whether you want to access the source object through an <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-points.html\">access point</a>:</p>\n         <ul>\n            <li>\n               <p>For objects not accessed through an access point, specify the name of the source bucket\n               and key of the source object, separated by a slash (/). For example, to copy the\n               object <code>reports/january.pdf</code> from the bucket\n               <code>awsexamplebucket</code>, use <code>awsexamplebucket/reports/january.pdf</code>.\n               The value must be URL-encoded.</p>\n            </li>\n            <li>\n               <p>For objects accessed through access points, specify the Amazon Resource Name (ARN) of the object as accessed through the access point, in the format <code>arn:aws:s3:<Region>:<account-id>:accesspoint/<access-point-name>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through access point <code>my-access-point</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3:us-west-2:123456789012:accesspoint/my-access-point/object/reports/january.pdf</code>. The value must be URL encoded.</p>\n               <note>\n                  <ul>\n                     <li>\n                        <p>Amazon S3 supports copy operations using Access points only when the source and destination buckets are in the same Amazon Web Services Region.</p>\n                     </li>\n                     <li>\n                        <p>Access points are not supported by directory buckets.</p>\n                     </li>\n                  </ul>\n               </note>\n               <p>Alternatively, for objects accessed through Amazon S3 on Outposts, specify the ARN of the object as accessed in the format <code>arn:aws:s3-outposts:<Region>:<account-id>:outpost/<outpost-id>/object/<key></code>. For example, to copy the object <code>reports/january.pdf</code> through outpost <code>my-outpost</code> owned by account <code>123456789012</code> in Region <code>us-west-2</code>, use the URL encoding of <code>arn:aws:s3-outposts:us-west-2:123456789012:outpost/my-outpost/object/reports/january.pdf</code>. The value must be URL-encoded.  </p>\n            </li>\n         </ul>\n         <p>If your bucket has versioning enabled, you could have multiple versions of the same\n         object. By default, <code>x-amz-copy-source</code> identifies the current version of the\n         source object to copy. To copy a specific version of the source object to copy, append\n            <code>?versionId=<version-id></code> to the <code>x-amz-copy-source</code> request\n         header (for example, <code>x-amz-copy-source:\n            /awsexamplebucket/reports/january.pdf?versionId=QUpfdndhfd8438MNFDN93jdnJFkdmqnh893</code>). </p>\n         <p>If the current version is a delete marker and you don't specify a versionId in the\n            <code>x-amz-copy-source</code> request header, Amazon S3 returns a <code>404 Not Found</code>\n         error, because the object does not exist. If you specify versionId in the\n            <code>x-amz-copy-source</code> and the versionId is a delete marker, Amazon S3 returns an\n         HTTP <code>400 Bad Request</code> error, because you are not allowed to specify a delete\n         marker as a version for the <code>x-amz-copy-source</code>. </p>\n         <note>\n            <p>\n               <b>Directory buckets</b> -\n            S3 Versioning isn't enabled and supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-copy-source",
             "smithy.api#required": {}
           }
@@ -34277,28 +34408,28 @@
         "CopySourceIfMatch": {
           "target": "com.amazonaws.s3#CopySourceIfMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) matches the specified tag.</p>\n         <p>If both of the\n      <code>x-amz-copy-source-if-match</code> and\n      <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the\n      request as follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,\n         and;</p>\n         <p>\n            <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n         <code>false</code>;</p>\n         <p>Amazon S3 returns <code>200 OK</code> and copies the data.\n         </p>",
+            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) matches the specified tag.</p>\n         <p>If both of the <code>x-amz-copy-source-if-match</code> and\n            <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request as\n         follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,\n         and;</p>\n         <p>\n            <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n            <code>false</code>;</p>\n         <p>Amazon S3 returns <code>200 OK</code> and copies the data.\n         </p>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-match"
           }
         },
         "CopySourceIfModifiedSince": {
           "target": "com.amazonaws.s3#CopySourceIfModifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if it has been modified since the specified time.</p>\n         <p>If both of the\n      <code>x-amz-copy-source-if-none-match</code> and\n      <code>x-amz-copy-source-if-modified-since</code> headers are present in the\n      request as follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-none-match</code> condition evaluates to\n         <code>false</code>, and;</p>\n         <p>\n            <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n         <code>true</code>;</p>\n         <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.\n         </p>",
+            "smithy.api#documentation": "<p>Copies the object if it has been modified since the specified time.</p>\n         <p>If both of the <code>x-amz-copy-source-if-none-match</code> and\n            <code>x-amz-copy-source-if-modified-since</code> headers are present in the request as\n         follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-none-match</code> condition evaluates to <code>false</code>,\n         and;</p>\n         <p>\n            <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n            <code>true</code>;</p>\n         <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.\n         </p>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-modified-since"
           }
         },
         "CopySourceIfNoneMatch": {
           "target": "com.amazonaws.s3#CopySourceIfNoneMatch",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) is different than the specified ETag.</p>\n         <p>If both of the\n      <code>x-amz-copy-source-if-none-match</code> and\n      <code>x-amz-copy-source-if-modified-since</code> headers are present in the\n      request as follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-none-match</code> condition evaluates to\n         <code>false</code>, and;</p>\n         <p>\n            <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n         <code>true</code>;</p>\n         <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.\n         </p>",
+            "smithy.api#documentation": "<p>Copies the object if its entity tag (ETag) is different than the specified ETag.</p>\n         <p>If both of the <code>x-amz-copy-source-if-none-match</code> and\n            <code>x-amz-copy-source-if-modified-since</code> headers are present in the request as\n         follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-none-match</code> condition evaluates to <code>false</code>,\n         and;</p>\n         <p>\n            <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n            <code>true</code>;</p>\n         <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.\n         </p>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-none-match"
           }
         },
         "CopySourceIfUnmodifiedSince": {
           "target": "com.amazonaws.s3#CopySourceIfUnmodifiedSince",
           "traits": {
-            "smithy.api#documentation": "<p>Copies the object if it hasn't been modified since the specified time.</p>\n         <p>If both of the\n         <code>x-amz-copy-source-if-match</code> and\n         <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the\n         request as follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,\n         and;</p>\n         <p>\n            <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n         <code>false</code>;</p>\n         <p>Amazon S3 returns <code>200 OK</code> and copies the data.\n         </p>",
+            "smithy.api#documentation": "<p>Copies the object if it hasn't been modified since the specified time.</p>\n         <p>If both of the <code>x-amz-copy-source-if-match</code> and\n            <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request as\n         follows:</p>\n         <p>\n            <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,\n         and;</p>\n         <p>\n            <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n            <code>false</code>;</p>\n         <p>Amazon S3 returns <code>200 OK</code> and copies the data.\n         </p>",
             "smithy.api#httpHeader": "x-amz-copy-source-if-unmodified-since"
           }
         },
@@ -34336,7 +34467,7 @@
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n         AES256).</p>\n         <note>\n            <p>This functionality is not supported when the destination bucket is a directory bucket.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>\n         <note>\n            <p>This functionality is not supported when the destination bucket is a directory bucket.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
@@ -34357,7 +34488,7 @@
         "CopySourceSSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#CopySourceSSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when decrypting the source object (for example,\n         <code>AES256</code>).</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when decrypting the source object (for example,\n            <code>AES256</code>).</p>\n         <note>\n            <p>This functionality is not supported when the source object is in a directory bucket.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-copy-source-server-side-encryption-customer-algorithm"
           }
         },
@@ -34406,7 +34537,7 @@
         "ServerSideEncryption": {
           "target": "com.amazonaws.s3#ServerSideEncryption",
           "traits": {
-            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for example,\n            <code>AES256</code>, <code>aws:kms</code>).</p>",
+            "smithy.api#documentation": "<p>The server-side encryption algorithm used when you store this object in Amazon S3 (for\n         example, <code>AES256</code>, <code>aws:kms</code>).</p>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption"
           }
         },
@@ -34455,7 +34586,7 @@
         "SSECustomerKeyMD5": {
           "target": "com.amazonaws.s3#SSECustomerKeyMD5",
           "traits": {
-            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification of\n         the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>If server-side encryption with a customer-provided encryption key was requested, the\n         response will include this header to provide the round-trip message integrity verification\n         of the customer-provided encryption key.</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-key-MD5"
           }
         },
@@ -34498,7 +34629,7 @@
         "Bucket": {
           "target": "com.amazonaws.s3#BucketName",
           "traits": {
-            "smithy.api#documentation": "<p>The name of the bucket to which the multipart upload was initiated.</p>\n         <p>\n            <b>Directory buckets</b> - When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
+            "smithy.api#documentation": "<p>The name of the bucket to which the multipart upload was initiated.</p>\n         <p>\n            <b>Directory buckets</b> -\n         When you use this operation with a directory bucket, you must use virtual-hosted-style requests in the format <code>\n               <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>. Path-style requests are not supported.  Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format <code>\n               <i>bucket_base_name</i>--<i>az-id</i>--x-s3</code> (for example, <code>\n               <i>DOC-EXAMPLE-BUCKET</i>--<i>usw2-az1</i>--x-s3</code>). For information about bucket naming\n         restrictions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-bucket-naming-rules.html\">Directory bucket naming\n            rules</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>\n            <b>Access points</b> - When you use this action with an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form <i>AccessPointName</i>-<i>AccountId</i>.s3-accesspoint.<i>Region</i>.amazonaws.com. When using this action with an access point through the Amazon Web Services SDKs, you provide the access point ARN in place of the bucket name. For more information about access point ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-access-points.html\">Using access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <note>\n            <p>Access points and Object Lambda access points are not supported by directory buckets.</p>\n         </note>\n         <p>\n            <b>S3 on Outposts</b> - When you use this action with Amazon S3 on Outposts, you must direct requests to the S3 on Outposts hostname. The S3 on Outposts hostname takes the form <code>\n               <i>AccessPointName</i>-<i>AccountId</i>.<i>outpostID</i>.s3-outposts.<i>Region</i>.amazonaws.com</code>. When you use this action with S3 on Outposts through the Amazon Web Services SDKs, you provide the Outposts access point ARN in place of the bucket name. For more information about S3 on Outposts ARNs, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/S3onOutposts.html\">What is S3 on Outposts?</a> in the <i>Amazon S3 User Guide</i>.</p>",
             "smithy.api#httpLabel": {},
             "smithy.api#required": {},
             "smithy.rules#contextParam": {
@@ -34585,7 +34716,7 @@
         "SSECustomerAlgorithm": {
           "target": "com.amazonaws.s3#SSECustomerAlgorithm",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example,\n         AES256).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
+            "smithy.api#documentation": "<p>Specifies the algorithm to use when encrypting the object (for example, AES256).</p>\n         <note>\n            <p>This functionality is not supported for directory buckets.</p>\n         </note>",
             "smithy.api#httpHeader": "x-amz-server-side-encryption-customer-algorithm"
           }
         },
@@ -34706,7 +34837,7 @@
       "traits": {
         "aws.auth#unsignedPayload": {},
         "smithy.api#auth": ["aws.auth#sigv4"],
-        "smithy.api#documentation": "<note>\n            <p>This operation is not supported by directory buckets.</p>\n         </note>\n         <p>Passes transformed objects to a <code>GetObject</code> operation when using Object Lambda access points. For\n         information about Object Lambda access points, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/transforming-objects.html\">Transforming objects with\n            Object Lambda access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>This operation supports metadata that can be returned by <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>, in addition to\n            <code>RequestRoute</code>, <code>RequestToken</code>, <code>StatusCode</code>,\n            <code>ErrorCode</code>, and <code>ErrorMessage</code>. The <code>GetObject</code>\n         response metadata is supported so that the <code>WriteGetObjectResponse</code> caller,\n         typically an Lambda function, can provide the same metadata when it internally invokes\n            <code>GetObject</code>. When <code>WriteGetObjectResponse</code> is called by a\n         customer-owned Lambda function, the metadata returned to the end user\n            <code>GetObject</code> call might differ from what Amazon S3 would normally return.</p>\n         <p>You can include any number of metadata headers. When including a metadata header, it\n         should be prefaced with <code>x-amz-meta</code>. For example,\n            <code>x-amz-meta-my-custom-header: MyCustomValue</code>. The primary use case for this\n         is to forward <code>GetObject</code> metadata.</p>\n         <p>Amazon Web Services provides some prebuilt Lambda functions that you can use with S3 Object Lambda to\n         detect and redact personally identifiable information (PII) and decompress S3 objects.\n         These Lambda functions are available in the Amazon Web Services Serverless Application Repository, and\n         can be selected through the Amazon Web Services Management Console when you create your Object Lambda access point.</p>\n         <p>Example 1: PII Access Control - This Lambda function uses Amazon Comprehend, a\n         natural language processing (NLP) service using machine learning to find insights and\n         relationships in text. It automatically detects personally identifiable information (PII)\n         such as names, addresses, dates, credit card numbers, and social security numbers from\n         documents in your Amazon S3 bucket. </p>\n         <p>Example 2: PII Redaction - This Lambda function uses Amazon Comprehend, a natural\n         language processing (NLP) service using machine learning to find insights and relationships\n         in text. It automatically redacts personally identifiable information (PII) such as names,\n         addresses, dates, credit card numbers, and social security numbers from documents in your\n         Amazon S3 bucket. </p>\n         <p>Example 3: Decompression - The Lambda function S3ObjectLambdaDecompression, is\n         equipped to decompress objects stored in S3 in one of six compressed file formats including\n         bzip2, gzip, snappy, zlib, zstandard and ZIP. </p>\n         <p>For information on how to view and use these functions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/olap-examples.html\">Using Amazon Web Services built Lambda\n            functions</a> in the <i>Amazon S3 User Guide</i>.</p>",
+        "smithy.api#documentation": "<note>\n            <p>This operation is not supported for directory buckets.</p>\n         </note>\n         <p>Passes transformed objects to a <code>GetObject</code> operation when using Object Lambda access points. For\n         information about Object Lambda access points, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/transforming-objects.html\">Transforming objects with\n            Object Lambda access points</a> in the <i>Amazon S3 User Guide</i>.</p>\n         <p>This operation supports metadata that can be returned by <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html\">GetObject</a>, in addition to\n            <code>RequestRoute</code>, <code>RequestToken</code>, <code>StatusCode</code>,\n            <code>ErrorCode</code>, and <code>ErrorMessage</code>. The <code>GetObject</code>\n         response metadata is supported so that the <code>WriteGetObjectResponse</code> caller,\n         typically an Lambda function, can provide the same metadata when it internally invokes\n            <code>GetObject</code>. When <code>WriteGetObjectResponse</code> is called by a\n         customer-owned Lambda function, the metadata returned to the end user\n            <code>GetObject</code> call might differ from what Amazon S3 would normally return.</p>\n         <p>You can include any number of metadata headers. When including a metadata header, it\n         should be prefaced with <code>x-amz-meta</code>. For example,\n            <code>x-amz-meta-my-custom-header: MyCustomValue</code>. The primary use case for this\n         is to forward <code>GetObject</code> metadata.</p>\n         <p>Amazon Web Services provides some prebuilt Lambda functions that you can use with S3 Object Lambda to\n         detect and redact personally identifiable information (PII) and decompress S3 objects.\n         These Lambda functions are available in the Amazon Web Services Serverless Application Repository, and\n         can be selected through the Amazon Web Services Management Console when you create your Object Lambda access point.</p>\n         <p>Example 1: PII Access Control - This Lambda function uses Amazon Comprehend, a\n         natural language processing (NLP) service using machine learning to find insights and\n         relationships in text. It automatically detects personally identifiable information (PII)\n         such as names, addresses, dates, credit card numbers, and social security numbers from\n         documents in your Amazon S3 bucket. </p>\n         <p>Example 2: PII Redaction - This Lambda function uses Amazon Comprehend, a natural\n         language processing (NLP) service using machine learning to find insights and relationships\n         in text. It automatically redacts personally identifiable information (PII) such as names,\n         addresses, dates, credit card numbers, and social security numbers from documents in your\n         Amazon S3 bucket. </p>\n         <p>Example 3: Decompression - The Lambda function S3ObjectLambdaDecompression, is\n         equipped to decompress objects stored in S3 in one of six compressed file formats including\n         bzip2, gzip, snappy, zlib, zstandard and ZIP. </p>\n         <p>For information on how to view and use these functions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/olap-examples.html\">Using Amazon Web Services built Lambda\n            functions</a> in the <i>Amazon S3 User Guide</i>.</p>",
         "smithy.api#endpoint": {
           "hostPrefix": "{RequestRoute}."
         },
@@ -34969,7 +35100,7 @@
         "SSEKMSKeyId": {
           "target": "com.amazonaws.s3#SSEKMSKeyId",
           "traits": {
-            "smithy.api#documentation": "<p> If present, specifies the ID (Key ID, Key ARN, or Key Alias) of the Amazon Web Services Key Management Service (Amazon Web Services KMS) symmetric\n         encryption customer managed key that was used for stored in Amazon S3 object. </p>",
+            "smithy.api#documentation": "<p> If present, specifies the ID (Key ID, Key ARN, or Key Alias) of the Amazon Web Services Key\n         Management Service (Amazon Web Services KMS) symmetric encryption customer managed key that was used for stored in\n         Amazon S3 object. </p>",
             "smithy.api#httpHeader": "x-amz-fwd-header-x-amz-server-side-encryption-aws-kms-key-id"
           }
         },
@@ -35013,6 +35144,9 @@
         "smithy.api#input": {}
       }
     },
+    "com.amazonaws.s3#WriteOffsetBytes": {
+      "type": "long"
+    },
     "com.amazonaws.s3#Years": {
       "type": "integer"
     }