EvoHub

AWS EventBridge alerts, routed to the right on-call engineer

Receive AWS events — GuardDuty and Security Hub findings, AWS Health events, CloudWatch alarms and any other EventBridge event — via an API destination or SNS. EvoHub turns each AWS EventBridge alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.

How the AWS EventBridge integration works

  1. Create a AWS EventBridge integration in EvoHub On-Call and pick the escalation policy it should notify.
  2. EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into AWS EventBridge using the steps below.
  3. Each AWS EventBridge alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
  4. Security Hub findings resolve when archived, resolved, suppressed or passed; AWS Health events when closed; CloudWatch alarms when back to OK. GuardDuty sends no recovery — resolve in EvoHub.

Set up AWS EventBridge

Create the integration in EvoHub first — it shows your personal integration URL to paste below.

# Two ways in — pick one.

# A) API destination (direct)
# 1. EventBridge → API destinations → Create API destination
API destination endpoint: <your EvoHub integration URL>
HTTP method: POST
#    Connection → Create a new connection:
#    Authorization type: API Key
API key name: X-EvoHub-Key
Value: <the key at the end of the URL above>

# 2. EventBridge → Rules → Create rule → event pattern, e.g.
#    GuardDuty, high and critical only:
{
  "source": ["aws.guardduty"],
  "detail-type": ["GuardDuty Finding"],
  "detail": {"severity": [{"numeric": [">=", 7]}]}
}
#    Target: the API destination. Keep "Matched events" —
#    do NOT add an input transformer.

# B) SNS topic instead
#    Rule target: an SNS topic, with an HTTPS subscription:
Protocol: HTTPS
Endpoint: <your EvoHub integration URL>
#    EvoHub checks SNS's signature and confirms the
#    subscription by itself.

# More patterns (one rule each, same target):
# Security Hub CSPM (ASFF), high and critical — plus the
# updates that close them:
{
  "source": ["aws.securityhub"],
  "detail-type": ["Security Hub Findings - Imported"],
  "detail": {"$or": [
    {"findings": {"Severity": {"Label": ["HIGH", "CRITICAL"]}}},
    {"findings": {"Compliance": {"Status": ["PASSED"]}}},
    {"findings": {"RecordState": ["ARCHIVED"]}},
    {"findings": {"Workflow": {"Status": ["RESOLVED", "SUPPRESSED"]}}}
  ]}
}
# Security Hub (OCSF findings), the same idea:
{
  "source": ["aws.securityhub"],
  "detail-type": ["Findings Imported V2"],
  "detail": {"$or": [
    {"findings": {"severity": ["High", "Critical"]}},
    {"findings": {"status": ["Resolved", "Suppressed", "Archived"]}},
    {"findings": {"compliance": {"status": ["Pass"]}}}
  ]}
}
#   A severity filter alone never lets the resolve through:
#   when a control passes, Security Hub updates the finding to
#   PASSED *and* severity INFORMATIONAL. Without any filter
#   every informational and low finding pages too.
# AWS Health:
{"source": ["aws.health"], "detail-type": ["AWS Health Event"]}
# CloudWatch alarms (ALARM pages critical, OK resolves):
{"source": ["aws.cloudwatch"], "detail-type": ["CloudWatch Alarm State Change"]}
#   For a multi-time-series alarm (Metrics Insights GROUP BY,
#   PromQL, log alarm with BY) use
#   "CloudWatch Alarm Contributor State Change" instead —
#   one alert per contributor. Not both, or it pages twice.

# GuardDuty findings also flow into Security Hub — route
# one of the two, or every finding pages twice.
# Any other event opens one medium alert per event.

AWS EventBridge + EvoHub — FAQ

How do I connect AWS EventBridge to EvoHub?

In EvoHub, go to On-Call → Integrations, add AWS EventBridge, and choose an escalation policy. Then configure AWS EventBridge with the integration URL EvoHub shows you — the exact steps are on this page.

Do AWS EventBridge alerts resolve automatically in EvoHub?

Security Hub findings resolve when archived, resolved, suppressed or passed; AWS Health events when closed; CloudWatch alarms when back to OK. GuardDuty sends no recovery — resolve in EvoHub.

How is the AWS EventBridge integration priced?

Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.

Start free — 200 EvoHub tokens every month. See pricing.

Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.