Build EventBridge rule event patterns and target configurations.
Last verified: May 2026
Build EventBridge rule event patterns and target configurations.
Required Fields
NameEventPatternTargetsOutput will appear here...Amazon EventBridge is a serverless event bus that routes events from AWS services, SaaS applications, and custom sources to targets like Lambda, SQS, Step Functions, and API destinations. Rules define which events match and where to send them using event patterns — JSON structures that filter on event source, detail-type, account, region, and custom detail fields. Writing event patterns requires understanding exact-match, prefix, numeric range, exists, and anything-but matchers. The EventBridge Rule Builder helps you construct rules with correct event pattern syntax, target configurations, input transformations, and dead-letter queue settings.
Your security team needs to alert on every IAM policy change across 30 AWS accounts. The builder generates a cross-account event bus rule: pattern matches `source: aws.iam` and `detail-type: AWS API Call via CloudTrail` with `eventName: prefix Put*Policy or Attach*`. Target: SNS topic that emails the security team. Within hours, every policy change in the org is visible to security in real-time. Without the builder, hand-crafting the event pattern from scratch took the team a half-day and missed several event names that the tool's catalog includes by default.
Event patterns use exact-match by default. The single most common mistake: writing `"detail-type": "EC2 Instance State-change Notification"` and getting nothing — the actual event uses different casing or punctuation. Always test patterns against real events using the EventBridge sandbox feature.
Input transformers replace the entire event with your transformed payload. If your downstream target expects fields outside what you transformed in, they'll be missing. For most cases, prefer adding additional fields via SetVariable rather than full-replace input transformers.
Always set a Dead Letter Queue (DLQ) on rules that target Lambda or SQS. Failed event deliveries without DLQ = silent data loss. EventBridge will retry up to 24 hours, but if the target is fundamentally broken, those events vanish without DLQ.
The builder constructs EventBridge rule definitions with: name + description, event pattern (JSON object with matchers — exact, prefix, suffix, anything-but, numeric range, exists), event bus selection (default vs custom), targets array (with role ARN, optional input transformer, optional DLQ, retry policy). Output is generated as aws events put-rule + put-targets CLI commands and Terraform aws_cloudwatch_event_rule + aws_cloudwatch_event_target resources.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.