@aws-sdk/client-s3 3.325.0 → 3.327.0

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

@@ -23,135 +23,145 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *          valid Amazon Web Services Access Key ID to authenticate requests. Anonymous requests are never allowed to
  *          create buckets. By creating the bucket, you become the bucket owner.</p>
  *          <p>Not every string is an acceptable bucket name. For information about bucket naming
- *          restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming rules</a>.</p>
+ *          restrictions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html">Bucket naming
+ *          rules</a>.</p>
  *          <p>If you want to create an Amazon S3 on Outposts bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_control_CreateBucket.html">Create Bucket</a>. </p>
  *          <p>By default, the bucket is created in the US East (N. Virginia) Region. You can
  *          optionally specify a Region in the request body. You might choose a Region to optimize
  *          latency, minimize costs, or address regulatory requirements. For example, if you reside in
  *          Europe, you will probably find it advantageous to create buckets in the Europe (Ireland)
  *          Region. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro">Accessing a
- *          bucket</a>.</p>
+ *             bucket</a>.</p>
  *          <note>
  *             <p>If you send your create bucket request to the <code>s3.amazonaws.com</code> endpoint,
  *             the request goes to the us-east-1 Region. Accordingly, the signature calculations in
  *             Signature Version 4 must use us-east-1 as the Region, even if the location constraint in
  *             the request specifies another Region where the bucket is to be created. If you create a
  *             bucket in a Region other than US East (N. Virginia), your application must be able to
- *             handle 307 redirect. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html">Virtual hosting of buckets</a>.</p>
+ *             handle 307 redirect. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html">Virtual hosting of
+ *             buckets</a>.</p>
  *          </note>
- *          <p>
- *             <b>Access control lists (ACLs)</b>
- *          </p>
- *          <p>When creating a bucket using this operation, you can optionally configure the bucket ACL to specify the accounts or
- *          groups that should be granted specific permissions on the bucket.</p>
- *          <important>
- *             <p>If your CreateBucket request sets bucket owner enforced for S3 Object Ownership and
- *             specifies a bucket ACL that provides access to an external Amazon Web Services account, your request
- *             fails with a <code>400</code> error and returns the
- *                <code>InvalidBucketAclWithObjectOwnership</code> error code. 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>
- *          <p>There are two ways to grant the appropriate permissions using the request headers.</p>
- *          <ul>
- *             <li>
- *                <p>Specify a canned ACL using 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. 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 using the <code>x-amz-grant-read</code>,
- *                   <code>x-amz-grant-write</code>, <code>x-amz-grant-read-acp</code>,
- *                   <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code>
- *                headers. These headers map to the set of permissions Amazon S3 supports in an ACL. For
- *                more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/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>
+ *          <dl>
+ *             <dt>Access control lists (ACLs)</dt>
+ *             <dd>
+ *                <p>When creating a bucket using this operation, you can optionally configure the bucket ACL
+ *                   to specify the accounts or groups that should be granted specific permissions on the
+ *                   bucket.</p>
+ *                <important>
+ *                   <p>If your CreateBucket request sets bucket owner enforced for S3 Object Ownership and
+ *                      specifies a bucket ACL that provides access to an external Amazon Web Services account, your request
+ *                      fails with a <code>400</code> error and returns the
+ *                      <code>InvalidBucketAclWithObjectOwnership</code> error code. 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>
+ *                <p>There are two ways to grant the appropriate permissions using the request
+ *                   headers.</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>Specify a canned ACL using 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. 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 using the <code>x-amz-grant-read</code>,
+ *                         <code>x-amz-grant-write</code>, <code>x-amz-grant-read-acp</code>,
+ *                         <code>x-amz-grant-write-acp</code>, and <code>x-amz-grant-full-control</code>
+ *                         headers. These headers map to the set of permissions Amazon S3 supports in an ACL. For
+ *                         more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/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>
+ *                         </li>
+ *                         <li>
+ *                            <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>
+ *                            <note>
+ *                               <p>Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions: </p>
+ *                               <ul>
+ *                                  <li>
+ *                                     <p>US East (N. Virginia)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p>US West (N. California)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p> US West (Oregon)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p> Asia Pacific (Singapore)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p>Asia Pacific (Sydney)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p>Asia Pacific (Tokyo)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p>Europe (Ireland)</p>
+ *                                  </li>
+ *                                  <li>
+ *                                     <p>South America (São Paulo)</p>
+ *                                  </li>
+ *                               </ul>
+ *                               <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href="https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>
+ *                            </note>
+ *                         </li>
+ *                      </ul>
+ *                      <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>
+ *                      <p>
+ *                         <code>x-amz-grant-read: id="11112222333", id="444455556666" </code>
+ *                      </p>
+ *                   </li>
+ *                </ul>
+ *                <note>
+ *                   <p>You can use either a canned ACL or specify access permissions explicitly. You cannot
+ *                      do both.</p>
+ *                </note>
+ *             </dd>
+ *             <dt>Permissions</dt>
+ *             <dd>
+ *                <p>In addition to <code>s3:CreateBucket</code>, the following permissions are required when
+ *                   your CreateBucket includes specific headers:</p>
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <code>id</code> – if the value specified is the canonical user ID of an Amazon Web Services account</p>
+ *                         <b>ACLs</b> - If your <code>CreateBucket</code> request
+ *                         specifies ACL permissions and the ACL is public-read, public-read-write,
+ *                         authenticated-read, or if you specify access permissions explicitly through any other
+ *                         ACL, both <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code> permissions
+ *                         are needed. If the ACL the <code>CreateBucket</code> request is private or doesn't
+ *                         specify any ACLs, only <code>s3:CreateBucket</code> permission is needed. </p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <code>uri</code> – if you are granting permissions to a predefined
- *                      group</p>
+ *                         <b>Object Lock</b> - If
+ *                         <code>ObjectLockEnabledForBucket</code> is set to true in your
+ *                         <code>CreateBucket</code> request,
+ *                         <code>s3:PutBucketObjectLockConfiguration</code> and
+ *                         <code>s3:PutBucketVersioning</code> permissions are required.</p>
  *                   </li>
  *                   <li>
  *                      <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>
