eks.deleted-clusters.purge

Delete what a deleted cluster kept, now: final snapshot, key material, volumes

POST /eks/api/deleted-clusters/{cluster}/purgeIAM eks:DeleteClusterChanges stateDestructive

Irreversible: the cluster can no longer be restored. Otherwise this happens on its own 7 days after the deletion. `confirm` must be the cluster’s name.

Request syntax

POST /eks/api/deleted-clusters/{cluster}/purge
{
  "confirm": "string"
}

Path parameters

  • clusterRequired

    string

    Constraints: 1-100 chars, /^[a-z0-9][a-z0-9-]*$/

Request body

  • confirmRequired

    string

    The deleted cluster’s name, to confirm: its final snapshot, key material and kept volumes are deleted now, irreversibly

    Constraints: 1-100 chars

Response

200 with { id, purged: true }. 400 when `confirm` is not its name; 404 for no deleted cluster by that id or name, 403 without eks:DeleteCluster on it; 409 when several deleted clusters have the name (use the id); 502 when a part could not be deleted (ask again).

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 eks:DeleteCluster 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 eks deleted-clusters purge cluster --confirm example

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