- Newest
- Most votes
- Most comments
It seems the severity attribute in the chatbot output comes from $.detail.packageVulnerabilityDetails.vendorSeverity in the original event, while the matching criterion for the EventBridge rule uses the $.detail.severity field of the original event from Inspector. That original value isn't shown in the output.
You might want to try including the original $.detail.severity value in the chatbot output temporarily to see what it contained. Based on your configuration, it would seem to contain either the value HIGH or CRITICAL. If you want your filter to match based on the same value that is currently shown in the chatbot output, you should define your EventBridge rule pattern to match the field $.detail.packageVulnerabilityDetails.vendorSeverity, such as like this:
{
"source": ["aws.inspector2"],
"detail-type": ["Inspector2 Finding"],
"detail": {
"status": ["ACTIVE"],
"packageVulnerabilityDetails": {
"vendorSeverity": ["HIGH", "CRITICAL"]
}
}
}
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 13 days ago

Of course, that's it! No idea how I did not see that. Thank you!