Introduction

AWS EventBridge just received a long-awaited upgrade that finally addresses developer frustrations around event bus limitations. The relaunched event buses introduce a flexible subscriber model, multi-format support, and cross-account capabilities that classic buses never offered.

What Happened

Classic EventBridge buses required rules and targets to live in the same account and region, making multi-region and multi-account deployments complex. The new event buses replace the rules-driven approach with a subscriber concept, where subscribers use filters to determine which events they receive and can apply transformations before passing them to a target. These new buses support multiple content types including JSON, Avro, Protobuf, and octet streams, and offer the choice between unordered and FIFO delivery per subscriber. Built-in retention ranges from one day to one year, and subscribers can start from any point within that window, enabling event replay without a dedicated API. AWS RAM also enables bus sharing across accounts, simplifying cross-organization event architectures.

Why This Matters

These changes remove the primary barriers to true event-driven architectures spanning multiple regions and accounts. Developers no longer need to forward events manually or maintain custom serverless platforms to work around EventBridge limitations. Native format support, delivery guarantees, and event replay within the retention window make it viable for production-grade, active-active designs. The subscriber model also gives teams finer control over how events are filtered, transformed, and delivered to downstream systems.

Key Takeaways

  • The new bus uses a subscriber model instead of rules, with filters and optional transforms.
  • Supports JSON, Avro, Protobuf, and octet stream content types at launch.
  • Offers unordered or FIFO delivery, batching, and content- or ID-based deduplication.
  • Retention configurable from 1 day to 1 year; subscribers can start from any point within the window.
  • AWS RAM simplifies cross-account bus sharing; target accounts accept invitations via the RAM console.
  • Early adopters should test in non-critical environments until IaC tooling and regional availability mature.

Conclusion

The EventBridge upgrade is a significant step forward for serverless eventing, especially for teams building cross-region, cross-account, or format-flexible workloads. While CloudFormation, CDK, and Terraform support is still catching up, the core functionality delivers the flexibility developers have been waiting for. Prototype aggressively, but wait on critical production workloads until IaC support catches up.