- Newest
- Most votes
- Most comments
Can you please describe the steps you've already taken?
There are several potential issues ranging from Access/Permissions issues to trigger issues and/or delivery issues.
Did you create a new/dedicated Event Bus? It's recommended to Not use the default bus.
Best practices also include:
- Set a single target for each rule
- Set rule permissions using least-privilege
- Monitor rule performance
Additional considerations:
- EventBridge ignores the fields in the event that aren't included in the event pattern. The effect is that there is a "": "" wildcard for fields that don't appear in the event pattern.
- The values that event patterns match follow JSON rules. You can include strings enclosed in quotation marks ("), numbers, and the keywords true, false, and null.
- For strings, EventBridge uses exact character-by-character matching without case-folding or any other string normalization.
- For numbers, EventBridge uses string representation. For example, 300, 300.0, and 3.0e2 are not considered equal.
- If multiple patterns are specified for the same JSON field, EventBridge only uses the last one.
- Be aware that when EventBridge compiles event patterns for use, it uses dot (.) as the joining character.
Are you seeing the "Events" counter increase in CloudWatch?
Thanks for the reply, Randy. Well, I’m still not sure. The rules seem okay, the permissions are okay, but the rule is not activated.
Hello.
Are trails enabled in CloudTrail?
If this is not enabled, EventBridge will not be able to retrieve AWS API events via CloudTrail.
https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-log-api-call.html
Thanks for the fast answer again, Riku-san! I’m afraid it’s enabled, though :( The permissions for the rule and the target are all set.
Relevant content
asked 6 years ago
asked 3 years ago
- AWS OFFICIALUpdated a year ago

BTW, The snippet above is not related to cloudwatch logs but Event Bridge Rule. Cloudwatch Log doesnt come into play here