CreateMultipartUpload
Returns an identifier that should be used in all further operations to load the object.
If custom metadata needs to be stored with the object, then it should be passed in this request.
POST /{bucket}/{key}?uploads HTTP/1.1
Parameter | Description |
bucket | Bucket name. |
key | Object key. The object will be saved in ColdStack under the specified name. |
Parameter | Description |
uploads | A flag denoting a composite load operation. |
Additionally, you can use the headings listed in the table below.
Heading | Description |
x-amz-meta-* | Custom object metadata.
All headers starting with x-amz-meta-ColdStack are treated as custom headers, they are not processed and stored in the form in which they are transmitted.
The total size of custom headers must not exceed 2KB. The size of the user data is defined as the length of the UTF-8 encoded string. The size takes into account both the names of the headings and their values. |
x-amz-storage-class | Object storage class.
Can have any of the following values:
- STANDARDto load an object into the standard storage.
- COLD, STANDARD_IAand NEARLINEto load the object into cold storage.
If the header is not specified, then the object is saved in the storage set in the bucket settings. |
The successful response contains additional data in XML format, the schema of which is described below.
<InitiateMultipartUploadResult>
<Bucket>bucket-name</Bucket>
<Key>object-key</Key>
<UploadId>upload-id</UploadId>
</InitiateMultipartUploadResult>
Tag | Description |
InitiateMultipartUploadResult | The root tag of the response.
Path: /InitiateMultipartUploadResult. |
Bucket | The name of the bucket into which the object is loaded.
Path: /InitiateMultipartUploadResult/Bucket. |
Key | The key that is associated with the object after the download is complete.
Path: /InitiateMultipartUploadResult/Key. |
UploadId | Download ID.
All subsequent upload operations must pass this identifier to ColdStack.
Path: /InitiateMultipartUploadResult/UploadId. |
Last modified 2yr ago