- *                            <li>
- *                               <p>US East (N. Virginia)</p>
- *                            </li>
- *                            <li>
- *                               <p>US West (N. California)</p>
- *                            </li>
- *                            <li>
- *                               <p> US West (Oregon)</p>
- *                            </li>
- *                            <li>
- *                               <p> Asia Pacific (Singapore)</p>
- *                            </li>
- *                            <li>
- *                               <p>Asia Pacific (Sydney)</p>
- *                            </li>
- *                            <li>
- *                               <p>Asia Pacific (Tokyo)</p>
- *                            </li>
- *                            <li>
- *                               <p>Europe (Ireland)</p>
- *                            </li>
- *                            <li>
- *                               <p>South America (São Paulo)</p>
- *                            </li>
- *                         </ul>
- *                         <p>For a list of all the Amazon S3 supported Regions and endpoints, see <a href="https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region">Regions and Endpoints</a> in the Amazon Web Services General Reference.</p>
- *                      </note>
+ *                         <b>S3 Object Ownership</b> - If your CreateBucket
+ *                         request includes the <code>x-amz-object-ownership</code> header,
+ *                         <code>s3:PutBucketOwnershipControls</code> permission is required.</p>
  *                   </li>
  *                </ul>
- *                <p>For example, the following <code>x-amz-grant-read</code> header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:</p>
- *                <p>
- *                   <code>x-amz-grant-read: id="11112222333", id="444455556666" </code>
- *                </p>
- *             </li>
- *          </ul>
- *          <note>
- *             <p>You can use either a canned ACL or specify access permissions explicitly. You cannot
- *             do both.</p>
- *          </note>
- *          <p>
- *             <b>Permissions</b>
- *          </p>
- *          <p>In addition to <code>s3:CreateBucket</code>, the following permissions are required when your CreateBucket includes specific headers:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <b>ACLs</b> - If your <code>CreateBucket</code> request specifies ACL permissions and the ACL is public-read, public-read-write,
- *                authenticated-read, or if you specify access permissions explicitly through any other ACL, both
- *                <code>s3:CreateBucket</code> and <code>s3:PutBucketAcl</code> permissions are needed. If the ACL the
- *                <code>CreateBucket</code> request is private or doesn't specify any ACLs, only <code>s3:CreateBucket</code> permission is needed. </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <b>Object Lock</b> - If
- *                   <code>ObjectLockEnabledForBucket</code> is set to true in your
- *                   <code>CreateBucket</code> request,
- *                   <code>s3:PutBucketObjectLockConfiguration</code> and
- *                   <code>s3:PutBucketVersioning</code> permissions are required.</p>
- *             </li>
- *             <li>
- *                <p>
- *                   <b>S3 Object Ownership</b> - If your CreateBucket
- *                request includes the the <code>x-amz-object-ownership</code> header,
- *                   <code>s3:PutBucketOwnershipControls</code> permission is required.</p>
- *             </li>
- *          </ul>
+ *             </dd>
+ *          </dl>
  *          <p>The following operations are related to <code>CreateBucket</code>:</p>
  *          <ul>
  *             <li>
@@ -187,6 +197,10 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  * };
  * const command = new CreateBucketCommand(input);
  * const response = await client.send(command);
+ * // { // CreateBucketOutput
+ * //   Location: "STRING_VALUE",
+ * // };
+ *
  * ```
  *
  * @param CreateBucketCommandInput - {@link CreateBucketCommandInput}
@@ -205,40 +219,42 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *          re-create an existing bucket that you already own in the North Virginia Region, Amazon S3
  *          returns 200 OK and resets the bucket access control lists (ACLs).</p>
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
- * @example To create a bucket in a specific region
+ * @example To create a bucket
  * ```javascript
- * // The following example creates a bucket. The request specifies an AWS region where to create the bucket.
+ * // The following example creates a bucket.
  * const input = {
- *   "Bucket": "examplebucket",
- *   "CreateBucketConfiguration": {
- *     "LocationConstraint": "eu-west-1"
- *   }
+ *   "Bucket": "examplebucket"
  * };
  * const command = new CreateBucketCommand(input);
  * const response = await client.send(command);
  * /* response ==
  * {
- *   "Location": "http://examplebucket.<Region>.s3.amazonaws.com/"
+ *   "Location": "/examplebucket"
  * }
  * *\/
- * // example id: to-create-a-bucket-in-a-specific-region-1483399072992
+ * // example id: to-create-a-bucket--1472851826060
  * ```
  *
- * @example To create a bucket
+ * @example To create a bucket in a specific region
  * ```javascript
- * // The following example creates a bucket.
+ * // The following example creates a bucket. The request specifies an AWS region where to create the bucket.
  * const input = {
- *   "Bucket": "examplebucket"
+ *   "Bucket": "examplebucket",
+ *   "CreateBucketConfiguration": {
+ *     "LocationConstraint": "eu-west-1"
+ *   }
  * };
  * const command = new CreateBucketCommand(input);
  * const response = await client.send(command);
  * /* response ==
  * {
- *   "Location": "/examplebucket"
+ *   "Location": "http://examplebucket.<Region>.s3.amazonaws.com/"
  * }
  * *\/
- * // example id: to-create-a-bucket--1472851826060
+ * // example id: to-create-a-bucket-in-a-specific-region-1483399072992
  * ```
  *
  */

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

@@ -28,39 +28,55 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *          <p>If you have configured a lifecycle rule to abort incomplete multipart uploads, the
  *          upload must complete within the number of days specified in the bucket lifecycle
  *          configuration. Otherwise, the incomplete multipart upload becomes eligible for an abort
- *          action and Amazon S3 aborts the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">Aborting
- *             Incomplete Multipart Uploads Using a Bucket Lifecycle Policy</a>.</p>
+ *          action and Amazon S3 aborts the multipart upload. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html#mpu-abort-incomplete-mpu-lifecycle-config">Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration</a>.</p>
  *          <p>For information about the 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>.</p>
+ *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart
+ *             Upload and Permissions</a>.</p>
  *          <p>For request signing, multipart upload is just a series of regular requests. You initiate
  *          a multipart upload, send one or more requests to upload parts, and then complete the
  *          multipart upload process. You sign each request individually. There is nothing special
- *          about signing multipart upload requests. For more information about signing, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html">Authenticating
- *             Requests (Amazon Web Services Signature Version 4)</a>.</p>
+ *          about signing multipart upload requests. For more information about signing, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html">Authenticating Requests (Amazon Web Services Signature Version 4)</a>.</p>
  *          <note>
- *             <p> After you initiate a multipart upload and upload one or more parts, to stop being
+ *             <p>After you initiate a multipart upload and upload one or more parts, to stop being
  *             charged for storing the uploaded parts, you must either complete or abort the multipart
  *             upload. Amazon S3 frees up the space used to store the parts and stop charging you for
  *             storing them only after you either complete or abort a multipart upload. </p>
  *          </note>
