lambda-live-debugger 1.8.2 → 1.8.4

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketAclRequest } from "../models/models_0";
+import { PutBucketAclRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -27,12 +27,20 @@ declare const PutBucketAclCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <note>
+ * <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>
+ *          <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Sets the permissions on an existing bucket using access control lists (ACL). For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. To set the ACL of a
- *          bucket, you must have the <code>WRITE_ACP</code> permission.</p>
+ *          <p>Sets the permissions on an existing bucket using access control lists (ACL). For more information,
+ *       see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. To
+ *       set the ACL of a bucket, you must have the <code>WRITE_ACP</code> permission.</p>
  *          <p>You can use one of the following two ways to set a bucket's permissions:</p>
  *          <ul>
  *             <li>
@@ -43,20 +51,18 @@ declare const PutBucketAclCommand_base: {
  *             </li>
  *          </ul>
  *          <note>
- *             <p>You cannot specify access permission using both the body and the request
- *             headers.</p>
+ *             <p>You cannot specify access permission using both the body and the request headers.</p>
  *          </note>
- *          <p>Depending on your application needs, you may choose to set the ACL on a bucket using
- *          either the request body or the headers. For example, if you have an existing application
- *          that updates a bucket ACL using the request body, then you can continue to use that
- *          approach.</p>
+ *          <p>Depending on your application needs, you may choose to set the ACL on a bucket using either the
+ *       request body or the headers. For example, if you have an existing application that updates a bucket ACL
+ *       using the request body, then you can continue to use that approach.</p>
  *          <important>
- *             <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs
- *             are disabled and no longer affect permissions. You must use policies to grant access to
- *             your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return
- *             the <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are
- *             still supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling object
- *                ownership</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *             <p>If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled
+ *         and no longer affect permissions. You must use policies to grant access to your bucket and the objects
+ *         in it. Requests to set ACLs or update ACLs fail and return the
+ *           <code>AccessControlListNotSupported</code> error code. Requests to read ACLs are still supported.
+ *         For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html">Controlling object ownership</a> in
+ *         the <i>Amazon S3 User Guide</i>.</p>
  *          </important>
  *          <dl>
  *             <dt>Permissions</dt>
@@ -64,43 +70,37 @@ declare const PutBucketAclCommand_base: {
  *                <p>You can set access permissions by using one of the following methods:</p>
  *                <ul>
  *                   <li>
- *                      <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. 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. Specify the canned ACL name as the value of
- *                            <code>x-amz-acl</code>. If you use this header, you cannot use other
- *                         access control-specific headers in your request. For more information, see
- *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned
- *                         ACL</a>.</p>
+ *                      <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. 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. Specify the canned ACL name as the value of
+ *                   <code>x-amz-acl</code>. If you use this header, you cannot use other access control-specific
+ *                 headers in your request. 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. When using these headers,
- *                         you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3
- *                         groups) who will receive the permission. If you use these ACL-specific
- *                         headers, you cannot use the <code>x-amz-acl</code> header to set a canned
- *                         ACL. 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>
- *                      <p>You specify each grantee as a type=value pair, where the type is one of
- *                         the following:</p>
+ *                      <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. When using these headers, you specify
+ *                 explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who will receive the
+ *                 permission. If you use these ACL-specific headers, you cannot use the <code>x-amz-acl</code>
+ *                 header to set a canned ACL. 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>
+ *                      <p>You specify each grantee as a type=value pair, where the type is one of the
+ *                 following:</p>
  *                      <ul>
  *                         <li>
  *                            <p>
- *                               <code>id</code> – if the value specified is the canonical user ID
- *                               of an Amazon Web Services account</p>
+ *                               <code>id</code> – if the value specified is the canonical user ID of an
+ *                     Amazon Web Services account</p>
  *                         </li>
  *                         <li>
  *                            <p>
- *                               <code>uri</code> – if you are granting permissions to a predefined
- *                               group</p>
+ *                               <code>uri</code> – if you are granting permissions to a predefined group</p>
  *                         </li>
  *                         <li>
  *                            <p>
- *                               <code>emailAddress</code> – if the value specified is the email
- *                               address of an Amazon Web Services account</p>
+ *                               <code>emailAddress</code> – if the value specified is the email address of an
+ *                     Amazon Web Services account</p>
  *                            <note>
  *                               <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
  *                               <ul>
@@ -133,31 +133,31 @@ declare const PutBucketAclCommand_base: {
  *                            </note>
  *                         </li>
  *                      </ul>
- *                      <p>For example, the following <code>x-amz-grant-write</code> header grants
- *                         create, overwrite, and delete objects permission to LogDelivery group
- *                         predefined by Amazon S3 and two Amazon Web Services accounts identified by their email
- *                         addresses.</p>
+ *                      <p>For example, the following <code>x-amz-grant-write</code> header grants create, overwrite,
+ *                 and delete objects permission to LogDelivery group predefined by Amazon S3 and two Amazon Web Services accounts
+ *                 identified by their email addresses.</p>
  *                      <p>
- *                         <code>x-amz-grant-write:
- *                            uri="http://acs.amazonaws.com/groups/s3/LogDelivery", id="111122223333",
- *                            id="555566667777" </code>
+ *                         <code>x-amz-grant-write: uri="http://acs.amazonaws.com/groups/s3/LogDelivery",
+ *                   id="111122223333", id="555566667777" </code>
  *                      </p>
  *                   </li>
  *                </ul>
- *                <p>You can use either a canned ACL or specify access permissions explicitly. You
- *                   cannot do both.</p>
+ *                <p>You can use either a canned ACL or specify access permissions explicitly. You cannot do
+ *             both.</p>
  *             </dd>
  *             <dt>Grantee Values</dt>
  *             <dd>
- *                <p>You can specify the person (grantee) to whom you're assigning access rights
- *                   (using request elements) in the following ways:</p>
+ *                <p>You can specify the person (grantee) to whom you're assigning access rights (using request
+ *             elements) in the following ways. For examples of how to specify these grantee values in JSON
+ *             format, see the Amazon Web Services CLI example in <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html"> Enabling Amazon S3 server
+ *               access logging</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                <ul>
  *                   <li>
  *                      <p>By the person's ID:</p>
  *                      <p>
  *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                            xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
- *                            </Grantee></code>
+ *                   xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName>
+ *                   </Grantee></code>
  *                      </p>
  *                      <p>DisplayName is optional and ignored in the request</p>
  *                   </li>
@@ -165,17 +165,17 @@ declare const PutBucketAclCommand_base: {
  *                      <p>By URI:</p>
  *                      <p>
  *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                            xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>
+ *                   xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee></code>
  *                      </p>
  *                   </li>
  *                   <li>
  *                      <p>By Email address:</p>
  *                      <p>
  *                         <code><Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- *                            xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee></code>
+ *                   xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee></code>
  *                      </p>
- *                      <p>The grantee is resolved to the CanonicalUser and, in a response to a GET
- *                         Object acl request, appears as the CanonicalUser. </p>
+ *                      <p>The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl
+ *                 request, appears as the CanonicalUser. </p>
  *                      <note>
  *                         <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
  *                         <ul>

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketAnalyticsConfigurationRequest } from "../models/models_0";
+import { PutBucketAnalyticsConfigurationRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -30,26 +30,25 @@ declare const PutBucketAnalyticsConfigurationCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Sets an analytics configuration for the bucket (specified by the analytics configuration
- *          ID). You can have up to 1,000 analytics configurations per bucket.</p>
- *          <p>You can choose to have storage class analysis export analysis reports sent to a
- *          comma-separated values (CSV) flat file. See the <code>DataExport</code> request element.
- *          Reports are updated daily and are based on the object filters that you configure. When
- *          selecting data export, you specify a destination bucket and an optional destination prefix
- *          where the file is written. You can export the data to a destination bucket in a different
- *          account. However, the destination bucket must be in the same Region as the bucket that you
- *          are making the PUT analytics configuration to. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html">Amazon S3
- *             Analytics – Storage Class Analysis</a>. </p>
+ *          <p>Sets an analytics configuration for the bucket (specified by the analytics configuration ID). You
+ *       can have up to 1,000 analytics configurations per bucket.</p>
+ *          <p>You can choose to have storage class analysis export analysis reports sent to a comma-separated
+ *       values (CSV) flat file. See the <code>DataExport</code> request element. Reports are updated daily and
+ *       are based on the object filters that you configure. When selecting data export, you specify a
+ *       destination bucket and an optional destination prefix where the file is written. You can export the data
+ *       to a destination bucket in a different account. However, the destination bucket must be in the same
+ *       Region as the bucket that you are making the PUT analytics configuration to. For more information, see
+ *         <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html">Amazon S3 Analytics –
+ *         Storage Class Analysis</a>. </p>
  *          <important>
- *             <p>You must create a bucket policy on the destination bucket where the exported file is
- *             written to grant permissions to Amazon S3 to write objects to the bucket. For an example
- *             policy, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html#example-bucket-policies-use-case-9">Granting Permissions for Amazon S3 Inventory and Storage Class Analysis</a>.</p>
+ *             <p>You must create a bucket policy on the destination bucket where the exported file is written to
+ *         grant permissions to Amazon S3 to write objects to the bucket. For an example policy, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html#example-bucket-policies-use-case-9">Granting
+ *           Permissions for Amazon S3 Inventory and Storage Class Analysis</a>.</p>
  *          </important>
  *          <p>To use this operation, you must have permissions to perform the
- *             <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission
- *          by default. The bucket owner can grant this permission to others. For more information
- *          about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions Related to Bucket Subresource Operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing
- *             Access Permissions to Your Amazon S3 Resources</a>.</p>
+ *         <code>s3:PutAnalyticsConfiguration</code> action. The bucket owner has this permission by default. The
+ *       bucket owner can grant this permission to others. For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions Related to Bucket Subresource Operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access Permissions to Your Amazon S3
+ *         Resources</a>.</p>
  *          <p>
  *             <code>PutBucketAnalyticsConfiguration</code> has the following special errors:</p>
  *          <ul>
@@ -86,8 +85,8 @@ declare const PutBucketAnalyticsConfigurationCommand_base: {
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <i>Cause: You are attempting to create a new configuration but have
- *                         already reached the 1,000-configuration limit.</i>
+ *                         <i>Cause: You are attempting to create a new configuration but have already reached
+ *                 the 1,000-configuration limit.</i>
  *                      </p>
  *                   </li>
  *                </ul>
@@ -106,16 +105,15 @@ declare const PutBucketAnalyticsConfigurationCommand_base: {
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <i>Cause: You are not the owner of the specified bucket, or you do
- *                         not have the s3:PutAnalyticsConfiguration bucket permission to set the
- *                         configuration on the bucket.</i>
+ *                         <i>Cause: You are not the owner of the specified bucket, or you do not have the
+ *                 s3:PutAnalyticsConfiguration bucket permission to set the configuration on the
+ *                 bucket.</i>
  *                      </p>
  *                   </li>
  *                </ul>
  *             </li>
  *          </ul>
- *          <p>The following operations are related to
- *          <code>PutBucketAnalyticsConfiguration</code>:</p>
+ *          <p>The following operations are related to <code>PutBucketAnalyticsConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>

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

@@ -30,42 +30,38 @@ declare const PutBucketCorsCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists,
- *          Amazon S3 replaces it.</p>
- *          <p>To use this operation, you must be allowed to perform the <code>s3:PutBucketCORS</code>
- *          action. By default, the bucket owner has this permission and can grant it to others.</p>
- *          <p>You set this configuration on a bucket so that the bucket can service cross-origin
- *          requests. For example, you might want to enable a request whose origin is
- *             <code>http://www.example.com</code> to access your Amazon S3 bucket at
- *             <code>my.example.bucket.com</code> by using the browser's <code>XMLHttpRequest</code>
- *          capability.</p>
- *          <p>To enable cross-origin resource sharing (CORS) on a bucket, you add the
- *             <code>cors</code> subresource to the bucket. The <code>cors</code> subresource is an XML
- *          document in which you configure rules that identify origins and the HTTP methods that can
- *          be executed on your bucket. The document is limited to 64 KB in size. </p>
- *          <p>When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a
- *          bucket, it evaluates the <code>cors</code> configuration on the bucket and uses the first
- *             <code>CORSRule</code> rule that matches the incoming browser request to enable a
- *          cross-origin request. For a rule to match, the following conditions must be met:</p>
+ *          <p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists, Amazon S3 replaces
+ *       it.</p>
+ *          <p>To use this operation, you must be allowed to perform the <code>s3:PutBucketCORS</code> action. By
+ *       default, the bucket owner has this permission and can grant it to others.</p>
+ *          <p>You set this configuration on a bucket so that the bucket can service cross-origin requests. For
+ *       example, you might want to enable a request whose origin is <code>http://www.example.com</code> to
+ *       access your Amazon S3 bucket at <code>my.example.bucket.com</code> by using the browser's
+ *         <code>XMLHttpRequest</code> capability.</p>
+ *          <p>To enable cross-origin resource sharing (CORS) on a bucket, you add the <code>cors</code>
+ *       subresource to the bucket. The <code>cors</code> subresource is an XML document in which you configure
+ *       rules that identify origins and the HTTP methods that can be executed on your bucket. The document is
+ *       limited to 64 KB in size. </p>
+ *          <p>When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a bucket, it
+ *       evaluates the <code>cors</code> configuration on the bucket and uses the first <code>CORSRule</code>
+ *       rule that matches the incoming browser request to enable a cross-origin request. For a rule to match,
+ *       the following conditions must be met:</p>
  *          <ul>
  *             <li>
- *                <p>The request's <code>Origin</code> header must match <code>AllowedOrigin</code>
- *                elements.</p>
+ *                <p>The request's <code>Origin</code> header must match <code>AllowedOrigin</code> elements.</p>
  *             </li>
  *             <li>
  *                <p>The request method (for example, GET, PUT, HEAD, and so on) or the
- *                   <code>Access-Control-Request-Method</code> header in case of a pre-flight
- *                   <code>OPTIONS</code> request must be one of the <code>AllowedMethod</code>
- *                elements. </p>
+ *             <code>Access-Control-Request-Method</code> header in case of a pre-flight <code>OPTIONS</code>
+ *           request must be one of the <code>AllowedMethod</code> elements. </p>
  *             </li>
  *             <li>
- *                <p>Every header specified in the <code>Access-Control-Request-Headers</code> request
- *                header of a pre-flight request must match an <code>AllowedHeader</code> element.
- *             </p>
+ *                <p>Every header specified in the <code>Access-Control-Request-Headers</code> request header of a
+ *           pre-flight request must match an <code>AllowedHeader</code> element. </p>
  *             </li>
  *          </ul>
- *          <p> For more information about CORS, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html">Enabling Cross-Origin Resource Sharing</a> in
- *          the <i>Amazon S3 User Guide</i>.</p>
+ *          <p> For more information about CORS, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html">Enabling Cross-Origin Resource Sharing</a> in the
+ *         <i>Amazon S3 User Guide</i>.</p>
  *          <p>The following operations are related to <code>PutBucketCors</code>:</p>
  *          <ul>
  *             <li>

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

@@ -27,8 +27,7 @@ declare const PutBucketEncryptionCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>This operation configures default encryption and Amazon S3 Bucket Keys for an existing
- *          bucket.</p>
+ * <p>This operation configures default encryption and Amazon S3 Bucket Keys for an existing bucket.</p>
  *          <note>
  *             <p>
  *                <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the Regional endpoint. These endpoints support path-style requests in the format <code>https://s3express-control.<i>region-code</i>.amazonaws.com/<i>bucket-name</i>
@@ -37,8 +36,8 @@ declare const PutBucketEncryptionCommand_base: {
  *     <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>
  *          </note>
- *          <p>By default, all buckets have a default encryption configuration that uses server-side
- *          encryption with Amazon S3 managed keys (SSE-S3).</p>
+ *          <p>By default, all buckets have a default encryption configuration that uses server-side encryption
+ *       with Amazon S3 managed keys (SSE-S3).</p>
  *          <note>
  *             <ul>
  *                <li>
@@ -47,35 +46,32 @@ declare const PutBucketEncryptionCommand_base: {
  *                   </p>
  *                   <ul>
  *                      <li>
- *                         <p>You can optionally configure default encryption for a bucket by using
- *                         server-side encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer
- *                         server-side encryption with Amazon Web Services KMS keys (DSSE-KMS). If you specify
- *                         default encryption by using SSE-KMS, you can also configure <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3
- *                            Bucket Keys</a>. For information about the bucket default encryption
- *                         feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3 Bucket Default
- *                            Encryption</a> in the <i>Amazon S3 User Guide</i>. </p>
+ *                         <p>You can optionally configure default encryption for a bucket by using server-side
+ *                 encryption with Key Management Service (KMS) keys (SSE-KMS) or dual-layer server-side encryption with
+ *                 Amazon Web Services KMS keys (DSSE-KMS). If you specify default encryption by using SSE-KMS, you can also
+ *                 configure <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket
+ *                   Keys</a>. For information about the bucket default encryption feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3 Bucket Default
+ *                   Encryption</a> in the <i>Amazon S3 User Guide</i>. </p>
  *                      </li>
  *                      <li>
- *                         <p>If you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket
- *                            encryption</a> to SSE-KMS, you should verify that your KMS key ID
- *                         is correct. Amazon S3 doesn't validate the KMS key ID provided in
- *                         PutBucketEncryption requests.</p>
+ *                         <p>If you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket encryption</a> to
+ *                 SSE-KMS, you should verify that your KMS key ID is correct. Amazon S3 doesn't validate the
+ *                 KMS key ID provided in PutBucketEncryption requests.</p>
  *                      </li>
  *                   </ul>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets </b> - You can
- *                   optionally configure default encryption for a bucket by using server-side
- *                   encryption with Key Management Service (KMS) keys (SSE-KMS).</p>
+ *                      <b>Directory buckets </b> - You can optionally configure
+ *             default encryption for a bucket by using server-side encryption with Key Management Service (KMS) keys
+ *             (SSE-KMS).</p>
  *                   <ul>
  *                      <li>
- *                         <p>We recommend that the bucket's default encryption uses the desired
- *                         encryption configuration and you don't override the bucket default
- *                         encryption in your <code>CreateSession</code> requests or <code>PUT</code>
- *                         object requests. Then, new objects are automatically encrypted with the
- *                         desired encryption settings.
- *                         For more information about the encryption overriding behaviors in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-specifying-kms-encryption.html">Specifying server-side encryption with KMS for new object uploads</a>.</p>
+ *                         <p>We recommend that the bucket's default encryption uses the desired encryption
+ *                 configuration and you don't override the bucket default encryption in your
+ *                   <code>CreateSession</code> requests or <code>PUT</code> object requests. Then, new objects
+ *                 are automatically encrypted with the desired encryption settings.
+ *                 For more information about the encryption overriding behaviors in directory buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-specifying-kms-encryption.html">Specifying server-side encryption with KMS for new object uploads</a>.</p>
  *                      </li>
  *                      <li>
  *                         <p>Your SSE-KMS configuration can only support 1 <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">customer managed key</a> per directory bucket's lifetime.
@@ -91,21 +87,21 @@ declare const PutBucketEncryptionCommand_base: {
  *                         <p>When you specify an <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk">KMS customer managed key</a> for encryption in your directory bucket, only use the key ID or key ARN. The key alias format of the KMS key isn't supported.</p>
  *                      </li>
  *                      <li>
- *                         <p>For directory buckets, if you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket encryption</a> to SSE-KMS, Amazon S3 validates the
- *                         KMS key ID provided in PutBucketEncryption requests.</p>
+ *                         <p>For directory buckets, if you use PutBucketEncryption to set your <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">default bucket
+ *                   encryption</a> to SSE-KMS, Amazon S3 validates the KMS key ID provided in
+ *                 PutBucketEncryption requests.</p>
  *                      </li>
  *                   </ul>
  *                </li>
  *             </ul>
  *          </note>
  *          <important>
- *             <p>If you're specifying a customer managed KMS key, we recommend using a fully
- *             qualified KMS key ARN. If you use a KMS key alias instead, then KMS resolves the
- *             key within the requester’s account. This behavior can result in data that's encrypted
- *             with a KMS key that belongs to the requester, and not the bucket owner.</p>
- *             <p>Also, this action requires Amazon Web Services Signature Version 4. For more information, see
- *                <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html"> Authenticating
- *                Requests (Amazon Web Services Signature Version 4)</a>. </p>
+ *             <p>If you're specifying a customer managed KMS key, we recommend using a fully qualified KMS key
+ *         ARN. If you use a KMS key alias instead, then KMS resolves the key within the requester’s account.
+ *         This behavior can result in data that's encrypted with a KMS key that belongs to the requester, and
+ *         not the bucket owner.</p>
+ *             <p>Also, this action requires Amazon Web Services Signature Version 4. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html"> Authenticating
+ *           Requests (Amazon Web Services Signature Version 4)</a>. </p>
  *          </important>
  *          <dl>
  *             <dt>Permissions</dt>
@@ -114,24 +110,20 @@ declare const PutBucketEncryptionCommand_base: {
  *                   <li>
  *                      <p>
  *                         <b>General purpose bucket permissions</b> - The
- *                            <code>s3:PutEncryptionConfiguration</code> permission is required in a
- *                         policy. The bucket owner has this permission by default. The bucket owner
- *                         can grant this permission to others. For more information about permissions,
- *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions Related to Bucket Operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access
- *                            Permissions to Your Amazon S3 Resources</a> in the
- *                            <i>Amazon S3 User Guide</i>.</p>
+ *                   <code>s3:PutEncryptionConfiguration</code> permission is required in a policy. The bucket
+ *                 owner has this permission by default. The bucket owner can grant this permission to others.
+ *                 For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-with-s3-actions.html#using-with-s3-actions-related-to-bucket-subresources">Permissions Related to Bucket Operations</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access Permissions to Your
+ *                   Amazon S3 Resources</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket permissions</b> -
- *                         To grant access to this API operation, you must have the
- *                            <code>s3express:PutEncryptionConfiguration</code> permission in
- *                         an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
- *                         For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
- *                      <p>To set a directory bucket default encryption with SSE-KMS, you must also
- *                         have the <code>kms:GenerateDataKey</code> and the <code>kms:Decrypt</code>
- *                         permissions in IAM identity-based policies and KMS key policies for the
- *                         target KMS key.</p>
+ *                         <b>Directory bucket permissions</b> - To grant access to
+ *                 this API operation, you must have the <code>s3express:PutEncryptionConfiguration</code>
+ *                 permission in an IAM identity-based policy instead of a bucket policy. Cross-account access to this API operation isn't supported. This operation can only be performed by the Amazon Web Services account that owns the resource.
+ *                 For more information about directory bucket policies and permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam.html">Amazon Web Services Identity and Access Management (IAM) for S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>To set a directory bucket default encryption with SSE-KMS, you must also have the
+ *                   <code>kms:GenerateDataKey</code> and the <code>kms:Decrypt</code> permissions in IAM
+ *                 identity-based policies and KMS key policies for the target KMS key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -168,7 +160,7 @@ declare const PutBucketEncryptionCommand_base: {
  *     Rules: [ // ServerSideEncryptionRules // required
  *       { // ServerSideEncryptionRule
  *         ApplyServerSideEncryptionByDefault: { // ServerSideEncryptionByDefault
- *           SSEAlgorithm: "AES256" || "aws:kms" || "aws:kms:dsse", // required
+ *           SSEAlgorithm: "AES256" || "aws:fsx" || "aws:kms" || "aws:kms:dsse", // required
  *           KMSMasterKeyID: "STRING_VALUE",
  *         },
  *         BucketKeyEnabled: true || false,

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

@@ -30,8 +30,8 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
  * <note>
  *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to
- *          1,000 S3 Intelligent-Tiering configurations per bucket.</p>
+ *          <p>Puts a S3 Intelligent-Tiering configuration to the specified bucket. You can have up to 1,000
+ *       S3 Intelligent-Tiering configurations per bucket.</p>
  *          <p>The S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.</p>
  *          <p>The S3 Intelligent-Tiering storage class is  the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.</p>
  *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html#sc-dynamic-data-access">Storage class for automatically optimizing frequently and infrequently accessed objects</a>.</p>
@@ -54,13 +54,12 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
  *             </li>
  *          </ul>
  *          <note>
- *             <p>You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically
- *             move objects stored in the S3 Intelligent-Tiering storage class to the Archive Access
- *             or Deep Archive Access tier.</p>
+ *             <p>You only need S3 Intelligent-Tiering enabled on a bucket if you want to automatically move objects
+ *         stored in the S3 Intelligent-Tiering storage class to the Archive Access or Deep Archive Access
+ *         tier.</p>
  *          </note>
  *          <p>
- *             <code>PutBucketIntelligentTieringConfiguration</code> has the following special
- *          errors:</p>
+ *             <code>PutBucketIntelligentTieringConfiguration</code> has the following special errors:</p>
  *          <dl>
  *             <dt>HTTP 400 Bad Request Error</dt>
  *             <dd>
@@ -74,15 +73,15 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
  *                <p>
  *                   <i>Code:</i> TooManyConfigurations</p>
  *                <p>
- *                   <i>Cause:</i> You are attempting to create a new configuration
- *                   but have already reached the 1,000-configuration limit. </p>
+ *                   <i>Cause:</i> You are attempting to create a new configuration but have already
+ *             reached the 1,000-configuration limit. </p>
  *             </dd>
  *             <dt>HTTP 403 Forbidden Error</dt>
  *             <dd>
  *                <p>
- *                   <i>Cause:</i> You are not the owner of the specified bucket, or
- *                   you do not have the <code>s3:PutIntelligentTieringConfiguration</code> bucket
- *                   permission to set the configuration on the bucket. </p>
+ *                   <i>Cause:</i> You are not the owner of the specified bucket, or you do not have
+ *             the <code>s3:PutIntelligentTieringConfiguration</code> bucket permission to set the configuration
+ *             on the bucket. </p>
  *             </dd>
  *          </dl>
  * @example
@@ -94,6 +93,7 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
  * const input = { // PutBucketIntelligentTieringConfigurationRequest
  *   Bucket: "STRING_VALUE", // required
  *   Id: "STRING_VALUE", // required
+ *   ExpectedBucketOwner: "STRING_VALUE",
  *   IntelligentTieringConfiguration: { // IntelligentTieringConfiguration
  *     Id: "STRING_VALUE", // required
  *     Filter: { // IntelligentTieringFilter