AWS Security ChangesHomeSearch

AWS eventbridge: EventBridge cross-account event bus targets no longer supported

Service: eventbridge · 2026-11-05 · Documentation medium

File: eventbridge/latest/userguide/eb-custom-bus-target-bus.md · Type: authz

Summary

Documentation for targeting another event bus was changed to state the destination bus must be in the same account as the subscriber, and that EventBridge rejects cross-account targets, including buses shared via AWS RAM; the guidance now recommends sharing the source bus so the other account creates its own subscriber.

Security assessment

The change documents a tightened authorization boundary: cross-account delivery via a target bus (including RAM-shared buses) is rejected, and the IAM actions events:PutEvents/events:PutRawEvents are still required on the destination bus. This restricts cross-account data flow and trust relationships, though no specific vulnerability or incident is cited.

Evidence

+To forward events to another event bus, set `TargetArn` to that bus's ARN. The destination can be another Custom Event Bus or a Custom Event Bus - Classic, in the same Region or a different one. The destination bus must be in the same account as the subscriber. No parameter block is needed. A Custom Event Bus - Classic rule can likewise name a Custom Event Bus as its target, so events can move in either direction during a migration.

Diff

diff --git a/eventbridge/latest/userguide/eb-custom-bus-target-bus.md b/eventbridge/latest/userguide/eb-custom-bus-target-bus.md
index eff030c..9313846 100644
--- a//eventbridge/latest/userguide/eb-custom-bus-target-bus.md
+++ b//eventbridge/latest/userguide/eb-custom-bus-target-bus.md
@@ -11 +11 @@ ParametersDelivery roleBatching and payloadLoop detection
-To forward events to another event bus, set `TargetArn` to that bus's ARN. The destination can be another Custom Event Bus or a Custom Event Bus - Classic, in your account or another account, in the same Region or a different one. No parameter block is needed. A Custom Event Bus - Classic rule can likewise name a Custom Event Bus as its target, so events can move in either direction during a migration.
+To forward events to another event bus, set `TargetArn` to that bus's ARN. The destination can be another Custom Event Bus or a Custom Event Bus - Classic, in the same Region or a different one. The destination bus must be in the same account as the subscriber. No parameter block is needed. A Custom Event Bus - Classic rule can likewise name a Custom Event Bus as its target, so events can move in either direction during a migration.
@@ -19 +19 @@ This target has no parameters; the payload is the whole request.
-The role needs `events:PutEvents` on the destination bus for events that carry a `PutEvents` envelope, and `events:PutRawEvents` for events published with `PutRawEvents`. EventBridge chooses the action per event and you cannot override it, so grant both when the source bus carries both kinds. A destination bus in another account must also allow your role in its resource policy or through an AWS RAM share; see [Sharing a Custom Event Bus with other accounts](./eb-custom-bus-sharing.html).
+The role needs `events:PutEvents` on the destination bus for events that carry a `PutEvents` envelope, and `events:PutRawEvents` for events published with `PutRawEvents`. EventBridge chooses the action per event and you cannot override it, so grant both when the source bus carries both kinds. EventBridge rejects a subscriber whose target is in another account, including a bus that is shared with you through AWS RAM. To deliver events to another account, share the source bus with that account so that it can create its own subscriber on the bus; see [Sharing a Custom Event Bus with other accounts](./eb-custom-bus-sharing.html).