@nocobase/plugin-file-manager 0.17.0-alpha.7 → 0.18.0-alpha.2

package/dist/node_modules/@aws-sdk/client-s3/dist-types/commands/UploadPartCommand.d.ts

@@ -1,25 +1,19 @@
-/// <reference types="node" />
 import { EndpointParameterInstructions } from "@smithy/middleware-endpoint";
 import { Command as $Command } from "@smithy/smithy-client";
-import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@smithy/types";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack, StreamingBlobPayloadInputTypes } from "@smithy/types";
 import { UploadPartOutput, UploadPartRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
  */
 export { __MetadataBearer, $Command };
-export type UploadPartCommandInputType = Omit<UploadPartRequest, "Body"> & {
-    /**
-     * For *`UploadPartRequest["Body"]`*, see {@link UploadPartRequest.Body}.
-     */
-    Body?: UploadPartRequest["Body"] | string | Uint8Array | Buffer;
-};
 /**
  * @public
  *
  * The input for {@link UploadPartCommand}.
  */
-export interface UploadPartCommandInput extends UploadPartCommandInputType {
+export interface UploadPartCommandInput extends Omit<UploadPartRequest, "Body"> {
+    Body?: StreamingBlobPayloadInputTypes;
 }
 /**
  * @public
@@ -32,100 +26,139 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  * @public
  * <p>Uploads a part in a multipart upload.</p>
  *          <note>
- *             <p>In this operation, you provide part data in your request. However, you have an option
+ *             <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
- *          upload ID, a unique identifier, that you must include in your upload part request.</p>
+ *          upload ID, a unique identifier that you must include in your upload part request.</p>
  *          <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely
  *          identifies a part and also defines its position within the object being created. If you
  *          upload a new part using the same part number that was used with a previous part, the
  *          previously uploaded part is overwritten.</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>
- *          <p>To ensure that data is not corrupted when 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. </p>
- *          <p>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>
- *          <p>
- *             <b>Note:</b> After you initiate multipart upload and upload
+ *          <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>
+ *          </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>
- *          <p>For information on the permissions required to use the multipart upload API, go to
- *             <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>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 three
- *          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). If you choose to provide your own
- *          encryption key, the request headers you provide in the request must match the headers you
- *          used in the request to initiate the upload by using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.
- *          For more information, go to <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>Server-side encryption is supported by the S3 Multipart Upload actions. 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 requested 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 headers.</p>
- *          <ul>
- *             <li>
- *                <p>x-amz-server-side-encryption-customer-algorithm</p>
- *             </li>
- *             <li>
- *                <p>x-amz-server-side-encryption-customer-key</p>
- *             </li>
- *             <li>
- *                <p>x-amz-server-side-encryption-customer-key-MD5</p>
- *             </li>
- *          </ul>
- *          <p>
- *             <code>UploadPart</code> has the following special errors:</p>
- *          <ul>
- *             <li>
+ *          <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>
+ *                </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>Permissions</dt>
+ *             <dd>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <i>Code: NoSuchUpload</i>
- *                      </p>
+ *                         <b>General purpose bucket permissions</b> - For information on the 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>
- *                         <i>Cause: The specified multipart upload does not exist. The upload
- *                         ID might be invalid, or the multipart upload might have been aborted or
- *                         completed.</i>
- *                      </p>
+ *                         <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">
+ *                            <code>CreateSession</code>
+ *                         </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.
+ * 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>
  *                   </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>
+ *                <note>
+ *                   <p>
+ *                      <b>Directory buckets</b> - MD5 is not supported by directory buckets. You can use checksum algorithms to check object integrity.</p>
+ *                </note>
+ *             </dd>
+ *             <dt>Encryption</dt>
+ *             <dd>
+ *                <ul>
  *                   <li>
  *                      <p>
- *                         <i> HTTP Status Code: 404 Not Found </i>
- *                      </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>
+ *                         </li>
+ *                         <li>
+ *                            <p>x-amz-server-side-encryption-customer-key</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>x-amz-server-side-encryption-customer-key-MD5</p>
+ *                         </li>
+ *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <i>SOAP Fault Code Prefix: Client</i>
+ *                         <b>Directory bucket</b> - For directory buckets, only server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) is supported. </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>
+ *             </dd>
+ *             <dt>Special errors</dt>
+ *             <dd>
+ *                <ul>
+ *                   <li>
+ *                      <p>Error Code: <code>NoSuchUpload</code>
  *                      </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>
+ *                         </li>
+ *                         <li>
+ *                            <p>HTTP Status Code: 404 Not Found </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>SOAP Fault Code Prefix: Client</p>
+ *                         </li>
+ *                      </ul>
  *                   </li>
  *                </ul>
- *             </li>
- *          </ul>
+ *             </dd>
+ *             <dt>HTTP Host header syntax</dt>
+ *             <dd>
+ *                <p>
+ *                   <b>Directory buckets </b> - The HTTP Host header syntax is <code>
+ *                      <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>
+ *             </dd>
+ *          </dl>
  *          <p>The following operations are related to <code>UploadPart</code>:</p>
  *          <ul>
  *             <li>

package/dist/node_modules/@aws-sdk/client-s3/dist-types/commands/UploadPartCopyCommand.d.ts

@@ -23,141 +23,150 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
 }
 /**
  * @public
- * <p>Uploads a part by copying data from an existing object as data source. You specify the
- *          data source by adding the request header <code>x-amz-copy-source</code> in your request and
- *          a byte range by adding the request header <code>x-amz-copy-source-range</code> in your
+ * <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>
  *          <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 using 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 and provide data 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 a unique identifier, the upload ID, that you must include in
+ *          initiate request, Amazon S3 returns the upload ID, a unique identifier that you must include in
  *          your upload part request.</p>
- *          <p>For more information about using the <code>UploadPartCopy</code> operation, see the
- *          following:</p>
- *          <ul>
- *             <li>
- *                <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>.</p>
- *             </li>
- *             <li>
- *                <p>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>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>
- *             </li>
- *             <li>
- *                <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>
- *          </ul>
- *          <p>Note the following additional considerations about the request headers
- *             <code>x-amz-copy-source-if-match</code>, <code>x-amz-copy-source-if-none-match</code>,
- *             <code>x-amz-copy-source-if-unmodified-since</code>, and
- *             <code>x-amz-copy-source-if-modified-since</code>:</p>
- *          <p> </p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <b>Consideration 1</b> - 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>
- *                <p>Amazon S3 returns <code>200 OK</code> and copies the data.
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <b>Consideration 2</b> - 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>
- *                <p>
- *                   <code>x-amz-copy-source-if-modified-since</code> condition evaluates to
- *                   <code>true</code>;</p>
- *                <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.
- *                </p>
- *             </li>
- *          </ul>
+ *          <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>
+ *                </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>Versioning</dt>
+ *             <dt>Authentication and authorization</dt>
  *             <dd>
- *                <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
- *                   object to copy. If the current version is a delete marker and you don't specify a versionId
- *                   in the <code>x-amz-copy-source</code>, Amazon S3 returns a 404 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 400 error, because you are not allowed to specify
- *                   a delete marker as a version for the <code>x-amz-copy-source</code>. </p>
- *                <p>You can optionally specify a specific version of the source object to copy by adding the
- *                   <code>versionId</code> subresource as shown in the following example:</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>
- *                   <code>x-amz-copy-source: /bucket/object?versionId=version id</code>
- *                </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>Special errors</dt>
+ *             <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>
  *                <ul>
  *                   <li>
+ *                      <p>
+ *                         <b>General purpose bucket permissions</b> - You must have the permissions in a policy based on the bucket types of your source bucket and destination bucket in an <code>UploadPartCopy</code> operation.</p>
  *                      <ul>
  *                         <li>
- *                            <p>
- *                               <i>Code: NoSuchUpload</i>
- *                            </p>
+ *                            <p>If the source object is in a general purpose bucket, you must have the <b>
+ *                                  <code>s3:GetObject</code>
+ *                               </b> permission to read the source object that is being copied. </p>
  *                         </li>
  *                         <li>
- *                            <p>
- *                               <i>Cause: The specified multipart upload does not exist. The upload
- *                               ID might be invalid, or the multipart upload might have been aborted or
- *                               completed.</i>
+ *                            <p>If the destination bucket is a general purpose bucket, you must have the <b>
+ *                                  <code>s3:PubObject</code>
+ *                               </b> permission to write the object copy to the destination bucket.
  *                            </p>
  *                         </li>
+ *                      </ul>
+ *                      <p>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>
+ *                         <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>
+ *                      <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>
+ *                         </li>
  *                         <li>
- *                            <p>
- *                               <i>HTTP Status Code: 404 Not Found</i>
- *                            </p>
+ *                            <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 cannot be set to <code>ReadOnly</code> on the copy destination. </p>
  *                         </li>
  *                      </ul>
+ *                      <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>
+ *             <dt>Encryption</dt>
+ *             <dd>
+ *                <ul>
+ *                   <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>
  *                   </li>
  *                   <li>
+ *                      <p>
+ *                         <b>Directory buckets </b> - For directory buckets, only server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) is supported.</p>
+ *                   </li>
+ *                </ul>
+ *             </dd>
+ *             <dt>Special errors</dt>
+ *             <dd>
+ *                <ul>
+ *                   <li>
+ *                      <p>Error Code: <code>NoSuchUpload</code>
+ *                      </p>
  *                      <ul>
  *                         <li>
- *                            <p>
- *                               <i>Code: InvalidRequest</i>
- *                            </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>
- *                               <i>Cause: The specified copy source is not supported as a byte-range
- *                               copy source.</i>
- *                            </p>
+ *                            <p>HTTP Status Code: 404 Not Found</p>
  *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                   <li>
+ *                      <p>Error Code: <code>InvalidRequest</code>
+ *                      </p>
+ *                      <ul>
  *                         <li>
- *                            <p>
- *                               <i>HTTP Status Code: 400 Bad Request</i>
- *                            </p>
+ *                            <p>Description: The specified copy source is not supported as a
+ *                                     byte-range copy source.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>HTTP Status Code: 400 Bad Request</p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                </ul>
  *             </dd>
+ *             <dt>HTTP Host header syntax</dt>
+ *             <dd>
+ *                <p>
+ *                   <b>Directory buckets </b> - The HTTP Host header syntax is <code>
+ *                      <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com</code>.</p>
+ *             </dd>
  *          </dl>
  *          <p>The following operations are related to <code>UploadPartCopy</code>:</p>
  *          <ul>

package/dist/node_modules/@aws-sdk/client-s3/dist-types/commands/WriteGetObjectResponseCommand.d.ts

@@ -1,25 +1,19 @@
-/// <reference types="node" />
 import { EndpointParameterInstructions } from "@smithy/middleware-endpoint";
 import { Command as $Command } from "@smithy/smithy-client";
-import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@smithy/types";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack, StreamingBlobPayloadInputTypes } from "@smithy/types";
 import { WriteGetObjectResponseRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
  */
 export { __MetadataBearer, $Command };
-export type WriteGetObjectResponseCommandInputType = Omit<WriteGetObjectResponseRequest, "Body"> & {
-    /**
-     * For *`WriteGetObjectResponseRequest["Body"]`*, see {@link WriteGetObjectResponseRequest.Body}.
-     */
-    Body?: WriteGetObjectResponseRequest["Body"] | string | Uint8Array | Buffer;
-};
 /**
  * @public
  *
  * The input for {@link WriteGetObjectResponseCommand}.
  */
-export interface WriteGetObjectResponseCommandInput extends WriteGetObjectResponseCommandInputType {
+export interface WriteGetObjectResponseCommandInput extends Omit<WriteGetObjectResponseRequest, "Body"> {
+    Body?: StreamingBlobPayloadInputTypes;
 }
 /**
  * @public
@@ -30,7 +24,10 @@ export interface WriteGetObjectResponseCommandOutput extends __MetadataBearer {
 }
 /**
  * @public
- * <p>Passes transformed objects to a <code>GetObject</code> operation when using Object Lambda access points. For
+ * <note>
+ *             <p>This operation is not supported by 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
  *             Object Lambda access points</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <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
@@ -102,14 +99,14 @@ export interface WriteGetObjectResponseCommandOutput extends __MetadataBearer {
  *   ObjectLockLegalHoldStatus: "ON" || "OFF",
  *   ObjectLockRetainUntilDate: new Date("TIMESTAMP"),
  *   PartsCount: Number("int"),
- *   ReplicationStatus: "COMPLETE" || "PENDING" || "FAILED" || "REPLICA",
+ *   ReplicationStatus: "COMPLETE" || "PENDING" || "FAILED" || "REPLICA" || "COMPLETED",
  *   RequestCharged: "requester",
  *   Restore: "STRING_VALUE",
  *   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
  *   SSECustomerAlgorithm: "STRING_VALUE",
  *   SSEKMSKeyId: "STRING_VALUE",
  *   SSECustomerKeyMD5: "STRING_VALUE",
- *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW",
+ *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW" || "EXPRESS_ONEZONE",
  *   TagCount: Number("int"),
  *   VersionId: "STRING_VALUE",
  *   BucketKeyEnabled: true || false,

package/dist/node_modules/@aws-sdk/client-s3/dist-types/commands/index.d.ts

@@ -3,6 +3,7 @@ export * from "./CompleteMultipartUploadCommand";
 export * from "./CopyObjectCommand";
 export * from "./CreateBucketCommand";
 export * from "./CreateMultipartUploadCommand";
+export * from "./CreateSessionCommand";
 export * from "./DeleteBucketAnalyticsConfigurationCommand";
 export * from "./DeleteBucketCommand";
 export * from "./DeleteBucketCorsCommand";
@@ -56,6 +57,7 @@ export * from "./ListBucketIntelligentTieringConfigurationsCommand";
 export * from "./ListBucketInventoryConfigurationsCommand";
 export * from "./ListBucketMetricsConfigurationsCommand";
 export * from "./ListBucketsCommand";
+export * from "./ListDirectoryBucketsCommand";
 export * from "./ListMultipartUploadsCommand";
 export * from "./ListObjectVersionsCommand";
 export * from "./ListObjectsCommand";

package/dist/node_modules/@aws-sdk/client-s3/dist-types/endpoint/EndpointParameters.d.ts

@@ -1,4 +1,7 @@
 import { Endpoint, EndpointParameters as __EndpointParameters, EndpointV2, Provider } from "@smithy/types";
+/**
+ * @public
+ */
 export interface ClientInputEndpointParameters {
     region?: string | Provider<string>;
     useFipsEndpoint?: boolean | Provider<boolean>;
@@ -9,6 +12,7 @@ export interface ClientInputEndpointParameters {
     useGlobalEndpoint?: boolean | Provider<boolean>;
     disableMultiregionAccessPoints?: boolean | Provider<boolean>;
     useArnRegion?: boolean | Provider<boolean>;
+    disableS3ExpressSessionAuth?: boolean | Provider<boolean>;
 }
 export type ClientResolvedEndpointParameters = ClientInputEndpointParameters & {
     defaultSigningName: string;
@@ -26,7 +30,11 @@ export interface EndpointParameters extends __EndpointParameters {
     Accelerate?: boolean;
     UseGlobalEndpoint?: boolean;
     UseObjectLambdaEndpoint?: boolean;
+    Key?: string;
+    Prefix?: string;
     DisableAccessPoints?: boolean;
     DisableMultiRegionAccessPoints?: boolean;
     UseArnRegion?: boolean;
+    UseS3ExpressControlEndpoint?: boolean;
+    DisableS3ExpressSessionAuth?: boolean;
 }

package/dist/node_modules/@aws-sdk/client-s3/dist-types/extensionConfiguration.d.ts

@@ -0,0 +1,8 @@
+import { AwsRegionExtensionConfiguration } from "@aws-sdk/types";
+import { HttpHandlerExtensionConfiguration } from "@smithy/protocol-http";
+import { DefaultExtensionConfiguration } from "@smithy/types";
+/**
+ * @internal
+ */
+export interface S3ExtensionConfiguration extends HttpHandlerExtensionConfiguration, DefaultExtensionConfiguration, AwsRegionExtensionConfiguration {
+}

package/dist/node_modules/@aws-sdk/client-s3/dist-types/index.d.ts

@@ -5,8 +5,12 @@
  */
 export * from "./S3Client";
 export * from "./S3";
+export { ClientInputEndpointParameters } from "./endpoint/EndpointParameters";
+export { RuntimeExtension } from "./runtimeExtensions";
+export { S3ExtensionConfiguration } from "./extensionConfiguration";
 export * from "./commands";
 export * from "./pagination";
 export * from "./waiters";
 export * from "./models";
+import "@aws-sdk/util-endpoints";
 export { S3ServiceException } from "./models/S3ServiceException";