Amazon EventBridge event buses relaunch with cross-account sharing and CloudEvents support

The relaunch of Amazon EventBridge event buses provides streaming engineers with the strict ordering and cross-account visibility required for complex, multi-tenant video workflows. By supporting CloudEvents and extending retention to one year, AWS is addressing the technical debt associated with custom event-handling logic and manual data recovery. Within the streaming ecosystem, this move simplifies the integration of third-party SaaS tools and internal microservices, potentially reducing the overhead of maintaining proprietary event brokers. Watch for how the new data-transfer pricing model affects the total cost of ownership for high-throughput metadata pipelines compared to the legacy 'Classic' event-based billing.

Amazon EventBridge has been building toward this relaunch through a series of incremental capability additions over the past two years. AWS introduced bus-to-bus event routing in EventBridge, allowing developers to forward events between different event buses in the same Region and account, which previously was limited to consuming events only from the default bus or dedicated partner-event buses. That routing feature enabled centralization of events from multiple buses into a single custom bus, a pattern directly relevant to multi-tenant streaming architectures where metadata from encoding, packaging, and delivery services must converge into unified pipelines. The pricing shift in this relaunch reflects AWS's broader effort to align EventBridge billing with actual data movement rather than simple event counts. AWS's published EventBridge pricing structure bills each 64 KB chunk of a payload as one event, meaning a 256 KB payload is charged as four events, and archive replay is billed at the same custom-events rate. For streaming workloads that generate high-volume, small-payload metadata (such as segment availability notifications, manifest update signals, or ad-decision callbacks), the new data-transfer-based model on relaunched custom buses could reduce costs compared to the legacy per-event billing, though the exact break-even depends on average payload size and throughput. Cross-account event sharing in Amazon EventBridge has also evolved with security requirements that affect enterprise streaming deployments. AWS now requires all new cross-account event bus targets to use IAM roles, a policy that applies to targets created after March 2, 2023, adding an explicit identity layer to inter-account event flows. Combined with the relaunch's integration with AWS Resource Access Manager, this means streaming organizations operating multi-account structures (common for separating production, staging, and partner-facing environments) can share event buses across organizational boundaries while maintaining auditable access controls. As data-driven streaming models become the industry standard, these infrastructure improvements provide the necessary foundation for real-time analytics at scale.