|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
This operation initiates a multipart upload (see Uploading Large Archives in Parts (Multipart Upload)). Amazon Glacier creates a multipart upload resource and returns its ID in the response. You use this Upload ID in subsequent multipart upload operations.
When you initiate a multipart upload, you specify the part size in number of bytes. The part size must be a megabyte (1024 KB) multiplied by a power of 2—for example, 1048576 (1 MB), 2097152 (2 MB), 4194304 (4 MB), 8388608 (8 MB), and so on. The minimum allowable part size is 1 MB, and the maximum is 4 GB.
Every part you upload using this upload ID, except the last one, must have the same size. The last one can be the same size or smaller. For example, suppose you want to upload a 16.2 MB file. If you initiate the multipart upload with a part size of 4 MB, you will upload four parts of 4 MB each and one part of 0.2 MB.
You don't need to know the size of the archive when you start a multipart upload because Amazon Glacier does not require you to specify the overall archive size.
After you complete the multipart upload, Amazon Glacier removes the multipart upload resource referenced by the ID. Amazon Glacier will also remove the multipart upload resource if you cancel the multipart upload or it may be removed if there is no activity for a period of 24 hours. The ID may still be available after 24 hours, but applications should not expect this behavior.
To initiate a multipart upload, you send an HTTP
POST request to the URI of the
multipart-uploads subresource of the vault in which you want to save
the archive. The request must include the part size and can optionally include a
description of the archive.
VaultName/multipart-uploads Host: glacier.us-east-1.amazonaws.com Date:
SignatureValuex-amz-glacier-version: 2012-06-01 x-amz-archive-description:
AccountId is the AWS Account ID. This value must match the AWS Account ID associated with the credentials used to sign the request. You can either specify AWS Account ID or optionally a '
-' in which case Amazon Glacier uses the AWS Account ID associated with the credentials used to sign the request. If you specify your Account ID, do not include dashes in it.
This operation does not use request parameters.
This operation uses the following request headers, in addition to the request headers that are common to all operations. For more information about the common request headers, see Common Request Headers.
The size of each part except the last, in bytes. The last part can be smaller than this part size.
Constraints: The part size must be a megabyte (1024 KB) multiplied by a power of 2—for example, 1048576 (1 MB), 2097152 (2 MB), 4194304 (4 MB), 8388608 (8 MB), and so on. The minimum allowable part size is 1 MB, and the maximum is 4 GB (4096 MB).
Archive description you are uploading in parts. It can be a plain-language description or some unique identifier you choose to assign. When you retrieve a vault inventory (see Initiate a Job (POST jobs) ), the inventory includes this description for each of the archives it returns in response. Leading whitespace in archive descriptions is removed.
Constraints: The description must be less than or equal to 1024 bytes. The allowable characters are 7 bit ASCII without control codes, specifically ASCII values 32-126 decimal or 0x20-0x7E hexadecimal.
This operation does not have a request body.
In the response, Amazon Glacier creates a multipart upload resource identified by an ID and returns the relative URI path of the multipart upload ID.
HTTP/1.1 201 Created x-amzn-RequestId: x-amzn-RequestId Date: Date Location: Location x-amz-multipart-upload-id: multiPartUploadId
A successful response includes the following response headers, in addition to the response headers that are common to all operations. For more information about common response headers, see Common Response Headers.
The relative URI path of the multipart upload ID Amazon Glacier created. You use this URI path to scope your requests to upload parts, and to complete the multipart upload.
The ID of the multipart upload. This value is also included
as part of the
This operation does not return a response body.
For information about Amazon Glacier exceptions and error messages, see Error Responses.
The following example initiates a multipart upload by sending an HTTP
request to the URI of the
multipart-uploads subresource of a vault
examplevault. The request includes headers to specify the part
size of 4 MB (4194304 bytes) and the optional archive description.
POST /-/vaults/examplevault/multipart-uploads Host: glacier.us-east-1.amazonaws.com x-amz-Date: 20120325T120000Z x-amz-archive-description: MyArchive-101 x-amz-part-size: 4194304 x-amz-glacier-version: 2012-06-01 Authorization: AWS4-HMAC-SHA256 Credential=AKIAIOSFODNN7EXAMPLE/20120525/us-east-1/glacier/aws4_request,SignedHeaders=host;x-amz-date;x-amz-glacier-version,Signature=9257c16da6b25a715ce900a5b45b03da0447acf430195dcb540091b12966f2a2
Amazon Glacier creates a multipart upload resource and adds it to the
multipart-uploads subresource of the vault. The
Location response header includes the relative URI path to the
multipart upload ID.
HTTP/1.1 201 Created x-amzn-RequestId: AAABZpJrTyioDC_HsOmHae8EZp_uBSJr6cnGOLKp_XJCl-Q Date: Sun, 25 Mar 2012 12:00:00 GMT Location: /111122223333/vaults/examplevault/multipart-uploads/OW2fM5iVylEpFEMM9_HpKowRapC3vn5sSL39_396UW9zLFUWVrnRHaPjUJddQ5OxSHVXjYtrN47NBZ-khxOjyEXAMPLE x-amz-multipart-upload-id: OW2fM5iVylEpFEMM9_HpKowRapC3vn5sSL39_396UW9zLFUWVrnRHaPjUJddQ5OxSHVXjYtrN47NBZ-khxOjyEXAMPLE
For information about uploading individual parts, see Upload Part (PUT uploadID).