Security in Monitoring

Who may read metrics and logs and manage alarms, checks and status pages (IAM), what is audited, and what leaves the platform.

Last updated 18 November 2026View as Markdown

IAM actions

Every request, through the API, the CLI, Terraform or the console, is checked against your IAM policies. Monitoring's resource names have no region:

Resource Resource name Actions checked on it
An alarm rn:ews::<organization id>:monitoring:alarm/<alarm id> Reading, changing and deleting one alarm, and its history
A check rn:ews::<organization id>:monitoring:check/<check id> Reading, changing, pausing, resuming and deleting one check, and its results and outages
A status page rn:ews::<organization id>:monitoring:status-page/<page id> Reading, changing and deleting one page, its components, its incidents and its subscribers
The service rn:ews::<organization id>:monitoring:* Every metric and log read, publishing custom metrics, every list, and creating alarms, checks and pages
ActionAccessWhat it allows
monitoring:ListMetricsReadList the monitored resources and the metrics recorded for each
monitoring:GetMetricDataReadRead metric datapoints for a resource over a time range
monitoring:PutMetricDataWritePublish datapoints to custom metrics (the API, OTLP/HTTP and StatsD through the deploy agent)
monitoring:DescribeAlarmsReadList alarms and their current state
monitoring:DescribeAlarmHistoryReadRead the state changes of an alarm
monitoring:PutMetricAlarmWrite · destructiveCreate an alarm or change its threshold, period or notifications
monitoring:DeleteAlarmsWrite · destructiveDelete an alarm and its history
monitoring:FilterLogEventsReadSearch the log lines an app box shipped
monitoring:DescribeChecksReadList uptime checks and their current state
monitoring:GetCheckResultsReadRead an uptime check’s results, response times and outages
monitoring:CreateCheckWriteCreate an uptime check that requests a URL on a schedule
monitoring:UpdateCheckWriteChange what an uptime check requests, how often, and who it notifies
monitoring:PauseChecksWrite · destructiveStop running an uptime check, without changing it
monitoring:ResumeChecksWriteRun a paused uptime check again
monitoring:DeleteChecksWrite · destructiveDelete an uptime check, its results and its outage log
monitoring:DescribeStatusPagesReadList status pages and read one: its components, incidents and subscribers
monitoring:CreateStatusPageWritePublish a status page at {slug}.status.{root}
monitoring:UpdateStatusPageWrite · destructiveChange a status page: its title, address, components and webhook subscribers
monitoring:DeleteStatusPageWrite · destructiveDelete a status page, its incidents and its subscribers
monitoring:CreateIncidentWritePost an incident on a status page; its subscribers are told
monitoring:UpdateIncidentWritePost an update to an incident, or resolve it; its subscribers are told
monitoring:DeleteIncidentWrite · destructiveRemove an incident and its updates from a status page

Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.

  • Metric and log reads cover every resource of the organization; a policy cannot grant the metrics or logs of one machine or one app.
  • A policy that grants monitoring:DescribeAlarms on one alarm lets its holder read that alarm, but not list alarms: the list needs the action on rn:ews::<organization id>:monitoring:*. The same holds for checks and status pages.
  • Incidents and subscribers are checked on their page, so someone on call can post incidents on one page and change nothing else.
  • Reading one alarm, check or status page you may not read answers 404, the same as one that does not exist. A refused write answers 403.
  • StatsD from an app's machine is published with the app's own credentials, not with monitoring:PutMetricData.

A policy for someone who may post and update incidents on one status page (replace org-id and page-id):

{
  "Version": "2024-01-01",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "monitoring:DescribeStatusPages",
        "monitoring:CreateIncident",
        "monitoring:UpdateIncident"
      ],
      "Resource": "rn:ews::org-id:monitoring:status-page/page-id"
    }
  ]
}

With it alone, the console's Status pages list shows an access-denied notice; the page itself opens at its own console address. To use the list, also grant monitoring:DescribeStatusPages on rn:ews::org-id:monitoring:*, which lets them see every page of the organization.

Audit

Creating, changing and deleting alarms, checks, status pages, components, incidents and subscribers, and pausing and resuming checks, are recorded in the audit log, allowed or denied, once the request has passed its validation: a request with a malformed body or an id that is not a UUID is refused before the permission check and not recorded. Publishing custom metrics is recorded only when it is denied. A refused list, metric read or log search (403) is recorded at most once a minute per user and action; a refused read of one alarm, check or status page answers 404 and is not recorded. Allowed reads are not recorded. See Audit log.

What leaves the platform

  • Alarm and check notifications are mailed to the addresses you enter, and posted to your webhooks over https, to public addresses only. Nothing confirms an alarm's or a check's addresses before they are mailed.
  • Uptime checks request your URLs from the control plane and the probe locations, and only public addresses.
  • A status page, its incidents and its summary.json are public, without sign-in. Subscriber addresses are not shown on it; the subscribe form answers the same whether or not an address was already subscribed.
Did this page help you?