# aws cloudwatch disable-alarm-actions

AWS CLI commands · Updated 16 November 2026

**Short answer:** aws cloudwatch disable-alarm-actions --alarm-names alarm-a alarm-b stops those alarms from sending notifications or running actions, while they keep evaluating and changing state. Turn them back on with enable-alarm-actions; until you do, the alarms stay silent indefinitely.

## What the command does

Each alarm has an `ActionsEnabled` flag. This command sets it to false for up to 100 alarms per call. The alarm still evaluates its metric, still moves between `OK`, `ALARM` and `INSUFFICIENT_DATA`, and still records history, but no SNS notifications, Auto Scaling policies or EC2 actions run.

That makes it the right tool for planned maintenance and the wrong tool for an alarm that is simply noisy, because muted alarms tend to be forgotten.

## Syntax

```
aws cloudwatch disable-alarm-actions --alarm-names <name> [<name> ...]
aws cloudwatch enable-alarm-actions  --alarm-names <name> [<name> ...]
```

Both print nothing on success, so confirm the result with `describe-alarms` and the `ActionsEnabled` field.

## Worked examples

**Mute every alarm for a service during a maintenance window**:

```
ALARMS=$(aws cloudwatch describe-alarms --alarm-name-prefix prod-orders- \
  --query "MetricAlarms[].AlarmName" --output text)
echo "$ALARMS" | tr '\t' '\n' > muted-alarms.txt
aws cloudwatch disable-alarm-actions --alarm-names $ALARMS
```

Saving the list means you re-enable exactly what you muted, not alarms someone else had muted deliberately.

**Unmute afterwards**:

```
aws cloudwatch enable-alarm-actions --alarm-names $(cat muted-alarms.txt)
```

**Find alarms that are still muted**:

```
aws cloudwatch describe-alarms --alarm-types MetricAlarm CompositeAlarm \
  --query "[MetricAlarms[?ActionsEnabled==\`false\`].AlarmName, CompositeAlarms[?ActionsEnabled==\`false\`].AlarmName][]" \
  --output text
```

**Check which of them are currently in ALARM**, a problem nobody is being told about:

```
aws cloudwatch describe-alarms --state-value ALARM \
  --query "MetricAlarms[?ActionsEnabled==\`false\`].[AlarmName,StateUpdatedTimestamp]" --output table
```

## Ways to quieten an alarm

| Approach | Best for |
|---|---|
| `disable-alarm-actions` | Planned maintenance, with a reminder to re-enable. |
| Composite alarm with an actions suppressor | Recurring windows, or muting children while a parent alarm (such as "deployment in progress") is active. |
| Tuning the alarm with `put-metric-alarm` | Noisy alarms: change the threshold, use M of N datapoints or a longer period. |
| `delete-alarms` | Alarms that nobody acts on; deleting is more honest than muting forever. |

## Gotchas

- **No expiry.** There is no "mute for two hours" option on this command. Schedule the re-enable (for example with EventBridge Scheduler) or put it in the change checklist.
- **Automation stops too.** Muting an alarm that drives scaling or EC2 recovery disables that behaviour, not just the emails.
- **Infrastructure as code.** A later stack deploy may re-enable actions if the template sets `ActionsEnabled: true`, which can surprise you mid-maintenance.
- **Re-enabling does not resend.** If the alarm went into `ALARM` while muted, enabling actions does not replay the notification; you will hear about it only on the next state change.
- **100 names per call.** The command accepts at most 100 alarm names at once, so split longer lists, for example with `xargs -n 100`.
- **Tell people.** Note the muted alarms in the change ticket or team channel so whoever is on call knows which signals are silent.

## Questions

### How do I disable a CloudWatch alarm permanently?

Disabling actions has no time limit, so it stays muted until you run enable-alarm-actions. If nobody needs the alarm, delete it with aws cloudwatch delete-alarms instead.

### Does disabling alarm actions stop the alarm evaluating?

No. It still evaluates and changes state; only notifications and automated actions stop.

### How do I mute CloudWatch alarms on a schedule?

Use a composite alarm with an actions suppressor, or schedule disable and enable calls with EventBridge Scheduler.

## When this happens away from your desk

Muting alarms is easy to do and easy to forget, which is risky when nobody is at a desk. CloudConsole, a phone app for AWS, is built with guardrails and to make muted alarms visible on a phone.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [AWS CLI Command Reference: cloudwatch disable-alarm-actions](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/disable-alarm-actions.html)
- [DisableAlarmActions API reference](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_DisableAlarmActions.html)
- [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html)

## Related

- [How to mute CloudWatch alarms](https://cloudconsole.dev/how-to/mute-cloudwatch-alarms)
- [aws cloudwatch describe-alarms](https://cloudconsole.dev/cli/cloudwatch-describe-alarms)
- [aws cloudwatch set-alarm-state](https://cloudconsole.dev/cli/cloudwatch-set-alarm-state)
- [aws cloudwatch put-metric-alarm](https://cloudconsole.dev/cli/cloudwatch-put-metric-alarm)
- [aws cloudwatch describe-alarm-history](https://cloudconsole.dev/cli/cloudwatch-describe-alarm-history)
- [aws cloudwatch get-metric-data](https://cloudconsole.dev/cli/cloudwatch-get-metric-data)

---

Source: https://cloudconsole.dev/cli/cloudwatch-disable-alarm-actions

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
