Skip to content

Security Alert Destination Required

URI: https://docs.ankatech.co/errors/security-alert-destination-required
HTTP Status: 403 Forbidden

When you see this

You deleted or changed a platform alert destination, and the change would leave CRITICAL or WARNING alerts with no enabled destination where at least one received them before. The platform's security-detective conditions fire at those severities, so removing their last destination silences them as surely as disabling them. Only a caller holding admin.platform.alerts.detective.manage, the platform super administrator, may do it.

Each severity is judged on its own: narrowing the only destination that accepts WARNING to CRITICAL is refused even though a destination remains. A severity that had no enabled destination before your change is not counted. Nothing was changed.

Common Causes

  • Deleting the last enabled ALERT destination, or the last one accepting CRITICAL or WARNING.
  • Replacing that destination with enabled: false.
  • Removing CRITICAL or WARNING from its acceptedSeverities when no other destination accepts it.
  • Replacing it with purpose: HEARTBEAT, which receives no alerts.

Response Example

{
  "type": "https://docs.ankatech.co/errors/security-alert-destination-required",
  "title": "Security Alert Destination Required",
  "status": 403,
  "detail": "This change would leave [WARNING] alerts with no enabled destination; it requires the 'admin.platform.alerts.detective.manage' scope",
  "instance": "/api/v3/admin/platform/alerts/destinations/8d1f3b2a-6c4e-4a90-b7d2-1e5f9c0a3b64",
  "extensions": {
    "requestId": "b52e7d19-0f3a-4c86-9e41-7a6c2d8f5b03"
  }
}

How to Resolve

  1. Declare the replacement destination first, enabled and accepting the same severities, then delete or narrow the old one.
  2. If no destination should receive those alerts any more, ask a platform super administrator to make the change.