UploadPart

Uploads a part in a multipart upload.

You must initiate a multipart upload (see CreateMultipartUpload) before you can upload any part. In response to your initiate request, Tebi returns an upload ID, a unique identifier, that you must include in your upload part request.

Tebi does not have any limitations on the number of parts or the minimum or maximum part size.

To ensure that data is not corrupted when traversing the network, specify the Content-MD5 header in the upload part request. Tebi checks the part data against the provided MD5 value. If they do not match, Tebi returns an error.

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. Once you either complete or abort multipart upload, Tebi stops charging you for the parts storage.

You must have Upload ACL to be able to call this action.

The following operations are related to UploadPart:

Request Syntax

1PUT /<KEY>?partNumber=<PART_NUMBER>&uploadId=<UPLOAD_ID> HTTP/1.1
2Host: <BUCKET>.s3.tebi.io
3Content-Length: <CONTENT_LENGTH>
4Content-MD5: <CONTENT_MD5>
5x-amz-server-side-encryption-customer-algorithm: <SSE_CUSTOMER_ALGORITHM>
6x-amz-server-side-encryption-customer-key: <SSE_CUSTOMER_KEY>
7x-amz-server-side-encryption-customer-key-MD5: <SSE_CUSTOMER_KEY_MD5>
8
9Body

  • <BUCKET>: Bucket name to which the upload was taking place. Required.

  • <KEY>: Key of the object for which the multipart upload was initiated. Required.

  • <PART_NUMBER>: Part number of part being uploaded.

  • <UPLOAD_ID>: Upload ID that identifies the multipart upload. Required.

  • <CONTENT_LENGTH>: Size of the body in bytes.

  • <CONTENT_MD5>: Base64-encoded 128-bit MD5 digest of the part data.

  • <SSE_CUSTOMER_ALGORITHM>: Specifies the algorithm to use when encrypting the object.

  • <SSE_CUSTOMER_KEY>: Specifies the customer-provided encryption key for Tebi to use in encrypting data.

  • <SSE_CUSTOMER_KEY_MD5>: Specifies the 128-bit MD5 digest of the encryption key.

The request accepts binary data.

Response Syntax

1HTTP/1.1 200
2Content-Length: 0
3ETag: ETag
4x-amz-server-side-encryption: ServerSideEncryption

If the action is successful, the service sends back an HTTP 200 response.

The response returns the following HTTP headers:

  • ETag: Entity tag that identifies the newly created object’s data.

  • x-amz-server-side-encryption: Server-side encryption algorithm used when storing this object.

See Also

Refer here for more information.