Uploads
Multipart Uploads into a Bucket
This operation initiates a multipart upload and returns an upload ID. This upload ID is used to associate all of the parts in the specific multipart upload. You specify this upload ID in each of your subsequent upload part requests. You also include this upload ID in the final request to either complete or abort the multipart upload request.
The bucket name.
my-bucketObject key for which the multipart upload is to be initiated.
Specifies caching behavior along the request/reply chain.
Specifies presentational information for the object.
Specifies what content encodings have been applied to the object and thus what decoding mechanisms must be applied to obtain the media-type referenced by the Content-Type header field.
A standard MIME type describing the format of the object data.
The date and time at which the object is no longer cacheable.
The server-side encryption algorithm used when storing this object in IONOS Object Storage (AES256).
IONOS Object Storage uses the STANDARD Storage Class to store newly created objects. The STANDARD storage class provides high durability and high availability.
If the bucket is configured as a website, redirects requests for this object to another object in the same bucket or to an external URL. IONOS Object Storage stores the value of this header in the object metadata.
Specifies the algorithm to use to when encrypting the object (AES256).
Specifies the customer-provided encryption key for IONOS Object Storage to use in encrypting data. This value is used to store the object and then it is discarded; IONOS Object Storage does not store the encryption key. The key must be appropriate for use with the algorithm specified in the x-amz-server-side-encryption-customer-algorithm header.
Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. IONOS Object Storage uses this header for a message integrity check to ensure that the encryption key was transmitted without error.
Specifies the Object Lock mode that you want to apply to the uploaded object.
Specifies the date and time when you want the Object Lock to expire.
Specifies whether you want to apply a Legal Hold to the uploaded object.
A map of metadata to store with the stored object.
POST /{Bucket}/{Key} HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Accept: */*
Successful operation
<?xml version="1.0" encoding="UTF-8"?>
<InitiateMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Bucket>my-bucket</Bucket>
<Key>video.mp4</Key>
<UploadId>M2ZiOTBhODgxNDE2OTM0MDU0NzQwNjQ</UploadId>
</InitiateMultipartUploadResult>
Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request. This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the `max-parts` request parameter. If your multipart upload consists of more than 1,000 parts, the response returns an `IsTruncated` field with the value of true, and a `NextPartNumberMarker` element. In subsequent `ListParts` requests you can include the part-number-marker query string parameter and set its value to the `NextPartNumberMarker` field value from the previous response.
The bucket name.
my-bucketObject key for which the multipart upload was initiated.
Sets the maximum number of parts to return.
Specifies the part after which listing should begin. Only parts with higher part numbers will be listed.
Upload ID identifying the multipart upload whose parts are being listed.
Pagination token
GET /{Bucket}/{Key} HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Accept: */*
Success
<?xml version="1.0" encoding="UTF-8"?>
<ListPartsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Bucket>my-bucket</Bucket>
<Key>mytext.txt</Key>
<UploadId>M2Y1YjZhODgwODE2OTM0MTE0NzU3MjM</UploadId>
<Initiator>
<ID>fb201d53c82788a9ed3208e1fe6eea8f</ID>
<DisplayName></DisplayName>
</Initiator>
<Owner>
<ID>fb201d53c82788a9ed3208e1fe6eea8f</ID>
<DisplayName></DisplayName>
</Owner>
<StorageClass>STANDARD</StorageClass>
<PartNumberMarker>0</PartNumberMarker>
<MaxParts>4</MaxParts>
<IsTruncated>false</IsTruncated>
<Part>
<PartNumber>1</PartNumber>
<LastModified>2023-08-30T16:04:35.723Z</LastModified>
<ETag>"e5f418115de697af0d466b971e24f3ef"</ETag>
<Size>37</Size>
</Part>
<Part>
<PartNumber>2</PartNumber>
<LastModified>2023-08-30T16:04:35.723Z</LastModified>
<ETag>"b14f0bc5827d7168afc8b4c1ef3b7899"</ETag>
<Size>81</Size>
</Part>
<Part>
<PartNumber>3</PartNumber>
<LastModified>2023-08-30T16:04:35.723Z</LastModified>
<ETag>"c597dd54bd9338b1f1814a3813bd731d"</ETag>
<Size>33</Size>
</Part>
</ListPartsResult>
Completes a multipart upload by assembling previously uploaded parts.
After successfully uploading all relevant parts of an upload, you call this operation to complete the upload. When IONOS Object Storage receives this request, it concatenates all the parts in ascending order by part number to create a new object. The parts list must be included in the Complete Multipart Upload request. You must ensure that the parts list is complete. This operation concatenates the parts that you provide in the list. For each part in the list, you must provide the part number and the `ETag` value, returned after that part was uploaded.
A Complete Multipart Upload request could take several minutes to process. After IONOS Object Storage begins processing the request, it sends an HTTP response header indicating a 200 OK response. While processing is in progress, IONOS Object Storage sends white space characters on a regular basis to keep the connection from timing out. Because a request may fail after receiving the initial 200 OK response, it is advisable to check the response body to establish whether the request was successful.
`CompleteMultipartUpload` has the following special errors:
Error code: `EntityTooSmall`
Description: Your proposed upload is smaller than the minimum allowed object size. Each part must be at least 5 MB in size, except the last part.
400 Bad Request
Error code: `InvalidPart`
Description: One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag.
400 Bad Request
Error code: `InvalidPartOrder`
Description: The list of parts was not in ascending order. The parts list must be specified in order by part number.
400 Bad Request
Error code: `NoSuchUpload`
Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
404 Not Found
The bucket name.
my-bucketObject key for which the multipart upload was initiated.
ID for the initiated multipart upload.
POST /{Bucket}/{Key} HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Content-Type: application/xml
Accept: */*
Content-Length: 417
"<CompleteMultipartUpload>
<Part>
<PartNumber>1</PartNumber>
<ETag>"e5f418115de697af0d466b971e24f3ef"</ETag>
</Part>
<Part>
<PartNumber>2</PartNumber>
<ETag>"b14f0bc5827d7168afc8b4c1ef3b7899"</ETag>
</Part>
<Part>
<PartNumber>3</PartNumber>
<ETag>"c597dd54bd9338b1f1814a3813bd731d"</ETag>
</Part>
</CompleteMultipartUpload>
"Success
<CompleteMultipartUpload>
<Part>
<PartNumber>1</PartNumber>
<ETag>"e5f418115de697af0d466b971e24f3ef"</ETag>
</Part>
<Part>
<PartNumber>2</PartNumber>
<ETag>"b14f0bc5827d7168afc8b4c1ef3b7899"</ETag>
</Part>
<Part>
<PartNumber>3</PartNumber>
<ETag>"c597dd54bd9338b1f1814a3813bd731d"</ETag>
</Part>
</CompleteMultipartUpload>
Uploads a part in a multipart upload.
In this operation, you provide part data in your request. However, you have an option to specify your existing IONOS Object Storage object as a data source for the part you are uploading. To upload a part from an existing object, you use the `UploadPartCopy` operation.
You must initiate a multipart upload (see `CreateMultipartUpload`) before you can upload any part. In response to your initiate request, IONOS Object Storage 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. Each part must be at least 5 MB in size, except the last part. There is no size limit on the last part of your multipart upload.
To ensure that data is not corrupted when traversing the network, specify the `Content-MD5` header in the upload part request. IONOS Object Storage checks the part data against the provided MD5 value. If they do not match, IONOS Object Storage returns an error.
If the upload request is signed with Signature Version 4, then IONOS Object Storage uses the `x-amz-content-sha256` header as a checksum instead of `Content-MD5`.
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, IONOS Object Storage frees up the parts storage and stops charging you for the parts storage.
The bucket name.
my-bucketObject key for which the multipart upload was initiated.
Part number of part being uploaded. This is a positive integer between 1 and 10,000.
Upload ID identifying the multipart upload whose part is being uploaded.
Size of the body in bytes. This parameter is useful when the size of the body cannot be determined automatically.
The base64 encoded MD5 digest of the message (without the headers) according to RFC 1864.
Specifies the algorithm to use to when encrypting the object (AES256).
Specifies the customer-provided encryption key for IONOS Object Storage to use in encrypting data. This value is used to store the object and then it is discarded; IONOS Object Storage does not store the encryption key. The key must be appropriate for use with the algorithm specified in the x-amz-server-side-encryption-customer-algorithm header. This must be the same encryption key specified in the initiate multipart upload request.
Specifies the 128-bit MD5 digest of the encryption key according to RFC 1321. IONOS Object Storage uses this header for a message integrity check to ensure that the encryption key was transmitted without error.
Object data.
{"Date":"2016-12-29T21:44:28.000Z","ETag":"d8c2eafd90c266e19ab9dcacc479f8af","x-amz-server-side-encryption-customer-algorithm":"AES256","x-amz-server-side-encryption-customer-key-MD5":"ZjQrne1X/iTcskbY2example"}PUT /{Bucket}/{Key} HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Content-Type: application/xml
Accept: */*
Content-Length: 15
"<?xml version=1.0?>
<Body>text</Body>
"Success
<?xml version="1.0"?>
<object>
<Date>2016-12-29T21:44:28.000Z</Date>
<ETag>d8c2eafd90c266e19ab9dcacc479f8af</ETag>
<x-amz-server-side-encryption-customer-algorithm>AES256</x-amz-server-side-encryption-customer-algorithm>
<x-amz-server-side-encryption-customer-key-MD5>ZjQrne1X/iTcskbY2example</x-amz-server-side-encryption-customer-key-MD5>
</object>
This operation aborts a multipart upload. After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts.
The bucket name.
my-bucketKey of the object for which the multipart upload was initiated. Possible values: length ≥ 1
Upload ID that identifies the multipart upload.
DELETE /{Bucket}/{Key} HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Accept: */*
<?xml version="1.0"?>
<object/>
This operation lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.
This operation returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the `max-uploads` parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain an `IsTruncated` element with the value true. To list the additional multipart uploads, use the `key-marker` and `upload-id-marker` request parameters.
In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.
The bucket name.
my-bucketRequests IONOS Object Storage to encode the object keys in the response and specifies the encoding method to use. An object key may contain any Unicode character; however, XML 1.0 parser cannot parse some characters, such as characters with an ASCII value from 0 to 10. For characters that are not supported in XML 1.0, you can add this parameter to request that IONOS Object Storage encode the keys in the response.
Sets the maximum number of multipart uploads, from 1 to 1,000, to return in the response body. 1,000 is the maximum number of uploads that can be returned in a response.
Lists in-progress uploads only for those keys that begin with the specified prefix. You can use prefixes to separate a bucket into different grouping of keys. (You can think of using prefix to make groups in the same way you'd use a folder in a file system.)
Together with key-marker, specifies the multipart upload after which listing should begin. If key-marker is not specified, the upload-id-marker parameter is ignored. Otherwise, any multipart uploads for a key equal to the key-marker might be included in the list only if they have an upload ID lexicographically greater than the specified upload-id-marker.
Pagination limit
Pagination token
Pagination token
GET /{Bucket} HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Accept: */*
Successful operation
<?xml version="1.0" encoding="UTF-8"?>
<ListMultipartUploadsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Bucket>my-bucket</Bucket>
<KeyMarker/>
<UploadIdMarker/>
<NextKeyMarker/>
<NextUploadIdMarker/>
<MaxUploads>1000</MaxUploads>
<IsTruncated>false</IsTruncated>
<Upload>
<Key>video.mp4</Key>
<UploadId>M2ZiOTBhODgxNDE2OTM0MDU0NzQwNjQ</UploadId>
<Initiator>
<ID>fb201d53c82788a9ed3208e1fe6eea2f</ID>
<DisplayName></DisplayName>
</Initiator>
<Owner>
<ID>fb201d53c82788a9ed3208e1fe6eea2f</ID>
<DisplayName></DisplayName>
</Owner>
<StorageClass>STANDARD</StorageClass>
<Initiated>2023-08-30T14:24:34.064Z</Initiated>
</Upload>
</ListMultipartUploadsResult>
Uploads a part by copying data from an existing object as data source. You specify the data source by adding the request header `x-amz-copy-source` in your request and a byte range by adding the request header `x-amz-copy-source-range` in your request.
The minimum allowable part size for a multipart upload is 5 MB.
Instead of using an existing object as part data, you might use the `UploadPart` operation and provide data in your request.
You must initiate a multipart upload before you can upload any part. In response to your initiate request. IONOS Object Storage returns a unique identifier, the upload ID, that you must include in your upload part request.
The bucket name.
my-bucketObject key for which the multipart upload was initiated.
Part number of part being copied. This is a positive integer between 1 and 10,000.
Upload ID identifying the multipart upload whose part is being copied.
\/.+\/.+Copies the object if its entity tag (ETag) matches the specified tag.
Copies the object if it has been modified since the specified time.
Copies the object if its entity tag (ETag) is different than the specified ETag.
Copies the object if it hasn't been modified since the specified time.
The range of bytes to copy from the source object. The range value must use the form bytes=first-last, where the first and last are the zero-based byte offsets to copy. For example, bytes=0-9 indicates that you want to copy the first 10 bytes of the source. You can copy a range only if the source object is greater than 5 MB.
Specifies the algorithm to use to when encrypting the object (AES256).
PUT /{Bucket}/{Key} HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
x-amz-copy-source: text
Accept: */*
Success
<?xml version="1.0"?>
<object>
<CopyPartResult>
<ETag>65d16d19e65a7508a51f043180edcc36</ETag>
<LastModified>2016-12-29T21:44:28.000Z</LastModified>
</CopyPartResult>
</object>
Was this helpful?