Overview

Send alerts from any AWS service to Callgoose SQIBS through one Amazon SNS topic. You subscribe your SQIBS API endpoint to the topic, then point CloudWatch alarms, Elastic Beanstalk, GuardDuty (through EventBridge) and other services at it. SQIBS opens an incident when an alarm goes into ALARM and resolves it when it returns to OK.

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

How it works

AWS
Alert fires
A CloudWatch alarm changes state.
AWS
Sends a webhook
The alarm publishes to the 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. In Select Integration Template, choose AwsCloud. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger (none) (anything) No key, so every message opens an incident.
  1. Choose the Priority for these incidents and click Save.

The template has no key, so every message opens an incident, including the subscription confirmation in step 3 (which is useful: it shows you the confirmation link). Once the subscription is confirmed and raw message delivery is on, use these values for CloudWatch alarms:

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 OK message to the incident it opened.
Title from "AlarmName" Becomes the incident title.
Description from "NewStateReason" Becomes the incident description.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

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: Create an SNS topic and subscribe SQIBS

  1. In the AWS console, open Simple Notification Service > Topics and click Create topic. Choose Standard, name it Callgoose_SQIBS_Alerts, and create it.
  2. In the topic, click Create subscription. Set Protocol to HTTPS and Endpoint to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=awssns&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.

  1. Click Create subscription. Its status is Pending confirmation.

Step 3: Confirm the subscription

SNS sends a confirmation message to SQIBS first. 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. In SQIBS, open the new incident (or the API log) and find the message with "Type": "SubscriptionConfirmation".
  2. Copy its SubscribeURL and open it in a browser, or paste it into Confirm subscription in the SNS console.
  3. The subscription status changes to Confirmed.
  4. Edit the subscription and turn on Enable raw message delivery. SNS then sends the alarm JSON itself, so the filter keys in step 1 match directly.

Step 4: Send alarms to the topic

  1. In CloudWatch > Alarms, create or edit an alarm.
  2. Under Notification, add an action In alarm that sends to Callgoose_SQIBS_Alerts, and a second action OK to the same topic so incidents resolve.
  3. Save the alarm. Do the same for any other AWS service that can publish to SNS.

Step 5: 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 state for a test, for example with 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).",
  "StateChangeTime": "2026-11-22T10:15:00.000+0000",
  "Region": "Asia Pacific (Singapore)",
  "OldStateValue": "OK"
}
  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 a CloudWatch alarm reports low free disk space on an instance, SQIBS can run a workflow that clears old logs and rechecks the space.

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: