Overview

Send Amazon CloudWatch alarms to Callgoose SQIBS. Each alarm publishes to an SNS topic that your SQIBS API endpoint subscribes to. SQIBS opens an incident when an alarm goes into ALARM and resolves it when the alarm returns to OK.

You need
An AWS account with permission to manage CloudWatch and SNS, and a SQIBS API token
Setup time
About 15 minutes
Result
CloudWatch alarms open and resolve SQIBS incidents

How it works

CloudWatch
Alert fires
An alarm changes to ALARM.
CloudWatch
Sends a webhook
The alarm publishes to an SNS topic, which posts to SQIBS.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
ALARM opens it, OK closes it.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. Add a filter with these values (there is no built-in CloudWatch template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "NewStateValue" ALARM Opens an incident.
Resolve "NewStateValue" OK Resolves the open incident.
Match "AlarmName" Ties the resolve message to the incident it opened.
Title from "AlarmName" Becomes the incident title.
Description from "NewStateReason" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Subscribe SQIBS to an SNS topic

Follow steps 2 and 3 of AWS Cloud (Amazon SNS): create a topic, subscribe your SQIBS endpoint over HTTPS, confirm the subscription from the API log, and turn on Enable raw message delivery. Raw delivery sends the alarm JSON itself, so the keys above match directly.

https://<your-endpoint>/sqibs-api/v1/process?from=cloudwatch&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

Step 3: Point alarms at the topic

  1. In CloudWatch > Alarms, create or edit an alarm.
  2. Under Notification, send In alarm to the topic, and add a second notification for OK to the same topic so incidents resolve.
  3. Save the alarm.

Step 4: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Set the alarm into ALARM for a test: aws cloudwatch set-alarm-state --alarm-name <name> --state-value ALARM --state-reason "test".
  2. In SQIBS, a new incident opens. With raw message delivery the payload looks like this (shortened):
{
  "AlarmName": "web-01-high-cpu",
  "AlarmDescription": "CPU above 90% on web-01",
  "NewStateValue": "ALARM",
  "NewStateReason": "Threshold Crossed: 1 datapoint [92.4] was greater than the threshold (90.0).",
  "OldStateValue": "OK",
  "StateChangeTime": "2026-11-22T10:15:00.000+0000"
}
  1. When the alarm returns to OK, SQIBS resolves the incident.

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the SNS subscription.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when CloudWatch reports low free storage on an RDS instance, SQIBS can run a workflow that purges old snapshots or scales the storage.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: