ec2.machine-images.deregister

Delete the provider snapshot and mark the image deregistered

DELETE /ec2/api/machine-images/{id}IAM ec2:DeregisterImageChanges stateDestructive

The row survives in the `deregistered` state — instances point at it — so this is not a delete. A platform base image is refused with 409.

Request syntax

DELETE /ec2/api/machine-images/{id}

Path parameters

  • idRequired

    string

    Constraints: /^ewi-[0-9a-f]{6,32}$/

Response

200: `data` is the image, now in state `deregistered` (also when it already was).

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 ec2:DeregisterImage 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 ec2 machine-images deregister id

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