npm - @aws-sdk/client-s3 - Versions diffs - 3.301.0 → 3.304.0 - Mend

@aws-sdk/client-s3 3.301.0 → 3.304.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (94) hide show

package/dist-types/commands/AbortMultipartUploadCommand.d.ts CHANGED Viewed

@@ -28,8 +28,8 @@ export interface AbortMultipartUploadCommandOutput extends AbortMultipartUploadO
  *          <p>To verify that all parts have been removed, so you don't get charged for the part
  *          storage, you should call the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html">ListParts</a> action and ensure that
  *          the parts list is empty.</p>
- *          <p>For information about permissions required to use the multipart upload, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
- *          Permissions</a>.</p>
+ *          <p>For information about permissions required to use the multipart upload, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload
+ *             and Permissions</a>.</p>
  *          <p>The following operations are related to <code>AbortMultipartUpload</code>:</p>
  *          <ul>
  *             <li>

package/dist-types/commands/CompleteMultipartUploadCommand.d.ts CHANGED Viewed

@@ -22,28 +22,36 @@ export interface CompleteMultipartUploadCommandOutput extends CompleteMultipartU
  * <p>Completes a multipart upload by assembling previously uploaded parts.</p>
  *          <p>You first initiate the multipart upload and then upload all parts using the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>
  *          operation. After successfully uploading all relevant parts of an upload, you call this
- *          action to complete the upload. Upon receiving this request, Amazon S3 concatenates all
- *          the parts in ascending order by part number to create a new object. In the Complete
- *          Multipart Upload request, you must provide the parts list. You must ensure that the parts
- *          list is complete. This action concatenates the parts that you provide in the list. For
- *          each part in the list, you must provide the part number and the <code>ETag</code> value,
- *          returned after that part was uploaded.</p>
+ *          action to complete the upload. Upon receiving this request, Amazon S3 concatenates all the
+ *          parts in ascending order by part number to create a new object. In the Complete Multipart
+ *          Upload request, you must provide the parts list. You must ensure that the parts list is
+ *          complete. This action concatenates the parts that you provide in the list. For each part in
+ *          the list, you must provide the part number and the <code>ETag</code> value, returned after
+ *          that part was uploaded.</p>
  *          <p>Processing of a Complete Multipart Upload request could take several minutes to
  *          complete. After Amazon S3 begins processing the request, it sends an HTTP response header that
  *          specifies a 200 OK response. While processing is in progress, Amazon S3 periodically sends white
- *          space characters to keep the connection from timing out. Because a request could fail after
- *          the initial 200 OK response has been sent, it is important that you check the response body
- *          to determine whether the request succeeded.</p>
+ *          space characters to keep the connection from timing out. A request could fail after the
+ *          initial 200 OK response has been sent. This means that a <code>200 OK</code> response can
+ *          contain either a success or an error. If you call the S3 API directly, make sure to design
+ *          your application to parse the contents of the response and handle it appropriately. If you
+ *          use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the embedded error and apply
+ *          error handling per your configuration settings (including automatically retrying the
+ *          request as appropriate). If the condition persists, the SDKs throws an exception (or, for
+ *          the SDKs that don't use exceptions, they return the error). </p>
  *          <p>Note that if <code>CompleteMultipartUpload</code> fails, applications should be prepared
- *          to retry the failed requests. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html">Amazon S3 Error Best Practices</a>.</p>
+ *          to retry the failed requests. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ErrorBestPractices.html">Amazon S3 Error Best
+ *          Practices</a>.</p>
  *          <important>
- *             <p>You cannot use <code>Content-Type: application/x-www-form-urlencoded</code> with Complete
- *             Multipart Upload requests. Also, if you do not provide a <code>Content-Type</code> header, <code>CompleteMultipartUpload</code> returns a 200 OK response.</p>
+ *             <p>You cannot use <code>Content-Type: application/x-www-form-urlencoded</code> with
+ *             Complete Multipart Upload requests. Also, if you do not provide a
+ *                <code>Content-Type</code> header, <code>CompleteMultipartUpload</code> returns a 200
+ *             OK response.</p>
  *          </important>
  *          <p>For more information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading Objects Using Multipart
  *             Upload</a>.</p>
- *          <p>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>.</p>
+ *          <p>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>.</p>
  *          <p>
  *             <code>CompleteMultipartUpload</code> has the following special errors:</p>
  *          <ul>

package/dist-types/commands/CopyObjectCommand.d.ts CHANGED Viewed

@@ -29,15 +29,20 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *          </note>
  *          <p>All copy requests must be authenticated. Additionally, you must have
  *             <i>read</i> access to the source object and <i>write</i>
- *          access to the destination bucket. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>. Both the Region
- *          that you want to copy the object from and the Region that you want to copy the object to
- *          must be enabled for your account.</p>
+ *          access to the destination bucket. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>. Both the
+ *          Region that you want to copy the object from and the Region that you want to copy the
+ *          object to must be enabled for your account.</p>
  *          <p>A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3
  *          is copying the files. If the error occurs before the copy action starts, you receive a
  *          standard Amazon S3 error. If the error occurs during the copy operation, the error response is
  *          embedded in the <code>200 OK</code> response. This means that a <code>200 OK</code>
- *          response can contain either a success or an error. Design your application to parse the
- *          contents of the response and handle it appropriately.</p>
+ *          response can contain either a success or an error. If you call the S3 API directly, make
+ *          sure to design your application to parse the contents of the response and handle it
+ *          appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the
+ *          embedded error and apply error handling per your configuration settings (including
+ *          automatically retrying the request as appropriate). If the condition persists, the SDKs
+ *          throws an exception (or, for the SDKs that don't use exceptions, they return the
+ *          error).</p>
  *          <p>If the copy is successful, you receive a response with information about the copied
  *          object.</p>
  *          <note>
@@ -50,7 +55,8 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *          <important>
  *             <p>Amazon S3 transfer acceleration does not support cross-Region copies. If you request a
  *             cross-Region copy using a transfer acceleration endpoint, you get a 400 <code>Bad
- *                Request</code> error. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer Acceleration</a>.</p>
+ *                Request</code> error. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer
+ *             Acceleration</a>.</p>
  *          </important>
  *          <p>
  *             <b>Metadata</b>
@@ -67,6 +73,11 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *             Policy</a> in the <i>Amazon S3 User Guide</i>. For a complete list of
  *          Amazon S3-specific condition keys, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/list_amazons3.html">Actions, Resources, and Condition Keys for
  *             Amazon S3</a>.</p>
+ *          <note>
+ *             <p>
+ *                <code>x-amz-website-redirect-location</code> is unique to each object and must be
+ *             specified in the request headers to copy the value.</p>
+ *          </note>
  *          <p>
  *             <b>x-amz-copy-source-if Headers</b>
  *          </p>
@@ -131,14 +142,27 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *          <p>
  *             <b>Server-side encryption</b>
  *          </p>
- *          <p>When you perform a CopyObject operation, you can optionally use the appropriate encryption-related
- *          headers to encrypt the object using server-side encryption with Amazon Web Services managed encryption keys
- *          (SSE-S3 or SSE-KMS) or a customer-provided encryption key. With server-side encryption, Amazon S3
- *          encrypts your data as it writes it to disks in its data centers and decrypts the data when
- *          you access it. For more information about server-side encryption, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Using
- *          Server-Side Encryption</a>.</p>
- *          <p>If a target object uses SSE-KMS, you can enable an S3 Bucket Key for the object. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket. When
+ *          copying an object, if you don't specify encryption information in your copy request, the
+ *          encryption setting of the target object 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 target
+ *          object copy. When you perform a CopyObject operation, if you want to use a different type
+ *          of encryption setting for the target object, you can use other appropriate
+ *          encryption-related headers to encrypt the target object with a KMS key, an Amazon S3 managed
+ *          key, or a customer-provided key. With server-side encryption, Amazon S3 encrypts your data as it
+ *          writes it to disks in its data centers and decrypts the data when you access it. 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 the
+ *          source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary
+ *          encryption information in your request so that Amazon S3 can decrypt the object for copying. For
+ *          more information about server-side encryption, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Using Server-Side
+ *          Encryption</a>.</p>
+ *          <p>If a target object uses SSE-KMS, you can enable an S3 Bucket Key for the object. For
+ *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <p>
  *             <b>Access Control List (ACL)-Specific Request
  *          Headers</b>
@@ -150,29 +174,29 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List (ACL) Overview</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-using-rest-api.html">Managing ACLs Using the REST
  *             API</a>. </p>
  *          <p>If the bucket that you're copying objects to uses the bucket owner enforced setting for
- *          S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that
- *          use this setting only accept PUT requests that don't specify an ACL or PUT requests that
- *          specify bucket owner full control ACLs, such as the <code>bucket-owner-full-control</code> canned
- *          ACL or an equivalent form of this ACL expressed in the XML format.</p>
+ *          S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that use
+ *          this setting only accept PUT requests that don't specify an ACL or PUT requests that
+ *          specify bucket owner full control ACLs, such as the <code>bucket-owner-full-control</code>
+ *          canned ACL or an equivalent form of this ACL expressed in the XML format.</p>
  *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html"> Controlling ownership of
- *          objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *             objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
- *             <p>If your bucket uses the bucket owner enforced setting for Object Ownership,
- *             all objects written to the bucket by any account will be owned by the bucket owner.</p>
+ *             <p>If your bucket uses the bucket owner enforced setting for Object Ownership, all
+ *             objects written to the bucket by any account will be owned by the bucket owner.</p>
  *          </note>
  *          <p>
  *             <b>Checksums</b>
  *          </p>
- *          <p>When copying an object, if it has a checksum, that checksum will be copied to the new object
- *            by default. When you copy the object over, you may optionally specify a different checksum
- *            algorithm to use with the <code>x-amz-checksum-algorithm</code> header.</p>
+ *          <p>When copying an object, if it has a checksum, that checksum will be copied to the new
+ *          object by default. When you copy the object over, you may optionally specify a different
+ *          checksum algorithm to use with the <code>x-amz-checksum-algorithm</code> header.</p>
  *          <p>
  *             <b>Storage Class Options</b>
  *          </p>
- *          <p>You can use the <code>CopyObject</code> action to change the storage class of an
- *          object that is already stored in Amazon S3 using the <code>StorageClass</code> parameter. For
- *          more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage
- *             Classes</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>You can use the <code>CopyObject</code> action to change the storage class of an object
+ *          that is already stored in Amazon S3 using the <code>StorageClass</code> parameter. For more
+ *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
  *          <p>
  *             <b>Versioning</b>
  *          </p>
@@ -201,8 +225,7 @@ export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBea
  *                </p>
  *             </li>
  *          </ul>
- *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html">Copying
- *             Objects</a>.</p>
+ *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html">Copying Objects</a>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -23,27 +23,30 @@ 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>
+ *          <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
@@ -52,7 +55,8 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *             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>
+ *          <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
@@ -65,14 +69,15 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *                   <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>
+ *                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>
+ *                         <code>id</code> – if the value specified is the canonical user ID of an
+ *                      Amazon Web Services account</p>
  *                   </li>
  *                   <li>
  *                      <p>
@@ -128,14 +133,17 @@ export interface CreateBucketCommandOutput extends CreateBucketOutput, __Metadat
  *          <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>
+ *          <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>
+ *                   <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>

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

@@ -28,39 +28,56 @@ 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 Policy</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 +87,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 +96,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 +104,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 +137,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 +170,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 +181,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 +198,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>

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

@@ -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

package/dist-types/commands/DeleteBucketCorsCommand.d.ts CHANGED Viewed

@@ -23,8 +23,8 @@ export interface DeleteBucketCorsCommandOutput extends __MetadataBearer {
  *          <p>To use this operation, you must have permission to perform the
  *             <code>s3:PutBucketCORS</code> action. The bucket owner has this permission by default
  *          and can grant this permission to others. </p>
- *          <p>For information about <code>cors</code>, see <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 information about <code>cors</code>, see <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 class="title">
  *             <b>Related Resources:</b>
  *          </p>

package/dist-types/commands/DeleteBucketEncryptionCommand.d.ts CHANGED Viewed

@@ -19,14 +19,16 @@ export interface DeleteBucketEncryptionCommandOutput extends __MetadataBearer {
 }
 /**
  * @public
- * <p>This implementation of the DELETE action removes default encryption from the bucket.
- *          For information about the Amazon S3 default encryption feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3 Default Bucket Encryption</a> in the
- *             <i>Amazon S3 User Guide</i>.</p>
+ * <p>This implementation of the DELETE action resets the default encryption for the
+ *          bucket as server-side encryption with Amazon S3 managed keys (SSE-S3). For information about the
+ *          bucket default encryption feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-encryption.html">Amazon S3 Bucket Default Encryption</a>
+ *          in the <i>Amazon S3 User Guide</i>.</p>
  *          <p>To use this operation, you must have permissions to perform the
  *             <code>s3:PutEncryptionConfiguration</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> in the <i>Amazon S3 User Guide</i>.</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> in the
+ *             <i>Amazon S3 User Guide</i>.</p>
  *          <p class="title">
  *             <b>Related Resources</b>
  *          </p>

package/dist-types/commands/DeleteBucketIntelligentTieringConfigurationCommand.d.ts CHANGED Viewed

@@ -23,8 +23,7 @@ export interface DeleteBucketIntelligentTieringConfigurationCommandOutput extend
  *          <p>The S3 Intelligent-Tiering storage class is designed to optimize storage costs by automatically moving data to the most cost-effective storage access tier, without performance impact or operational overhead. S3 Intelligent-Tiering delivers automatic cost savings in three low latency and high throughput access tiers. To get the lowest storage cost on data that can be accessed in minutes to hours, you can choose to activate additional archiving capabilities.</p>
  *          <p>The S3 Intelligent-Tiering storage class is  the ideal storage class for data with unknown, changing, or unpredictable access patterns, independent of object size or retention period. If the size of an object is less than 128 KB, it is not monitored and not eligible for auto-tiering. Smaller objects can be stored, but they are always charged at the Frequent Access tier rates in the S3 Intelligent-Tiering storage class.</p>
  *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html#sc-dynamic-data-access">Storage class for automatically optimizing frequently and infrequently accessed objects</a>.</p>
- *          <p>Operations related to
- *             <code>DeleteBucketIntelligentTieringConfiguration</code> include: </p>
+ *          <p>Operations related to <code>DeleteBucketIntelligentTieringConfiguration</code> include: </p>
  *          <ul>
  *             <li>
  *                <p>

package/dist-types/commands/DeleteBucketInventoryConfigurationCommand.d.ts CHANGED Viewed

@@ -24,8 +24,8 @@ export interface DeleteBucketInventoryConfigurationCommandOutput extends __Metad
  *          <p>To use this operation, you must have permissions to perform the
  *             <code>s3:PutInventoryConfiguration</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 inventory feature, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-inventory.html">Amazon S3 Inventory</a>.</p>
  *          <p>Operations related to <code>DeleteBucketInventoryConfiguration</code> include: </p>
  *          <ul>