Change an alarm

Change an alarm's rule or recipients, or stop and resume its notifications.

Last updated 18 November 2026View as Markdown

Replace alarm-id with the alarm's id. Send only the fields to change; the others keep their values.

Important

Changing what the alarm measures (resource type, resource, metric, dimensions, statistic, comparison, threshold, period or evaluation periods) resets it to INSUFFICIENT_DATA, with the reason "The alarm was changed and has not been evaluated since.". The reset notifies nobody and adds no history entry, also when the alarm was in ALARM. Changing its name, addresses, webhook or notifications does not reset it.

Prerequisites

  • Permission for monitoring:PutMetricAlarm on the alarm, rn:ews::<organization id>:monitoring:alarm/<alarm id>.
  • In the console, also monitoring:DescribeAlarms to open Alarms. Without monitoring:PutMetricAlarm on an alarm, its notification switch is unavailable, with the note "Needs monitoring:PutMetricAlarm on this alarm."

Stop or resume notifications

With notifications stopped, the alarm keeps being evaluated and its state stays current; only the mail and the webhook stop.

  1. Open Monitoring, then Alarms.
  2. Open the alarm's action menu and choose Stop notifications, or Resume notifications for an alarm whose notifications are off.

The Notifies column shows off while they are stopped.

Change the rule or the recipients

Not available in Console. The console only stops and resumes notifications; change the rest with the CLI, the API or Terraform.

When the change is refused

The alarm as it would be after the change is checked as a whole:

  • 400 "An alarm looks back at most one day (period × evaluation periods)" when the new period or evaluation periods, with the other's current value, pass one day; when the request sets both, the message starts "evaluationPeriods: ".
  • 400 when the new metric is not recorded for the resource type, 404 "Resource not found" for a new resource your organization does not have.
  • 409 "An alarm named "…" already exists" for a new name that is taken.
  • 404 "Alarm not found" when your organization has no such alarm.
Did this page help you?