@gemeentenijmegen/webapp 1.1.0 → 1.1.2

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

@@ -28,7 +28,7 @@ declare const PutObjectTaggingCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Sets the supplied tag-set to an object that already exists in a bucket. A tag is a
  *          key-value pair. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html">Object Tagging</a>.</p>

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

@@ -28,7 +28,7 @@ declare const PutPublicAccessBlockCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <p>Creates or modifies the <code>PublicAccessBlock</code> configuration for an Amazon S3 bucket.
  *          To use this operation, you must have the <code>s3:PutBucketPublicAccessBlock</code>

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

@@ -28,12 +28,8 @@ declare const RestoreObjectCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <important>
- *             <p>The <code>SELECT</code> job type for the RestoreObject operation is no longer available to new customers. Existing customers of Amazon S3 Select can continue to use the feature as usual. <a href="http://aws.amazon.com/blogs/storage/how-to-optimize-querying-your-data-in-amazon-s3/">Learn more</a>
- *             </p>
- *          </important>
  *          <p>Restores an archived copy of an object back into Amazon S3</p>
  *          <p>This functionality is not supported for Amazon S3 on Outposts.</p>
  *          <p>This action performs the following types of requests: </p>

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

@@ -28,12 +28,8 @@ declare const SelectObjectContentCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
- *          <important>
- *             <p>The SelectObjectContent operation is no longer available to new customers. Existing customers of Amazon S3 Select can continue to use the operation as usual. <a href="http://aws.amazon.com/blogs/storage/how-to-optimize-querying-your-data-in-amazon-s3/">Learn more</a>
- *             </p>
- *          </important>
  *          <p>This action filters the contents of an Amazon S3 object based on a simple structured query
  *          language (SQL) statement. In the request, along with the SQL expression, you must also
  *          specify a data serialization format (JSON, CSV, or Apache Parquet) of the object. Amazon S3 uses

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

@@ -30,10 +30,9 @@ declare const UploadPartCommand_base: {
 /**
  * <p>Uploads a part in a multipart upload.</p>
  *          <note>
- *             <p>In this operation, you provide new data as a part of an object in your request. However, you have an option
- *             to specify your existing Amazon S3 object as a data source for the part you are uploading. To
- *             upload a part from an existing object, you use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> operation.
- *          </p>
+ *             <p>In this operation, you provide new data as a part of an object in your request.
+ *             However, you have an option to specify your existing Amazon S3 object as a data source for
+ *             the part you are uploading. To upload a part from an existing object, you use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> operation. </p>
  *          </note>
  *          <p>You must initiate a multipart upload (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>)
  *          before you can upload any part. In response to your initiate request, Amazon S3 returns an
@@ -45,17 +44,17 @@ declare const UploadPartCommand_base: {
  *          <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>After you initiate multipart upload and upload
- *          one or more parts, you must either complete or abort multipart upload in order to stop
- *          getting charged for storage of the uploaded parts. Only after you either complete or abort
- *          multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts
- *          storage.</p>
+ *             <p>After you initiate multipart upload and upload one or more parts, you must either
+ *             complete or abort multipart upload in order to stop getting charged for storage of the
+ *             uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up
+ *             the parts storage and stops charging you for the parts storage.</p>
  *          </note>
  *          <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>
+ *             <i>Amazon S3 User Guide </i>.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
@@ -89,20 +88,24 @@ declare const UploadPartCommand_base: {
  * Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
  *                            <code>CreateSession</code>
  *                         </a>.</p>
- *                      <p>If the object is encrypted with
- *                         SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
+ *                      <p>If the object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
  *                   </li>
  *                </ul>
  *             </dd>
  *             <dt>Data integrity</dt>
  *             <dd>
  *                <p>
- *                   <b>General purpose bucket</b> - To ensure that data is not corrupted 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. 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>
+ *                   <b>General purpose bucket</b> - To ensure that data
+ *                   is not corrupted 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. 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>
  *                <note>
  *                   <p>
  *                      <b>Directory buckets</b> - MD5 is not supported by directory buckets. You can use checksum algorithms to check object integrity.</p>
@@ -113,23 +116,28 @@ declare const UploadPartCommand_base: {
  *                <ul>
  *                   <li>
  *                      <p>
- *                         <b>General purpose bucket</b> - 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
- *                         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).</p>
- *                      <p>Server-side encryption is supported by the S3 Multipart Upload operations. Unless you are
- *                         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 request 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 request headers.</p>
+ *                         <b>General purpose bucket</b> - 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 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).</p>
+ *                      <p>Server-side encryption is supported by the S3 Multipart Upload
+ *                         operations. Unless you are 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 request 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 request headers.</p>
  *                      <ul>
  *                         <li>
  *                            <p>x-amz-server-side-encryption-customer-algorithm</p>
@@ -141,13 +149,14 @@ declare const UploadPartCommand_base: {
  *                            <p>x-amz-server-side-encryption-customer-key-MD5</p>
  *                         </li>
  *                      </ul>
- *                      <p>
- *                         For more information, see <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> For more information, see <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>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>).</p>
+ *                         <b>Directory buckets </b> -
+ *                         For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>).</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -159,7 +168,9 @@ declare const UploadPartCommand_base: {
  *                      </p>
  *                      <ul>
  *                         <li>
- *                            <p>Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.</p>
+ *                            <p>Description: The specified multipart upload does not exist. The
+ *                               upload ID might be invalid, or the multipart upload might have been
+ *                               aborted or completed.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 404 Not Found </p>

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

@@ -28,43 +28,50 @@ declare const UploadPartCopyCommand_base: {
 };
 /**
  * <p>Uploads a part by copying data from an existing object as data source. To specify the
- *          data source, you add the request header <code>x-amz-copy-source</code> in your request. To specify
- *          a byte range, you add the request header <code>x-amz-copy-source-range</code> in your
- *          request. </p>
+ *          data source, you add the request header <code>x-amz-copy-source</code> in your request. To
+ *          specify a byte range, you add 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>
  *          <note>
- *             <p>Instead of copying data from 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 to upload new data as a part of an object in your request.</p>
+ *             <p>Instead of copying data from 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 to upload new data as a part of an object in your
+ *             request.</p>
  *          </note>
  *          <p>You must initiate a multipart upload before you can upload any part. In response to your
  *          initiate request, Amazon S3 returns the upload ID, a unique identifier that you must include in
  *          your upload part request.</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>. For information about copying objects using a single atomic action vs. a multipart
- *          upload, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html">Operations on Objects</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>. For information about
+ *          copying objects using a single atomic action vs. a multipart upload, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html">Operations on
+ *             Objects</a> in the <i>Amazon S3 User Guide</i>.</p>
  *          <note>
  *             <p>
- *                <b>Directory buckets</b> -  For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
+ *                <b>Directory buckets</b> -
+ *             For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format <code>https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
  *                </code>. Path-style requests are not supported. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-Regions-and-Zones.html">Regional and Zonal endpoints</a> in the
  *     <i>Amazon S3 User Guide</i>.</p>
  *          </note>
  *          <dl>
  *             <dt>Authentication and authorization</dt>
  *             <dd>
- *                <p>All <code>UploadPartCopy</code> requests must be authenticated and signed by using IAM credentials (access key ID and secret access key for the IAM identities). All headers with the <code>x-amz-</code> prefix, including
- *                         <code>x-amz-copy-source</code>, must be signed. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
+ *                <p>All <code>UploadPartCopy</code> requests must be authenticated and signed by
+ *                   using IAM credentials (access key ID and secret access key for the IAM
+ *                   identities). All headers with the <code>x-amz-</code> prefix, including
+ *                      <code>x-amz-copy-source</code>, must be signed. For more information, see
+ *                      <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>.</p>
  *                <p>
- *                   <b>Directory buckets</b> - You must use IAM credentials to authenticate and authorize your access to the <code>UploadPartCopy</code> API operation, instead of using the
- *                   temporary security credentials through the <code>CreateSession</code> API operation.</p>
- *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your behalf.</p>
+ *                   <b>Directory buckets</b> - You must use IAM
+ *                   credentials to authenticate and authorize your access to the
+ *                      <code>UploadPartCopy</code> API operation, instead of using the temporary
+ *                   security credentials through the <code>CreateSession</code> API operation.</p>
+ *                <p>Amazon Web Services CLI or SDKs handles authentication and authorization on your
+ *                   behalf.</p>
  *             </dd>
  *             <dt>Permissions</dt>
  *             <dd>
- *                <p>You must have <code>READ</code> access to the source object and <code>WRITE</code>
- *                   access to the destination bucket.</p>
+ *                <p>You must have <code>READ</code> access to the source object and
+ *                      <code>WRITE</code> access to the destination bucket.</p>
  *                <ul>
  *                   <li>
  *                      <p>
@@ -110,8 +117,9 @@ declare const UploadPartCopyCommand_base: {
  *                   <li>
  *                      <p>
  *                         <b>Directory bucket permissions</b> -
- *                         You must have permissions in a bucket policy or an IAM identity-based policy based on the source and destination
- *                         bucket types in an <code>UploadPartCopy</code> operation.</p>
+ *                         You must have permissions in a bucket policy or an IAM identity-based policy based on the
+ *                         source and destination bucket types in an <code>UploadPartCopy</code>
+ *                         operation.</p>
  *                      <ul>
  *                         <li>
  *                            <p>If the source object that you want to copy is in a
@@ -126,19 +134,21 @@ declare const UploadPartCopyCommand_base: {
  *                         </li>
  *                         <li>
  *                            <p>If the copy destination is a directory bucket, you must have the
- *                               <b>
+ *                                  <b>
  *                                  <code>s3express:CreateSession</code>
  *                               </b> permission in the
- *                               <code>Action</code> element of a policy to write the object
- *                               to the destination. The <code>s3express:SessionMode</code> condition
- *                               key cannot be set to <code>ReadOnly</code> on the copy destination. </p>
+ *                                  <code>Action</code> element of a policy to write the object to the
+ *                               destination. The <code>s3express:SessionMode</code> condition key
+ *                               cannot be set to <code>ReadOnly</code> on the copy destination.
+ *                            </p>
  *                         </li>
  *                      </ul>
- *                      <p>If the object is encrypted with
- *                         SSE-KMS, you must also have the
- *                         <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions in IAM identity-based policies and KMS key policies for the KMS key.</p>
- *                      <p>For example policies, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html">Example bucket policies for S3 Express One Zone</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for S3 Express One Zone</a> in the
- *                         <i>Amazon S3 User Guide</i>.</p>
+ *                      <p>If the object is encrypted with SSE-KMS, you must also have the
+ *                            <code>kms:GenerateDataKey</code> and <code>kms:Decrypt</code> permissions
+ *                         in IAM identity-based policies and KMS key policies for the KMS
+ *                         key.</p>
+ *                      <p>For example policies, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-example-bucket-policies.html">Example bucket policies for S3 Express One Zone</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-security-iam-identity-policies.html">Amazon Web Services Identity and Access Management (IAM) identity-based policies for
+ *                            S3 Express One Zone</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                   </li>
  *                </ul>
  *             </dd>
@@ -148,18 +158,22 @@ declare const UploadPartCopyCommand_base: {
  *                   <li>
  *                      <p>
  *                         <b>General purpose buckets </b> -
- *
- *                      For information about using server-side encryption with customer-provided
- *                            encryption keys with the <code>UploadPartCopy</code> operation, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>.
- *                      </p>
+ *                          For information about using
+ *                         server-side encryption with customer-provided encryption keys with the
+ *                            <code>UploadPartCopy</code> operation, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html">CopyObject</a> and
+ *                            <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html">UploadPart</a>. </p>
  *                   </li>
  *                   <li>
  *                      <p>
- *                         <b>Directory buckets </b> - For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). For more
+ *                         <b>Directory buckets </b> -
+ *                         For directory buckets, there are only two supported options for server-side encryption: server-side encryption with Amazon S3 managed keys (SSE-S3) (<code>AES256</code>) and server-side encryption with KMS keys (SSE-KMS) (<code>aws:kms</code>). For more
  *          information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-express-serv-side-encryption.html">Protecting data with server-side encryption</a> in the <i>Amazon S3 User Guide</i>.</p>
  *                      <note>
- *                         <p>For directory buckets, when you perform a <code>CreateMultipartUpload</code> operation and an <code>UploadPartCopy</code> operation,
- *                         the request headers you provide in the <code>CreateMultipartUpload</code> request must match the default encryption configuration of the destination bucket. </p>
+ *                         <p>For directory buckets, when you perform a
+ *                               <code>CreateMultipartUpload</code> operation and an
+ *                               <code>UploadPartCopy</code> operation, the request headers you provide
+ *                            in the <code>CreateMultipartUpload</code> request must match the default
+ *                            encryption configuration of the destination bucket. </p>
  *                      </note>
  *                      <p>S3 Bucket Keys aren't supported, when you copy SSE-KMS encrypted objects from general purpose buckets
  * to directory buckets, from directory buckets to general purpose buckets, or between directory buckets, through <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a>. In this case, Amazon S3 makes a call to KMS every time a copy request is made for a KMS-encrypted object.</p>
@@ -175,8 +189,8 @@ declare const UploadPartCopyCommand_base: {
  *                      <ul>
  *                         <li>
  *                            <p>Description: The specified multipart upload does not exist. The
- *                                  upload ID might be invalid, or the multipart upload might have been
- *                                  aborted or completed.</p>
+ *                               upload ID might be invalid, or the multipart upload might have been
+ *                               aborted or completed.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 404 Not Found</p>
@@ -189,7 +203,7 @@ declare const UploadPartCopyCommand_base: {
  *                      <ul>
  *                         <li>
  *                            <p>Description: The specified copy source is not supported as a
- *                                     byte-range copy source.</p>
+ *                               byte-range copy source.</p>
  *                         </li>
  *                         <li>
  *                            <p>HTTP Status Code: 400 Bad Request</p>
@@ -297,15 +311,14 @@ declare const UploadPartCopyCommand_base: {
  * <p>Base exception class for all service exceptions from S3 service.</p>
  *
  * @public
- * @example To upload a part by copying byte range from an existing object as data source
+ * @example To upload a part by copying data from an existing object as data source
  * ```javascript
- * // The following example uploads a part of a multipart upload by copying a specified byte range from an existing object as data source.
+ * // The following example uploads a part of a multipart upload by copying data from an existing object as data source.
  * const input = {
  *   "Bucket": "examplebucket",
  *   "CopySource": "/bucketname/sourceobjectkey",
- *   "CopySourceRange": "bytes=1-100000",
  *   "Key": "examplelargeobject",
- *   "PartNumber": "2",
+ *   "PartNumber": "1",
  *   "UploadId": "exampleuoh_10OhKhT7YukE9bjzTPRiuaCotmZM_pFngJFir9OZNrSr5cWa3cq3LZSUsfjI4FI7PkP91We7Nrw--"
  * };
  * const command = new UploadPartCopyCommand(input);
@@ -313,22 +326,23 @@ declare const UploadPartCopyCommand_base: {
  * /* response ==
  * {
  *   "CopyPartResult": {
- *     "ETag": "\"65d16d19e65a7508a51f043180edcc36\"",
- *     "LastModified": "2016-12-29T21:44:28.000Z"
+ *     "ETag": "\"b0c6f0e7e054ab8fa2536a2677f8734d\"",
+ *     "LastModified": "2016-12-29T21:24:43.000Z"
  *   }
  * }
  * *\/
- * // example id: to-upload-a-part-by-copying-byte-range-from-an-existing-object-as-data-source-1483048068594
+ * // example id: to-upload-a-part-by-copying-data-from-an-existing-object-as-data-source-1483046746348
  * ```
  *
- * @example To upload a part by copying data from an existing object as data source
+ * @example To upload a part by copying byte range from an existing object as data source
  * ```javascript
- * // The following example uploads a part of a multipart upload by copying data from an existing object as data source.
+ * // The following example uploads a part of a multipart upload by copying a specified byte range from an existing object as data source.
  * const input = {
  *   "Bucket": "examplebucket",
  *   "CopySource": "/bucketname/sourceobjectkey",
+ *   "CopySourceRange": "bytes=1-100000",
  *   "Key": "examplelargeobject",
- *   "PartNumber": "1",
+ *   "PartNumber": "2",
  *   "UploadId": "exampleuoh_10OhKhT7YukE9bjzTPRiuaCotmZM_pFngJFir9OZNrSr5cWa3cq3LZSUsfjI4FI7PkP91We7Nrw--"
  * };
  * const command = new UploadPartCopyCommand(input);
@@ -336,12 +350,12 @@ declare const UploadPartCopyCommand_base: {
  * /* response ==
  * {
  *   "CopyPartResult": {
- *     "ETag": "\"b0c6f0e7e054ab8fa2536a2677f8734d\"",
- *     "LastModified": "2016-12-29T21:24:43.000Z"
+ *     "ETag": "\"65d16d19e65a7508a51f043180edcc36\"",
+ *     "LastModified": "2016-12-29T21:44:28.000Z"
  *   }
  * }
  * *\/
- * // example id: to-upload-a-part-by-copying-data-from-an-existing-object-as-data-source-1483046746348
+ * // example id: to-upload-a-part-by-copying-byte-range-from-an-existing-object-as-data-source-1483048068594
  * ```
  *
  */

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

@@ -29,7 +29,7 @@ declare const WriteGetObjectResponseCommand_base: {
 };
 /**
  * <note>
- *             <p>This operation is not supported by directory buckets.</p>
+ *             <p>This operation is not supported for directory buckets.</p>
  *          </note>
  *          <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