In Flashduty On-call
You can get the integration push URL in either of the following ways.Use a dedicated integration
Choose this option if all alerts go to one channel. It’s the simpler setup.View dedicated integration setup steps
View dedicated integration setup steps
- In the Flashduty console, select Channel and open a channel
- Select Configuration → Integrations → Private integration, then click Add integration
- Choose AWS EventBridge integration and click Save to generate a card
- Open the generated integration card and copy the Push URL
Use a shared integration
Choose this option if you need to route alerts to different channels based on the alert payload.Configure in AWS EventBridge
1
Create an API destination that points to Flashduty in Amazon EventBridge
- API destination (recommended)
- SNS topic
Where: Amazon EventBridge › Integration › API destinations › Connections › Create connection
Where: Amazon EventBridge › Integration › API destinations › Create API destination
Click Create to save.
Where: Amazon EventBridge › Integration › API destinations › Create API destinationClick Create to save.

2
Create an event rule in Amazon EventBridge
Where: Amazon EventBridge › Rules › Create rule › Advanced BuilderAWS Health sends events to the Region where they occur; events of global services arrive in 
Use an event pattern in the rule, for example:
us-east-1. Create the rule in every Region you care about.
3
Send a test CloudWatch alarm event and confirm
Where: A terminal that can reach the Flashduty push URLThe rule only forwards events that AWS really emits. To verify right away, POST a test event shaped like the real one to the push URL:Send it again with
state.value set to OK to confirm that the alert recovers automatically. A few seconds later, go back to Flashduty. The integration shows a latest event time, which means the setup works.Alert key and recovery
- Later events of the same source (repeated GuardDuty findings, Security Hub updates, AWS Health progress) merge into the original alert
- When one Security Hub event carries several findings, each finding creates its own alert
- An event missing the Alert Key field listed above is rejected (HTTP 400)
- GuardDuty sends no event when a finding is archived, so close the alert manually
Status and severity
EventBridge events have no common severity field, so every event triggers as Warning, as it always has. The source’s own severity is kept in a label, and an alert pipeline can rewrite the severity based on it:
For CloudWatch alarms, set the severity with
flashduty_severity: critical (critical, warning or info) in the Alarm description, the same way as in the AWS CloudWatch integration.
Title and labels
- The alert title is
source::detail-type, for exampleaws.guardduty::GuardDuty Finding - Every event carries the labels
source,region,account,check(detail-type),detail(the eventdetailas JSON) andresources - The
summarylabel is a readable summary: the finding or alarm title for sources with dedicated handling; for other events, in order, CloudTraileventSource eventName, RDSSourceIdentifier Message, ECSgroup stoppedReason, or EC2instance-id state - Sources with dedicated handling also add source fields such as
finding_id,finding_arn,event_arn,config_rule_nameandinsight_id;resourceis the affected resource (DevOps Guru insights have none)
Troubleshooting
- API destination invocations fail: Make sure the endpoint is the full push URL including
integration_keyandHTTP methodisPOST - SNS subscription stays in
Pending confirmation: Make sure the subscription points to this integration’s push URL, then run Request confirmation in the SNS console - Alert does not recover: Check whether the rule’s event pattern filters out recovery states, and whether the target has an input transformer
- One finding creates several alerts: Make sure the event comes from a source in the table above and its
detail-typeis not rewritten