A company is designing an event-driven architecture using Amazon EventBridge. They have multiple AWS accounts that need to receive events from a central account. What is the MOST scalable and secure way to route events to these accounts?
Cross-account event buses let the central account publish events that each target account's bus receives via resource-based policies, avoiding per-account polling or fan-out infrastructure. This satisfies the scalability and security constraints through native, policy-scoped cross-account delivery.
Why this answer
Amazon EventBridge cross-account event buses allow a central account to route events directly to event buses in target accounts using resource-based policies. This approach is serverless, fully managed, and scales horizontally without any intermediate components, making it the most scalable and secure solution. It avoids the complexity and potential bottlenecks of Lambda invocations, Kinesis stream management, or SNS-to-SQS fan-out across accounts.
Exam trap
The trap here is that candidates often default to SNS or SQS for cross-account messaging, but EventBridge's native cross-account event bus feature is specifically designed for this use case and is more scalable and secure because it uses resource-based policies and avoids intermediate services.
How to eliminate wrong answers
Option B is wrong because publishing events to a Lambda function in each target account introduces a single point of failure and scaling bottleneck per function, and requires managing cross-account IAM roles for each invocation, which is less scalable and more complex than native EventBridge cross-account routing. Option C is wrong because Amazon Kinesis Data Streams is designed for real-time data streaming with consumer-based processing, not for event routing to multiple accounts; it would require custom consumers and cross-account access policies, adding operational overhead and latency compared to EventBridge's direct push model. Option D is wrong because creating an SNS topic in the central account and subscribing SQS queues in each target account requires SQS to poll from SNS, which introduces latency and does not support event filtering or schema validation natively; also, SNS does not natively support cross-account subscriptions without additional SQS policy configuration, making it less secure and more complex than EventBridge's resource-based policies.