s3.access-keys.createCreate an S3 access key
POST /s3/api/access-keysIAM s3:CreateAccessKeyChanges state
The secretAccessKey is in this response and nowhere else; store it now. The key acts as the calling IAM user.
Request syntax
POST /s3/api/access-keys
{
"description": "string"
}Request body
descriptionOptionalstring
What the key is for
Constraints: max 200 chars
Response
201; data is the key (id, accessKeyId, description, status, iamUserId, createdAt) with its secretAccessKey and the S3 endpoint.
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:CreateAccessKey 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 access-keys createcurl -X POST "https://console.platform-development.deutschecloud.app/s3/api/access-keys" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_s3_access-keys_create.