s3.bucket-objects.upload-urlA presigned PUT for one key, valid 15 minutes
Send the file as the body of a PUT to url with the returned headers (Content-Type). The console origin may read the answer from the browser; other origins need the bucket's CORS rules.
Request syntax
POST /s3/api/buckets/{name}/objects/upload-url
{
"key": "string",
"contentType": "string"
}Path parameters
nameRequiredstring
Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/
Request body
keyRequiredstring
Key the file is stored under, e.g. photos/2026/cat.jpg
Constraints: min 1 chars
contentTypeOptionalstring
Content-Type the object is stored with; application/octet-stream when omitted
Constraints: max 255 chars
Response
200; data is { url, headers, method: "PUT", expiresInSeconds }: the presigned URL, the headers (Content-Type) the PUT must carry, 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 upload-url name --key examplecurl -X POST "https://console.platform-development.deutschecloud.app/s3/api/buckets/name/objects/upload-url" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"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_upload-url.