lambda-live-debugger 1.8.3 → 1.8.5

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

@@ -0,0 +1,182 @@
+import { Command as $Command } from "@smithy/smithy-client";
+import { MetadataBearer as __MetadataBearer } from "@smithy/types";
+import { CreateBucketMetadataConfigurationRequest } from "../models/models_0";
+import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
+/**
+ * @public
+ */
+export type { __MetadataBearer };
+export { $Command };
+/**
+ * @public
+ *
+ * The input for {@link CreateBucketMetadataConfigurationCommand}.
+ */
+export interface CreateBucketMetadataConfigurationCommandInput extends CreateBucketMetadataConfigurationRequest {
+}
+/**
+ * @public
+ *
+ * The output of {@link CreateBucketMetadataConfigurationCommand}.
+ */
+export interface CreateBucketMetadataConfigurationCommandOutput extends __MetadataBearer {
+}
+declare const CreateBucketMetadataConfigurationCommand_base: {
+    new (input: CreateBucketMetadataConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl<CreateBucketMetadataConfigurationCommandInput, CreateBucketMetadataConfigurationCommandOutput, S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (input: CreateBucketMetadataConfigurationCommandInput): import("@smithy/smithy-client").CommandImpl<CreateBucketMetadataConfigurationCommandInput, CreateBucketMetadataConfigurationCommandOutput, S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+};
+/**
+ * <p>Creates an S3 Metadata V2 metadata configuration for a general purpose bucket. For more information, see
+ *       <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-overview.html">Accelerating
+ *         data discovery with S3 Metadata</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <dl>
+ *             <dt>Permissions</dt>
+ *             <dd>
+ *                <p>To use this operation, you must have the following permissions. For more information, see
+ *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-permissions.html">Setting up permissions for configuring metadata tables</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
+ *                <p>If you want to encrypt your metadata tables with server-side encryption with Key Management Service
+ *             (KMS) keys (SSE-KMS), you need additional permissions in your KMS key policy. For more
+ *             information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-permissions.html">
+ *               Setting up permissions for configuring metadata tables</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
+ *                <p>If you also want to integrate your table bucket with Amazon Web Services analytics services so that you can
+ *             query your metadata table, you need additional permissions. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-integrating-aws.html"> Integrating
+ *               Amazon S3 Tables with Amazon Web Services analytics services</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
+ *                <p>To query your metadata tables, you need additional permissions. For more information, see
+ *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-bucket-query-permissions.html">
+ *               Permissions for querying metadata tables</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>
+ *                         <code>s3:CreateBucketMetadataTableConfiguration</code>
+ *                      </p>
+ *                      <note>
+ *                         <p>The IAM policy action name is the same for the V1 and V2 API operations.</p>
+ *                      </note>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <code>s3tables:CreateTableBucket</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <code>s3tables:CreateNamespace</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <code>s3tables:GetTable</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <code>s3tables:CreateTable</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <code>s3tables:PutTablePolicy</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <code>s3tables:PutTableEncryption</code>
+ *                      </p>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <code>kms:DescribeKey</code>
+ *                      </p>
+ *                   </li>
+ *                </ul>
+ *             </dd>
+ *          </dl>
+ *          <p>The following operations are related to <code>CreateBucketMetadataConfiguration</code>:</p>
+ *          <ul>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketMetadataConfiguration.html">DeleteBucketMetadataConfiguration</a>
+ *                </p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketMetadataConfiguration.html">GetBucketMetadataConfiguration</a>
+ *                </p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UpdateBucketMetadataInventoryTableConfiguration.html">UpdateBucketMetadataInventoryTableConfiguration</a>
+ *                </p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UpdateBucketMetadataJournalTableConfiguration.html">UpdateBucketMetadataJournalTableConfiguration</a>
+ *                </p>
+ *             </li>
+ *          </ul>
+ * @example
+ * Use a bare-bones client and the command you need to make an API call.
+ * ```javascript
+ * import { S3Client, CreateBucketMetadataConfigurationCommand } from "@aws-sdk/client-s3"; // ES Modules import
+ * // const { S3Client, CreateBucketMetadataConfigurationCommand } = require("@aws-sdk/client-s3"); // CommonJS import
+ * const client = new S3Client(config);
+ * const input = { // CreateBucketMetadataConfigurationRequest
+ *   Bucket: "STRING_VALUE", // required
+ *   ContentMD5: "STRING_VALUE",
+ *   ChecksumAlgorithm: "CRC32" || "CRC32C" || "SHA1" || "SHA256" || "CRC64NVME",
+ *   MetadataConfiguration: { // MetadataConfiguration
+ *     JournalTableConfiguration: { // JournalTableConfiguration
+ *       RecordExpiration: { // RecordExpiration
+ *         Expiration: "ENABLED" || "DISABLED", // required
+ *         Days: Number("int"),
+ *       },
+ *       EncryptionConfiguration: { // MetadataTableEncryptionConfiguration
+ *         SseAlgorithm: "aws:kms" || "AES256", // required
+ *         KmsKeyArn: "STRING_VALUE",
+ *       },
+ *     },
+ *     InventoryTableConfiguration: { // InventoryTableConfiguration
+ *       ConfigurationState: "ENABLED" || "DISABLED", // required
+ *       EncryptionConfiguration: {
+ *         SseAlgorithm: "aws:kms" || "AES256", // required
+ *         KmsKeyArn: "STRING_VALUE",
+ *       },
+ *     },
+ *   },
+ *   ExpectedBucketOwner: "STRING_VALUE",
+ * };
+ * const command = new CreateBucketMetadataConfigurationCommand(input);
+ * const response = await client.send(command);
+ * // {};
+ *
+ * ```
+ *
+ * @param CreateBucketMetadataConfigurationCommandInput - {@link CreateBucketMetadataConfigurationCommandInput}
+ * @returns {@link CreateBucketMetadataConfigurationCommandOutput}
+ * @see {@link CreateBucketMetadataConfigurationCommandInput} for command's `input` shape.
+ * @see {@link CreateBucketMetadataConfigurationCommandOutput} 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>
+ *
+ *
+ * @public
+ */
+export declare class CreateBucketMetadataConfigurationCommand extends CreateBucketMetadataConfigurationCommand_base {
+    /** @internal type navigation helper, not in runtime. */
+    protected static __types: {
+        api: {
+            input: CreateBucketMetadataConfigurationRequest;
+            output: {};
+        };
+        sdk: {
+            input: CreateBucketMetadataConfigurationCommandInput;
+            output: CreateBucketMetadataConfigurationCommandOutput;
+        };
+    };
+}

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

@@ -27,21 +27,34 @@ declare const CreateBucketMetadataTableConfigurationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a metadata table configuration for a general purpose bucket. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-overview.html">Accelerating data
- *             discovery with S3 Metadata</a> in the <i>Amazon S3 User Guide</i>. </p>
+ * <important>
+ *             <p>
+ *         We recommend that you create your S3 Metadata configurations by using the V2
+ *         <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucketMetadataConfiguration.html">CreateBucketMetadataConfiguration</a> API operation. We no longer recommend using the V1
+ *         <code>CreateBucketMetadataTableConfiguration</code> API operation.
+ *       </p>
+ *             <p>If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete
+ *         and re-create your configuration by using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucketMetadataConfiguration.html">CreateBucketMetadataConfiguration</a> so that you can expire journal table records and create
+ *         a live inventory table.</p>
+ *          </important>
+ *          <p>Creates a V1 S3 Metadata configuration for a general purpose bucket. For more information, see
+ *         <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-overview.html">Accelerating
+ *         data discovery with S3 Metadata</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <dl>
  *             <dt>Permissions</dt>
  *             <dd>
- *                <p>To use this operation, you must have the following permissions. For more
- *                   information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-permissions.html">Setting up
- *                      permissions for configuring metadata tables</a> in the
- *                      <i>Amazon S3 User Guide</i>.</p>
- *                <p>If you also want to integrate your table bucket with Amazon Web Services analytics services so that you
- *                   can query your metadata table, you need additional permissions. For more information, see
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-integrating-aws.html">
- *                      Integrating Amazon S3 Tables with Amazon Web Services analytics services</a> in the
- *                   <i>Amazon S3 User Guide</i>.</p>
+ *                <p>To use this operation, you must have the following permissions. For more information, see
+ *               <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-permissions.html">Setting up permissions for configuring metadata tables</a> in the
+ *               <i>Amazon S3 User Guide</i>.</p>
+ *                <p>If you want to encrypt your metadata tables with server-side encryption with Key Management Service
+ *             (KMS) keys (SSE-KMS), you need additional permissions. For more
+ *             information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/metadata-tables-permissions.html">
+ *               Setting up permissions for configuring metadata tables</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
+ *                <p>If you also want to integrate your table bucket with Amazon Web Services analytics services so that you can
+ *             query your metadata table, you need additional permissions. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-integrating-aws.html"> Integrating
+ *               Amazon S3 Tables with Amazon Web Services analytics services</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
  *                <ul>
  *                   <li>
  *                      <p>

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

@@ -27,34 +27,41 @@ declare const CreateMultipartUploadCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <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>
+ * <important>
+ *             <p>End of support notice: Beginning October 1, 2025, Amazon S3 will discontinue support for creating new Email Grantee Access Control Lists (ACL).
+ *  Email Grantee ACLs created prior to this date will continue to work and remain accessible through the Amazon Web Services Management Console, Command Line Interface (CLI), SDKs,
+ *  and REST API. However, you will no longer be able to create new Email Grantee ACLs.
+ * </p>
+ *             <p>This change affects the following Amazon Web Services Regions: US East (N. Virginia) Region, US West (N. California) Region, US West (Oregon) Region, Asia Pacific (Singapore) Region, Asia Pacific (Sydney) Region,
+ *  Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.</p>
+ *          </important>
+ *          <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>
  *          <note>
- *             <p>After you initiate a multipart upload and upload one or more parts, to stop being
- *             charged for storing the uploaded parts, you must either complete or abort the multipart
- *             upload. Amazon S3 frees up the space used to store the parts and stops charging you for
- *             storing them only after you either complete or abort a multipart upload. </p>
+ *             <p>After you initiate a multipart upload and upload one or more parts, to stop being charged for
+ *         storing the uploaded parts, you must either complete or abort the multipart upload. Amazon S3 frees up the
+ *         space used to store the parts and stops charging you for storing them only after you either complete
+ *         or abort a multipart upload. </p>
  *          </note>
- *          <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the
- *          created multipart upload must be completed within the number of days specified in the
- *          bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible
- *          for an abort action and Amazon S3 aborts the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle
- *          Configuration</a>.</p>
+ *          <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the created multipart
+ *       upload must be completed within the number of days specified in the bucket lifecycle configuration.
+ *       Otherwise, the incomplete multipart upload becomes eligible for an abort action and Amazon S3 aborts the
+ *       multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">Aborting
+ *         Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration</a>.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
  *                      <b>Directory buckets </b> -
- *                   S3 Lifecycle is not supported by directory buckets.</p>
+ *             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>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</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>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/endpoint-directory-buckets-AZ.html">Regional and Zonal endpoints for directory buckets in Availability Zones</a> in the
  *     <i>Amazon S3 User Guide</i>. For more information about endpoints in Local Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.html">Concepts for directory buckets in Local Zones</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
@@ -64,33 +71,28 @@ declare const CreateMultipartUploadCommand_base: {
  *          <dl>
  *             <dt>Request signing</dt>
  *             <dd>
- *                <p>For request signing, multipart upload is just a series of regular requests. You
- *                   initiate a multipart upload, send one or more requests to upload parts, and then
- *                   complete the multipart upload process. You sign each request individually. There
- *                   is nothing special about signing multipart upload requests. For more information
- *                   about signing, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html">Authenticating
- *                      Requests (Amazon Web Services Signature Version 4)</a> in the
- *                      <i>Amazon S3 User Guide</i>.</p>
+ *                <p>For request signing, multipart upload is just a series of regular requests. You initiate a
+ *             multipart upload, send one or more requests to upload parts, and then complete the multipart
+ *             upload process. You sign each request individually. There is nothing special about signing
+ *             multipart upload requests. For more information about signing, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html">Authenticating Requests (Amazon Web Services
+ *               Signature Version 4)</a> in the <i>Amazon S3 User Guide</i>.</p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - To
- *                         perform a multipart upload with encryption using an Key Management Service (KMS)
- *                         KMS key, the requester must have permission to the
- *                            <code>kms:Decrypt</code> and <code>kms:GenerateDataKey</code> actions on
- *                         the key. The requester must also have permissions for the
- *                            <code>kms:GenerateDataKey</code> action for the
- *                            <code>CreateMultipartUpload</code> API. Then, the requester needs
- *                         permissions for the <code>kms:Decrypt</code> action on the
- *                            <code>UploadPart</code> and <code>UploadPartCopy</code> APIs. 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>
+ *                         <b>General purpose bucket permissions</b> - To perform a
+ *                 multipart upload with encryption using an Key Management Service (KMS) KMS key, the requester must have
+ *                 permission to the <code>kms:Decrypt</code> and <code>kms:GenerateDataKey</code> actions on the
+ *                 key. The requester must also have permissions for the <code>kms:GenerateDataKey</code> action
+ *                 for the <code>CreateMultipartUpload</code> API. Then, the requester needs permissions for the
+ *                   <code>kms:Decrypt</code> action on the <code>UploadPart</code> and
+ *                   <code>UploadPartCopy</code> APIs. These permissions are required because Amazon S3 must decrypt
+ *                 and read data from the encrypted file parts before it completes the multipart upload. For more
+ *                 information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions">Multipart upload API and
+ *                   permissions</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting data using server-side
+ *                   encryption with Amazon Web Services KMS</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -108,36 +110,29 @@ declare const CreateMultipartUploadCommand_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose buckets</b> - Server-side
- *                         encryption is for data encryption at rest. Amazon S3 encrypts your data as it
- *                         writes it to disks in its data centers and decrypts it when you access it.
- *                         Amazon S3 automatically encrypts all new objects that are uploaded to an S3
- *                         bucket. When doing a multipart upload, if you don't specify encryption
- *                         information in your request, the encryption setting of the uploaded parts is
- *                         set to the default encryption configuration of the destination bucket. By
- *                         default, all buckets have a base level of encryption configuration that uses
- *                         server-side encryption with Amazon S3 managed keys (SSE-S3). If the destination
- *                         bucket has a default encryption configuration that uses server-side
- *                         encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided
- *                         encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a
- *                         customer-provided key to encrypt the uploaded parts. When you perform a
- *                         CreateMultipartUpload operation, if you want to use a different type of
- *                         encryption setting for the uploaded parts, you can request that Amazon S3
- *                         encrypts the object with a different encryption key (such as an Amazon S3 managed
- *                         key, a KMS key, or a customer-provided key). When the encryption setting
- *                         in your request is different from the default encryption configuration of
- *                         the destination bucket, the encryption setting in your request takes
- *                         precedence. If you choose to provide your own encryption key, the request
- *                         headers you provide in <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a> and
- *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>
- *                         requests must match the headers you used in the
- *                            <code>CreateMultipartUpload</code> request.</p>
+ *                         <b>General purpose buckets</b> - Server-side encryption is for
+ *                 data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers
+ *                 and decrypts it when you access it. Amazon S3 automatically encrypts all new objects that are
+ *                 uploaded to an S3 bucket. When doing a multipart upload, if you don't specify encryption
+ *                 information in your request, the encryption setting of the uploaded parts is set to the
+ *                 default encryption configuration of the destination bucket. By default, all buckets have a
+ *                 base level of encryption configuration that uses server-side encryption with Amazon S3 managed keys
+ *                 (SSE-S3). If the destination bucket has a default encryption configuration that uses
+ *                 server-side encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided
+ *                 encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a customer-provided key to
+ *                 encrypt the uploaded parts. When you perform a CreateMultipartUpload operation, if you want to
+ *                 use a different type of encryption setting for the uploaded parts, you can request that Amazon S3
+ *                 encrypts the object with a different encryption key (such as an Amazon S3 managed key, a KMS key,
+ *                 or a customer-provided key). When the encryption setting in your request is different from the
+ *                 default encryption configuration of the destination bucket, the encryption setting in your
+ *                 request takes precedence. If you choose to provide your own encryption key, the request
+ *                 headers you provide in <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> requests must match the headers you used in the
+ *                   <code>CreateMultipartUpload</code> request.</p>
  *                      <ul>
  *                         <li>
- *                            <p>Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key
- *                                  (<code>aws/s3</code>) and KMS customer managed keys stored in Key Management Service
- *                               (KMS) – If you want Amazon Web Services to manage the keys used to encrypt data,
- *                               specify the following headers in the request.</p>
+ *                            <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>
@@ -158,53 +153,42 @@ declare const CreateMultipartUploadCommand_base: {
  *                            <note>
  *                               <ul>
  *                                  <li>
- *                                     <p>If you specify
- *                                           <code>x-amz-server-side-encryption:aws:kms</code>, but
- *                                        don't provide
- *                                           <code>x-amz-server-side-encryption-aws-kms-key-id</code>,
- *                                        Amazon S3 uses the Amazon Web Services managed key (<code>aws/s3</code> key) in
- *                                        KMS to protect the data.</p>
+ *                                     <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but don't
+ *                           provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>, Amazon S3 uses the
+ *                           Amazon Web Services managed key (<code>aws/s3</code> key) in KMS to protect the data.</p>
  *                                  </li>
  *                                  <li>
- *                                     <p>To perform a multipart upload with encryption by using an
- *                                        Amazon Web Services KMS key, the requester must have permission to the
- *                                           <code>kms:Decrypt</code> and
- *                                           <code>kms:GenerateDataKey*</code> actions on the key.
- *                                        These permissions are required because Amazon S3 must decrypt and
- *                                        read data from the encrypted file parts before it completes
- *                                        the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions">Multipart upload API and permissions</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting data using server-side encryption with Amazon Web Services
- *                                           KMS</a> in the
- *                                        <i>Amazon S3 User Guide</i>.</p>
+ *                                     <p>To perform a multipart upload with encryption by using an Amazon Web Services KMS key, the
+ *                           requester must have permission to the <code>kms:Decrypt</code> and
+ *                             <code>kms:GenerateDataKey*</code> actions on the key. These permissions are
+ *                           required because Amazon S3 must decrypt and read data from the encrypted file parts
+ *                           before it completes the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions">Multipart
+ *                             upload API and permissions</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting data using
+ *                             server-side encryption with Amazon Web Services KMS</a> in the
+ *                             <i>Amazon S3 User Guide</i>.</p>
  *                                  </li>
  *                                  <li>
- *                                     <p>If your Identity and Access Management (IAM) user or role is in the same
- *                                        Amazon Web Services account as the KMS key, then you must have these
- *                                        permissions on the key policy. If your IAM user or role is
- *                                        in a different account from the key, then you must have the
- *                                        permissions on both the key policy and your IAM user or
- *                                        role.</p>
+ *                                     <p>If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account as the
+ *                           KMS key, then you must have these permissions on the key policy. If your IAM
+ *                           user or role is in a different account from the key, then you must have the
+ *                           permissions on both the key policy and your IAM user or role.</p>
  *                                  </li>
  *                                  <li>
- *                                     <p>All <code>GET</code> and <code>PUT</code> requests for an
- *                                        object protected by KMS fail if you don't make them by
- *                                        using Secure Sockets Layer (SSL), Transport Layer Security
- *                                        (TLS), or Signature Version 4. For information about
- *                                        configuring any of the officially supported Amazon Web Services SDKs and
- *                                        Amazon Web Services CLI, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version">Specifying the Signature Version in
- *                                           Request Authentication</a> in the
- *                                           <i>Amazon S3 User Guide</i>.</p>
+ *                                     <p>All <code>GET</code> and <code>PUT</code> requests for an object protected by
+ *                           KMS fail if you don't make them by using Secure Sockets Layer (SSL), Transport
+ *                           Layer Security (TLS), or Signature Version 4. For information about configuring any
+ *                           of the officially supported Amazon Web Services SDKs and Amazon Web Services CLI, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version">Specifying the Signature Version in Request
+ *                             Authentication</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                                  </li>
  *                               </ul>
  *                            </note>
- *                            <p>For more information about server-side encryption with KMS keys
- *                               (SSE-KMS), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting
- *                                  Data Using Server-Side Encryption with KMS keys</a> in the
- *                                  <i>Amazon S3 User Guide</i>.</p>
+ *                            <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>
+ *                            <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>
@@ -222,17 +206,17 @@ declare const CreateMultipartUploadCommand_base: {
  *                                  </p>
  *                               </li>
  *                            </ul>
- *                            <p>For more information about server-side encryption with
- *                               customer-provided encryption keys (SSE-C), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html"> Protecting data using server-side encryption with
- *                                  customer-provided encryption keys (SSE-C)</a> in the
- *                                  <i>Amazon S3 User Guide</i>.</p>
+ *                            <p>For more information about server-side encryption with customer-provided encryption
+ *                     keys (SSE-C), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html"> Protecting data
+ *                       using server-side encryption with customer-provided encryption keys (SSE-C)</a> in
+ *                     the <i>Amazon S3 User Guide</i>.</p>
  *                         </li>
  *                      </ul>
  *                   </li>
  *                   <li>
  *                      <p>
  *                         <b>Directory buckets</b> -
- *                         For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
+ *                 For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). We recommend that the bucket's default encryption uses the desired encryption configuration and you don't override the bucket default encryption in your
  *             <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects
  *  are automatically encrypted with the desired encryption settings. For more
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>. For more information about the encryption overriding behaviors in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-specifying-kms-encryption.html">Specifying server-side encryption with KMS for new object uploads</a>.</p>
@@ -250,11 +234,10 @@ declare const CreateMultipartUploadCommand_base: {
  * </p>
  *                      </note>
  *                      <note>
- *                         <p>For directory buckets, when you perform a
- *                               <code>CreateMultipartUpload</code> operation and an
- *                               <code>UploadPartCopy</code> operation, the request headers you provide
- *                            in the <code>CreateMultipartUpload</code> request must match the default
- *                            encryption configuration of the destination bucket. </p>
+ *                         <p>For directory buckets, when you perform a <code>CreateMultipartUpload</code> operation
+ *                   and an <code>UploadPartCopy</code> operation, the request headers you provide in the
+ *                     <code>CreateMultipartUpload</code> request must match the default encryption configuration
+ *                   of the destination bucket. </p>
  *                      </note>
  *                   </li>
  *                </ul>
@@ -317,8 +300,8 @@ declare const CreateMultipartUploadCommand_base: {
  *   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",
+ *   ServerSideEncryption: "AES256" || "aws:fsx" || "aws:kms" || "aws:kms:dsse",
+ *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW" || "EXPRESS_ONEZONE" || "FSX_OPENZFS",
  *   WebsiteRedirectLocation: "STRING_VALUE",
  *   SSECustomerAlgorithm: "STRING_VALUE",
  *   SSECustomerKey: "STRING_VALUE",
@@ -343,7 +326,7 @@ declare const CreateMultipartUploadCommand_base: {
  * //   Bucket: "STRING_VALUE",
  * //   Key: "STRING_VALUE",
  * //   UploadId: "STRING_VALUE",
- * //   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
+ * //   ServerSideEncryption: "AES256" || "aws:fsx" || "aws:kms" || "aws:kms:dsse",
  * //   SSECustomerAlgorithm: "STRING_VALUE",
  * //   SSECustomerKeyMD5: "STRING_VALUE",
  * //   SSEKMSKeyId: "STRING_VALUE",