Alert on denied calls and on changes to the agent's role or policies
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 30 of 30: Alert on denied calls and on changes to the agent's role or policies. A string of denied calls or an edit to the agent's role is often the first visible sign of misuse. Without an alert, these show up only after the damage.
The whole checklist ยท The map
Why it matters
A string of denied calls or an edit to the agent's role is often the first visible sign of misuse. Without an alert, these show up only after the damage.
How, in each cloud
- AWS
- Send CloudTrail events to CloudWatch Logs and alarm on matching events.
- Google Cloud
- Create log-based alerting policies that notify you when a specific message appears in logs.
- Azure
- Create Azure Monitor alert rules on log data.
What the documentation says
- "Complete the following steps to configure CloudTrail with CloudWatch Logs to monitor your trail logs and" (source)
- "You can configure an alerting policy to notify you whenever a specific message" (source)
- "You can alert on any metric or log data source in the Azure Monitor data platform." (source)
Related pages
- Give each agent its own role or service account, not a shared one: the check, and how in AWS, Google Cloud and Azure
- Use short-lived role credentials and no long-lived access keys for the agent: the check, and how in AWS, Google Cloud and Azure
- Limit who can pass, attach or impersonate the agent's role: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/awscloudtrail/latest/userguide/monitor-cloudtrail-log-files-, read 10 Nov 2026
- cloud.google.com/logging/docs/alerting/log-based-alerts, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-overview, read 10 Nov 2026
Last reviewed 16 Nov 2026.