ecr.auth.login-tokenMint a short-lived docker login token
Mints a 12-hour bearer credential for the whole org registry, so the IAM descriptor classifies GetAuthorizationToken as a write: the operation reports mutates: true and every issuance is audited. The answer carries the token id, which revokes it.
Request syntax
POST /ecr/api/login-tokenResponse
200 with { id, token, registryHost, expiresIn }: the token (shown only here) is the docker login password for registryHost ({org}.ecr.<domain>), valid for expiresIn seconds (43200, 12 hours); id revokes it.
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 ecr:GetAuthorizationToken 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 ecr auth login-tokencurl -X POST "https://console.platform-development.deutschecloud.app/ecr/api/login-token" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ecr_auth_login-token.