AWS adds enhanced custom event buses to Amazon EventBridge

Amazon Web Services has announced an enhanced custom event bus for Amazon EventBridge, positioning the update as a way for larger organisations to simplify event-driven application architectures across multiple AWS accounts.

In a post on the AWS News Blog, the company said teams often begin with a single custom event bus in one account, but complexity increases as more teams adopt EventBridge and AWS best practices push organisations towards multi-account structures. According to AWS, teams have typically used multiple event buses connected through cross-account rules or bus-to-bus configurations, creating additional operational work and potentially compounding routing charges.

The new enhanced custom event bus is intended to let platform teams deploy one central bus that can be shared across AWS accounts in an organisation. AWS says publishers can send events to the shared bus without needing to know which teams consume them, while subscribers can create their own subscriptions independently. The company says platform teams retain visibility into event flows and control over who can publish and consume events.

AWS said sharing is handled through AWS Resource Access Manager, rather than requiring teams to configure cross-account permissions or bus-to-bus routing themselves. The blog describes sharing options including an AWS account, an organisation, an organisational unit, or an IAM role or user.

The enhanced bus also adds support for event ordering on the same bus as unordered event flows. AWS said publishers can include an EventGroupId when sending events, although the supplied material does not provide full implementation details.

Other cited features include event retention, routing, delivery, filter patterns and replay. AWS said the new bus has a default quota of 10,000 subscribers per bus, with higher quotas available by request.

AWS also referred to a new pricing model designed to improve economics at scale and support cost allocation for publishers and subscribers. Specific prices, regional availability and customer adoption details were not included in the supplied source.