Search (SHIFT+S)
ECS Management API
ECS Object Service API
-
Amazon S3
- S3 Bucket
- S3 Bucket ACL
- S3 Bucket Cors
- S3 Bucket Empty Status Operations
- S3 Bucket Is Stale Allowed
- S3 Bucket Lifecycle
- S3 Bucket List Fanout (Cloud DVR)
- S3 Bucket List Uploads
- S3 Bucket Location
- S3 Bucket Lock Configuration Operations
- S3 Bucket Object Lock Operations
- S3 Bucket Policy
- S3 Bucket Versioning
- S3 Bucket Versions
- S3 Data Node
- S3 Metadata Key List
- S3 Metadata Key System List
- S3 Metadata Search
- S3 Multi Object Delete
- S3 Object
- S3 Object ACL
- S3 Object Detailed Replication Status Operations
- S3 Object Init Uploads
- S3 Object Legal Hold Operations
- S3 Object Replication Info Operations
- S3 Object Retention Operations
- S3 Object Tagging Operations
- S3 Object Uploads
- S3 Options
- S3 Ping
- S3 Retention Update Operation
- S3 Select Operations
- EMC Atmos
- OpenStack Swift
ECS API Changes
Upload Part
PUT /{object_name}?uploadId={upload_id}&partNumber={partNumber}
Uploads a part when performing a multi-part upload.
Used in the following two cases:
Upload a part in the multipart upload where the part content is encoded in the content header.
Copy a range from an existing object as part of the multi-part upload. The object and the bytes to be copied from the object are specified in the request headers.
URL Format
Host Style: http://bucketname.ns1.emc.com/{object_name}?uploadId={upload_id}&partNumber={partNumber}
Path Style: http://ns1.emc.com/bucketname/{object_name}?uploadId={upload_id}&partNumber={partNumber}
Alternatively, both styles can specify the namespace using the x-emc-namespace header.
Query Parameters
| uploadId | Unique identifier of the multi-part upload. Obtained from the Object Init Uploads operation. |
| partNumber | Unique identifier for a part that also defines its position in the created object. A number between 1 to 10000. |
Request Headers
| Content-Length | required | Specifies the size of the part in bytes (case 1) |
| Content-MD5 | optional | Base64-encoded 128-bit MD5 digest of the part data (Case 1) |
| Expect | optional | When your application uses 100-continue, it does not send the request body until it receives an acknowledgment. If the message is rejected based on the headers, the body of the message is not sent (Case 1) Valid values : 100-continue |
| x-amz-copy-source | required | Name of the source bucket and the source object key name separated by / (Case 2) |
| x-amz-copy-source-range | optional | Range of bytes to copy from the source object |
| x-amz-copy-source-if-match | optional | Perform a copy if the source object entity tag (ETag) matches the specified value (Case 2) |
| x-amz-copy-source-if-none-match | optional | Perform a copy if the source object entity tag (ETag) is different than the value specified using this header (Case 2) |
| x-amz-copy-source-if-unmodified-since | optional | Perform a copy if the source object is not modified after the time specified using this header (Case 2) |
| x-amz-copy-source-if-modified-since | optional | Perform a copy if the source object is modified after the time specified using this header (Case 2) |
Prerequisites
The following conditions must be met in order to call this operation.
A multi-part upload must have been initiated and returned a valid uploadId
User should have WRITE permission on the bucket
BaseUrl used in a host-style request URL should be pre-configured using the ECS Management API or the ECS Portal (for example, emc.com in the URL: bucketname.ns1.emc.com).
Namespace and bucket corresponding to this object should exist
Request Payload
No Request Payload
Response Headers
| x-amz-copy-source-version-id | optional | Version number of the source object copied if versioning is enabled on the source bucket (Case 2) |
Response Body
Response indicating Success or Failure for this operation.