1 Answer
- Newest
- Most votes
- Most comments
0
EventBridge is used for events that indicate a change in your resources, for example - Describe*, Put*, Get*
actions etc. And, for your use case 'Subscription filter' is an appropriate solution which is native to CloudWatch Logs. Using Subscription filter, which monitors for a particular pattern you mention - for any newly ingested events, you can set a destination (like a target in EventBridge) where these filtered out events are sent.
Please keep in mind that these filters don't work retroactively, and are meant for only the log events ingested once after the filter is created.
Relevant content
- asked 2 years ago
- asked 7 months ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago