@aws-sdk/client-s3 3.844.0 → 3.845.0

package/dist-types/commands/ListObjectsV2Command.d.ts

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { ListObjectsV2Output, ListObjectsV2Request } from "../models/models_0";
+import { ListObjectsV2Output, ListObjectsV2Request } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -27,31 +27,30 @@ declare const ListObjectsV2Command_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Returns some or all (up to 1,000) of the objects in a bucket with each request. You can
- *          use the request parameters as selection criteria to return a subset of the objects in a
- *          bucket. A <code>200 OK</code> response can contain valid or invalid XML. Make sure to
- *          design your application to parse the contents of the response and handle it appropriately.
- *          For more information about listing objects, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ListingKeysUsingAPIs.html">Listing object keys
- *             programmatically</a> in the <i>Amazon S3 User Guide</i>. To get a list of
- *          your buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html">ListBuckets</a>.</p>
+ * <p>Returns some or all (up to 1,000) of the objects in a bucket with each request. You can use the
+ *       request parameters as selection criteria to return a subset of the objects in a bucket. A <code>200
+ *         OK</code> response can contain valid or invalid XML. Make sure to design your application to parse the
+ *       contents of the response and handle it appropriately. For more information about listing objects, see
+ *         <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ListingKeysUsingAPIs.html">Listing object
+ *         keys programmatically</a> in the <i>Amazon S3 User Guide</i>. To get a list of your
+ *       buckets, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListBuckets.html">ListBuckets</a>.</p>
  *          <note>
  *             <ul>
  *                <li>
  *                   <p>
  *                      <b>General purpose bucket</b> - For general purpose buckets,
- *                      <code>ListObjectsV2</code> doesn't return prefixes that are related only to
- *                   in-progress multipart uploads.</p>
+ *               <code>ListObjectsV2</code> doesn't return prefixes that are related only to in-progress
+ *             multipart uploads.</p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> - For
- *                   directory buckets, <code>ListObjectsV2</code> response includes the prefixes that
- *                   are related only to in-progress multipart uploads. </p>
+ *                      <b>Directory buckets</b> - For directory buckets,
+ *               <code>ListObjectsV2</code> response includes the prefixes that are related only to in-progress
+ *             multipart uploads. </p>
  *                </li>
  *                <li>
  *                   <p>
- *                      <b>Directory buckets</b> -
- *                   For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
+ *                      <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
  *                      </code>. Path-style requests are not supported. For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/endpoint-directory-buckets-AZ.html">Regional and Zonal endpoints for directory buckets in Availability Zones</a> in the
  *     <i>Amazon S3 User Guide</i>. For more information about endpoints in Local Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.html">Concepts for directory buckets in Local Zones</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
@@ -64,13 +63,12 @@ declare const ListObjectsV2Command_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket permissions</b> - To
- *                         use this operation, you must have READ access to the bucket. You must have
- *                         permission to perform the <code>s3:ListBucket</code> action. The bucket
- *                         owner has this permission by default and 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> in the
- *                            <i>Amazon S3 User Guide</i>.</p>
+ *                         <b>General purpose bucket permissions</b> - To use this
+ *                 operation, you must have READ access to the bucket. You must have permission to perform the
+ *                   <code>s3:ListBucket</code> action. The bucket owner has this permission by default and 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> in the
+ *                 <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -88,15 +86,14 @@ declare const ListObjectsV2Command_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - For
- *                         general purpose buckets, <code>ListObjectsV2</code> returns objects in
- *                         lexicographical order based on their key names.</p>
+ *                         <b>General purpose bucket</b> - For general purpose buckets,
+ *                   <code>ListObjectsV2</code> returns objects in lexicographical order based on their key
+ *                 names.</p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory bucket</b> - For
- *                         directory buckets, <code>ListObjectsV2</code> does not return objects in
- *                         lexicographical order.</p>
+ *                         <b>Directory bucket</b> - For directory buckets,
+ *                   <code>ListObjectsV2</code> does not return objects in lexicographical order.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -108,9 +105,9 @@ declare const ListObjectsV2Command_base: {
  *             </dd>
  *          </dl>
  *          <important>
- *             <p>This section describes the latest revision of this action. We recommend that you use
- *             this revised API operation for application development. For backward compatibility, Amazon S3
- *             continues to support the prior version of this API operation, <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html">ListObjects</a>.</p>
+ *             <p>This section describes the latest revision of this action. We recommend that you use this revised
+ *         API operation for application development. For backward compatibility, Amazon S3 continues to support the
+ *         prior version of this API operation, <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html">ListObjects</a>.</p>
  *          </important>
  *          <p>The following operations are related to <code>ListObjectsV2</code>:</p>
  *          <ul>

package/dist-types/commands/ListPartsCommand.d.ts

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { ListPartsOutput, ListPartsRequest } from "../models/models_0";
+import { ListPartsOutput, ListPartsRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -35,22 +35,21 @@ declare const ListPartsCommand_base: {
  *  Asia Pacific (Tokyo) Region, Europe (Ireland) Region, and South America (São Paulo) Region.</p>
  *          </important>
  *          <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>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>
+ *          <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>
  *          <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>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/endpoint-directory-buckets-AZ.html">Regional and Zonal endpoints for directory buckets in Availability Zones</a> in the
  *     <i>Amazon S3 User Guide</i>. For more information about endpoints in Local Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.html">Concepts for directory buckets in Local Zones</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
@@ -61,15 +60,13 @@ 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>

package/dist-types/commands/PutBucketAccelerateConfigurationCommand.d.ts

@@ -1,6 +1,6 @@
 import { Command as $Command } from "@smithy/smithy-client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
-import { PutBucketAccelerateConfigurationRequest } from "../models/models_0";
+import { PutBucketAccelerateConfigurationRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
 /**
  * @public
@@ -31,14 +31,12 @@ declare const PutBucketAccelerateConfigurationCommand_base: {
  *             <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>
+ *       bucket-level feature that enables you to perform faster data transfers to Amazon S3.</p>
  *          <p> To use this operation, you must have permission to perform the
- *             <code>s3:PutAccelerateConfiguration</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> The Transfer Acceleration state of a bucket can be set to one of the following two
- *          values:</p>
+ *         <code>s3:PutAccelerateConfiguration</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> The Transfer Acceleration state of a bucket can be set to one of the following two values:</p>
  *          <ul>
  *             <li>
  *                <p> Enabled – Enables accelerated data transfers to the bucket.</p>
@@ -47,16 +45,14 @@ declare const PutBucketAccelerateConfigurationCommand_base: {
  *                <p> Suspended – Disables accelerated data transfers to the bucket.</p>
  *             </li>
  *          </ul>
- *          <p>The <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAccelerateConfiguration.html">GetBucketAccelerateConfiguration</a> action returns the transfer acceleration state
- *          of a bucket.</p>
- *          <p>After setting the Transfer Acceleration state of a bucket to Enabled, it might take up
- *          to thirty minutes before the data transfer rates to the bucket increase.</p>
- *          <p> The name of the bucket used for Transfer Acceleration must be DNS-compliant and must
- *          not contain periods (".").</p>
- *          <p> For more information about transfer acceleration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer
- *          Acceleration</a>.</p>
- *          <p>The following operations are related to
- *          <code>PutBucketAccelerateConfiguration</code>:</p>
+ *          <p>The <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketAccelerateConfiguration.html">GetBucketAccelerateConfiguration</a> action returns the transfer acceleration state of a
+ *       bucket.</p>
+ *          <p>After setting the Transfer Acceleration state of a bucket to Enabled, it might take up to thirty
+ *       minutes before the data transfer rates to the bucket increase.</p>
+ *          <p> The name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain
+ *       periods (".").</p>
+ *          <p> For more information about transfer acceleration, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer Acceleration</a>.</p>
+ *          <p>The following operations are related to <code>PutBucketAccelerateConfiguration</code>:</p>
  *          <ul>
  *             <li>
  *                <p>

package/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
@@ -38,9 +38,9 @@ declare const PutBucketAclCommand_base: {
  *          <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>
@@ -51,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>
@@ -72,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>
@@ -141,34 +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. 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>
+ *                <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>
@@ -176,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/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/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>