Skip to main content
Every ECS API error uses the same response envelope:
Use error.code for programmatic handling. The message field contains request-specific detail. The docs_url field links to the matching article in this section.

Error code directory

Authentication

Invalid credentials, suspended accounts, and access scope.

Request and resource

Invalid input and missing resources.

Operations

Quotas, deployments, and unexpected failures.

Retry strategy

  • Do not retry 401, 403, 404, or 422 unchanged.
  • Back off before retrying 429 responses.
  • Retry transient 500 responses carefully.
  • Do not blindly repeat destructive operations.
  • A create or redeploy request may return while its status is still provisioning. Use the service status endpoint before treating it as failed.

Client handling example

Private ClearLake buckets are not available through Waymark custom domains and return not_implemented. Use the standard ClearLake download URL flow instead.