@aws-sdk/client-s3 3.303.0 → 3.304.0

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

@@ -43,14 +43,15 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  *          identifies a part and also defines its position within the object being created. If you
  *          upload a new part using the same part number that was used with a previous part, the
  *          previously uploaded part is overwritten.</p>
- *          <p>For information about maximum and minimum part sizes and other multipart upload specifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>For information about maximum and minimum part sizes and other multipart upload
+ *          specifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <p>To ensure that data is not corrupted when traversing the network, specify the
  *             <code>Content-MD5</code> header in the upload part request. Amazon S3 checks the part data
  *          against the provided MD5 value. If they do not match, Amazon S3 returns an error. </p>
  *          <p>If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the
  *             <code>x-amz-content-sha256</code> header as a checksum instead of
- *             <code>Content-MD5</code>. For more information see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html">Authenticating Requests: Using the Authorization Header (Amazon Web Services Signature Version
- *             4)</a>. </p>
+ *             <code>Content-MD5</code>. For more information see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html">Authenticating
+ *             Requests: Using the Authorization Header (Amazon Web Services Signature Version 4)</a>. </p>
  *          <p>
  *             <b>Note:</b> After you initiate multipart upload and upload
  *          one or more parts, you must either complete or abort multipart upload in order to stop
@@ -60,23 +61,29 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  *          <p>For more information on multipart uploads, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html">Multipart Upload Overview</a> in the
  *             <i>Amazon S3 User Guide </i>.</p>
  *          <p>For information on the permissions required to use the multipart upload API, go to
- *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and
- *             Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
- *          <p>You can optionally request server-side encryption where Amazon S3 encrypts your data as it
- *          writes it to disks in its data centers and decrypts it for you when you access it. You have
- *          the option of providing your own encryption key, or you can use the Amazon Web Services managed encryption
- *          keys. If you choose to provide your own encryption key, the request headers you provide in
- *          the request must match the headers you used in the request to initiate the upload by using
- *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>. For more information, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using Server-Side Encryption</a> in
- *          the <i>Amazon S3 User Guide</i>.</p>
+ *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart
+ *             Upload and Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *          <p>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. You have three
+ *          mutually exclusive options to protect data using server-side encryption in Amazon S3, depending
+ *          on how you choose to manage the encryption keys. Specifically, the encryption key options
+ *          are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and Customer-Provided Keys
+ *          (SSE-C). Amazon S3 encrypts data with server-side encryption using Amazon S3 managed keys (SSE-S3) by
+ *          default. You can optionally tell Amazon S3 to encrypt data at rest 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 key (SSE-C). If you choose to provide your own
+ *          encryption key, the request headers you provide in the request must match the headers you
+ *          used in the request to initiate the upload by using <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.
+ *          For more information, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using Server-Side
+ *             Encryption</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <p>Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are
- *          using a customer-provided encryption key, you don't need to specify the encryption
+ *          using a customer-provided encryption key (SSE-C), you don't need to specify the encryption
  *          parameters in each UploadPart request. Instead, you only need to specify the server-side
  *          encryption parameters in the initial Initiate Multipart request. For more information, see
  *             <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>.</p>
- *          <p>If you requested server-side encryption using a customer-provided encryption key in your
- *          initiate multipart upload request, you must provide identical encryption information in
- *          each part upload using the following headers.</p>
+ *          <p>If you requested server-side encryption using a customer-provided encryption key (SSE-C)
+ *          in your initiate multipart upload request, you must provide identical encryption
+ *          information in each part upload using the following headers.</p>
  *          <ul>
  *             <li>
  *                <p>x-amz-server-side-encryption-customer-algorithm</p>

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

@@ -23,7 +23,8 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
  *          data source by adding the request header <code>x-amz-copy-source</code> in your request and
  *          a byte range by adding the request header <code>x-amz-copy-source-range</code> in your
  *          request. </p>
- *          <p>For information about maximum and minimum part sizes and other multipart upload specifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>. </p>
+ *          <p>For information about maximum and minimum part sizes and other multipart upload
+ *          specifications, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/qfacts.html">Multipart upload limits</a> in the <i>Amazon S3 User Guide</i>. </p>
  *          <note>
  *             <p>Instead of using an existing object as part data, you might use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>
  *             action and provide data in your request.</p>
@@ -35,13 +36,14 @@ export interface UploadPartCopyCommandOutput extends UploadPartCopyOutput, __Met
  *          following:</p>
  *          <ul>
  *             <li>
- *                <p>For conceptual information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading Objects Using Multipart
- *                   Upload</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                <p>For conceptual information about multipart uploads, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html">Uploading
+ *                   Objects Using Multipart Upload</a> in the
+ *                <i>Amazon S3 User Guide</i>.</p>
  *             </li>
  *             <li>
  *                <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> in the <i>Amazon S3 User Guide</i>.</p>
+ *                   <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and Permissions</a> in the
+ *                   <i>Amazon S3 User Guide</i>.</p>
  *             </li>
  *             <li>
  *                <p>For information about copying objects using a single atomic action vs. a multipart

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

@@ -29,29 +29,40 @@ export interface WriteGetObjectResponseCommandOutput extends __MetadataBearer {
 }
 /**
  * @public
- * <p>Passes transformed
- *          objects to a <code>GetObject</code> operation when using Object Lambda access points. For information about
- *          Object Lambda access points, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/transforming-objects.html">Transforming objects with
+ * <p>Passes transformed objects to a <code>GetObject</code> operation when using Object Lambda access points. For
+ *          information about Object Lambda access points, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/transforming-objects.html">Transforming objects with
  *             Object Lambda access points</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <p>This operation supports metadata that can be returned by <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html">GetObject</a>, in addition to
- *            <code>RequestRoute</code>, <code>RequestToken</code>, <code>StatusCode</code>,
- *            <code>ErrorCode</code>, and <code>ErrorMessage</code>. The <code>GetObject</code>
- *         response metadata is supported so that the <code>WriteGetObjectResponse</code> caller,
- *         typically an Lambda function, can provide the same metadata when it internally invokes
- *            <code>GetObject</code>. When <code>WriteGetObjectResponse</code> is called by a
- *         customer-owned Lambda function, the metadata returned to the end user
- *            <code>GetObject</code> call might differ from what Amazon S3 would normally return.</p>
- *          <p>You can include any number of metadata headers. When including a metadata header, it should be
- *          prefaced with <code>x-amz-meta</code>. For example, <code>x-amz-meta-my-custom-header: MyCustomValue</code>.
- *          The primary use case for this is to forward <code>GetObject</code> metadata.</p>
- *          <p>Amazon Web Services provides some prebuilt Lambda functions that you can use with S3 Object Lambda to detect and redact
- *          personally identifiable information (PII) and decompress S3 objects. These Lambda functions
- *          are available in the Amazon Web Services Serverless Application Repository, and can be selected through the Amazon Web Services Management Console when you create your
- *          Object Lambda access point.</p>
- *          <p>Example 1: PII Access Control - This Lambda function uses Amazon Comprehend, a natural language processing (NLP) service using machine learning to find insights and relationships in text. It automatically detects personally identifiable information (PII) such as names, addresses, dates, credit card numbers, and social security numbers from documents in your Amazon S3 bucket. </p>
- *          <p>Example 2: PII Redaction - This Lambda function uses Amazon Comprehend, a natural language processing (NLP) service using machine learning to find insights and relationships in text. It automatically redacts personally identifiable information (PII) such as names, addresses, dates, credit card numbers, and social security numbers from documents in your Amazon S3 bucket. </p>
- *          <p>Example 3: Decompression - The Lambda function S3ObjectLambdaDecompression, is equipped to decompress objects stored in S3 in one of six compressed file formats including bzip2, gzip, snappy, zlib, zstandard and ZIP. </p>
- *          <p>For information on how to view and use these functions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/olap-examples.html">Using Amazon Web Services built Lambda functions</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *             <code>RequestRoute</code>, <code>RequestToken</code>, <code>StatusCode</code>,
+ *             <code>ErrorCode</code>, and <code>ErrorMessage</code>. The <code>GetObject</code>
+ *          response metadata is supported so that the <code>WriteGetObjectResponse</code> caller,
+ *          typically an Lambda function, can provide the same metadata when it internally invokes
+ *             <code>GetObject</code>. When <code>WriteGetObjectResponse</code> is called by a
+ *          customer-owned Lambda function, the metadata returned to the end user
+ *             <code>GetObject</code> call might differ from what Amazon S3 would normally return.</p>
+ *          <p>You can include any number of metadata headers. When including a metadata header, it
+ *          should be prefaced with <code>x-amz-meta</code>. For example,
+ *             <code>x-amz-meta-my-custom-header: MyCustomValue</code>. The primary use case for this
+ *          is to forward <code>GetObject</code> metadata.</p>
+ *          <p>Amazon Web Services provides some prebuilt Lambda functions that you can use with S3 Object Lambda to
+ *          detect and redact personally identifiable information (PII) and decompress S3 objects.
+ *          These Lambda functions are available in the Amazon Web Services Serverless Application Repository, and
+ *          can be selected through the Amazon Web Services Management Console when you create your Object Lambda access point.</p>
+ *          <p>Example 1: PII Access Control - This Lambda function uses Amazon Comprehend, a
+ *          natural language processing (NLP) service using machine learning to find insights and
+ *          relationships in text. It automatically detects personally identifiable information (PII)
+ *          such as names, addresses, dates, credit card numbers, and social security numbers from
+ *          documents in your Amazon S3 bucket. </p>
+ *          <p>Example 2: PII Redaction - This Lambda function uses Amazon Comprehend, a natural
+ *          language processing (NLP) service using machine learning to find insights and relationships
+ *          in text. It automatically redacts personally identifiable information (PII) such as names,
+ *          addresses, dates, credit card numbers, and social security numbers from documents in your
+ *          Amazon S3 bucket. </p>
+ *          <p>Example 3: Decompression - The Lambda function S3ObjectLambdaDecompression, is
+ *          equipped to decompress objects stored in S3 in one of six compressed file formats including
+ *          bzip2, gzip, snappy, zlib, zstandard and ZIP. </p>
+ *          <p>For information on how to view and use these functions, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/olap-examples.html">Using Amazon Web Services built Lambda
+ *             functions</a> in the <i>Amazon S3 User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript