s3.bucket-objects.multipart-part-urls

Presigned PUT URLs for up to 100 parts, valid 15 minutes

POST /s3/api/buckets/{name}/objects/multipart/part-urlsIAM s3:PutObjectChanges stateDestructive

Send each part as the body of a PUT to its url; the answer carries the part’s ETag, which the console origin may read from the browser.

Request syntax

POST /s3/api/buckets/{name}/objects/multipart/part-urls
{
  "key": "string",
  "uploadId": "string",
  "partNumbers": "array of number"
}

Path parameters

  • nameRequired

    string

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

Request body

  • keyRequired

    string

    Key the upload was started for

    Constraints: min 1 chars

  • uploadIdRequired

    string

    From multipart create

    Constraints: 1-1024 chars

  • partNumbersRequired

    array of number

    Up to 100 part numbers (1–10000)

    Constraints: integer, 1-10000

Response

200; data is { urls: [{ partNumber, url }], method: "PUT", expiresInSeconds }: one presigned URL per part number asked for, valid 900 seconds.

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-part-urls name --key example --upload-id example --part-numbers '[1]'

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