Skip to content

Why doesn't my EventBridge rule work in Regions other than the one I created it in?

1 minute read
0

I created an Amazon EventBridge rule in us-west-1, but matching events in ca-central-1 don't trigger the rule.

Resolution

To monitor events in your AWS environment, the EventBridge rule and the source event that the rule monitors must exist in the same AWS Region.

For example, you have an Amazon Elastic Compute Cloud (Amazon EC2) instance in us-west-1 Region. The event rule that you create to monitor the instance's state changes must also exist in us-west-1 Region.

AWS global services, such as AWS Identity and Access Management (IAM), AWS Organizations, and AWS Account Management deliver events only to us-east-1 Region. For these services, create event rules only in the us-east-1 Region.

To create workflows that trigger in one Region but invoke targets in a different Region or AWS account, use cross-Region and cross-account event buses as targets. For more information, see Sending and receiving events between AWS Regions in Amazon EventBridge

Related information

Why does my EventBridge rule for IAM events only trigger in the us-east-1 Region?

How do I troubleshoot issues with cross-account or cross-Region Amazon EventBridge rules?

AWS OFFICIALUpdated 10 months ago
1 Comment

Thanks, the resolution section offers practical advice on using cross-Region and cross-account event buses as targets to enable workflows triggered in one region but invoking targets in a different region or account. This solution provides flexibility and ensures efficient event routing across different AWS environments.

replied 2 years ago