@gemeentenijmegen/webapp 1.1.8 → 1.1.10

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

@@ -30,43 +30,40 @@ declare const PutBucketInventoryConfigurationCommand_base: {
  * <note>
  *             <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
- *          configurations per bucket. </p>
- *          <p>Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly
- *          basis, and the results are published to a flat file. The bucket that is inventoried is
- *          called the <i>source</i> bucket, and the bucket where the inventory flat file
- *          is stored is called the <i>destination</i> bucket. The
- *             <i>destination</i> bucket must be in the same Amazon Web Services Region as the
- *             <i>source</i> bucket. </p>
- *          <p>When you configure an inventory for a <i>source</i> bucket, you specify
- *          the <i>destination</i> bucket where you want the inventory to be stored, and
- *          whether to generate the inventory daily or weekly. You can also configure what object
- *          metadata to include and whether to inventory all object versions or only current versions.
- *          For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html">Amazon S3 Inventory</a> in the
- *          Amazon S3 User Guide.</p>
+ *          <p>This implementation of the <code>PUT</code> action adds an S3 Inventory configuration (identified by
+ *       the inventory ID) to the bucket. You can have up to 1,000 inventory configurations per bucket. </p>
+ *          <p>Amazon S3 inventory generates inventories of the objects in the bucket on a daily or weekly basis, and
+ *       the results are published to a flat file. The bucket that is inventoried is called the
+ *         <i>source</i> bucket, and the bucket where the inventory flat file is stored is called
+ *       the <i>destination</i> bucket. The <i>destination</i> bucket must be in the
+ *       same Amazon Web Services Region as the <i>source</i> bucket. </p>
+ *          <p>When you configure an inventory for a <i>source</i> bucket, you specify the
+ *         <i>destination</i> bucket where you want the inventory to be stored, and whether to
+ *       generate the inventory daily or weekly. You can also configure what object metadata to include and
+ *       whether to inventory all object versions or only current versions. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html">Amazon S3 Inventory</a> in the
+ *       Amazon S3 User Guide.</p>
  *          <important>
- *             <p>You must create a bucket policy on the <i>destination</i> bucket to
- *             grant permissions to Amazon S3 to write objects to the bucket in the defined location. 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 <i>destination</i> bucket to grant
+ *         permissions to Amazon S3 to write objects to the bucket in the defined location. 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>
  *          <dl>
  *             <dt>Permissions</dt>
  *             <dd>
  *                <p>To use this operation, you must have permission to perform the
- *                      <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this
- *                   permission by default and can grant this permission to others. </p>
- *                <p>The <code>s3:PutInventoryConfiguration</code> permission allows a user to
- *                   create an <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html">S3 Inventory</a>
- *                   report that includes all object metadata fields available and to specify the
- *                   destination bucket to store the inventory. A user with read access to objects in
- *                   the destination bucket can also access all object metadata fields that are
- *                   available in the inventory report. </p>
+ *               <code>s3:PutInventoryConfiguration</code> action. The bucket owner has this permission by
+ *             default and can grant this permission to others. </p>
+ *                <p>The <code>s3:PutInventoryConfiguration</code> permission allows a user to create an <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html">S3 Inventory</a>
+ *             report that includes all object metadata fields available and to specify the destination bucket to
+ *             store the inventory. A user with read access to objects in the destination bucket can also access
+ *             all object metadata fields that are available in the inventory report. </p>
  *                <p>To restrict access to an inventory report, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html#example-bucket-policies-use-case-10">Restricting access to an Amazon S3 Inventory report</a> in the
- *                      <i>Amazon S3 User Guide</i>. For more information about the metadata
- *                   fields available in S3 Inventory, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html#storage-inventory-contents">Amazon S3 Inventory lists</a> in the <i>Amazon S3 User Guide</i>. 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">Identity and access management in Amazon S3</a> in the
- *                      <i>Amazon S3 User Guide</i>.</p>
+ *               <i>Amazon S3 User Guide</i>. For more information about the metadata fields available
+ *             in S3 Inventory, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html#storage-inventory-contents">Amazon S3 Inventory
+ *               lists</a> in the <i>Amazon S3 User Guide</i>. 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">Identity and access management in
+ *               Amazon S3</a> in the <i>Amazon S3 User Guide</i>.</p>
  *             </dd>
  *          </dl>
  *          <p>
@@ -84,19 +81,18 @@ declare const PutBucketInventoryConfigurationCommand_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:PutInventoryConfiguration</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:PutInventoryConfiguration</code> bucket permission to set the configuration on the
+ *             bucket. </p>
  *             </dd>
  *          </dl>
- *          <p>The following operations are related to
- *          <code>PutBucketInventoryConfiguration</code>:</p>
+ *          <p>The following operations are related to <code>PutBucketInventoryConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>

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

@@ -28,73 +28,69 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
 };
 /**
  * <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>
+ *       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>
+ *             <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 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>
+ *                <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 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>
+ *                   <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>
  *                   </li>
  *                   <li>
- *                      <p>One or more lifecycle transition and expiration actions that you want
- *                         Amazon S3 to perform on the objects identified by the filter. If the state of
- *                         your bucket is versioning-enabled or versioning-suspended, you can have many
- *                         versions of the same object (one current version and zero or more noncurrent
- *                         versions). Amazon S3 provides predefined actions that you can specify for current
- *                         and noncurrent object versions.</p>
+ *                      <p>One or more lifecycle transition and expiration actions that you want Amazon S3 to perform on
+ *                 the objects identified by the filter. If the state of your bucket is versioning-enabled or
+ *                 versioning-suspended, you can have many versions of the same object (one current version and
+ *                 zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for
+ *                 current and noncurrent object versions.</p>
  *                   </li>
  *                </ul>
- *                <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html">Object Lifecycle
- *                      Management</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html">Lifecycle Configuration
- *                      Elements</a>.</p>
+ *                <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html">Object Lifecycle Management</a> and
+ *               <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html">Lifecycle
+ *               Configuration Elements</a>.</p>
  *             </dd>
  *             <dd>
  *                <ul>
  *                   <li>
  *                      <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>
+ *                         <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>
@@ -110,8 +106,8 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
  *                            <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>
+ *                            <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>
@@ -119,16 +115,13 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
  *                <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>
+ *                         <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>
@@ -142,11 +135,9 @@ declare const PutBucketLifecycleConfigurationCommand_base: {
  *             </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>
+ *                   <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>

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

@@ -27,36 +27,43 @@ declare const PutBucketLoggingCommand_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>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
- *          the source bucket. To set the logging status of a bucket, you must be the bucket
- *          owner.</p>
- *          <p>The bucket owner is automatically granted FULL_CONTROL to all logs. You use the
- *             <code>Grantee</code> request element to grant access to other people. The
- *             <code>Permissions</code> request element specifies the kind of access the grantee has to
- *          the logs.</p>
+ *          <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 the source bucket. To set
+ *       the logging status of a bucket, you must be the bucket owner.</p>
+ *          <p>The bucket owner is automatically granted FULL_CONTROL to all logs. You use the <code>Grantee</code>
+ *       request element to grant access to other people. The <code>Permissions</code> request element specifies
+ *       the kind of access the grantee has to the logs.</p>
  *          <important>
- *             <p>If the target bucket for log delivery uses the bucket owner enforced setting for S3
- *             Object Ownership, you can't use the <code>Grantee</code> request element to grant access
- *             to others. Permissions can only be granted using policies. For more information, see
- *                <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html#grant-log-delivery-permissions-general">Permissions for server access log delivery</a> in the
- *                <i>Amazon S3 User Guide</i>.</p>
+ *             <p>If the target bucket for log delivery uses the bucket owner enforced setting for S3 Object
+ *         Ownership, you can't use the <code>Grantee</code> request element to grant access to others.
+ *         Permissions can only be granted using policies. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html#grant-log-delivery-permissions-general">Permissions for server access log delivery</a> in the
+ *         <i>Amazon S3 User Guide</i>.</p>
  *          </important>
  *          <dl>
  *             <dt>Grantee Values</dt>
  *             <dd>
- *                <p>You can specify the person (grantee) to whom you're assigning access rights (by
- *                   using request elements) in the following ways:</p>
+ *                <p>You can specify the person (grantee) to whom you're assigning access rights (by 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>
  *                         <code>DisplayName</code> is optional and ignored in the request.</p>
@@ -65,33 +72,30 @@ declare const PutBucketLoggingCommand_base: {
  *                      <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 <code>CanonicalUser</code> and, in a
- *                         response to a <code>GETObjectAcl</code> request, appears as the
- *                         CanonicalUser.</p>
+ *                      <p>The grantee is resolved to the <code>CanonicalUser</code> and, in a response to a
+ *                   <code>GETObjectAcl</code> request, appears as the CanonicalUser.</p>
  *                   </li>
  *                   <li>
  *                      <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>
  *                </ul>
  *             </dd>
  *          </dl>
- *          <p>To enable logging, you use <code>LoggingEnabled</code> and its children request
- *          elements. To disable logging, you use an empty <code>BucketLoggingStatus</code> request
- *          element:</p>
+ *          <p>To enable logging, you use <code>LoggingEnabled</code> and its children request elements. To disable
+ *       logging, you use an empty <code>BucketLoggingStatus</code> request element:</p>
  *          <p>
- *             <code><BucketLoggingStatus xmlns="http://doc.s3.amazonaws.com/2006-03-01"
- *             /></code>
+ *             <code><BucketLoggingStatus xmlns="http://doc.s3.amazonaws.com/2006-03-01" /></code>
  *          </p>
  *          <p>For more information about server access logging, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerLogs.html">Server Access Logging</a> in the
- *             <i>Amazon S3 User Guide</i>. </p>
- *          <p>For more information about creating a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html">CreateBucket</a>. For more
- *          information about returning the logging status of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLogging.html">GetBucketLogging</a>.</p>
+ *         <i>Amazon S3 User Guide</i>. </p>
+ *          <p>For more information about creating a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html">CreateBucket</a>. For more information about
+ *       returning the logging status of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLogging.html">GetBucketLogging</a>.</p>
  *          <p>The following operations are related to <code>PutBucketLogging</code>:</p>
  *          <ul>
  *             <li>

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

@@ -30,19 +30,17 @@ declare const PutBucketMetricsConfigurationCommand_base: {
  * <note>
  *             <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
- *          metrics configuration, note that this is a full replacement of the existing metrics
- *          configuration. If you don't include the elements you want to keep, they are erased.</p>
+ *          <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 metrics
+ *       configuration, note that this is a full replacement of the existing metrics configuration. If you don't
+ *       include the elements you want to keep, they are erased.</p>
  *          <p>To use this operation, you must have permissions to perform the
- *             <code>s3:PutMetricsConfiguration</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>For information about CloudWatch request metrics for Amazon S3, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html">Monitoring
- *             Metrics with Amazon CloudWatch</a>.</p>
- *          <p>The following operations are related to
- *          <code>PutBucketMetricsConfiguration</code>:</p>
+ *         <code>s3:PutMetricsConfiguration</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>For information about CloudWatch request metrics for Amazon S3, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/cloudwatch-monitoring.html">Monitoring Metrics with Amazon
+ *       CloudWatch</a>.</p>
+ *          <p>The following operations are related to <code>PutBucketMetricsConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -68,8 +66,8 @@ declare const PutBucketMetricsConfigurationCommand_base: {
  *                </p>
  *                <ul>
  *                   <li>
- *                      <p>Description: You are attempting to create a new configuration but have
- *                      already reached the 1,000-configuration limit.</p>
+ *                      <p>Description: You are attempting to create a new configuration but have already reached the
+ *               1,000-configuration limit.</p>
  *                   </li>
  *                   <li>
  *                      <p>HTTP Status Code: HTTP 400 Bad Request</p>

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

@@ -31,50 +31,44 @@ declare const PutBucketNotificationConfigurationCommand_base: {
  *             <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
- *          Notifications</a>.</p>
- *          <p>Using this API, you can replace an existing notification configuration. The
- *          configuration is an XML file that defines the event types that you want Amazon S3 to publish and
- *          the destination where you want Amazon S3 to publish an event notification when it detects an
- *          event of the specified type.</p>
+ *       notifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Event Notifications</a>.</p>
+ *          <p>Using this API, you can replace an existing notification configuration. The configuration is an XML
+ *       file that defines the event types that you want Amazon S3 to publish and the destination where you want Amazon S3
+ *       to publish an event notification when it detects an event of the specified type.</p>
  *          <p>By default, your bucket has no event notifications configured. That is, the notification
- *          configuration will be an empty <code>NotificationConfiguration</code>.</p>
+ *       configuration will be an empty <code>NotificationConfiguration</code>.</p>
  *          <p>
  *             <code><NotificationConfiguration></code>
  *          </p>
  *          <p>
  *             <code></NotificationConfiguration></code>
  *          </p>
- *          <p>This action replaces the existing notification configuration with the configuration you
- *          include in the request body.</p>
- *          <p>After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification
- *          Service (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and
- *          that the bucket owner has permission to publish to it by sending a test notification. In
- *          the case of Lambda destinations, Amazon S3 verifies that the Lambda function permissions
- *          grant Amazon S3 permission to invoke the function from the Amazon S3 bucket. For more information,
- *          see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Notifications for Amazon S3 Events</a>.</p>
- *          <p>You can disable notifications by adding the empty NotificationConfiguration
- *          element.</p>
- *          <p>For more information about the number of event notification configurations that you can
- *          create per bucket, see <a href="https://docs.aws.amazon.com/general/latest/gr/s3.html#limits_s3">Amazon S3 service quotas</a> in <i>Amazon Web Services
- *             General Reference</i>.</p>
- *          <p>By default, only the bucket owner can configure notifications on a bucket. However,
- *          bucket owners can use a bucket policy to grant permission to other users to set this
- *          configuration with the required <code>s3:PutBucketNotification</code> permission.</p>
+ *          <p>This action replaces the existing notification configuration with the configuration you include in
+ *       the request body.</p>
+ *          <p>After Amazon S3 receives this request, it first verifies that any Amazon Simple Notification Service
+ *       (Amazon SNS) or Amazon Simple Queue Service (Amazon SQS) destination exists, and that the bucket owner
+ *       has permission to publish to it by sending a test notification. In the case of Lambda destinations,
+ *       Amazon S3 verifies that the Lambda function permissions grant Amazon S3 permission to invoke the function from the
+ *       Amazon S3 bucket. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html">Configuring Notifications for Amazon S3
+ *       Events</a>.</p>
+ *          <p>You can disable notifications by adding the empty NotificationConfiguration element.</p>
+ *          <p>For more information about the number of event notification configurations that you can create per
+ *       bucket, see <a href="https://docs.aws.amazon.com/general/latest/gr/s3.html#limits_s3">Amazon S3 service
+ *         quotas</a> in <i>Amazon Web Services General Reference</i>.</p>
+ *          <p>By default, only the bucket owner can configure notifications on a bucket. However, bucket owners
+ *       can use a bucket policy to grant permission to other users to set this configuration with the required
+ *         <code>s3:PutBucketNotification</code> permission.</p>
  *          <note>
- *             <p>The PUT notification is an atomic operation. For example, suppose your notification
- *             configuration includes SNS topic, SQS queue, and Lambda function configurations. When
- *             you send a PUT request with this configuration, Amazon S3 sends test messages to your SNS
- *             topic. If the message fails, the entire PUT action will fail, and Amazon S3 will not add the
- *             configuration to your bucket.</p>
+ *             <p>The PUT notification is an atomic operation. For example, suppose your notification configuration
+ *         includes SNS topic, SQS queue, and Lambda function configurations. When you send a PUT request with
+ *         this configuration, Amazon S3 sends test messages to your SNS topic. If the message fails, the entire PUT
+ *         action will fail, and Amazon S3 will not add the configuration to your bucket.</p>
  *          </note>
- *          <p>If the configuration in the request body includes only one
- *             <code>TopicConfiguration</code> specifying only the
- *             <code>s3:ReducedRedundancyLostObject</code> event type, the response will also include
- *          the <code>x-amz-sns-test-message-id</code> header containing the message ID of the test
- *          notification sent to the topic.</p>
- *          <p>The following action is related to
- *          <code>PutBucketNotificationConfiguration</code>:</p>
+ *          <p>If the configuration in the request body includes only one <code>TopicConfiguration</code>
+ *       specifying only the <code>s3:ReducedRedundancyLostObject</code> event type, the response will also
+ *       include the <code>x-amz-sns-test-message-id</code> header containing the message ID of the test
+ *       notification sent to the topic.</p>
+ *          <p>The following action is related to <code>PutBucketNotificationConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>

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

@@ -30,12 +30,10 @@ declare const PutBucketOwnershipControlsCommand_base: {
  * <note>
  *             <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
- *          more information about Amazon S3 permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-with-s3-actions.html">Specifying permissions in a
- *             policy</a>. </p>
- *          <p>For information about Amazon S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/about-object-ownership.html">Using object
- *             ownership</a>. </p>
+ *          <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 more information about Amazon S3
+ *       permissions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-with-s3-actions.html">Specifying permissions in a policy</a>. </p>
+ *          <p>For information about Amazon S3 Object Ownership, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/user-guide/about-object-ownership.html">Using object ownership</a>. </p>
  *          <p>The following operations are related to <code>PutBucketOwnershipControls</code>:</p>
  *          <ul>
  *             <li>
@@ -66,6 +64,7 @@ declare const PutBucketOwnershipControlsCommand_base: {
  *       },
  *     ],
  *   },
+ *   ChecksumAlgorithm: "CRC32" || "CRC32C" || "SHA1" || "SHA256" || "CRC64NVME",
  * };
  * const command = new PutBucketOwnershipControlsCommand(input);
  * const response = await client.send(command);