Featured
New EventBridge Custom Event Bus vs SQS FIFO: when to switch
- Context
Cross-team integration on EventBridge Classic, an SQS FIFO queue behind every consumer, an archive for replay and a resource policy that grows with every new account.
- Rule of thumb
For a cross-team backbone, in a supported Region, with fast idempotent consumers and per-entity ordering within one publisher: new bus with per-account subscribers, no SQS FIFO in the middle.
- Trade-offWhat you gain
Cross-account sharing through AWS RAM (Resource Access Manager), native retention and replay, and FIFO by EventGroupId, with fewer parts between teams.
What you payA 30 s ceiling on REQUEST_RESPONSE, head-of-line blocking during retries, ordering only within the publishing account, and no sa-east-1 yet.




