iam.access-keys.set-expiry

Give every key of the organization that never expires an expiry

POST /iam/api/access-keys/set-expiryIAM iam:UpdateAccessKeyChanges stateDestructive

For keys made before keys expired. Keys Deutsche Cloud mints for app machines are left out; role session keys carry their own expiry.

Request syntax

POST /iam/api/access-keys/set-expiry
{
  "expiresInDays": "number"
}

Request body

  • expiresInDaysRequired

    number

    Days from now, at most the organization’s maximum

    Constraints: integer, 1-3650

Response

200 with { updated, expiresAt }: how many keys got the expiry, and the expiry.

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 iam:UpdateAccessKey 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 iam access-keys set-expiry --expires-in-days 1

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_access-keys_set-expiry.