Unfortunately, the there is no integration in place yet between AWS Config Aggregator feature and AWS CloudWatch event rules. The reason for this is the AWS Config Aggregator feature is supporting Multi-account & Multi-region. However, AWS CloudWatch service (event rules) is a regional service. Therefore, at the moment we can't build Cloudwatch event rule based on the aggregated data received from multi-account & multi-region. Hence, as of now there is no out of the box solution.
However that there is an existing feature request in place for this functionality of including CloudWatch Event Delivery along with the Config Aggregation, As is the case with all feature requests, the internal team takes them seriously and evaluates every request, but we are unable to share any rough ETA for delivering this feature as inclusion of any new feature needs rigorous testing and shall be prioritized along with the team's additional workload. However, any new announcements will be made in our What's New page What's New page [https://aws.amazon.com/new/] and our Official Blog [https://aws.amazon.com/blogs/aws/].
any update about this topic?
Today, EventBridge Rules can only match on events published in the same account.
However, you can set as a target of that Rule an Event Bus in another account.
Meaning, you should be able to create rules that match events in each accounts where they're occurring, then route them to a central account and event bus, then process them all there.
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- Why is my AWS Config data not getting collected by the aggregator for my AWS account or AWS Organizations account?AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago