Amazon EventBridge: Event Routing

An event bus routes events by meaning

Amazon EventBridge provides event-driven integration for events from AWS services, custom applications, and supported partner sources. An event bus receives events, rules evaluate them, and matching rules send events to configured targets. Unlike a simple topic subscription, a rule can inspect the structured event and route it according to fields such as source, detail-type, and values nested inside detail.

The default event bus receives events from supported AWS services. Custom event buses can create application or organizational routing boundaries, and partner event buses support integrated SaaS sources where available. Event buses can also participate in cross-account and cross-Region architectures through explicitly configured bus targets and resource permissions.

Event patterns are declarative JSON filters

An EventBridge event pattern specifies only the fields that matter for a match; fields omitted from the pattern are ignored by that rule. Patterns can match top-level event metadata and nested detail values and support documented matching operators for more expressive selection. This lets consumers subscribe to business-relevant events without requiring producers to know every downstream destination.

Rules should be designed around stable event contracts. A pattern that depends on an incidental field or on a string generated for human display can make routing fragile. EventBridge does not turn every API call into an event automatically; scenarios should verify that the relevant AWS service emits the needed event or that a producer explicitly calls PutEvents.

• Only fields present in the event pattern participate in matching.
• One event can match multiple rules and therefore reach multiple target paths.
• Targets need the permissions required for EventBridge to invoke or deliver to them.
• Cross-account buses require both routing configuration and resource-based authorization.

Event buses and Pipes solve different integration shapes

Event buses are well suited to many-to-many event routing where multiple producers and rules share an event fabric. EventBridge Pipes target a more direct source-to-target integration: a pipe reads from a supported source and can apply filtering, optional enrichment, and transformation before sending to one target. This reduces glue code for point-to-point event paths without requiring a shared event bus.

For failures, event-driven designs should distinguish retry behavior at the EventBridge delivery layer from failure handling inside the target. Supported rules can use dead-letter queues and retry policies for target delivery. Once a Lambda function or downstream workflow accepts an event, its own retry/idempotency model becomes a separate concern.