- Newest
- Most votes
- Most comments
Hi,
You can have an introductory read on this: https://aws.amazon.com/blogs/compute/introducing-cross-region-event-routing-with-amazon-eventbridge/
It provides some good practices and limitations on the approach.
Hope it helps ;)
Duplicate Your Event Sources & Targets in the Secondary Region It appears that your event sources (daily 9pm trigger and file drop to S3 bucket) and targets (ECS Clusters) are already in both regions. If not, you'll need to duplicate your setup in the secondary region.
Cross-Region EventBridge Setup AWS EventBridge does not support cross-region event delivery natively. However, you can work around this by leveraging SNS, SQS, or Lambda. Here's an example with SNS:
Create an SNS Topic in your secondary region. Create an EventBridge rule in your primary region that targets the SNS Topic in the secondary region. Create an EventBridge rule in the secondary region that triggers based on messages published to the SNS Topic. This setup allows events triggered in your primary region to be sent to your secondary region.
Consider Implementing Cross-Region Replication for S3 If you want to make sure the S3 bucket event is also triggered in the secondary region if the primary region is down, consider implementing cross-region replication (CRR) for your S3 buckets. CRR automatically copies new objects across buckets in different AWS regions.
Implement Failover Strategy In case of failure in the primary region, you'll want a mechanism to failover to the secondary region. You can do this with Route53's DNS failover feature. You can set up health checks and if a check fails, Route53 can reroute traffic to your resources in your secondary region.
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
Yes, I did read that guide. The event producers reside in a single region, which is problematic for our DR plan. If we lose that region, there will be no event for the consumers to process.