s3.bucket-lifecycle.setReplace the lifecycle rules
rules: [{ id, prefix?, enabled?, expirationDays?, noncurrentVersionExpirationDays?, abortIncompleteMultipartUploadDays?, expiredObjectDeleteMarker? }]. Applied by object storage once a day.
Request syntax
PUT /s3/api/buckets/{name}/lifecycle
{
"rules": "array of json"
}Path parameters
nameRequiredstring
Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/
Request body
rulesRequiredarray of json
The rules, replacing the current ones; each has its own id and at least one action (expirationDays, noncurrentVersionExpirationDays, abortIncompleteMultipartUploadDays or expiredObjectDeleteMarker)
Response
200; data is { rules }: the lifecycle rules as object storage now holds them.
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:PutLifecycleConfiguration 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-lifecycle set name --rules '["example"]'curl -X PUT "https://console.platform-development.deutschecloud.app/s3/api/buckets/name/lifecycle" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"rules":["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-lifecycle_set.