ecr.signing.verifyVerify an image's signatures against the trusted keys
status: signed (a trusted key verifies a signature), untrusted (signatures, none trusted), unsigned. Each signature: format (cosign-bundle, cosign-simplesigning, notation-jws), status (verified, untrusted, invalid, unsupported — keyless cosign and COSE notation), the key that verified it and why not. deployable says whether the policy would let it deploy.
Request syntax
GET /ecr/api/repositories/{repoId}/images/{manifestId}/signaturesPath parameters
repoIdRequiredstring
Constraints: uuid
manifestIdRequiredstring
Constraints: uuid
Response
200 with { digest, status, deployable, requireSignedImages, signatures }: each signature { signatureDigest, format, status, keyId, keyName, signer, detail }. 404 when the repository or the image does not exist.
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:DescribeImageSignatures 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 verify repoId manifestIdcurl -X GET "https://console.platform-development.deutschecloud.app/ecr/api/repositories/repoId/images/manifestId/signatures" \
-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_signing_verify.