s3.bucket-objects.multipart-create

Start a multipart upload (files over 5 GiB must use one)

POST /s3/api/buckets/{name}/objects/multipartIAM s3:PutObjectChanges stateDestructive

Answers { key, uploadId }. Then ask multipart-part-urls for presigned part URLs, PUT each part (5 MiB minimum except the last) and keep the ETag it answers, then multipart-complete. Until completed or aborted, the stored parts count as storage.

Request syntax

POST /s3/api/buckets/{name}/objects/multipart
{
  "key": "string",
  "contentType": "string"
}

Path parameters

  • nameRequired

    string

    Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/

Request body

  • keyRequired

    string

    Key the assembled object is stored under

    Constraints: min 1 chars

  • contentTypeOptional

    string

    Content-Type the object is stored with; application/octet-stream when omitted

    Constraints: max 255 chars

Response

201; data is { key, uploadId }: the upload id every later multipart call takes.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow s3:PutObject on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud s3 bucket-objects multipart-create name --key example

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_s3_bucket-objects_multipart-create.