@aws-sdk/client-s3 3.697.0 → 3.698.0

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

@@ -28,16 +28,13 @@ declare const PutBucketVersioningCommand_base: {
 };
 /**
  * <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>

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

@@ -28,7 +28,7 @@ declare const PutBucketWebsiteCommand_base: {
 };
 /**
  * <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

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

@@ -28,7 +28,7 @@ declare const PutObjectAclCommand_base: {
 };
 /**
  * <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>

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

@@ -32,46 +32,49 @@ declare const PutObjectCommand_base: {
  *          <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>
@@ -83,28 +86,34 @@ declare const PutObjectCommand_base: {
  *                <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>
@@ -116,9 +125,10 @@ declare const PutObjectCommand_base: {
  * 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>
@@ -127,15 +137,18 @@ declare const PutObjectCommand_base: {
  *                <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>
@@ -188,6 +201,7 @@ declare const PutObjectCommand_base: {
  *   GrantReadACP: "STRING_VALUE",
  *   GrantWriteACP: "STRING_VALUE",
  *   Key: "STRING_VALUE", // required
+ *   WriteOffsetBytes: Number("long"),
  *   Metadata: { // Metadata
  *     "<keys>": "STRING_VALUE",
  *   },
@@ -223,6 +237,7 @@ declare const PutObjectCommand_base: {
  * //   SSEKMSKeyId: "STRING_VALUE",
  * //   SSEKMSEncryptionContext: "STRING_VALUE",
  * //   BucketKeyEnabled: true || false,
+ * //   Size: Number("long"),
  * //   RequestCharged: "requester",
  * // };
  *
@@ -234,6 +249,39 @@ declare const PutObjectCommand_base: {
  * @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>
  *

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

@@ -28,7 +28,7 @@ declare const PutObjectLegalHoldCommand_base: {
 };
 /**
  * <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

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

@@ -28,7 +28,7 @@ declare const PutObjectLockConfigurationCommand_base: {
 };
 /**
  * <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
@@ -45,8 +45,8 @@ declare const PutObjectLockConfigurationCommand_base: {
  *                      <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>

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

@@ -24,11 +24,11 @@ export interface PutObjectRetentionCommandOutput extends PutObjectRetentionOutpu
 declare const PutObjectRetentionCommand_base: {
     new (input: PutObjectRetentionCommandInput): import("@smithy/smithy-client").CommandImpl<PutObjectRetentionCommandInput, PutObjectRetentionCommandOutput, S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
     new (__0_0: PutObjectRetentionCommandInput): import("@smithy/smithy-client").CommandImpl<PutObjectRetentionCommandInput, PutObjectRetentionCommandOutput, S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions; /** @internal type navigation helper, not in runtime. */
 };
 /**
  * <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

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

@@ -28,7 +28,7 @@ declare const PutObjectTaggingCommand_base: {
 };
 /**
  * <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>

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

@@ -28,7 +28,7 @@ declare const PutPublicAccessBlockCommand_base: {
 };
 /**
  * <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>

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

@@ -28,7 +28,7 @@ declare const RestoreObjectCommand_base: {
 };
 /**
  * <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>

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

@@ -28,7 +28,7 @@ declare const SelectObjectContentCommand_base: {
 };
 /**
  * <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

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

@@ -30,10 +30,9 @@ declare const UploadPartCommand_base: {
 /**
  * <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
@@ -45,17 +44,17 @@ declare const UploadPartCommand_base: {
  *          <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>
@@ -89,20 +88,24 @@ declare const UploadPartCommand_base: {
  * 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>
@@ -113,23 +116,28 @@ declare const UploadPartCommand_base: {
  *                <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>
@@ -141,13 +149,14 @@ declare const UploadPartCommand_base: {
  *                            <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>
@@ -159,7 +168,9 @@ declare const UploadPartCommand_base: {
  *                      </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>