- *          <p>You can optionally request server-side encryption. For server-side encryption, Amazon S3
- *          encrypts your data as it writes it to disks in its data centers and decrypts it when you
- *          access it. You can provide your own encryption key, or use Amazon Web Services KMS keys or Amazon S3-managed encryption keys. If you choose to provide
- *          your own encryption key, the request headers you provide in <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> requests must match the headers you used in the request to
- *          initiate the upload by using <code>CreateMultipartUpload</code>. </p>
- *          <p>To perform a multipart upload with encryption using an Amazon Web Services KMS key, the requester must
- *          have permission to the <code>kms:Decrypt</code> and <code>kms:GenerateDataKey*</code>
+ *          <p>Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it
+ *          writes it to disks in its data centers and decrypts it when you access it. Amazon S3
+ *          automatically encrypts all new objects that are uploaded to an S3 bucket. When doing a
+ *          multipart upload, if you don't specify encryption information in your request, the
+ *          encryption setting of the uploaded parts is set to the default encryption configuration of
+ *          the destination bucket. By default, all buckets have a base level of encryption
+ *          configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the
+ *          destination bucket has a default encryption configuration that uses server-side encryption
+ *          with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided encryption key (SSE-C),
+ *          Amazon S3 uses the corresponding KMS key, or a customer-provided key to encrypt the uploaded
+ *          parts. When you perform a CreateMultipartUpload operation, if you want to use a different
+ *          type of encryption setting for the uploaded parts, you can request that Amazon S3 encrypts the
+ *          object with a KMS key, an Amazon S3 managed key, or a customer-provided key. If the encryption
+ *          setting in your request is different from the default encryption configuration of the
+ *          destination bucket, the encryption setting in your request takes precedence. If you choose
+ *          to provide your own encryption key, the request headers you provide in <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>
+ *          and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> requests must match the headers you used in the request to
+ *          initiate the upload by using <code>CreateMultipartUpload</code>. You can request that Amazon S3
+ *          save the uploaded parts encrypted with server-side encryption with an Amazon S3 managed key
+ *          (SSE-S3), an Key Management Service (KMS) key (SSE-KMS), or a customer-provided encryption key
+ *          (SSE-C). </p>
+ *          <p>To perform a multipart upload with encryption by using an Amazon Web Services KMS key, the requester
+ *          must have permission to the <code>kms:Decrypt</code> and <code>kms:GenerateDataKey*</code>
  *          actions on the key. These permissions are required because Amazon S3 must decrypt and read data
  *          from the encrypted file parts before it completes the multipart upload. For more
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html#mpuAndPermissions">Multipart upload API
- *             and permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
- *          <p>If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account
- *          as the KMS key, then you must have these permissions on the key policy. If your IAM
- *          user or role belongs to a different account than the key, then you must have the
- *          permissions on both the key policy and your IAM user or role.</p>
- *          <p> For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Protecting
- *             Data Using Server-Side Encryption</a>.</p>
+ *             and permissions</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting data using
+ *             server-side encryption with Amazon Web Services KMS</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
+ *          <p>If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account as the KMS key,
+ *          then you must have these permissions on the key policy. If your IAM user or role belongs
+ *          to a different account than the key, then you must have the permissions on both the key
+ *          policy and your IAM user or role.</p>
+ *          <p> For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Protecting Data Using Server-Side
+ *             Encryption</a>.</p>
  *          <dl>
  *             <dt>Access Permissions</dt>
  *             <dd>
@@ -70,7 +86,8 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                <ul>
  *                   <li>
  *                      <p>Specify a canned ACL with the <code>x-amz-acl</code> request header. For
- *                         more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#CannedACL">Canned ACL</a>.</p>
+ *                         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
@@ -78,8 +95,7 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                            <code>x-amz-grant-write-acp</code>, and
  *                            <code>x-amz-grant-full-control</code> headers. 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>
+ *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL) Overview</a>.</p>
  *                   </li>
  *                </ul>
  *                <p>You can use either a canned ACL or specify access permissions explicitly. You
@@ -87,16 +103,19 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *             </dd>
  *             <dt>Server-Side- Encryption-Specific Request Headers</dt>
  *             <dd>
