ecr.images.scanTrigger a vulnerability scan on an image
POST /ecr/api/repositories/{repoId}/images/{manifestId}/scanIAM ecr:ScanImageChanges state
Request syntax
POST /ecr/api/repositories/{repoId}/images/{manifestId}/scanPath parameters
repoIdRequiredstring
Constraints: uuid
manifestIdRequiredstring
Constraints: uuid
Response
202 with { scanId }: the scan is recorded as pending and runs in the background (by digest, so a moved tag does not matter); read it with GET …/scan or /ecr/api/scan-results/{scanId}. 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:ScanImage 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 images scan repoId manifestIdcurl -X POST "https://console.platform-development.deutschecloud.app/ecr/api/repositories/repoId/images/manifestId/scan" \
-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_images_scan.