@nocobase/plugin-file-manager 1.6.0-beta.2 → 1.6.0-beta.4

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

@@ -1,217 +1,265 @@
-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 { EndpointParameterInstructions } from "@aws-sdk/middleware-endpoint";
+import { Command as $Command } from "@aws-sdk/smithy-client";
+import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
 import { CreateMultipartUploadOutput, CreateMultipartUploadRequest } from "../models/models_0";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
-/**
- * @public
- */
-export { __MetadataBearer, $Command };
-/**
- * @public
- *
- * The input for {@link CreateMultipartUploadCommand}.
- */
 export interface CreateMultipartUploadCommandInput extends CreateMultipartUploadRequest {
 }
-/**
- * @public
- *
- * The output of {@link CreateMultipartUploadCommand}.
- */
 export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploadOutput, __MetadataBearer {
 }
 /**
- * @public
  * <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>
+ *          request.</p>
+ *
+ *          <p>For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a>.</p>
+ *
+ *          <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the
+ *          upload must complete 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 Policy</a>.</p>
+ *
+ *          <p>For information about 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>.</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>.</p>
+ *
  *          <note>
- *             <p>After you initiate a multipart upload and upload one or more parts, to stop being
+ *             <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
+ *             upload. Amazon S3 frees up the space used to store the parts and stop 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>
- *          <note>
- *             <ul>
- *                <li>
- *                   <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>
- *                      </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>You can optionally request server-side encryption. For server-side encryption, Amazon S3
+ *          encrypts your data as it writes it to disks in its data centers and decrypts it when you
+ *          access it. You can provide your own encryption key, or use Amazon Web Services KMS keys or Amazon S3-managed encryption keys. 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 request to
+ *          initiate the upload by using <code>CreateMultipartUpload</code>. </p>
+ *          <p>To perform a multipart upload with encryption 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> in the <i>Amazon S3 User Guide</i>.</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 belongs to a different account than the key, then you must have the
+ *          permissions on both the key policy and your IAM user or role.</p>
+ *
+ *
+ *          <p> For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Protecting
+ *             Data Using Server-Side Encryption</a>.</p>
+ *
  *          <dl>
- *             <dt>Request signing</dt>
+ *             <dt>Access Permissions</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>When copying an object, you can optionally specify the accounts or groups that
+ *                   should be granted specific permissions on the new object. There are two ways to
+ *                   grant the permissions using the request headers:</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. For
+ *                         more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned ACL</a>.</p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Specify access permissions explicitly with the
+ *                            <code>x-amz-grant-read</code>, <code>x-amz-grant-read-acp</code>,
+ *                            <code>x-amz-grant-write-acp</code>, and
+ *                            <code>x-amz-grant-full-control</code> headers. These parameters map to
+ *                         the set of 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>.</p>
+ *                   </li>
+ *                </ul>
+ *                <p>You can use either a canned ACL or specify access permissions explicitly. You
+ *                   cannot do both.</p>
  *             </dd>
- *             <dt>Permissions</dt>
+ *             <dt>Server-Side- Encryption-Specific Request Headers</dt>
  *             <dd>
+ *                <p>You can optionally tell Amazon S3 to encrypt data at rest using server-side
+ *                   encryption. 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. The option you use depends on whether you want to use Amazon Web Services managed
+ *                   encryption keys or provide your own encryption key. </p>
  *                <ul>
  *                   <li>
- *                      <p>
- *                         <b>General purpose bucket permissions</b> - For information about 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>
- *                      <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>Use encryption keys managed by Amazon S3 or customer managed key stored
+ *                         in Amazon Web Services Key Management Service (Amazon Web Services 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>
+ *                               <code>x-amz-server-side-encryption</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-server-side-encryption-aws-kms-key-id</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-server-side-encryption-context</code>
+ *                            </p>
+ *                         </li>
+ *                      </ul>
+ *                      <note>
+ *                         <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 in Amazon Web Services KMS to protect the data.</p>
+ *                      </note>
+ *                      <important>
+ *                         <p>All GET and PUT requests for an object protected by Amazon Web Services KMS fail if
+ *                            you don't make them with SSL or by using SigV4.</p>
+ *                      </important>
+ *                      <p>For more information about server-side encryption with KMS key (SSE-KMS),
+ *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html">Protecting Data Using Server-Side Encryption with KMS keys</a>.</p>
  *                   </li>
  *                   <li>
- *                      <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>
+ *                      <p>Use customer-provided encryption keys – If you want to manage your own
+ *                         encryption keys, provide all the following headers in the request.</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-server-side-encryption-customer-algorithm</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-server-side-encryption-customer-key</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-server-side-encryption-customer-key-MD5</code>
+ *                            </p>
+ *                         </li>
+ *                      </ul>
+ *                      <p>For more information about server-side encryption with KMS keys (SSE-KMS),
+ *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html">Protecting Data Using Server-Side Encryption with KMS keys</a>.</p>
  *                   </li>
  *                </ul>
  *             </dd>
- *             <dt>Encryption</dt>
+ *             <dt>Access-Control-List (ACL)-Specific Request Headers</dt>
  *             <dd>
+ *                <p>You also can use the following access control–related headers with this
+ *                   operation. By default, all objects are private. Only the owner has full access
+ *                   control. When adding a new object, you can grant 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 object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. With this
+ *                   operation, you can grant access permissions using one of the following two
+ *                   methods:</p>
  *                <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>
+ *                      <p>Specify a canned ACL (<code>x-amz-acl</code>) — 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>.</p>
+ *                   </li>
+ *                   <li>
+ *                      <p>Specify access permissions explicitly — To explicitly grant access
+ *                         permissions to specific Amazon Web Services accounts or groups, use the following headers.
+ *                         Each 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 header, you specify a list of
+ *                         grantees who get the specific permission. To grant permissions explicitly,
+ *                         use:</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>
- *                            <ul>
- *                               <li>
- *                                  <p>
- *                                     <code>x-amz-server-side-encryption</code>
- *                                  </p>
- *                               </li>
- *                               <li>
- *                                  <p>
- *                                     <code>x-amz-server-side-encryption-aws-kms-key-id</code>
- *                                  </p>
- *                               </li>
- *                               <li>
- *                                  <p>
- *                                     <code>x-amz-server-side-encryption-context</code>
- *                                  </p>
- *                               </li>
- *                            </ul>
+ *                            <p>
+ *                               <code>x-amz-grant-read</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-grant-write</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-grant-read-acp</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-grant-write-acp</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>x-amz-grant-full-control</code>
+ *                            </p>
+ *                         </li>
+ *                      </ul>
+ *                      <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>
+ *                         </li>
+ *                         <li>
+ *                            <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>
  *                            <note>
+ *                               <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
  *                               <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>US East (N. Virginia)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p>US West (N. California)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p> US West (Oregon)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p> Asia Pacific (Singapore)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p>Asia Pacific (Sydney)</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>Asia Pacific (Tokyo)</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>Europe (Ireland)</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>South America (São Paulo)</p>
  *                                  </li>
  *                               </ul>
+ *                               <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>
  *                            </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>
- *                         </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>
- *                            <ul>
- *                               <li>
- *                                  <p>
- *                                     <code>x-amz-server-side-encryption-customer-algorithm</code>
- *                                  </p>
- *                               </li>
- *                               <li>
- *                                  <p>
- *                                     <code>x-amz-server-side-encryption-customer-key</code>
- *                                  </p>
- *                               </li>
- *                               <li>
- *                                  <p>
- *                                     <code>x-amz-server-side-encryption-customer-key-MD5</code>
- *                                  </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>
  *                         </li>
  *                      </ul>
- *                   </li>
- *                   <li>
+ *                      <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>
  *                      <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>
+ *                         <code>x-amz-grant-read: id="11112222333", id="444455556666" </code>
+ *                      </p>
  *                   </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>CreateMultipartUpload</code>:</p>
  *          <ul>
  *             <li>
@@ -246,106 +294,23 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  * import { S3Client, CreateMultipartUploadCommand } from "@aws-sdk/client-s3"; // ES Modules import
  * // const { S3Client, CreateMultipartUploadCommand } = require("@aws-sdk/client-s3"); // CommonJS import
  * const client = new S3Client(config);
- * const input = { // CreateMultipartUploadRequest
- *   ACL: "private" || "public-read" || "public-read-write" || "authenticated-read" || "aws-exec-read" || "bucket-owner-read" || "bucket-owner-full-control",
- *   Bucket: "STRING_VALUE", // required
- *   CacheControl: "STRING_VALUE",
- *   ContentDisposition: "STRING_VALUE",
- *   ContentEncoding: "STRING_VALUE",
- *   ContentLanguage: "STRING_VALUE",
- *   ContentType: "STRING_VALUE",
- *   Expires: new Date("TIMESTAMP"),
- *   GrantFullControl: "STRING_VALUE",
- *   GrantRead: "STRING_VALUE",
- *   GrantReadACP: "STRING_VALUE",
- *   GrantWriteACP: "STRING_VALUE",
- *   Key: "STRING_VALUE", // required
- *   Metadata: { // Metadata
- *     "<keys>": "STRING_VALUE",
- *   },
- *   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
- *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW" || "EXPRESS_ONEZONE",
- *   WebsiteRedirectLocation: "STRING_VALUE",
- *   SSECustomerAlgorithm: "STRING_VALUE",
- *   SSECustomerKey: "STRING_VALUE",
- *   SSECustomerKeyMD5: "STRING_VALUE",
- *   SSEKMSKeyId: "STRING_VALUE",
- *   SSEKMSEncryptionContext: "STRING_VALUE",
- *   BucketKeyEnabled: true || false,
- *   RequestPayer: "requester",
- *   Tagging: "STRING_VALUE",
- *   ObjectLockMode: "GOVERNANCE" || "COMPLIANCE",
- *   ObjectLockRetainUntilDate: new Date("TIMESTAMP"),
- *   ObjectLockLegalHoldStatus: "ON" || "OFF",
- *   ExpectedBucketOwner: "STRING_VALUE",
- *   ChecksumAlgorithm: "CRC32" || "CRC32C" || "SHA1" || "SHA256",
- * };
  * const command = new CreateMultipartUploadCommand(input);
  * const response = await client.send(command);
- * // { // CreateMultipartUploadOutput
- * //   AbortDate: new Date("TIMESTAMP"),
- * //   AbortRuleId: "STRING_VALUE",
- * //   Bucket: "STRING_VALUE",
- * //   Key: "STRING_VALUE",
- * //   UploadId: "STRING_VALUE",
- * //   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
- * //   SSECustomerAlgorithm: "STRING_VALUE",
- * //   SSECustomerKeyMD5: "STRING_VALUE",
- * //   SSEKMSKeyId: "STRING_VALUE",
- * //   SSEKMSEncryptionContext: "STRING_VALUE",
- * //   BucketKeyEnabled: true || false,
- * //   RequestCharged: "requester",
- * //   ChecksumAlgorithm: "CRC32" || "CRC32C" || "SHA1" || "SHA256",
- * // };
- *
  * ```
  *
- * @param CreateMultipartUploadCommandInput - {@link CreateMultipartUploadCommandInput}
- * @returns {@link CreateMultipartUploadCommandOutput}
  * @see {@link CreateMultipartUploadCommandInput} for command's `input` shape.
  * @see {@link CreateMultipartUploadCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
- * @throws {@link S3ServiceException}
- * <p>Base exception class for all service exceptions from S3 service.</p>
- *
- * @example To initiate a multipart upload
- * ```javascript
- * // The following example initiates a multipart upload.
- * const input = {
- *   "Bucket": "examplebucket",
- *   "Key": "largeobject"
- * };
- * const command = new CreateMultipartUploadCommand(input);
- * const response = await client.send(command);
- * /* response ==
- * {
- *   "Bucket": "examplebucket",
- *   "Key": "largeobject",
- *   "UploadId": "ibZBv_75gd9r8lH_gqXatLdxMVpAlj6ZQjEs.OwyF3953YdwbcQnMA2BLGn8Lx12fQNICtMw5KyteFeHw.Sjng--"
- * }
- * *\/
- * // example id: to-initiate-a-multipart-upload-1481836794513
- * ```
- *
  */
 export declare class CreateMultipartUploadCommand extends $Command<CreateMultipartUploadCommandInput, CreateMultipartUploadCommandOutput, S3ClientResolvedConfig> {
     readonly input: CreateMultipartUploadCommandInput;
     static getEndpointParameterInstructions(): EndpointParameterInstructions;
-    /**
-     * @public
-     */
     constructor(input: CreateMultipartUploadCommandInput);
     /**
      * @internal
      */
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<CreateMultipartUploadCommandInput, CreateMultipartUploadCommandOutput>;
-    /**
-     * @internal
-     */
     private serialize;
-    /**
-     * @internal
-     */
     private deserialize;
 }