
Create the bus and add Subscribers
Create the event bus, then add one Subscriber per service, each with a filter so it receives only the events it needs, and watch the admin dashboard update as tickets are reserved and sold.
Avro and schema registries
The gate system already publishes Avro. Point it at the bus unchanged: the bus decodes each event with the schema registry, and Subscribers receive JSON without an Avro library or access to the registry.
JSONata, replay and universal targets
Give a partner a live dashboard with the full sales history and no fan data. A new Subscriber replays retained events from the start, reshapes each one with JSONata, and writes it straight to the target with a universal target, with no function in the path.
Ordered delivery
Make sure no refund is processed before its payment. A FIFO Subscriber delivers the events in each event group in the order they were published, while different groups are still processed in parallel.
Enterprise scale
The session ran in one account. To use one bus across teams, share it with other accounts or your whole organization through AWS RAM, and let each team create its own Subscribers.
Why the new Custom event bus
One governed bus for many teams
Multi-account growth with cross-account rules and bus-to-bus routing adds cost and complexity with every account. The Custom event bus gives you one governed bus that many accounts can share, with end-to-end observability.