@aws-sdk/client-s3
Version:
AWS SDK for JavaScript S3 Client for Node.js, Browser and React Native
223 lines (222 loc) • 14.1 kB
TypeScript
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 { CopyObjectOutput, CopyObjectRequest } from "../models/models_0";
import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client";
export interface CopyObjectCommandInput extends CopyObjectRequest {
}
export interface CopyObjectCommandOutput extends CopyObjectOutput, __MetadataBearer {
}
/**
* <p>Creates a copy of an object that is already stored in Amazon S3.</p>
* <note>
* <p>You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your
* object up to 5 GB in size in a single atomic action using this API. However, to copy an
* object greater than 5 GB, you must use the multipart upload Upload Part - Copy
* (UploadPartCopy) API. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjctsUsingRESTMPUapi.html">Copy Object Using the
* REST Multipart Upload API</a>.</p>
* </note>
* <p>All copy requests must be authenticated. Additionally, you must have
* <i>read</i> access to the source object and <i>write</i>
* access to the destination bucket. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html">REST Authentication</a>. Both the Region
* that you want to copy the object from and the Region that you want to copy the object to
* must be enabled for your account.</p>
* <p>A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3
* is copying the files. If the error occurs before the copy action starts, you receive a
* standard Amazon S3 error. If the error occurs during the copy operation, the error response is
* embedded in the <code>200 OK</code> response. This means that a <code>200 OK</code>
* response can contain either a success or an error. Design your application to parse the
* contents of the response and handle it appropriately.</p>
* <p>If the copy is successful, you receive a response with information about the copied
* object.</p>
* <note>
* <p>If the request is an HTTP 1.1 request, the response is chunk encoded. If it were not,
* it would not contain the content-length, and you would need to read the entire
* body.</p>
* </note>
* <p>The copy request charge is based on the storage class and Region that you specify for
* the destination object. For pricing information, see <a href="http://aws.amazon.com/s3/pricing/">Amazon S3 pricing</a>.</p>
* <important>
* <p>Amazon S3 transfer acceleration does not support cross-Region copies. If you request a
* cross-Region copy using a transfer acceleration endpoint, you get a 400 <code>Bad
* Request</code> error. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html">Transfer Acceleration</a>.</p>
* </important>
* <p>
* <b>Metadata</b>
* </p>
* <p>When copying an object, you can preserve all metadata (default) or specify new metadata.
* However, the ACL is not preserved and is set to private for the user making the request. To
* override the default ACL setting, specify a new ACL when generating a copy request. For
* more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_ACLs_UsingACLs.html">Using ACLs</a>. </p>
* <p>To specify whether you want the object metadata copied from the source object or
* replaced with metadata provided in the request, you can optionally add the
* <code>x-amz-metadata-directive</code> header. When you grant permissions, you can use
* the <code>s3:x-amz-metadata-directive</code> condition key to enforce certain metadata
* behavior when objects are uploaded. For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/amazon-s3-policy-keys.html">Specifying Conditions in a
* Policy</a> in the <i>Amazon S3 User Guide</i>. For a complete list of
* Amazon S3-specific condition keys, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/list_amazons3.html">Actions, Resources, and Condition Keys for
* Amazon S3</a>.</p>
* <p>
* <b>x-amz-copy-source-if Headers</b>
* </p>
* <p>To only copy an object under certain conditions, such as whether the <code>Etag</code>
* matches or whether the object was modified before or after a specified date, use the
* following request parameters:</p>
* <ul>
* <li>
* <p>
* <code>x-amz-copy-source-if-match</code>
* </p>
* </li>
* <li>
* <p>
* <code>x-amz-copy-source-if-none-match</code>
* </p>
* </li>
* <li>
* <p>
* <code>x-amz-copy-source-if-unmodified-since</code>
* </p>
* </li>
* <li>
* <p>
* <code>x-amz-copy-source-if-modified-since</code>
* </p>
* </li>
* </ul>
* <p> If both the <code>x-amz-copy-source-if-match</code> and
* <code>x-amz-copy-source-if-unmodified-since</code> headers are present in the request
* and evaluate as follows, Amazon S3 returns <code>200 OK</code> and copies the data:</p>
* <ul>
* <li>
* <p>
* <code>x-amz-copy-source-if-match</code> condition evaluates to true</p>
* </li>
* <li>
* <p>
* <code>x-amz-copy-source-if-unmodified-since</code> condition evaluates to
* false</p>
* </li>
* </ul>
*
* <p>If both the <code>x-amz-copy-source-if-none-match</code> and
* <code>x-amz-copy-source-if-modified-since</code> headers are present in the request and
* evaluate as follows, Amazon S3 returns the <code>412 Precondition Failed</code> response
* code:</p>
* <ul>
* <li>
* <p>
* <code>x-amz-copy-source-if-none-match</code> condition evaluates to false</p>
* </li>
* <li>
* <p>
* <code>x-amz-copy-source-if-modified-since</code> condition evaluates to
* true</p>
* </li>
* </ul>
*
* <note>
* <p>All headers with the <code>x-amz-</code> prefix, including
* <code>x-amz-copy-source</code>, must be signed.</p>
* </note>
* <p>
* <b>Server-side encryption</b>
* </p>
* <p>When you perform a CopyObject operation, you can optionally use the appropriate encryption-related
* headers to encrypt the object using server-side encryption with Amazon Web Services managed encryption keys
* (SSE-S3 or SSE-KMS) or a customer-provided encryption key. With server-side encryption, Amazon S3
* encrypts your data as it writes it to disks in its data centers and decrypts the data when
* you access it. For more information about server-side encryption, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html">Using
* Server-Side Encryption</a>.</p>
* <p>If a target object uses SSE-KMS, you can enable an S3 Bucket Key for the object. For more
* information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/bucket-key.html">Amazon S3 Bucket Keys</a> in the <i>Amazon S3 User Guide</i>.</p>
* <p>
* <b>Access Control List (ACL)-Specific Request
* Headers</b>
* </p>
* <p>When copying an object, you can optionally 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 copying objects to uses the bucket owner enforced setting for
* S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that
* use this setting only accept PUT requests that don't specify an ACL or PUT requests that
* specify bucket owner full control ACLs, such as the <code>bucket-owner-full-control</code> canned
* ACL or an equivalent form of this ACL expressed in the XML format.</p>
* <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>Checksums</b>
* </p>
* <p>When copying an object, if it has a checksum, that checksum will be copied to the new object
* by default. When you copy the object over, you may optionally specify a different checksum
* algorithm to use with the <code>x-amz-checksum-algorithm</code> header.</p>
* <p>
* <b>Storage Class Options</b>
* </p>
* <p>You can use the <code>CopyObject</code> action to change the storage class of an
* object that is already stored in Amazon S3 using the <code>StorageClass</code> parameter. For
* more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html">Storage
* Classes</a> in the <i>Amazon S3 User Guide</i>.</p>
* <p>
* <b>Versioning</b>
* </p>
* <p>By default, <code>x-amz-copy-source</code> identifies the current version of an object
* to copy. If the current version is a delete marker, Amazon S3 behaves as if the object was
* deleted. To copy a different version, use the <code>versionId</code> subresource.</p>
* <p>If you enable versioning on the target bucket, Amazon S3 generates a unique version ID for
* the object being copied. This version ID is different from the version ID of the source
* object. Amazon S3 returns the version ID of the copied object in the
* <code>x-amz-version-id</code> response header in the response.</p>
* <p>If you do not enable versioning or suspend it on the target bucket, the version ID that
* Amazon S3 generates is always null.</p>
* <p>If the source object's storage class is GLACIER, you must restore a copy of this object
* before you can use it as a source object for the copy operation. For more information, see
* <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_RestoreObject.html">RestoreObject</a>.</p>
* <p>The following operations are related to <code>CopyObject</code>:</p>
* <ul>
* <li>
* <p>
* <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html">PutObject</a>
* </p>
* </li>
* <li>
* <p>
* <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObject.html">GetObject</a>
* </p>
* </li>
* </ul>
* <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/CopyingObjectsExamples.html">Copying
* Objects</a>.</p>
* @example
* Use a bare-bones client and the command you need to make an API call.
* ```javascript
* import { S3Client, CopyObjectCommand } from "@aws-sdk/client-s3"; // ES Modules import
* // const { S3Client, CopyObjectCommand } = require("@aws-sdk/client-s3"); // CommonJS import
* const client = new S3Client(config);
* const command = new CopyObjectCommand(input);
* const response = await client.send(command);
* ```
*
* @see {@link CopyObjectCommandInput} for command's `input` shape.
* @see {@link CopyObjectCommandOutput} for command's `response` shape.
* @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape.
*
*/
export declare class CopyObjectCommand extends $Command<CopyObjectCommandInput, CopyObjectCommandOutput, S3ClientResolvedConfig> {
readonly input: CopyObjectCommandInput;
static getEndpointParameterInstructions(): EndpointParameterInstructions;
constructor(input: CopyObjectCommandInput);
/**
* @internal
*/
resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<CopyObjectCommandInput, CopyObjectCommandOutput>;
private serialize;
private deserialize;
}