A company uses an API Gateway REST endpoint as a webhook so an on-premises SCM system can publish events to EventBridge in a central AWS account. An EventBridge rule in the central account handles deployments. The company also needs the same events to be available in multiple receiver AWS accounts, without changing the SCM webhook configuration. How can a developer accomplish this?

The correct solution leverages EventBridge's cross-account capabilities. By granting the central account's EventBridge permission to publish to event buses in the receiver accounts, and then configuring the existing central EventBridge rule to target these remote event buses, the events are automatically fanned out to all desired accounts without modifying the SCM webhook. Incorrect options: Deploying API Gateway into every receiver account and using the same custom domain is not feasible as custom domains are unique per API Gateway and region. Even if it were, the SCM webhook would still need to know how to address multiple endpoints, which contradicts the requirement of not changing the SCM webhook configuration. Deploying API Gateway into each receiver account and creating separate webhooks violates the requirement of not changing the SCM webhook configuration, as it would necessitate multiple webhooks. Converting to an HTTP API does not inherently solve the cross-account event distribution problem and doesn't align with the existing REST API setup.