@aws-sdk/client-s3

/// <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 { UploadPartOutput, UploadPartRequest } from "../models/models_1"; import { S3ClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../S3Client"; declare type UploadPartCommandInputType = Omit<UploadPartRequest, "Body"> & { /** * For *`UploadPartRequest["Body"]`*, see {@link UploadPartRequest.Body}. */ Body?: UploadPartRequest["Body"] | string | Uint8Array | Buffer; }; /** * This interface extends from `UploadPartRequest` interface. There are more parameters than `Body` defined in {@link UploadPartRequest} */ export interface UploadPartCommandInput extends UploadPartCommandInputType { } export interface UploadPartCommandOutput extends UploadPartOutput, __MetadataBearer { } /** * Uploads a part in a multipart upload. * <note> * In this operation, you provide part data in your request. However, you have an option * to specify your existing Amazon S3 object as a data source for the part you are uploading. To * upload a part from an existing object, you use the <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_UploadPartCopy.html">UploadPartCopy</a> operation. * * </note> * * You must initiate a multipart upload (see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>) * before you can upload any part. In response to your initiate request, Amazon S3 returns an * upload ID, a unique identifier, that you must include in your upload part request. * 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. * 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 Amazon S3 User Guide. * 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. * * If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the * <code>x-amz-content-sha256</code> header as a checksum instead of * <code>Content-MD5</code>. For more information see <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html">Authenticating Requests: Using the Authorization Header (Amazon Web Services Signature Version * 4)</a>. * * * * * Note: After you initiate multipart upload and upload * one or more parts, you must either complete or abort multipart upload in order to stop * getting charged for storage of the uploaded parts. Only after you either complete or abort * multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts * storage. * * 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 * Amazon S3 User Guide . * For information on the permissions required to use the multipart upload API, go to * <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html">Multipart Upload and * Permissions</a> in the Amazon S3 User Guide. * * You can optionally request server-side encryption where Amazon S3 encrypts your data as it * writes it to disks in its data centers and decrypts it for you when you access it. You have * the option of providing your own encryption key, or you can use the Amazon Web Services managed encryption * keys. If you choose to provide your own encryption key, the request headers you provide in * the request must match the headers you used in the request to initiate the upload by using * <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>. For more information, go to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html">Using Server-Side Encryption</a> in * the Amazon S3 User Guide. * * Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are * using a customer-provided encryption key, you don't need to specify the encryption * parameters in each UploadPart request. Instead, you only need to specify the server-side * encryption parameters in the initial Initiate Multipart request. For more information, see * <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a>. * * If you requested server-side encryption using a customer-provided encryption key in your * initiate multipart upload request, you must provide identical encryption information in * each part upload using the following headers. * * * <ul> * <li> * x-amz-server-side-encryption-customer-algorithm * </li> * <li> * x-amz-server-side-encryption-customer-key * </li> * <li> * x-amz-server-side-encryption-customer-key-MD5 * </li> * </ul> * * * Special Errors * * <ul> * <li> * <ul> * <li> * * Code: NoSuchUpload * * </li> * <li> * * Cause: The specified multipart upload does not exist. The upload * ID might be invalid, or the multipart upload might have been aborted or * completed. * * </li> * <li> * * HTTP Status Code: 404 Not Found * * </li> * <li> * * SOAP Fault Code Prefix: Client * * </li> * </ul> * </li> * </ul> * * * * * * * * Related Resources * * <ul> * <li> * * <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateMultipartUpload.html">CreateMultipartUpload</a> * * </li> * <li> * * <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_CompleteMultipartUpload.html">CompleteMultipartUpload</a> * * </li> * <li> * * <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_AbortMultipartUpload.html">AbortMultipartUpload</a> * * </li> * <li> * * <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListParts.html">ListParts</a> * * </li> * <li> * * <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListMultipartUploads.html">ListMultipartUploads</a> * * </li> * </ul> * @example * Use a bare-bones client and the command you need to make an API call. * ```javascript * import { S3Client, UploadPartCommand } from "@aws-sdk/client-s3"; // ES Modules import * // const { S3Client, UploadPartCommand } = require("@aws-sdk/client-s3"); // CommonJS import * const client = new S3Client(config); * const command = new UploadPartCommand(input); * const response = await client.send(command); * ``` * * @see {@link UploadPartCommandInput} for command's `input` shape. * @see {@link UploadPartCommandOutput} for command's `response` shape. * @see {@link S3ClientResolvedConfig | config} for S3Client's `config` shape. * */ export declare class UploadPartCommand extends $Command<UploadPartCommandInput, UploadPartCommandOutput, S3ClientResolvedConfig> { readonly input: UploadPartCommandInput; static getEndpointParameterInstructions(): EndpointParameterInstructions; constructor(input: UploadPartCommandInput); /** * @internal */ resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: S3ClientResolvedConfig, options?: __HttpHandlerOptions): Handler<UploadPartCommandInput, UploadPartCommandOutput>; private serialize; private deserialize; } export {};