This is AWESOME!! EventBridge now delivers events to cross-account targets directly without having to send them to the default bus in the target account first. More details here: aws.amazon.com/about-aws/wh... - ThreadSky

theburningmonk.com • 129 days ago

This is AWESOME!!

EventBridge now delivers events to cross-account targets directly without having to send them to the default bus in the target account first.

More details here:
https://aws.amazon.com/about-aws/whats-new/2025/01/amazon-eventbridge-direct-delivery-cross-account-targets/

Comments

mikebroberts.com•129 days ago

I like that it's possible, but I'm not sure when I'd use it. For me, multiple accounts is usually a "service to service" communication, and I like using EB or http as the intermediary in that situation. Directly pointing to resource x-account feels too tight a binding, no? cc: @danilop.bsky.social

danilop.bsky.social•129 days ago

With this new capability, you can (fro example) send a message to an SQS queue or SNS topic, or trigger a Lambda function in another account without having to use an event bus in the target account.

skwashd.wtf•127 days ago

I’m not a fan. Having a bus on each end provides a clean boundary.

For example my lambda is struggling I can put a SQS queue between it and the bus. Those pushing the events to my bus would’ve none the wiser. Trying to coordinate such a change across teams doesn’t scale.

danilop.bsky.social•129 days ago

In a multi-account setup, you can have a dedicated account with an event bus that acts as a router for events across the different accounts.

mikebroberts.com•129 days ago

OK, "central account as event orchestrator" I can see as a use case for this, if you want to go the orchestration route. I tend not to, but I admit it's useful sometimes.

I still think it likely means having separate deployment processes for rule and receiver, since cross-account CFn is awkward.

matthias-pichler.bsky.social•127 days ago

In this case the EventBridge team actually added some nice features. By specifying a Resource Policy on the EventBus (e.g. that allows all accounts in the same organization to add rules) you can use the ARN of the EventBus to directly deploy cross-account rules from a single CloudFormation stack

mikebroberts.com•127 days ago

Oh, that *is* nice! OK, I'm starting to get a little more on board with this now. If Service A (event producer) is basically offering its Event Bus as a service interface that Service B (event consumer) can attach its own rules to then that could clean a few things up.

spliceruk.bsky.social•128 days ago

Yup, We are in the middle of a roll out of event bridge and wanted this feature 6 weeks ago now we can change course before it is finished. a great change which should reduce cost and latency.

Comments

Posting Rules

Reply