Cloud platforms

Send AWS Config alerts to on-call with CallHeim.

Config rule compliance changes via EventBridge → webhook. 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.

awsconfigAWSsource names also accepted: aws-config, aws.config

Needs a forwarder

AWS Config 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 Config 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 Config 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 Config’s webhook format.

AWS Config documentation →

Setup snippetawsconfig
# AWS Config compliance changes 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.config"],"detail-type":["Config Rules Compliance Change"],"detail":{"newEvaluationResult":{"complianceType":["NON_COMPLIANT","COMPLIANT"]}}}
# 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).
# NON_COMPLIANT opens an incident for that rule and resource; COMPLIANT for the same rule and resource resolves it. NOT_APPLICABLE and INSUFFICIENT_DATA are left out of the pattern because they would open an incident.
# EventBridge rules, connections and API destinations are regional: repeat the connection, API destination and rule in every region you want covered.
Check AWS Config’s current documentation for the exact fields.

After it arrives

What CallHeim does with AWS Config alerts.

Each platform or account event is mapped to the service the integration is bound to. A repeat of the same event (the same rule and resource, event ARN, alert instance or policy incident, depending on the source) attaches to the open incident, and the provider’s own grouping is not carried over. An Orchestration Rule can route or re-prioritize by fields in the event.

CallHeim maps AWS Config’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 →

If AWS Config sends a recovery notification, CallHeim records it against the incident.

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 →

CallHeim

Point AWS Config at CallHeim and see what it does with your alerts.

Start on the free trial, connect AWS Config and send a test alert to see the incident it opens.