@gemeentenijmegen/webapp 1.1.1 → 1.1.3

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

@@ -28,21 +28,24 @@ declare const ListPartsCommand_base: {
 };
 /**
  * <p>Lists the parts that have been uploaded for a specific multipart upload.</p>
- *          <p>To use this operation, you must provide the <code>upload ID</code> in the request. You obtain this uploadID by sending the initiate multipart upload
- *          request through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.</p>
- *          <p>The <code>ListParts</code> request returns a maximum of 1,000 uploaded parts. The limit of 1,000 parts is also the default value. You can restrict the number of parts in a response by specifying the
- *             <code>max-parts</code> request parameter. If your multipart upload consists of more than
- *          1,000 parts, the response returns an <code>IsTruncated</code> field with the value of <code>true</code>,
- *          and a <code>NextPartNumberMarker</code> element. To list remaining uploaded parts, in subsequent <code>ListParts</code>
- *          requests, include the <code>part-number-marker</code> query string parameter and set its value to
- *          the <code>NextPartNumberMarker</code> field value from the previous response.</p>
+ *          <p>To use this operation, you must provide the <code>upload ID</code> in the request. You
+ *          obtain this uploadID by sending the initiate multipart upload request through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.</p>
+ *          <p>The <code>ListParts</code> request returns a maximum of 1,000 uploaded parts. The limit
+ *          of 1,000 parts is also the default value. You can restrict the number of parts in a
+ *          response by specifying the <code>max-parts</code> request parameter. If your multipart
+ *          upload consists of more than 1,000 parts, the response returns an <code>IsTruncated</code>
+ *          field with the value of <code>true</code>, and a <code>NextPartNumberMarker</code> element.
+ *          To list remaining uploaded parts, in subsequent <code>ListParts</code> requests, include
+ *          the <code>part-number-marker</code> query string parameter and set its value to the
+ *             <code>NextPartNumberMarker</code> field value from the previous response.</p>
  *          <p>For more information on multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading Objects Using Multipart
- *          Upload</a> in the <i>Amazon S3
- *             User Guide</i>.</p>
+ *             Upload</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
- *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
+ *                <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>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/s3-express-Regions-and-Zones.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">Available Local Zone for directory buckets</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
  *          <dl>
@@ -51,12 +54,15 @@ declare const ListPartsCommand_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - For information about permissions required to use the multipart upload API, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload
- *                         and Permissions</a> in the <i>Amazon S3
- *                            User Guide</i>.</p>
- *                      <p>If the upload was created 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), you must have permission
- *                         to the <code>kms:Decrypt</code> action for the <code>ListParts</code> request to succeed.</p>
+ *                         <b>General purpose bucket permissions</b> - For
+ *                         information about permissions required to use the multipart upload API, see
+ *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
+ *                            Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>If the upload was created 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), you must have permission to the
+ *                            <code>kms:Decrypt</code> action for the <code>ListParts</code> request to
+ *                         succeed.</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -73,7 +79,7 @@ declare const ListPartsCommand_base: {
  *             <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>
+ *                      <i>Bucket-name</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com</code>.</p>
  *             </dd>
  *          </dl>
  *          <p>The following operations are related to <code>ListParts</code>:</p>

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

@@ -28,7 +28,7 @@ declare const PutBucketAccelerateConfigurationCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the accelerate configuration of an existing bucket. Amazon S3 Transfer Acceleration is a
  *          bucket-level feature that enables you to perform faster data transfers to Amazon S3.</p>

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

@@ -28,7 +28,7 @@ declare const PutBucketAclCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the 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

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

@@ -28,7 +28,7 @@ declare const PutBucketAnalyticsConfigurationCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets an analytics configuration for the bucket (specified by the analytics configuration
  *          ID). You can have up to 1,000 analytics configurations per bucket.</p>

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketCorsRequest } from "../models/models_0";
+import { PutBucketCorsRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -28,7 +28,7 @@ declare const PutBucketCorsCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the <code>cors</code> configuration for your bucket. If the configuration exists,
  *          Amazon S3 replaces it.</p>

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketEncryptionRequest } from "../models/models_0";
+import { PutBucketEncryptionRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -27,13 +27,14 @@ 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>
+ *                <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>
  *                </code>. Virtual-hosted-style requests aren't 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
+ * For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.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">Available Local Zone for directory buckets</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
@@ -46,30 +47,35 @@ 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 for the lifetime of the bucket.
@@ -85,19 +91,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>
@@ -105,24 +113,32 @@ declare const PutBucketEncryptionCommand_base: {
  *                <ul>
  *                   <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>
+ *                         <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>
  *                   </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>
  *             <dt>HTTP Host header syntax</dt>
  *             <dd>
  *                <p>
- *                   <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
+ *                   <b>Directory buckets </b> - The HTTP Host header syntax is <code>s3express-control.<i>region-code</i>.amazonaws.com</code>.</p>
  *             </dd>
  *          </dl>
  *          <p>The following operations are related to <code>PutBucketEncryption</code>:</p>

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketIntelligentTieringConfigurationRequest } from "../models/models_0";
+import { PutBucketIntelligentTieringConfigurationRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -28,7 +28,7 @@ declare const PutBucketIntelligentTieringConfigurationCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <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>

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketInventoryConfigurationRequest } from "../models/models_0";
+import { PutBucketInventoryConfigurationRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -28,7 +28,7 @@ declare const PutBucketInventoryConfigurationCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>This implementation of the <code>PUT</code> action adds an inventory configuration
  *          (identified by the inventory ID) to the bucket. You can have up to 1,000 inventory

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketLifecycleConfigurationOutput, PutBucketLifecycleConfigurationRequest } from "../models/models_0";
+import { PutBucketLifecycleConfigurationOutput, PutBucketLifecycleConfigurationRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -27,26 +27,41 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <note>
- *             <p>This operation is not supported by directory buckets.</p>
- *          </note>
- *          <p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle
+ * <p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle
  *          configuration. Keep in mind that this will overwrite an existing lifecycle configuration,
  *          so if you want to retain any configuration details, they must be included in the new
  *          lifecycle configuration. For information about lifecycle configuration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html">Managing
  *             your storage lifecycle</a>.</p>
+ *          <note>
+ *             <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, object size, or any combination of these. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility.
+ *             For the related API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>.</p>
+ *          </note>
  *          <dl>
  *             <dt>Rules</dt>
+ *             <dt>Permissions</dt>
+ *             <dt>HTTP Host header syntax</dt>
  *             <dd>
  *                <p>You specify the lifecycle configuration in your request body. The lifecycle
  *                   configuration is specified as XML consisting of one or more rules. An Amazon S3
- *                   Lifecycle configuration can have up to 1,000 rules. This limit is not adjustable.</p>
- *                <p>Bucket lifecycle configuration supports specifying a lifecycle rule using an object key name prefix, one or more object tags, object size, or any combination of these. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility.
- *                      For the related API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>.</p>
+ *                   Lifecycle configuration can have up to 1,000 rules. This limit is not
+ *                   adjustable.</p>
+ *                <p>Bucket lifecycle configuration supports specifying a lifecycle rule using an
+ *                   object key name prefix, one or more object tags, object size, or any combination
+ *                   of these. Accordingly, this section describes the latest API. The previous version
+ *                   of the API supported filtering based only on an object key name prefix, which is
+ *                   supported for backward compatibility for general purpose buckets. For the related
+ *                   API description, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html">PutBucketLifecycle</a>. </p>
+ *                <note>
+ *                   <p>Lifecyle configurations for directory buckets only support expiring objects and
+ *                      cancelling multipart uploads. Expiring of versioned objects,transitions and tag
+ *                      filters are not supported.</p>
+ *                </note>
  *                <p>A lifecycle rule consists of the following:</p>
  *                <ul>
  *                   <li>
- *                      <p>A filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object tags, object size, or any combination of these.</p>
+ *                      <p>A filter identifying a subset of objects to which the rule applies. The
+ *                         filter can be based on a key name prefix, object tags, object size, or any
+ *                         combination of these.</p>
  *                   </li>
  *                   <li>
  *                      <p>A status indicating whether the rule is in effect.</p>
@@ -64,59 +79,88 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
  *                      Management</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html">Lifecycle Configuration
  *                      Elements</a>.</p>
  *             </dd>
- *             <dt>Permissions</dt>
  *             <dd>
- *                <p>By default, all Amazon S3 resources are private, including buckets, objects, and
- *                   related subresources (for example, lifecycle configuration and website
- *                   configuration). Only the resource owner (that is, the Amazon Web Services account that created
- *                   it) can access the resource. The resource owner can optionally grant access
- *                   permissions to others by writing an access policy. For this operation, a user must
- *                   get the <code>s3:PutLifecycleConfiguration</code> permission.</p>
- *                <p>You can also explicitly deny permissions. An explicit deny also supersedes any
- *                   other permissions. If you want to block users or accounts from removing or
- *                   deleting objects from your bucket, you must deny them permissions for the
- *                   following actions:</p>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <code>s3:DeleteObject</code>
- *                      </p>
+ *                         <b>General purpose bucket permissions</b> - By
+ *                         default, all Amazon S3 resources are private, including buckets, objects, and
+ *                         related subresources (for example, lifecycle configuration and website
+ *                         configuration). Only the resource owner (that is, the Amazon Web Services account that
+ *                         created it) can access the resource. The resource owner can optionally grant
+ *                         access permissions to others by writing an access policy. For this
+ *                         operation, a user must have the <code>s3:PutLifecycleConfiguration</code>
+ *                         permission.</p>
+ *                      <p>You can also explicitly deny permissions. An explicit deny also
+ *                         supersedes any other permissions. If you want to block users or accounts
+ *                         from removing or deleting objects from your bucket, you must deny them
+ *                         permissions for the following actions:</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>
+ *                               <code>s3:DeleteObject</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>s3:DeleteObjectVersion</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <code>s3:PutLifecycleConfiguration</code>
+ *                            </p>
+ *                            <p>For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing
+ *                                  Access Permissions to Your Amazon S3 Resources</a>.</p>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                </ul>
+ *                <ul>
+ *                   <li>
+ *                      <p>
+ *                         <b>Directory bucket permissions</b> -
+ *                         You must have the <code>s3express:PutLifecycleConfiguration</code>
+ *                         permission in an IAM identity-based policy to use this operation.
+ *                         Cross-account access to this API operation isn't supported. The resource
+ *                         owner can optionally grant access permissions to others by creating a role
+ *                         or user for them as long as they are within the same account as the owner
+ *                         and resource.</p>
+ *                      <p>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">Authorizing Regional endpoint APIs with IAM</a> in the
+ *                            <i>Amazon S3 User Guide</i>.</p>
+ *                      <note>
+ *                         <p>
+ *                            <b>Directory buckets </b> - For directory buckets, you must make requests for this API operation to the 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>
+ *                            </code>. Virtual-hosted-style requests aren't supported.
+ * For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.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">Available Local Zone for directory buckets</a> in the
+ *     <i>Amazon S3 User Guide</i>.</p>
+ *                      </note>
  *                   </li>
+ *                </ul>
+ *             </dd>
+ *             <dd>
+ *                <p>
+ *                   <b>Directory buckets </b> - The HTTP Host
+ *                   header syntax is
+ *                      <code>s3express-control.<i>region</i>.amazonaws.com</code>.</p>
+ *                <p>The following operations are related to
+ *                      <code>PutBucketLifecycleConfiguration</code>:</p>
+ *                <ul>
  *                   <li>
  *                      <p>
- *                         <code>s3:DeleteObjectVersion</code>
+ *                         <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html">GetBucketLifecycleConfiguration</a>
  *                      </p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <code>s3:PutLifecycleConfiguration</code>
+ *                         <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html">DeleteBucketLifecycle</a>
  *                      </p>
  *                   </li>
  *                </ul>
- *                <p>For more information about permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html">Managing Access
- *                      Permissions to Your Amazon S3 Resources</a>.</p>
  *             </dd>
  *          </dl>
- *          <p>The following operations are related to
- *          <code>PutBucketLifecycleConfiguration</code>:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html">Examples of
- *                   Lifecycle Configuration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html">GetBucketLifecycleConfiguration</a>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html">DeleteBucketLifecycle</a>
- *                </p>
- *             </li>
- *          </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketLoggingRequest } from "../models/models_0";
+import { PutBucketLoggingRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -28,7 +28,7 @@ declare const PutBucketLoggingCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Set the logging parameters for a bucket and to specify permissions for who can view and
  *          modify the logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as

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

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketMetricsConfigurationRequest } from "../models/models_0";
+import { PutBucketMetricsConfigurationRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -28,7 +28,7 @@ declare const PutBucketMetricsConfigurationCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets a metrics configuration (specified by the metrics configuration ID) for the bucket.
  *          You can have up to 1,000 metrics configurations per bucket. If you're updating an existing

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

@@ -28,7 +28,7 @@ declare const PutBucketNotificationConfigurationCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Enables notifications of specified events for a bucket. For more information about event
  *          notifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Event

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

@@ -28,7 +28,7 @@ declare const PutBucketOwnershipControlsCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Creates or modifies <code>OwnershipControls</code> for an Amazon S3 bucket. To use this
  *          operation, you must have the <code>s3:PutBucketOwnershipControls</code> permission. For