- *                <p>You can optionally tell Amazon S3 to encrypt data at rest using server-side
- *                   encryption. Server-side encryption is for data encryption at rest. Amazon S3 encrypts
+ *                <p>Amazon S3 encrypts data
+ *                   by using server-side encryption with an Amazon S3 managed key (SSE-S3) by default. Server-side encryption is for data encryption at rest. Amazon S3 encrypts
  *                   your data as it writes it to disks in its data centers and decrypts it when you
- *                   access it. The option you use depends on whether you want to use Amazon Web Services managed
- *                   encryption keys or provide your own encryption key. </p>
+ *                   access it. You can request that Amazon S3 encrypts
+ *                   data at rest by using server-side encryption with other key options. The option you use depends on
+ *                   whether you want to use KMS keys (SSE-KMS) or provide your own encryption keys
+ *                   (SSE-C).</p>
  *                <ul>
  *                   <li>
- *                      <p>Use encryption keys managed by Amazon S3 or customer managed key stored
- *                         in Amazon Web Services Key Management Service (Amazon Web Services KMS) – If you want Amazon Web Services to manage the keys
- *                         used to encrypt data, specify the following headers in the request.</p>
+ *                      <p>Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key
+ *                         (<code>aws/s3</code>) and KMS customer managed keys stored in Key Management Service (KMS) – If you
+ *                         want Amazon Web Services to manage the keys used to encrypt data, specify the following
+ *                         headers in the request.</p>
  *                      <ul>
  *                         <li>
  *                            <p>
@@ -117,18 +136,22 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                      <note>
  *                         <p>If you specify <code>x-amz-server-side-encryption:aws:kms</code>, but
  *                            don't provide <code>x-amz-server-side-encryption-aws-kms-key-id</code>,
- *                            Amazon S3 uses the Amazon Web Services managed key in Amazon Web Services KMS to protect the data.</p>
+ *                            Amazon S3 uses the Amazon Web Services managed key (<code>aws/s3</code> key) in KMS to
+ *                            protect the data.</p>
  *                      </note>
  *                      <important>
- *                         <p>All GET and PUT requests for an object protected by Amazon Web Services KMS fail if
- *                            you don't make them with SSL or by using SigV4.</p>
+ *                         <p>All <code>GET</code> and <code>PUT</code> requests for an object protected
+ *                            by KMS fail if you don't make them by using Secure Sockets Layer (SSL),
+ *                            Transport Layer Security (TLS), or Signature Version 4.</p>
  *                      </important>
- *                      <p>For more information about server-side encryption with KMS key (SSE-KMS),
- *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html">Protecting Data Using Server-Side Encryption with KMS keys</a>.</p>
+ *                      <p>For more information about server-side encryption with KMS keys
+ *                         (SSE-KMS), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingKMSEncryption.html">Protecting Data
+ *                            Using Server-Side Encryption with KMS keys</a>.</p>
  *                   </li>
  *                   <li>
- *                      <p>Use customer-provided encryption keys – If you want to manage your own
- *                         encryption keys, provide all the following headers in the request.</p>
+ *                      <p>Use customer-provided encryption keys (SSE-C) – If you want to manage
+ *                         your own encryption keys, provide all the following headers in the
+ *                         request.</p>
  *                      <ul>
  *                         <li>
  *                            <p>
@@ -146,8 +169,10 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                            </p>
  *                         </li>
  *                      </ul>
- *                      <p>For more information about server-side encryption with KMS keys (SSE-KMS),
- *                         see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html">Protecting Data Using Server-Side Encryption with KMS keys</a>.</p>
+ *                      <p>For more information about server-side encryption with customer-provided
+ *                         encryption keys (SSE-C), see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/ServerSideEncryptionCustomerKeys.html">
+ *                            Protecting data using server-side encryption with customer-provided
+ *                            encryption keys (SSE-C)</a>.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -155,10 +180,11 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *             <dd>
  *                <p>You also can use the following access control–related headers with this
  *                   operation. By default, all objects are private. Only the owner has full access
- *                   control. When adding a new object, you can grant permissions to individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then added
- *                   to the access control list (ACL) on the object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. With this
- *                   operation, you can grant access permissions using one of the following two
- *                   methods:</p>
+ *                   control. When adding a new object, you can grant permissions to individual
+ *                   Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then
+ *                   added to the access control list (ACL) on the object. For more information, see
+ *                      <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. With this operation, you can grant access permissions
+ *                   using one of the following two methods:</p>
  *                <ul>
  *                   <li>
  *                      <p>Specify a canned ACL (<code>x-amz-acl</code>) — Amazon S3 supports a set of
