grant cross-account access to an eventbridge custom event bus using a resource-based policy
domain: docs.aws.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call PutPermission on the target event bus, specifying either an individual AWS account ID or an AWS Organization ID as the principal.
To allow every account in an AWS Organization at once, specify the principal as a wildcard with a condition referencing the Organization ID rather than calling PutPermission per account.
On the sending account's side, create a rule whose target is the remote account's event bus ARN, granting the rule's execution role permission to put events.
Keep the resulting resource policy under the event bus policy size limit; for many accounts, prefer the Organization-based condition over enumerating each account ID.
Verify delivery by sending a test event and confirming it lands on the target bus, then add a rule and target on the receiving account to route it further.
Known gotchas
The event bus resource policy has a hard size limit, so enumerating individual account IDs at scale can hit it; use the AWS Organization condition instead of one PutPermission call per account.
Granting PutEvents cross-account only allows events to arrive; it does not automatically let the sending account's rule invoke targets in the receiving account, which requires additional target-side configuration.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?