Guided architecture tour · 5–7 min
EventBridge and Lambda architecture
Route business events using patterns and repair a rule that matches the wrong event type.
This tour teaches architecture decisions. Its services are not provisioned in the emulator.
Play this architecture tour1. Choose content-based routing
Orders and inventory publish events onto a bus. A handler only wants OrderPlaced events from your shop.
Which feature selects those events?
An EventBridge rule with an event pattern.
A rule matches event fields and sends matching events to its configured targets.
The rule selects the source and event type before invoking its target.
{ "source": ["my.shop"], "detail-type": ["OrderPlaced"] }2. Repair the pattern
The event has detail-type OrderPlaced. The rule currently expects orderplaced.
What should you compare first?
The exact field values in the event and pattern.
Pattern values must match the intended event data. Inspect the actual envelope before changing the target.
The corrected pattern matches OrderPlaced with the intended capitalization.
Event: "detail-type": "OrderPlaced"
Pattern: "detail-type": ["OrderPlaced"]3. Handle target failures
The rule matches, but its target repeatedly fails.
What belongs in the delivery design?
Appropriate target permissions, retry policy, and a dead-letter queue.
Matching, delivery, and successful processing are distinct. Preserve failed deliveries for diagnosis.
The design makes failed delivery observable and recoverable.
Match → delivery attempt → retry policy → dead-letter queuePractice, then check your understanding
In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.
Read the official AWS documentation for service behavior and production details.