@@ -171,10 +197,9 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  *                      <p>Specify access permissions explicitly — To explicitly grant access
  *                         permissions to specific Amazon Web Services accounts or groups, use the following headers.
  *                         Each header maps to specific 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>. In the header, you specify a list of
- *                         grantees who get the specific permission. To grant permissions explicitly,
- *                         use:</p>
+ *                         more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL)
+ *                            Overview</a>. In the header, you specify a list of grantees who get
+ *                         the specific permission. To grant permissions explicitly, use:</p>
  *                      <ul>
  *                         <li>
  *                            <p>
@@ -329,6 +354,22 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  * };
  * const command = new CreateMultipartUploadCommand(input);
  * const response = await client.send(command);
+ * // { // CreateMultipartUploadOutput
+ * //   AbortDate: new Date("TIMESTAMP"),
+ * //   AbortRuleId: "STRING_VALUE",
+ * //   Bucket: "STRING_VALUE",
+ * //   Key: "STRING_VALUE",
+ * //   UploadId: "STRING_VALUE",
+ * //   ServerSideEncryption: "AES256" || "aws:kms",
+ * //   SSECustomerAlgorithm: "STRING_VALUE",
+ * //   SSECustomerKeyMD5: "STRING_VALUE",
+ * //   SSEKMSKeyId: "STRING_VALUE",
+ * //   SSEKMSEncryptionContext: "STRING_VALUE",
+ * //   BucketKeyEnabled: true || false,
+ * //   RequestCharged: "requester",
+ * //   ChecksumAlgorithm: "CRC32" || "CRC32C" || "SHA1" || "SHA256",
+ * // };
+ *
  * ```
  *
  * @param CreateMultipartUploadCommandInput - {@link CreateMultipartUploadCommandInput}
@@ -337,6 +378,8 @@ export interface CreateMultipartUploadCommandOutput extends CreateMultipartUploa
  * @see {@link CreateMultipartUploadCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  * @example To initiate a multipart upload
  * ```javascript

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

@@ -24,8 +24,8 @@ export interface DeleteBucketAnalyticsConfigurationCommandOutput extends __Metad
  *          <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>
+ *          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 the Amazon S3 analytics feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/analytics-storage-class.html">Amazon S3 Analytics – Storage Class
  *             Analysis</a>. </p>
  *          <p>The following operations are related to
@@ -60,6 +60,8 @@ export interface DeleteBucketAnalyticsConfigurationCommandOutput extends __Metad
  * };
  * const command = new DeleteBucketAnalyticsConfigurationCommand(input);
  * const response = await client.send(command);
+ * // {};
+ *
  * ```
  *
  * @param DeleteBucketAnalyticsConfigurationCommandInput - {@link DeleteBucketAnalyticsConfigurationCommandInput}
@@ -68,6 +70,8 @@ export interface DeleteBucketAnalyticsConfigurationCommandOutput extends __Metad
  * @see {@link DeleteBucketAnalyticsConfigurationCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  */
 export declare class DeleteBucketAnalyticsConfigurationCommand extends $Command<DeleteBucketAnalyticsConfigurationCommandInput, DeleteBucketAnalyticsConfigurationCommandOutput, S3ClientResolvedConfig> {

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

@@ -21,9 +21,7 @@ export interface DeleteBucketCommandOutput extends __MetadataBearer {
  * @public
  * <p>Deletes the S3 bucket. All objects (including all object versions and delete markers) in
  *          the bucket must be deleted before the bucket itself can be deleted.</p>
- *          <p class="title">
- *             <b>Related Resources</b>
- *          </p>
+ *          <p>The following operations are related to <code>DeleteBucket</code>:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -48,6 +46,8 @@ export interface DeleteBucketCommandOutput extends __MetadataBearer {
  * };
  * const command = new DeleteBucketCommand(input);
  * const response = await client.send(command);
+ * // {};
+ *
  * ```
  *
  * @param DeleteBucketCommandInput - {@link DeleteBucketCommandInput}
@@ -56,6 +56,8 @@ export interface DeleteBucketCommandOutput extends __MetadataBearer {
  * @see {@link DeleteBucketCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  * @example To delete a bucket
  * ```javascript