ColdStack Docs
  • Introduction
  • ColdStack FAQ
  • Binance Smart Chain Bridge
    • Release
    • Customer Support
    • FAQ
    • Step-by-Step Guide
  • Concepts
    • Bucket versioning
    • Logging actions with a bucket
  • Tools
    • Supported tools
      • CyberDuck S3 Client
      • S3 Browser
      • AWS CLI Console client
      • SDKs for different languages
        • JavaScript SDK
        • Using extended API with JavaScript
        • AWS SDK for Java
        • Python SDK (boto)
  • S3 Compatible API
    • How to use the API
    • Signing Requests
    • API Reference
      • Bucket
        • HeadBucket
        • ListObjects/ListObjectsV2
        • PutBucketVersioning
        • PutBucketLogging
        • RenameBucket
        • GetBucketLocation
        • ListBuckets
      • Object
        • PutObject
        • GetObject
        • HeadObject
        • RenameObject
        • PutObjectAcl
      • Multipart upload
        • General multipart upload order
        • CreateMultipartUpload
        • UploadPart
        • CompleteMultipartUpload
        • ListMultipartUploads
      • Analytics
        • GetStatistics
        • GetBandwidthAnalytics
        • GetStorageAnalytics
      • Common request headers
      • Common response headers
      • Responses
Powered by GitBook
On this page
  • Request
  • Answer

Was this helpful?

  1. S3 Compatible API
  2. API Reference
  3. Multipart upload

CreateMultipartUpload

PreviousGeneral multipart upload orderNextUploadPart

Last updated 4 years ago

Was this helpful?

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.

Request

POST /{bucket}/{key}?uploads HTTP/1.1

Path parameters

Parameter

Description

bucket

Bucket name.

key

Object key. The object will be saved in ColdStack under the specified name.

Query parameters

Parameter

Description

uploads

A flag denoting a composite load operation.

Headings

Use the required in the request .

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.

Answer

Headings

Answer codes

The successful response contains additional data in XML format, the schema of which is described below.

Data schema

<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.

The response can only contain .

For a list of possible answers, see the section .

common headers
general headers
Answers