ecr.signing.put-policyTurn "only signed images deploy" on or off
{"requireSignedImages": true} makes the deploy service refuse an image from the registry that no trusted key signed, and every image from another registry. Images Deutsche Cloud builds from source pass by provenance. New deployments only — running apps keep running.
Request syntax
PUT /ecr/api/signing-policy
{
"requireSignedImages": "boolean"
}Request body
requireSignedImagesRequiredboolean
true: a new deployment is refused unless a trusted key signed its image (images built from source pass by provenance; images from another registry are refused). false: signatures are shown, nothing is refused. Running apps are not affected either way
Response
200 with { requireSignedImages, keys, warning }: keys counts the trusted keys; warning is set when the policy is on with no key trusted (every image except those built from source is refused), else null.
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:PutSigningPolicy 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 signing put-policy --require-signed-imagescurl -X PUT "https://console.platform-development.deutschecloud.app/ecr/api/signing-policy" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"requireSignedImages":true}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ecr_signing_put-policy.