EvoHub DocsEvoHub Docs Sign in

AWS CloudWatch

Use with AI
View as MarkdownThis page as plain text, for pasting into an AI tool Open in ClaudeAsk Claude questions about this page Open in ChatGPTAsk ChatGPT questions about this page
Connect to Cursor / VS Code / ClaudeSearch and read these docs from your AI tool (MCP server)

MCP server URL

https://docs.evohub.io/mcp

Add to CursorAdd to VS Code

Claude Code

claude mcp add --transport http evohub-docs https://docs.evohub.io/mcp

Claude (claude.ai and Claude Desktop): Settings → Connectors → Add custom connector, and paste the URL above.

Claude Desktop — claude_desktop_config.json

{
  "mcpServers": {
    "evohub-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs.evohub.io/mcp"
      ]
    }
  }
}

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "evohub-docs": {
      "url": "https://docs.evohub.io/mcp"
    }
  }
}

VS Code — .vscode/mcp.json

{
  "servers": {
    "evohub-docs": {
      "type": "http",
      "url": "https://docs.evohub.io/mcp"
    }
  }
}

llms.txtllms-full.txt

EvoHub receives CloudWatch alarms through an Amazon SNS topic with an HTTPS subscription. An alarm that goes to ALARM opens an EvoHub alert; the same alarm returning to OK resolves it.

Set it up

Create the integration

In EvoHub, go to On-Call → Integrations → + Add Integration, choose AWS CloudWatch, pick an Escalation Policy and click Create Integration. Copy the Webhook URL.

Create the SNS topic

In Amazon SNS, create a Standard topic (or use one you have).

Subscribe EvoHub to the topic

Add a subscription to the topic with Protocol HTTPS and Endpoint your webhook URL. Leave Raw message delivery off: EvoHub needs the SNS envelope to check its signature.

Check the subscription

EvoHub confirms the subscription by itself. In SNS, check that the subscription shows an ARN rather than PendingConfirmation.

Point your alarms at the topic

In each CloudWatch alarm, set the topic as the In alarm action and the OK action. Without the OK action CloudWatch never tells EvoHub the alarm has cleared.

Note

EvoHub checks the SNS signature on every message against Amazon's signing certificate, so only messages that really come from Amazon SNS are accepted; anything else is refused with 403. If the certificate cannot be fetched at that moment, EvoHub answers 503 and SNS delivers the message again.

What EvoHub reads

EvoHub alert Taken from
Title AlarmName (else the SNS subject).
Description AlarmDescription and NewStateReason (what crossed the threshold), each when set.
Labels state — the alarm's new state — and each of the Trigger's dimensions, for example InstanceId.
Link The alarm in the CloudWatch console, in the region named by AlarmArn. It opens from the alert.
Values metric (Namespace/MetricName) and threshold (ComparisonOperator and Threshold).

Severity

Alarm state EvoHub severity
ALARM critical
INSUFFICIENT_DATA low
OK resolves the alert

INSUFFICIENT_DATA only reaches EvoHub if you also set the topic as the alarm's Insufficient data action; leave that action empty unless a metric that stops reporting should open a low alert.

Resolve and deduplication

An alert is identified by the AWS account, the region and the alarm name (plus the contributor, for a multi-time-series alarm, so each contributor is its own alert and its title names the contributor), so identically named alarms in two accounts or regions stay two alerts. While it is open, the alarm firing again is recorded as Retriggered instead of paging again; OK resolves it. One SNS topic can carry any number of alarms.

CloudTrail

CloudTrail activity — a root sign-in, logging turned off — pages through this same integration, with a metric filter and an alarm. See AWS CloudTrail.

Last updated Powered by