@nocobase/plugin-file-manager 1.6.0-beta.7 → 1.6.0-beta.9

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

@@ -1,118 +1,176 @@
-/// <reference types="node" />
-import { EndpointParameterInstructions } from "@aws-sdk/middleware-endpoint";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import { Handler, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, MiddlewareStack } from "@aws-sdk/types";
-import { PutObjectOutput, PutObjectRequest } from "../models/models_0";
+import { Command as $Command } from "@smithy/smithy-client";
+import { MetadataBearer as __MetadataBearer, StreamingBlobPayloadInputTypes } from "@smithy/types";
+import { PutObjectOutput, PutObjectRequest } from "../models/models_1";
 import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
-declare type PutObjectCommandInputType = Omit<PutObjectRequest, "Body"> & {
-    /**
-     * For *`PutObjectRequest["Body"]`*, see {@link PutObjectRequest.Body}.
-     */
-    Body?: PutObjectRequest["Body"] | string | Uint8Array | Buffer;
-};
 /**
- * This interface extends from `PutObjectRequest` interface. There are more parameters than `Body` defined in {@link PutObjectRequest}
+ * @public
  */
-export interface PutObjectCommandInput extends PutObjectCommandInputType {
+export type { __MetadataBearer };
+export { $Command };
+/**
+ * @public
+ *
+ * The input for {@link PutObjectCommand}.
+ */
+export interface PutObjectCommandInput extends Omit<PutObjectRequest, "Body"> {
+    Body?: StreamingBlobPayloadInputTypes;
 }
+/**
+ * @public
+ *
+ * The output of {@link PutObjectCommand}.
+ */
 export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBearer {
 }
+declare const PutObjectCommand_base: {
+    new (input: PutObjectCommandInput): import("@smithy/smithy-client").CommandImpl<PutObjectCommandInput, PutObjectCommandOutput, S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    new (__0_0: PutObjectCommandInput): import("@smithy/smithy-client").CommandImpl<PutObjectCommandInput, PutObjectCommandOutput, S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
+};
 /**
- * <p>Adds an object to a bucket. You must have WRITE permissions on a bucket to add an object
- *          to it.</p>
- *
- *
- *          <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the
- *          entire object to the bucket.</p>
- *
- *          <p>Amazon S3 is a distributed system. If it receives multiple write requests for the same object
- *          simultaneously, it overwrites all but the last object written. Amazon S3 does not provide object
- *          locking; if you need this, make sure to build it into your application layer or use
- *          versioning instead.</p>
- *
- *          <p>To ensure that data is not corrupted traversing the network, use the
- *             <code>Content-MD5</code> header. When you use this header, Amazon S3 checks the object
- *          against the provided MD5 value and, if they do not match, returns an error. Additionally,
- *          you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to
- *          the calculated MD5 value.</p>
+ * <p>Adds an object to a bucket.</p>
  *          <note>
  *             <ul>
  *                <li>
- *                   <p>To successfully complete the <code>PutObject</code> request, you must have the
- *                <code>s3:PutObject</code> in your IAM permissions.</p>
+ *                   <p>Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added
+ *                   the entire object to the bucket. You cannot use <code>PutObject</code> to only
+ *                   update a single piece of metadata for an existing object. You must put the entire
+ *                   object with updated metadata if you want to update some values.</p>
  *                </li>
  *                <li>
- *                   <p>To successfully change the objects acl of your <code>PutObject</code> request,
- *                you must have the <code>s3:PutObjectAcl</code> in your IAM permissions.</p>
+ *                   <p>If your bucket uses the bucket owner enforced setting for Object Ownership,
+ *                   ACLs are disabled and no longer affect permissions. All objects written to the
+ *                   bucket by any account will be owned by the bucket owner.</p>
  *                </li>
  *                <li>
- *                   <p> The <code>Content-MD5</code> header is required for any request to upload an object
- *                   with a retention period configured using Amazon S3 Object Lock. For more information about
- *                   Amazon S3 Object Lock, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lock-overview.html">Amazon S3 Object Lock Overview</a>
- *                   in the <i>Amazon S3 User Guide</i>. </p>
+ *                   <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>amzn-s3-demo-bucket</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com/<i>key-name</i>
+ *                      </code>. Path-style requests are not supported. For more information about endpoints in Availability Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/endpoint-directory-buckets-AZ.html">Regional and Zonal endpoints for directory buckets in Availability Zones</a> in the
+ *     <i>Amazon S3 User Guide</i>. For more information about endpoints in Local Zones, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-lzs-for-directory-buckets.html">Concepts for directory buckets in Local Zones</a> in the
+ *     <i>Amazon S3 User Guide</i>.</p>
  *                </li>
  *             </ul>
  *          </note>
- *          <p>
- *             <b>Server-side Encryption</b>
- *          </p>
- *          <p>You can optionally request server-side encryption. With server-side encryption, Amazon S3 encrypts
- *          your data as it writes it to disks in its data centers and decrypts the data
- *          when you access it. You have the option to provide your own encryption key or use Amazon Web Services
- *          managed encryption keys (SSE-S3 or SSE-KMS). For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using Server-Side
- *             Encryption</a>.</p>
- *          <p>If you request server-side encryption using Amazon Web Services Key Management Service (SSE-KMS), you can enable
- *          an S3 Bucket Key at the object-level. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the
- *          <i>Amazon S3 User Guide</i>.</p>
- *          <p>
- *             <b>Access Control List (ACL)-Specific Request
- *          Headers</b>
- *          </p>
- *          <p>You can use headers to grant ACL- based permissions. By default, all objects are
- *          private. Only the owner has full access control. When adding a new object, you can grant
- *          permissions to individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These
- *          permissions are then added to the ACL on the object. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html">Access Control List
- *             (ACL) Overview</a> and <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-using-rest-api.html">Managing ACLs Using the REST
- *             API</a>. </p>
- *          <p>If the bucket that you're uploading objects to uses the bucket owner enforced setting
- *          for S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that
- *          use this setting only accept PUT requests that don't specify an ACL or PUT requests that
- *          specify bucket owner full control ACLs, such as the <code>bucket-owner-full-control</code> canned
- *          ACL or an equivalent form of this ACL expressed in the XML format. PUT requests that contain other
- *          ACLs (for example, custom grants to certain Amazon Web Services accounts) fail and return a
- *             <code>400</code> error with the error code
- *          <code>AccessControlListNotSupported</code>.</p>
- *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html"> Controlling ownership of
- *          objects and disabling ACLs</a> in the <i>Amazon S3 User Guide</i>.</p>
- *          <note>
- *             <p>If your bucket uses the bucket owner enforced setting for Object Ownership,
- *             all objects written to the bucket by any account will be owned by the bucket owner.</p>
- *          </note>
- *          <p>
- *             <b>Storage Class Options</b>
- *          </p>
- *          <p>By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The
- *          STANDARD storage class provides high durability and high availability. Depending on
- *          performance needs, you can specify a different Storage Class. Amazon S3 on Outposts only uses
- *          the OUTPOSTS Storage Class. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage Classes</a> in the
- *          <i>Amazon S3 User Guide</i>.</p>
- *
- *
- *          <p>
- *             <b>Versioning</b>
- *          </p>
- *          <p>If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID
- *          for the object being stored. Amazon S3 returns this ID in the response. When you enable
- *          versioning for a bucket, if Amazon S3 receives multiple write requests for the same object
- *          simultaneously, it stores all of the objects.</p>
- *          <p>For more information about versioning, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding Objects to
- *             Versioning Enabled Buckets</a>. For information about returning the versioning state
- *          of a bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
- *
- *
- *          <p class="title">
- *             <b>Related Resources</b>
- *          </p>
+ *          <p>Amazon S3 is a distributed system. If it receives multiple write requests for the same object
+ *          simultaneously, it overwrites all but the last object written. However, Amazon S3 provides
+ *          features that can modify this behavior:</p>
+ *          <ul>
+ *             <li>
+ *                <p>
+ *                   <b>S3 Object Lock</b> - To prevent objects from
+ *                being deleted or overwritten, you can use <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html">Amazon S3 Object
+ *                   Lock</a> in the <i>Amazon S3 User Guide</i>.</p>
+ *                <note>
+ *                   <p>This functionality is not supported for directory buckets.</p>
+ *                </note>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <b>If-None-Match</b> - Uploads the object only if the object key name does not already exist in the specified bucket. Otherwise, Amazon S3 returns a <code>412 Precondition Failed</code> error. If a conflicting operation occurs during the upload, S3 returns a <code>409 ConditionalRequestConflict</code> response. On a 409 failure, retry the upload.</p>
+ *                <p>Expects the * character (asterisk).</p>
+ *                <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/conditional-requests.html">Add preconditions to S3 operations with conditional requests</a> in the <i>Amazon S3 User Guide</i> or <a href="https://datatracker.ietf.org/doc/rfc7232/">RFC 7232</a>.
+ *             </p>
+ *                <note>
+ *                   <p>This functionality is not supported for S3 on Outposts.</p>
+ *                </note>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <b>S3 Versioning</b> - When you enable versioning
+ *                for a bucket, if Amazon S3 receives multiple write requests for the same object
+ *                simultaneously, it stores all versions of the objects. For each write request that is
+ *                made to the same object, Amazon S3 automatically generates a unique version ID of that
+ *                object being stored in Amazon S3. You can retrieve, replace, or delete any version of the
+ *                object. For more information about versioning, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/AddingObjectstoVersioningEnabledBuckets.html">Adding
+ *                   Objects to Versioning-Enabled Buckets</a> in the <i>Amazon S3 User
+ *                   Guide</i>. For information about returning the versioning state of a
+ *                bucket, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetBucketVersioning.html">GetBucketVersioning</a>. </p>
+ *                <note>
+ *                   <p>This functionality is not supported for directory buckets.</p>
+ *                </note>
+ *             </li>
+ *          </ul>
+ *          <dl>
+ *             <dt>Permissions</dt>
+ *             <dd>
+ *                <ul>
+ *                   <li>
+ *                      <p>
+ *                         <b>General purpose bucket permissions</b> - The
+ *                         following permissions are required in your policies when your
+ *                            <code>PutObject</code> request includes specific headers.</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>
+ *                               <b>
+ *                                  <code>s3:PutObject</code>
+ *                               </b> -
+ *                               To successfully complete the <code>PutObject</code> request, you must
+ *                               always have the <code>s3:PutObject</code> permission on a bucket to
+ *                               add an object to it.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <b>
+ *                                  <code>s3:PutObjectAcl</code>
+ *                               </b> - To successfully change the objects ACL of your
+ *                                  <code>PutObject</code> request, you must have the
+ *                                  <code>s3:PutObjectAcl</code>.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>
+ *                               <b>
+ *                                  <code>s3:PutObjectTagging</code>
+ *                               </b> - To successfully set the tag-set with your
+ *                                  <code>PutObject</code> request, you must have the
+ *                                  <code>s3:PutObjectTagging</code>.</p>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <b>Directory bucket permissions</b> - To grant access to this API operation on a directory bucket, we recommend that you use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateSession.html">
+ *                            <code>CreateSession</code>
+ *                         </a> API operation for session-based authorization. Specifically, you grant the <code>s3express:CreateSession</code> permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the <code>CreateSession</code> API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another <code>CreateSession</code> API call to generate a new session token for use.
+ * 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>
+ *                   </li>
+ *                </ul>
+ *             </dd>
+ *             <dt>Data integrity with Content-MD5</dt>
+ *             <dd>
+ *                <ul>
+ *                   <li>
+ *                      <p>
+ *                         <b>General purpose bucket</b> - To ensure that
+ *                         data is not corrupted traversing the network, use the
+ *                            <code>Content-MD5</code> header. When you use this header, Amazon S3 checks
+ *                         the object against the provided MD5 value and, if they do not match, Amazon S3
+ *                         returns an error. Alternatively, when the object's ETag is its MD5 digest,
+ *                         you can calculate the MD5 while putting the object to Amazon S3 and compare the
+ *                         returned ETag to the calculated MD5 value.</p>
+ *                   </li>
+ *                   <li>
+ *                      <p>
+ *                         <b>Directory bucket</b> -
+ *                         This functionality is not supported for directory buckets.</p>
+ *                   </li>
+ *                </ul>
+ *             </dd>
+ *             <dt>HTTP Host header syntax</dt>
+ *             <dd>
+ *                <p>
+ *                   <b>Directory buckets </b> - The HTTP Host header syntax is <code>
+ *                      <i>Bucket-name</i>.s3express-<i>zone-id</i>.<i>region-code</i>.amazonaws.com</code>.</p>
+ *             </dd>
+ *          </dl>
+ *          <p>For more information about related Amazon S3 APIs, see the following:</p>
  *          <ul>
  *             <li>
  *                <p>
@@ -131,24 +189,274 @@ export interface PutObjectCommandOutput extends PutObjectOutput, __MetadataBeare
  * import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3"; // ES Modules import
  * // const { S3Client, PutObjectCommand } = require("@aws-sdk/client-s3"); // CommonJS import
  * const client = new S3Client(config);
+ * const input = { // PutObjectRequest
+ *   ACL: "private" || "public-read" || "public-read-write" || "authenticated-read" || "aws-exec-read" || "bucket-owner-read" || "bucket-owner-full-control",
+ *   Body: "MULTIPLE_TYPES_ACCEPTED", // see \@smithy/types -> StreamingBlobPayloadInputTypes
+ *   Bucket: "STRING_VALUE", // required
+ *   CacheControl: "STRING_VALUE",
+ *   ContentDisposition: "STRING_VALUE",
+ *   ContentEncoding: "STRING_VALUE",
+ *   ContentLanguage: "STRING_VALUE",
+ *   ContentLength: Number("long"),
+ *   ContentMD5: "STRING_VALUE",
+ *   ContentType: "STRING_VALUE",
+ *   ChecksumAlgorithm: "CRC32" || "CRC32C" || "SHA1" || "SHA256" || "CRC64NVME",
+ *   ChecksumCRC32: "STRING_VALUE",
+ *   ChecksumCRC32C: "STRING_VALUE",
+ *   ChecksumCRC64NVME: "STRING_VALUE",
+ *   ChecksumSHA1: "STRING_VALUE",
+ *   ChecksumSHA256: "STRING_VALUE",
+ *   Expires: new Date("TIMESTAMP"),
+ *   IfMatch: "STRING_VALUE",
+ *   IfNoneMatch: "STRING_VALUE",
+ *   GrantFullControl: "STRING_VALUE",
+ *   GrantRead: "STRING_VALUE",
+ *   GrantReadACP: "STRING_VALUE",
+ *   GrantWriteACP: "STRING_VALUE",
+ *   Key: "STRING_VALUE", // required
+ *   WriteOffsetBytes: Number("long"),
+ *   Metadata: { // Metadata
+ *     "<keys>": "STRING_VALUE",
+ *   },
+ *   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
+ *   StorageClass: "STANDARD" || "REDUCED_REDUNDANCY" || "STANDARD_IA" || "ONEZONE_IA" || "INTELLIGENT_TIERING" || "GLACIER" || "DEEP_ARCHIVE" || "OUTPOSTS" || "GLACIER_IR" || "SNOW" || "EXPRESS_ONEZONE",
+ *   WebsiteRedirectLocation: "STRING_VALUE",
+ *   SSECustomerAlgorithm: "STRING_VALUE",
+ *   SSECustomerKey: "STRING_VALUE",
+ *   SSECustomerKeyMD5: "STRING_VALUE",
+ *   SSEKMSKeyId: "STRING_VALUE",
+ *   SSEKMSEncryptionContext: "STRING_VALUE",
+ *   BucketKeyEnabled: true || false,
+ *   RequestPayer: "requester",
+ *   Tagging: "STRING_VALUE",
+ *   ObjectLockMode: "GOVERNANCE" || "COMPLIANCE",
+ *   ObjectLockRetainUntilDate: new Date("TIMESTAMP"),
+ *   ObjectLockLegalHoldStatus: "ON" || "OFF",
+ *   ExpectedBucketOwner: "STRING_VALUE",
+ * };
  * const command = new PutObjectCommand(input);
  * const response = await client.send(command);
+ * // { // PutObjectOutput
+ * //   Expiration: "STRING_VALUE",
+ * //   ETag: "STRING_VALUE",
+ * //   ChecksumCRC32: "STRING_VALUE",
+ * //   ChecksumCRC32C: "STRING_VALUE",
+ * //   ChecksumCRC64NVME: "STRING_VALUE",
+ * //   ChecksumSHA1: "STRING_VALUE",
+ * //   ChecksumSHA256: "STRING_VALUE",
+ * //   ChecksumType: "COMPOSITE" || "FULL_OBJECT",
+ * //   ServerSideEncryption: "AES256" || "aws:kms" || "aws:kms:dsse",
+ * //   VersionId: "STRING_VALUE",
+ * //   SSECustomerAlgorithm: "STRING_VALUE",
+ * //   SSECustomerKeyMD5: "STRING_VALUE",
+ * //   SSEKMSKeyId: "STRING_VALUE",
+ * //   SSEKMSEncryptionContext: "STRING_VALUE",
+ * //   BucketKeyEnabled: true || false,
+ * //   Size: Number("long"),
+ * //   RequestCharged: "requester",
+ * // };
+ *
  * ```
  *
+ * @param PutObjectCommandInput - {@link PutObjectCommandInput}
+ * @returns {@link PutObjectCommandOutput}
  * @see {@link PutObjectCommandInput} for command's `input` shape.
  * @see {@link PutObjectCommandOutput} for command's `response` shape.
  * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
  *
+ * @throws {@link EncryptionTypeMismatch} (client fault)
+ *  <p>
+ *          The existing object was created with a different encryption type.
+ *          Subsequent write requests must include the appropriate encryption
+ *          parameters in the request or while creating the session.
+ *       </p>
+ *
+ * @throws {@link InvalidRequest} (client fault)
+ *  <p>You may receive this error in multiple cases. Depending on the reason for the error, you may receive one of the messages below:</p>
+ *          <ul>
+ *             <li>
+ *                <p>Cannot specify both a write offset value and user-defined object metadata for existing objects.</p>
+ *             </li>
+ *             <li>
+ *                <p>Checksum Type mismatch occurred, expected checksum Type: sha1, actual checksum Type: crc32c.</p>
+ *             </li>
+ *             <li>
+ *                <p>Request body cannot be empty when 'write offset' is specified.</p>
+ *             </li>
+ *          </ul>
+ *
+ * @throws {@link InvalidWriteOffset} (client fault)
+ *  <p>
+ *          The write offset value that you specified does not match the current object size.
+ *       </p>
+ *
+ * @throws {@link TooManyParts} (client fault)
+ *  <p>
+ *          You have attempted to add more parts than the maximum of 10000
+ *          that are allowed for this object. You can use the CopyObject operation
+ *          to copy this object to another and then add more data to the newly copied object.
+ *       </p>
+ *
+ * @throws {@link S3ServiceException}
+ * <p>Base exception class for all service exceptions from S3 service.</p>
+ *
+ * @public
+ * @example To upload an object
+ * ```javascript
+ * // The following example uploads an object to a versioning-enabled bucket. The source file is specified using Windows file syntax. S3 returns VersionId of the newly created object.
+ * const input = {
+ *   "Body": "HappyFace.jpg",
+ *   "Bucket": "examplebucket",
+ *   "Key": "HappyFace.jpg"
+ * };
+ * const command = new PutObjectCommand(input);
+ * const response = await client.send(command);
+ * /* response ==
+ * {
+ *   "ETag": "\"6805f2cfc46c0f04559748bb039d69ae\"",
+ *   "VersionId": "tpf3zF08nBplQK1XLOefGskR7mGDwcDk"
+ * }
+ * *\/
+ * // example id: to-upload-an-object-1481760101010
+ * ```
+ *
+ * @example To upload an object (specify optional headers)
+ * ```javascript
+ * // The following example uploads an object. The request specifies optional request headers to directs S3 to use specific storage class and use server-side encryption.
+ * const input = {
+ *   "Body": "HappyFace.jpg",
+ *   "Bucket": "examplebucket",
+ *   "Key": "HappyFace.jpg",
+ *   "ServerSideEncryption": "AES256",
+ *   "StorageClass": "STANDARD_IA"
+ * };
+ * const command = new PutObjectCommand(input);
+ * const response = await client.send(command);
+ * /* response ==
+ * {
+ *   "ETag": "\"6805f2cfc46c0f04559748bb039d69ae\"",
+ *   "ServerSideEncryption": "AES256",
+ *   "VersionId": "CG612hodqujkf8FaaNfp8U..FIhLROcp"
+ * }
+ * *\/
+ * // example id: to-upload-an-object-(specify-optional-headers)
+ * ```
+ *
+ * @example To create an object.
+ * ```javascript
+ * // The following example creates an object. If the bucket is versioning enabled, S3 returns version ID in response.
+ * const input = {
+ *   "Body": "filetoupload",
+ *   "Bucket": "examplebucket",
+ *   "Key": "objectkey"
+ * };
+ * const command = new PutObjectCommand(input);
+ * const response = await client.send(command);
+ * /* response ==
+ * {
+ *   "ETag": "\"6805f2cfc46c0f04559748bb039d69ae\"",
+ *   "VersionId": "Bvq0EDKxOcXLJXNo_Lkz37eM3R4pfzyQ"
+ * }
+ * *\/
+ * // example id: to-create-an-object-1483147613675
+ * ```
+ *
+ * @example To upload an object and specify optional tags
+ * ```javascript
+ * // The following example uploads an object. The request specifies optional object tags. The bucket is versioned, therefore S3 returns version ID of the newly created object.
+ * const input = {
+ *   "Body": "c:\\HappyFace.jpg",
+ *   "Bucket": "examplebucket",
+ *   "Key": "HappyFace.jpg",
+ *   "Tagging": "key1=value1&key2=value2"
+ * };
+ * const command = new PutObjectCommand(input);
+ * const response = await client.send(command);
+ * /* response ==
+ * {
+ *   "ETag": "\"6805f2cfc46c0f04559748bb039d69ae\"",
+ *   "VersionId": "psM2sYY4.o1501dSx8wMvnkOzSBB.V4a"
+ * }
+ * *\/
+ * // example id: to-upload-an-object-and-specify-optional-tags-1481762310955
+ * ```
+ *
+ * @example To upload an object and specify server-side encryption and object tags
+ * ```javascript
+ * // The following example uploads an object. The request specifies the optional server-side encryption option. The request also specifies optional object tags. If the bucket is versioning enabled, S3 returns version ID in response.
+ * const input = {
+ *   "Body": "filetoupload",
+ *   "Bucket": "examplebucket",
+ *   "Key": "exampleobject",
+ *   "ServerSideEncryption": "AES256",
+ *   "Tagging": "key1=value1&key2=value2"
+ * };
+ * const command = new PutObjectCommand(input);
+ * const response = await client.send(command);
+ * /* response ==
+ * {
+ *   "ETag": "\"6805f2cfc46c0f04559748bb039d69ae\"",
+ *   "ServerSideEncryption": "AES256",
+ *   "VersionId": "Ri.vC6qVlA4dEnjgRV4ZHsHoFIjqEMNt"
+ * }
+ * *\/
+ * // example id: to-upload-an-object-and-specify-server-side-encryption-and-object-tags-1483398331831
+ * ```
+ *
+ * @example To upload object and specify user-defined metadata
+ * ```javascript
+ * // The following example creates an object. The request also specifies optional metadata. If the bucket is versioning enabled, S3 returns version ID in response.
+ * const input = {
+ *   "Body": "filetoupload",
+ *   "Bucket": "examplebucket",
+ *   "Key": "exampleobject",
+ *   "Metadata": {
+ *     "metadata1": "value1",
+ *     "metadata2": "value2"
+ *   }
+ * };
+ * const command = new PutObjectCommand(input);
+ * const response = await client.send(command);
+ * /* response ==
+ * {
+ *   "ETag": "\"6805f2cfc46c0f04559748bb039d69ae\"",
+ *   "VersionId": "pSKidl4pHBiNwukdbcPXAIs.sshFFOc0"
+ * }
+ * *\/
+ * // example id: to-upload-object-and-specify-user-defined-metadata-1483396974757
+ * ```
+ *
+ * @example To upload an object and specify canned ACL.
+ * ```javascript
+ * // The following example uploads and object. The request specifies optional canned ACL (access control list) to all READ access to authenticated users. If the bucket is versioning enabled, S3 returns version ID in response.
+ * const input = {
+ *   "ACL": "authenticated-read",
+ *   "Body": "filetoupload",
+ *   "Bucket": "examplebucket",
+ *   "Key": "exampleobject"
+ * };
+ * const command = new PutObjectCommand(input);
+ * const response = await client.send(command);
+ * /* response ==
+ * {
+ *   "ETag": "\"6805f2cfc46c0f04559748bb039d69ae\"",
+ *   "VersionId": "Kirh.unyZwjQ69YxcQLA8z4F5j3kJJKr"
+ * }
+ * *\/
+ * // example id: to-upload-an-object-and-specify-canned-acl-1483397779571
+ * ```
+ *
  */
-export declare class PutObjectCommand extends $Command<PutObjectCommandInput, PutObjectCommandOutput, S3ClientResolvedConfig> {
-    readonly input: PutObjectCommandInput;
-    static getEndpointParameterInstructions(): EndpointParameterInstructions;
-    constructor(input: PutObjectCommandInput);
-    /**
-     * @internal
-     */
-    resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<PutObjectCommandInput, PutObjectCommandOutput>;
-    private serialize;
-    private deserialize;
+export declare class PutObjectCommand extends PutObjectCommand_base {
+    /** @internal type navigation helper, not in runtime. */
+    protected static __types: {
+        api: {
+            input: PutObjectRequest;
+            output: PutObjectOutput;
+        };
+        sdk: {
+            input: PutObjectCommandInput;
+            output: PutObjectCommandOutput;
+        };
+    };
 }
-export {};