Overview

Send AWS events to Callgoose SQIBS. An EventBridge rule matches the events you care about and sends them to an API destination that points at your SQIBS API endpoint. This page uses CloudWatch alarm state changes as the example: 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 EventBridge, and a SQIBS API token
Setup time
About 15 minutes
Result
CloudWatch alarms open and resolve SQIBS incidents

How it works

EventBridge
Alert fires
A rule matches an AWS event, such as an alarm state change.
EventBridge
Sends a webhook
To an API destination, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
State 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 Amazon Event Bridge. 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 it opens an incident for every event. For CloudWatch alarms, use these values instead so SQIBS opens on ALARM and resolves on OK:

Part Payload JSON key Key value contains What it does
Trigger "detail"."state"."value" ALARM Opens an incident.
Resolve "detail"."state"."value" OK Resolves the open incident.
Match "detail"."alarmName" Ties the OK event to the incident it opened.
Title from "detail"."alarmName" Becomes the incident title.
Description from "detail"."state"."reason" 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 the API destination

  1. In the AWS console, open Amazon EventBridge and go to API destinations (under Integration). Click Create API destination.
  2. Set Name to Callgoose_SQIBS_API, HTTP method to POST, and API destination endpoint to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=eventbridge&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. Choose Create a new connection. Set Connection name to Callgoose_SQIBS_Connection, Destination type to Other and Authorization type to API Key. EventBridge requires a key, so enter a header the SQIBS API ignores: API key name X-Callgoose-Source, Value eventbridge. The token travels in the endpoint URL.
  2. Click Create.

Step 3: Create a rule that sends events to SQIBS

  1. In EventBridge, go to Rules and click Create rule. Give it a name, for example cloudwatch-alarms-to-sqibs, and keep the rule type Rule with an event pattern.
  2. Use this event pattern to match every CloudWatch alarm state change (narrow it with resources or detail.alarmName if you like):
{
  "source": [
    "aws.cloudwatch"
  ],
  "detail-type": [
    "CloudWatch Alarm State Change"
  ]
}
  1. For the target, choose EventBridge API destination, then Use an existing API destination and pick Callgoose_SQIBS_API. Let EventBridge create a role for it.
  2. Review and click Create rule.

The same API destination works for any AWS event: GuardDuty findings, Health events, ECS task changes. Add a rule for each and a filter in SQIBS that matches its keys.

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 a CloudWatch 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. The event looks like this (shortened):
{
  "version": "0",
  "id": "c4c1c1c9-6542-e61b-6ef0-8c4d36933a92",
  "detail-type": "CloudWatch Alarm State Change",
  "source": "aws.cloudwatch",
  "account": "123456789012",
  "time": "2026-11-22T10:15:00Z",
  "region": "ap-southeast-1",
  "resources": [
    "arn:aws:cloudwatch:ap-southeast-1:123456789012:alarm:web-01-high-cpu"
  ],
  "detail": {
    "alarmName": "web-01-high-cpu",
    "state": {
      "value": "ALARM",
      "reason": "Threshold Crossed: 1 datapoint [92.4] was greater than the threshold (90.0)."
    },
    "previousState": {
      "value": "OK"
    }
  }
}
  1. Set the alarm back to OK (or let it recover) and 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 API destination.

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 high CPU on an instance, SQIBS can run a workflow that restarts the runaway process.

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: