AWS EventBridge
AWS EventBridge is a serverless event bus that routes events from AWS services, SaaS applications, and custom sources to targets like Lambda, SQS, and Step Functions based on rules you define. We design EventBridge architectures that make the event flow through a system explicit and auditable rather than implicit in point-to-point integrations.
Capabilities
What we build with EventBridge
EC2 · S3 · RDS · CodePipeline
AWS Service Event Routing
Rules that capture AWS service events — EC2 state changes, S3 object creation, RDS snapshot completion, CodePipeline stage transitions — and route them to Lambda handlers or SQS queues.
Domain event bus
Custom Application Events
Custom event bus for application domain events. Services publish typed events to EventBridge; rules route events to the correct handlers without the publisher knowing about downstream consumers.
Source → filter → target
EventBridge Pipes
EventBridge Pipes for point-to-point integrations: SQS to Lambda, DynamoDB streams to Step Functions, Kinesis to EventBridge bus — with optional filtering and enrichment in between.
Partner event sources
SaaS Integration
Native EventBridge partner integrations for SaaS applications like Salesforce, Zendesk, and GitHub. Events from these platforms delivered to your event bus without custom webhook infrastructure.
Cron · Rate
Scheduled Rules
EventBridge scheduled rules as a fully managed cron replacement, triggering Lambda functions or Step Functions workflows on fixed rates or cron expressions without managing a scheduler.
Event contracts
Schema Registry
EventBridge Schema Registry for discovering and documenting the structure of events flowing through the bus, with code binding generation for TypeScript, Python, and Java.
Our approach
The default bus versus a custom bus
The default EventBridge bus carries AWS service events. For application events, we create custom event buses so that application events are separated from AWS noise, bus policies are scoped correctly, and cross-account delivery is controlled.
Schema first
Before publishing a custom event, we define its schema in the Schema Registry. This documents the event contract, enables code binding generation, and makes the event structure discoverable by other teams. An event schema is as much a public API contract as an HTTP endpoint.
Rule patterns are precise
EventBridge rule patterns match on specific event source, detail-type, and detail field values. Overly broad patterns route events to the wrong targets. We write precise patterns and test them with EventBridge's pattern tester before deploying.
Defined as infrastructure code
Event buses, rules, targets, and schema definitions are all defined in Terraform. The complete event routing topology is documented in code, not discovered by reverse-engineering a list of rules in the console.
All engineering work is done by US-based engineers. We do not offshore any development or architecture work.
Part of our serverless practice
FAQ
Common questions
Virginia · United States
Designing an EventBridge architecture?
Reach out and we will discuss the event model, bus design, and rule patterns before any work begins.