Skip to content

Deployment Backend Unreachable

URI: https://docs.ankatech.co/errors/deployment-backend-unreachable
HTTP Status: 503 Service Unavailable

When you see this

The deployment key-protection backend could not be addressed at all with the configuration and credential recorded for it — no client could be built, so no request ever left the platform. The response carries a Retry-After header and nothing was changed. The underlying cause is retained for server logs only and is never rendered, because every cloud SDK puts the vault URL, the resource path, the region and the account id into its exception text.

Common Causes

  • The recorded descriptor is incomplete, or its declared token is not a Cloud KMS token.
  • The sealed credential could not be unsealed or decoded.
  • The credential belongs to a different provider family than the declared backend.

Response Example

{
  "type": "https://docs.ankatech.co/errors/deployment-backend-unreachable",
  "title": "Deployment Backend Unreachable",
  "status": 503,
  "detail": "The deployment key-protection backend could not be addressed with the configuration and credential recorded for it. Nothing was changed.",
  "instance": "/api/v3/admin/platform/setup/backend/activate",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "0a3d7c81-6e24-4b95-a0f7-92c15d84e3b6"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Re-read the recorded coordinates with GET /api/v3/admin/platform/setup/backend/configuration and confirm the declared backend token and every coordinate the family requires.
  2. Confirm the credential you supplied belongs to the same provider family as the declared backend, then re-submit it with PATCH /api/v3/admin/platform/setup/backend/credential.
  3. Rehearse with POST /api/v3/admin/platform/setup/backend/validate before activating again.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.