---
title: "Select CloudWatch alarms to investigate | Proofline Help"
description: "Choose the alarms Proofline should watch for an environment in a particular AWS account and region. Saving the watch tests the history read for the selected alarms."
url: https://proofline.sh/help/aws-watch-cloudwatch-alarms/
---

[Help center](/help/)

# Select CloudWatch alarms to investigate

Choose the alarms Proofline should watch for an environment in a particular AWS account and region. Saving the watch tests the history read for the selected alarms.

## Save the watch on deploy verification setup

1.  Open the environment's **Setup → Deploy verification** page.
2.  Under **Watched alarms**, select **Choose alarms**.
3.  Select the linked **AWS account and region**.
4.  Select up to 20 alarms from the metric and composite alarms the read role can describe there.
5.  Select **Save alarms**.

Proofline watches each linked AWS account and region on its own. To also read alarms in another one, such as us-east-1 for Route 53 health checks or CloudFront, select **Watch another account or region** under **Watched alarms** and repeat steps 3 to 5. **Watched alarms** lists each watch under its account and region, with its own **Change alarms** and **Stop watching**. Saving or stopping one leaves the others as they are, and so does unlinking an account or region from the environment.

Saving reads each chosen alarm's recent history through the read role first, so a saved watch can read every alarm it holds. If AWS refuses that read, nothing is saved, and the form names the alarm and the refused `cloudwatch:DescribeAlarmHistory` beside the alarm list. Select **Update the AWS role**, update the installed role to the current template, which grants it, and save again.

## Related guides

-   [Turn on the production loop for AWS](/help/aws-production-loop/)
-   [Connect Amazon Web Services](/help/connect-aws/)
