Security
Send AWS GuardDuty alerts to on-call with CallHeim.
GuardDuty findings via EventBridge → webhook (API destination). CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.
Needs a forwarder
AWS GuardDuty does not post to CallHeim on its own for this. You set up a forwarder, rule or script that sends the event to your CallHeim URL; the setup steps show what to send.
Setting it up
Create an Integration in CallHeim and choose AWS GuardDuty from the Catalog to get its ingest URL, and use that URL as the target of your forwarder. CallHeim’s ingest URL takes a JSON request body. The snippet beside this shows the request it expects, with {{WEBHOOK_URL}} replaced by your real URL.
AWS GuardDuty cannot sign its requests in a format CallHeim verifies, so the integration URL is the credential. Keep it secret, and if it is exposed, disable the integration and create a new one. Do not set a signing secret unless a signing proxy you run signs each request. With a secret set, every unsigned delivery is rejected.
CallHeim includes a payload mapping for AWS GuardDuty’s webhook format.
# GuardDuty findings reach CallHeim through an EventBridge rule you create in your own AWS account — nothing forwards them for you.
# EventBridge → API destinations → Connections → Create connection. Authorization type: API Key, with API key name X-Placeholder and any value. EventBridge requires one; CallHeim does not read it. Do not use Authorization or an X-CallHeim- / X-ItOnCall- header name, which CallHeim does read.
# EventBridge → API destinations → Create API destination: endpoint {{WEBHOOK_URL}}, HTTP method POST, using the connection you created above.
# EventBridge → Rules → Create rule on the default event bus, with this event pattern:
{"source":["aws.guardduty"],"detail-type":["GuardDuty Finding"]}
# Target: EventBridge API destination → the API destination you created above. Keep the target input as "Matched events" — no input transformer — so CallHeim receives the event exactly as EventBridge emits it. Let the console create the rule's execution role (it needs events:InvokeApiDestination on the destination).
# Each finding opens an incident: severity 7 and above is P1, 4 to 6.9 is P2, lower is P3. To page on high-severity findings only, add "severity":[{"numeric":[">=",7]}] inside "detail" in the pattern.
# CallHeim reads no resolved state from a GuardDuty finding, so these incidents do not auto-resolve: resolve them in CallHeim once the finding is dealt with.
# EventBridge rules, connections and API destinations are regional: repeat the connection, API destination and rule in every region you want covered.After it arrives
What CallHeim does with AWS GuardDuty alerts.
A repeat of the same finding attaches to the incident already open for it, and an Orchestration Rule can route findings by severity, title or any payload field to the team that owns them.
CallHeim maps AWS GuardDuty’s severity or priority field to a P1 to P5 level where the source sends one, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →
Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →
The thresholds it passes through
- Repeat, sender-supplied dedup key
- attaches, any age
- Repeat, title or subject only
- attaches, incident under 24 h old
- Flap threshold
- 4 transitions / 600s
- Title correlation
- similarity ≥ 0.6, same source and service
- Group window default
- 600s
All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →
Point AWS GuardDuty at CallHeim and see what it does with your alerts.
Start on the free trial, connect AWS GuardDuty and send a test alert to see the incident it opens.