From d3b2e8c537c679318dfefbfbbf7ffb1bcdddf655 Mon Sep 17 00:00:00 2001
From: awstools <awstools@amazon.com>
Date: Tue, 3 May 2022 21:10:30 +0000
Subject: [PATCH] docs(client-s3): Documentation only update for doc bug fixes
 for the S3 API docs.

---
 clients/client-s3/src/S3.ts                         | 13 ++++++-------
 .../PutBucketLifecycleConfigurationCommand.ts       |  5 +++--
 clients/client-s3/src/commands/UploadPartCommand.ts |  4 ++--
 .../client-s3/src/commands/UploadPartCopyCommand.ts |  4 +---
 clients/client-s3/src/models/models_0.ts            |  6 ++++--
 codegen/sdk-codegen/aws-models/s3.json              | 10 +++++-----
 6 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/clients/client-s3/src/S3.ts b/clients/client-s3/src/S3.ts
index c3542948db4f..924089873d21 100644
--- a/clients/client-s3/src/S3.ts
+++ b/clients/client-s3/src/S3.ts
@@ -5979,8 +5979,9 @@ export class S3 extends S3Client {
    *             <b>Rules</b>
    *          </p>
    *          <p>You specify the lifecycle configuration in your request body. The lifecycle
-   *          configuration is specified as XML consisting of one or more rules. Each rule consists of
-   *          the following:</p>
+   *          configuration is specified as XML consisting of one or more rules. An Amazon S3 Lifecycle
+   *          configuration can have up to 1,000 rules. This limit is not adjustable. Each rule consists
+   *          of the following:</p>
    *
    *          <ul>
    *             <li>
@@ -8147,8 +8148,8 @@ export class S3 extends S3Client {
    *          <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely
    *          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. Each part must be at least 5 MB in size, except
-   *          the last part. There is no size limit on the last part of your multipart upload.</p>
+   *          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>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>
@@ -8300,9 +8301,7 @@ export class S3 extends S3Client {
    *          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>The minimum allowable part size for a multipart upload is 5 MB. For more information
-   *          about multipart upload limits, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/qfacts.html">Quick
-   *             Facts</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>
diff --git a/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts b/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts
index 1a1b1b97d218..3ef295c358a1 100644
--- a/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts
+++ b/clients/client-s3/src/commands/PutBucketLifecycleConfigurationCommand.ts
@@ -44,8 +44,9 @@ export interface PutBucketLifecycleConfigurationCommandOutput extends __Metadata
  *             <b>Rules</b>
  *          </p>
  *          <p>You specify the lifecycle configuration in your request body. The lifecycle
- *          configuration is specified as XML consisting of one or more rules. Each rule consists of
- *          the following:</p>
+ *          configuration is specified as XML consisting of one or more rules. An Amazon S3 Lifecycle
+ *          configuration can have up to 1,000 rules. This limit is not adjustable. Each rule consists
+ *          of the following:</p>
  *
  *          <ul>
  *             <li>
diff --git a/clients/client-s3/src/commands/UploadPartCommand.ts b/clients/client-s3/src/commands/UploadPartCommand.ts
index 75b8fcce9fe7..d6a6a97f3e72 100644
--- a/clients/client-s3/src/commands/UploadPartCommand.ts
+++ b/clients/client-s3/src/commands/UploadPartCommand.ts
@@ -48,8 +48,8 @@ export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBea
  *          <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely
  *          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. Each part must be at least 5 MB in size, except
- *          the last part. There is no size limit on the last part of your multipart upload.</p>
+ *          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>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>
diff --git a/clients/client-s3/src/commands/UploadPartCopyCommand.ts b/clients/client-s3/src/commands/UploadPartCopyCommand.ts
index 83ef6276ca77..e1c163576ce2 100644
--- a/clients/client-s3/src/commands/UploadPartCopyCommand.ts
+++ b/clients/client-s3/src/commands/UploadPartCopyCommand.ts
@@ -29,9 +29,7 @@ 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>The minimum allowable part size for a multipart upload is 5 MB. For more information
- *          about multipart upload limits, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/qfacts.html">Quick
- *             Facts</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>
diff --git a/clients/client-s3/src/models/models_0.ts b/clients/client-s3/src/models/models_0.ts
index 43c259bffdc2..91513250665c 100644
--- a/clients/client-s3/src/models/models_0.ts
+++ b/clients/client-s3/src/models/models_0.ts
@@ -5439,7 +5439,7 @@ export namespace LifecycleRuleFilter {
 export interface NoncurrentVersionExpiration {
   /**
    * <p>Specifies the number of days an object is noncurrent before Amazon S3 can perform the
-   *          associated action. For information about the noncurrent days calculations, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#non-current-days-calculations">How
+   *          associated action. The value must be a non-zero positive integer. For information about the noncurrent days calculations, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#non-current-days-calculations">How
    *             Amazon S3 Calculates When an Object Became Noncurrent</a> in the <i>Amazon S3 User Guide</i>.</p>
    */
   NoncurrentDays?: number;
@@ -9911,7 +9911,9 @@ export interface _Object {
    *             </li>
    *             <li>
    *                <p>If an object is created by either the Multipart Upload or Part Copy operation, the
-   *                ETag is not an MD5 digest, regardless of the method of encryption.</p>
+   *                ETag is not an MD5 digest, regardless of the method of encryption. If an object
+   *                is larger than 16 MB, the Amazon Web Services Management Console will upload or copy that object as a
+   *                Multipart Upload, and therefore the ETag will not be an MD5 digest.</p>
    *             </li>
    *          </ul>
    */
diff --git a/codegen/sdk-codegen/aws-models/s3.json b/codegen/sdk-codegen/aws-models/s3.json
index 4c0df050fcde..f5aef9000204 100644
--- a/codegen/sdk-codegen/aws-models/s3.json
+++ b/codegen/sdk-codegen/aws-models/s3.json
@@ -9077,7 +9077,7 @@
         "NoncurrentDays": {
           "target": "com.amazonaws.s3#Days",
           "traits": {
-            "smithy.api#documentation": "<p>Specifies the number of days an object is noncurrent before Amazon S3 can perform the\n         associated action. For information about the noncurrent days calculations, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#non-current-days-calculations\">How\n            Amazon S3 Calculates When an Object Became Noncurrent</a> in the <i>Amazon S3 User Guide</i>.</p>"
+            "smithy.api#documentation": "<p>Specifies the number of days an object is noncurrent before Amazon S3 can perform the\n         associated action. The value must be a non-zero positive integer. For information about the noncurrent days calculations, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html#non-current-days-calculations\">How\n            Amazon S3 Calculates When an Object Became Noncurrent</a> in the <i>Amazon S3 User Guide</i>.</p>"
           }
         },
         "NewerNoncurrentVersions": {
@@ -9207,7 +9207,7 @@
         "ETag": {
           "target": "com.amazonaws.s3#ETag",
           "traits": {
-            "smithy.api#documentation": "<p>The entity tag is a hash of the object. The ETag reflects changes only to the contents\n         of an object, not its metadata. The ETag may or may not be an MD5 digest of the object\n         data. Whether or not it is depends on how the object was created and how it is encrypted as\n         described below:</p>\n         <ul>\n            <li>\n               <p>Objects created by the PUT Object, POST Object, or Copy operation, or through the\n               Amazon Web Services Management Console, and are encrypted by SSE-S3 or plaintext, have ETags that are\n               an MD5 digest of their object data.</p>\n            </li>\n            <li>\n               <p>Objects created by the PUT Object, POST Object, or Copy operation, or through the\n               Amazon Web Services Management Console, and are encrypted by SSE-C or SSE-KMS, have ETags that are\n               not an MD5 digest of their object data.</p>\n            </li>\n            <li>\n               <p>If an object is created by either the Multipart Upload or Part Copy operation, the\n               ETag is not an MD5 digest, regardless of the method of encryption.</p>\n            </li>\n         </ul>"
+            "smithy.api#documentation": "<p>The entity tag is a hash of the object. The ETag reflects changes only to the contents\n         of an object, not its metadata. The ETag may or may not be an MD5 digest of the object\n         data. Whether or not it is depends on how the object was created and how it is encrypted as\n         described below:</p>\n         <ul>\n            <li>\n               <p>Objects created by the PUT Object, POST Object, or Copy operation, or through the\n               Amazon Web Services Management Console, and are encrypted by SSE-S3 or plaintext, have ETags that are\n               an MD5 digest of their object data.</p>\n            </li>\n            <li>\n               <p>Objects created by the PUT Object, POST Object, or Copy operation, or through the\n               Amazon Web Services Management Console, and are encrypted by SSE-C or SSE-KMS, have ETags that are\n               not an MD5 digest of their object data.</p>\n            </li>\n            <li>\n               <p>If an object is created by either the Multipart Upload or Part Copy operation, the\n               ETag is not an MD5 digest, regardless of the method of encryption. If an object\n               is larger than 16 MB, the Amazon Web Services Management Console will upload or copy that object as a\n               Multipart Upload, and therefore the ETag will not be an MD5 digest.</p>\n            </li>\n         </ul>"
           }
         },
         "ChecksumAlgorithm": {
@@ -10476,7 +10476,7 @@
           "requestAlgorithmMember": "ChecksumAlgorithm",
           "requestChecksumRequired": true
         },
-        "smithy.api#documentation": "<p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle\n         configuration. Keep in mind that this will overwrite an existing lifecycle configuration, so if\n         you want to retain any configuration details, they must be included in the new lifecycle\n         configuration. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\">Managing your storage\n            lifecycle</a>.</p>\n\n         <note>\n            <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an\n            object key name prefix, one or more object tags, or a combination of both. Accordingly,\n            this section describes the latest API. The previous version of the API supported\n            filtering based only on an object key name prefix, which is supported for backward\n            compatibility. For the related API description, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html\">PutBucketLifecycle</a>.</p>\n         </note>\n\n      \n\n         <p>\n            <b>Rules</b>\n         </p>\n         <p>You specify the lifecycle configuration in your request body. The lifecycle\n         configuration is specified as XML consisting of one or more rules. Each rule consists of\n         the following:</p>\n\n         <ul>\n            <li>\n               <p>Filter identifying a subset of objects to which the rule applies. The filter can\n               be based on a key name prefix, object tags, or a combination of both.</p>\n            </li>\n            <li>\n               <p>Status whether the rule is in effect.</p>\n            </li>\n            <li>\n               <p>One or more lifecycle transition and expiration actions that you want Amazon S3 to\n               perform on the objects identified by the filter. If the state of your bucket is\n               versioning-enabled or versioning-suspended, you can have many versions of the same\n               object (one current version and zero or more noncurrent versions). Amazon S3 provides\n               predefined actions that you can specify for current and noncurrent object\n               versions.</p>\n            </li>\n         </ul>\n\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object\n            Lifecycle Management</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html\">Lifecycle Configuration Elements</a>.</p>\n\n\n         <p>\n            <b>Permissions</b>\n         </p>\n\n\n         <p>By default, all Amazon S3 resources are private, including buckets, objects, and related\n         subresources (for example, lifecycle configuration and website configuration). Only the\n         resource owner (that is, the Amazon Web Services account that created it) can access the resource. The\n         resource owner can optionally grant access permissions to others by writing an access\n         policy. For this operation, a user must get the <code>s3:PutLifecycleConfiguration</code>\n         permission.</p>\n\n         <p>You can also explicitly deny permissions. Explicit deny also supersedes any other\n         permissions. If you want to block users or accounts from removing or deleting objects from\n         your bucket, you must deny them permissions for the following actions:</p>\n\n         <ul>\n            <li>\n               <p>\n                  <code>s3:DeleteObject</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>s3:DeleteObjectVersion</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>s3:PutLifecycleConfiguration</code>\n               </p>\n            </li>\n         </ul>\n\n\n         <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing Access Permissions to Your Amazon S3\n            Resources</a>.</p>\n\n         <p>The following are related to <code>PutBucketLifecycleConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html\">Examples of\n                  Lifecycle Configuration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html\">DeleteBucketLifecycle</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle\n         configuration. Keep in mind that this will overwrite an existing lifecycle configuration, so if\n         you want to retain any configuration details, they must be included in the new lifecycle\n         configuration. For information about lifecycle configuration, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\">Managing your storage\n            lifecycle</a>.</p>\n\n         <note>\n            <p>Bucket lifecycle configuration now supports specifying a lifecycle rule using an\n            object key name prefix, one or more object tags, or a combination of both. Accordingly,\n            this section describes the latest API. The previous version of the API supported\n            filtering based only on an object key name prefix, which is supported for backward\n            compatibility. For the related API description, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketLifecycle.html\">PutBucketLifecycle</a>.</p>\n         </note>\n\n      \n\n         <p>\n            <b>Rules</b>\n         </p>\n         <p>You specify the lifecycle configuration in your request body. The lifecycle\n         configuration is specified as XML consisting of one or more rules. An Amazon S3 Lifecycle\n         configuration can have up to 1,000 rules. This limit is not adjustable. Each rule consists\n         of the following:</p>\n\n         <ul>\n            <li>\n               <p>Filter identifying a subset of objects to which the rule applies. The filter can\n               be based on a key name prefix, object tags, or a combination of both.</p>\n            </li>\n            <li>\n               <p>Status whether the rule is in effect.</p>\n            </li>\n            <li>\n               <p>One or more lifecycle transition and expiration actions that you want Amazon S3 to\n               perform on the objects identified by the filter. If the state of your bucket is\n               versioning-enabled or versioning-suspended, you can have many versions of the same\n               object (one current version and zero or more noncurrent versions). Amazon S3 provides\n               predefined actions that you can specify for current and noncurrent object\n               versions.</p>\n            </li>\n         </ul>\n\n         <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html\">Object\n            Lifecycle Management</a> and <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/intro-lifecycle-rules.html\">Lifecycle Configuration Elements</a>.</p>\n\n\n         <p>\n            <b>Permissions</b>\n         </p>\n\n\n         <p>By default, all Amazon S3 resources are private, including buckets, objects, and related\n         subresources (for example, lifecycle configuration and website configuration). Only the\n         resource owner (that is, the Amazon Web Services account that created it) can access the resource. The\n         resource owner can optionally grant access permissions to others by writing an access\n         policy. For this operation, a user must get the <code>s3:PutLifecycleConfiguration</code>\n         permission.</p>\n\n         <p>You can also explicitly deny permissions. Explicit deny also supersedes any other\n         permissions. If you want to block users or accounts from removing or deleting objects from\n         your bucket, you must deny them permissions for the following actions:</p>\n\n         <ul>\n            <li>\n               <p>\n                  <code>s3:DeleteObject</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>s3:DeleteObjectVersion</code>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <code>s3:PutLifecycleConfiguration</code>\n               </p>\n            </li>\n         </ul>\n\n\n         <p>For more information about permissions, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-access-control.html\">Managing Access Permissions to Your Amazon S3\n            Resources</a>.</p>\n\n         <p>The following are related to <code>PutBucketLifecycleConfiguration</code>:</p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html\">Examples of\n                  Lifecycle Configuration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketLifecycleConfiguration.html\">GetBucketLifecycleConfiguration</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html\">DeleteBucketLifecycle</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}?lifecycle",
@@ -13690,7 +13690,7 @@
         "aws.protocols#httpChecksum": {
           "requestAlgorithmMember": "ChecksumAlgorithm"
         },
-        "smithy.api#documentation": "<p>Uploads a part in a multipart upload.</p>\n         <note>\n            <p>In this operation, you provide part data in your request. However, you have an option\n            to specify your existing Amazon S3 object as a data source for the part you are uploading. To\n            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.\n         </p>\n         </note>\n\n         <p>You must initiate a multipart upload (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>)\n         before you can upload any part. In response to your initiate request, Amazon S3 returns an\n         upload ID, a unique identifier, that you must include in your upload part request.</p>\n         <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely\n         identifies a part and also defines its position within the object being created. If you\n         upload a new part using the same part number that was used with a previous part, the\n         previously uploaded part is overwritten. Each part must be at least 5 MB in size, except\n         the last part. There is no size limit on the last part of your multipart upload.</p>\n         <p>To ensure that data is not corrupted when traversing the network, specify the\n            <code>Content-MD5</code> header in the upload part request. Amazon S3 checks the part data\n         against the provided MD5 value. If they do not match, Amazon S3 returns an error. </p>\n\n         <p>If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the\n            <code>x-amz-content-sha256</code> header as a checksum instead of\n            <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\n            4)</a>. </p>\n\n\n\n         <p>\n            <b>Note:</b> After you initiate multipart upload and upload\n         one or more parts, you must either complete or abort multipart upload in order to stop\n         getting charged for storage of the uploaded parts. Only after you either complete or abort\n         multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts\n         storage.</p>\n\n         <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\n            <i>Amazon S3 User Guide </i>.</p>\n         <p>For information on the permissions required to use the multipart upload API, go to\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload and\n            Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n\n         <p>You can optionally request server-side encryption where Amazon S3 encrypts your data as it\n         writes it to disks in its data centers and decrypts it for you when you access it. You have\n         the option of providing your own encryption key, or you can use the Amazon Web Services managed encryption\n         keys. If you choose to provide your own encryption key, the request headers you provide in\n         the request must match the headers you used in the request to initiate the upload by using\n            <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\n         the <i>Amazon S3 User Guide</i>.</p>\n\n         <p>Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are\n         using a customer-provided encryption key, you don't need to specify the encryption\n         parameters in each UploadPart request. Instead, you only need to specify the server-side\n         encryption parameters in the initial Initiate Multipart request. For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>.</p>\n\n         <p>If you requested server-side encryption using a customer-provided encryption key in your\n         initiate multipart upload request, you must provide identical encryption information in\n         each part upload using the following headers.</p>\n\n\n         <ul>\n            <li>\n               <p>x-amz-server-side-encryption-customer-algorithm</p>\n            </li>\n            <li>\n               <p>x-amz-server-side-encryption-customer-key</p>\n            </li>\n            <li>\n               <p>x-amz-server-side-encryption-customer-key-MD5</p>\n            </li>\n         </ul>\n\n         <p class=\"title\">\n            <b>Special Errors</b>\n         </p>\n         <ul>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>Code: NoSuchUpload</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: The specified multipart upload does not exist. The upload\n                        ID might be invalid, or the multipart upload might have been aborted or\n                        completed.</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i> HTTP Status Code: 404 Not Found </i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>SOAP Fault Code Prefix: Client</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n\n      \n\n\n\n\n         <p class=\"title\">\n            <b>Related Resources</b>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Uploads a part in a multipart upload.</p>\n         <note>\n            <p>In this operation, you provide part data in your request. However, you have an option\n            to specify your existing Amazon S3 object as a data source for the part you are uploading. To\n            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.\n         </p>\n         </note>\n\n         <p>You must initiate a multipart upload (see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>)\n         before you can upload any part. In response to your initiate request, Amazon S3 returns an\n         upload ID, a unique identifier, that you must include in your upload part request.</p>\n         <p>Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely\n         identifies a part and also defines its position within the object being created. If you\n         upload a new part using the same part number that was used with a previous part, the\n         previously uploaded part is overwritten.</p> \n         <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>\n         <p>To ensure that data is not corrupted when traversing the network, specify the\n            <code>Content-MD5</code> header in the upload part request. Amazon S3 checks the part data\n         against the provided MD5 value. If they do not match, Amazon S3 returns an error. </p>\n\n         <p>If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the\n            <code>x-amz-content-sha256</code> header as a checksum instead of\n            <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\n            4)</a>. </p>\n\n\n\n         <p>\n            <b>Note:</b> After you initiate multipart upload and upload\n         one or more parts, you must either complete or abort multipart upload in order to stop\n         getting charged for storage of the uploaded parts. Only after you either complete or abort\n         multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts\n         storage.</p>\n\n         <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\n            <i>Amazon S3 User Guide </i>.</p>\n         <p>For information on the permissions required to use the multipart upload API, go to\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload and\n            Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n\n         <p>You can optionally request server-side encryption where Amazon S3 encrypts your data as it\n         writes it to disks in its data centers and decrypts it for you when you access it. You have\n         the option of providing your own encryption key, or you can use the Amazon Web Services managed encryption\n         keys. If you choose to provide your own encryption key, the request headers you provide in\n         the request must match the headers you used in the request to initiate the upload by using\n            <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\n         the <i>Amazon S3 User Guide</i>.</p>\n\n         <p>Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are\n         using a customer-provided encryption key, you don't need to specify the encryption\n         parameters in each UploadPart request. Instead, you only need to specify the server-side\n         encryption parameters in the initial Initiate Multipart request. For more information, see\n            <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>.</p>\n\n         <p>If you requested server-side encryption using a customer-provided encryption key in your\n         initiate multipart upload request, you must provide identical encryption information in\n         each part upload using the following headers.</p>\n\n\n         <ul>\n            <li>\n               <p>x-amz-server-side-encryption-customer-algorithm</p>\n            </li>\n            <li>\n               <p>x-amz-server-side-encryption-customer-key</p>\n            </li>\n            <li>\n               <p>x-amz-server-side-encryption-customer-key-MD5</p>\n            </li>\n         </ul>\n\n         <p class=\"title\">\n            <b>Special Errors</b>\n         </p>\n         <ul>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>Code: NoSuchUpload</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: The specified multipart upload does not exist. The upload\n                        ID might be invalid, or the multipart upload might have been aborted or\n                        completed.</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i> HTTP Status Code: 404 Not Found </i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>SOAP Fault Code Prefix: Client</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n\n      \n\n\n\n\n         <p class=\"title\">\n            <b>Related Resources</b>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}/{Key+}?x-id=UploadPart",
@@ -13707,7 +13707,7 @@
         "target": "com.amazonaws.s3#UploadPartCopyOutput"
       },
       "traits": {
-        "smithy.api#documentation": "<p>Uploads a part by copying data from an existing object as data source. You specify the\n         data source by adding the request header <code>x-amz-copy-source</code> in your request and\n         a byte range by adding the request header <code>x-amz-copy-source-range</code> in your\n         request. </p>\n         <p>The minimum allowable part size for a multipart upload is 5 MB. For more information\n         about multipart upload limits, go to <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/qfacts.html\">Quick\n            Facts</a> in the <i>Amazon S3 User Guide</i>. </p>\n         <note>\n            <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>\n            action and provide data in your request.</p>\n         </note>\n\n         <p>You must initiate a multipart upload before you can upload any part. In response to your\n         initiate request. Amazon S3 returns a unique identifier, the upload ID, that you must include in\n         your upload part request.</p>\n         <p>For more information about using the <code>UploadPartCopy</code> operation, see the\n         following:</p>\n\n         <ul>\n            <li>\n               <p>For conceptual information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n                  Upload</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>For information about permissions required to use the multipart upload API, see\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload  and\n                  Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>For information about copying objects using a single atomic action vs. a multipart\n               upload, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html\">Operations on Objects</a> in\n               the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>For information about using server-side encryption with customer-provided\n               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>\n            </li>\n         </ul>\n         <p>Note the following additional considerations about the request headers\n            <code>x-amz-copy-source-if-match</code>, <code>x-amz-copy-source-if-none-match</code>,\n            <code>x-amz-copy-source-if-unmodified-since</code>, and\n            <code>x-amz-copy-source-if-modified-since</code>:</p>\n         <p> </p>\n         <ul>\n            <li>\n               <p>\n                  <b>Consideration 1</b> - If both of the\n                  <code>x-amz-copy-source-if-match</code> and\n                  <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the\n               request as follows:</p>\n               <p>\n                  <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,\n               and;</p>\n               <p>\n                  <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n                  <code>false</code>;</p>\n               <p>Amazon S3 returns <code>200 OK</code> and copies the data.\n               </p>\n\n            </li>\n            <li>\n               <p>\n                  <b>Consideration 2</b> - If both of the\n                  <code>x-amz-copy-source-if-none-match</code> and\n                  <code>x-amz-copy-source-if-modified-since</code> headers are present in the\n               request as follows:</p>\n               <p>\n                  <code>x-amz-copy-source-if-none-match</code> condition evaluates to\n                  <code>false</code>, and;</p>\n               <p>\n                  <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n                  <code>true</code>;</p>\n               <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.\n               </p>\n            </li>\n         </ul>\n         <p>\n            <b>Versioning</b>\n         </p>\n         <p>If your bucket has versioning enabled, you could have multiple versions of the same\n         object. By default, <code>x-amz-copy-source</code> identifies the current version of the\n         object to copy. If the current version is a delete marker and you don't specify a versionId\n         in the <code>x-amz-copy-source</code>, Amazon S3 returns a 404 error, because the object does\n         not exist. If you specify versionId in the <code>x-amz-copy-source</code> and the versionId\n         is a delete marker, Amazon S3 returns an HTTP 400 error, because you are not allowed to specify\n         a delete marker as a version for the <code>x-amz-copy-source</code>. </p>\n         <p>You can optionally specify a specific version of the source object to copy by adding the\n            <code>versionId</code> subresource as shown in the following example:</p>\n         <p>\n            <code>x-amz-copy-source: /bucket/object?versionId=version id</code>\n         </p>\n\n         <p class=\"title\">\n            <b>Special Errors</b>\n         </p>\n         <ul>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>Code: NoSuchUpload</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: The specified multipart upload does not exist. The upload\n                        ID might be invalid, or the multipart upload might have been aborted or\n                        completed.</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>HTTP Status Code: 404 Not Found</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>Code: InvalidRequest</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: The specified copy source is not supported as a byte-range\n                        copy source.</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>HTTP Status Code: 400 Bad Request</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n\n      \n\n\n\n\n         <p class=\"title\">\n            <b>Related Resources</b>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
+        "smithy.api#documentation": "<p>Uploads a part by copying data from an existing object as data source. You specify the\n         data source by adding the request header <code>x-amz-copy-source</code> in your request and\n         a byte range by adding the request header <code>x-amz-copy-source-range</code> in your\n         request. </p>\n         <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>\n         <note>\n            <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>\n            action and provide data in your request.</p>\n         </note>\n\n         <p>You must initiate a multipart upload before you can upload any part. In response to your\n         initiate request. Amazon S3 returns a unique identifier, the upload ID, that you must include in\n         your upload part request.</p>\n         <p>For more information about using the <code>UploadPartCopy</code> operation, see the\n         following:</p>\n\n         <ul>\n            <li>\n               <p>For conceptual information about multipart uploads, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html\">Uploading Objects Using Multipart\n                  Upload</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>For information about permissions required to use the multipart upload API, see\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html\">Multipart Upload  and\n                  Permissions</a> in the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>For information about copying objects using a single atomic action vs. a multipart\n               upload, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/ObjectOperations.html\">Operations on Objects</a> in\n               the <i>Amazon S3 User Guide</i>.</p>\n            </li>\n            <li>\n               <p>For information about using server-side encryption with customer-provided\n               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>\n            </li>\n         </ul>\n         <p>Note the following additional considerations about the request headers\n            <code>x-amz-copy-source-if-match</code>, <code>x-amz-copy-source-if-none-match</code>,\n            <code>x-amz-copy-source-if-unmodified-since</code>, and\n            <code>x-amz-copy-source-if-modified-since</code>:</p>\n         <p> </p>\n         <ul>\n            <li>\n               <p>\n                  <b>Consideration 1</b> - If both of the\n                  <code>x-amz-copy-source-if-match</code> and\n                  <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the\n               request as follows:</p>\n               <p>\n                  <code>x-amz-copy-source-if-match</code> condition evaluates to <code>true</code>,\n               and;</p>\n               <p>\n                  <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to\n                  <code>false</code>;</p>\n               <p>Amazon S3 returns <code>200 OK</code> and copies the data.\n               </p>\n\n            </li>\n            <li>\n               <p>\n                  <b>Consideration 2</b> - If both of the\n                  <code>x-amz-copy-source-if-none-match</code> and\n                  <code>x-amz-copy-source-if-modified-since</code> headers are present in the\n               request as follows:</p>\n               <p>\n                  <code>x-amz-copy-source-if-none-match</code> condition evaluates to\n                  <code>false</code>, and;</p>\n               <p>\n                  <code>x-amz-copy-source-if-modified-since</code> condition evaluates to\n                  <code>true</code>;</p>\n               <p>Amazon S3 returns <code>412 Precondition Failed</code> response code.\n               </p>\n            </li>\n         </ul>\n         <p>\n            <b>Versioning</b>\n         </p>\n         <p>If your bucket has versioning enabled, you could have multiple versions of the same\n         object. By default, <code>x-amz-copy-source</code> identifies the current version of the\n         object to copy. If the current version is a delete marker and you don't specify a versionId\n         in the <code>x-amz-copy-source</code>, Amazon S3 returns a 404 error, because the object does\n         not exist. If you specify versionId in the <code>x-amz-copy-source</code> and the versionId\n         is a delete marker, Amazon S3 returns an HTTP 400 error, because you are not allowed to specify\n         a delete marker as a version for the <code>x-amz-copy-source</code>. </p>\n         <p>You can optionally specify a specific version of the source object to copy by adding the\n            <code>versionId</code> subresource as shown in the following example:</p>\n         <p>\n            <code>x-amz-copy-source: /bucket/object?versionId=version id</code>\n         </p>\n\n         <p class=\"title\">\n            <b>Special Errors</b>\n         </p>\n         <ul>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>Code: NoSuchUpload</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: The specified multipart upload does not exist. The upload\n                        ID might be invalid, or the multipart upload might have been aborted or\n                        completed.</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>HTTP Status Code: 404 Not Found</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n            <li>\n               <ul>\n                  <li>\n                     <p>\n                        <i>Code: InvalidRequest</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>Cause: The specified copy source is not supported as a byte-range\n                        copy source.</i>\n                     </p>\n                  </li>\n                  <li>\n                     <p>\n                        <i>HTTP Status Code: 400 Bad Request</i>\n                     </p>\n                  </li>\n               </ul>\n            </li>\n         </ul>\n\n      \n\n\n\n\n         <p class=\"title\">\n            <b>Related Resources</b>\n         </p>\n         <ul>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html\">CreateMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPart.html\">UploadPart</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html\">CompleteMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html\">AbortMultipartUpload</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html\">ListParts</a>\n               </p>\n            </li>\n            <li>\n               <p>\n                  <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html\">ListMultipartUploads</a>\n               </p>\n            </li>\n         </ul>",
         "smithy.api#http": {
           "method": "PUT",
           "uri": "/{Bucket}/{Key+}?x-id=UploadPartCopy",