> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/monitoring/appsec-aws-319.md).

# CloudWatch alarm actions are not enabled misconfiguration detected in code

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_319                        |
| Category - Subcategory | Monitoring - Alerting And Notifications |
| Provider               | AWS                                     |
| Severity               | MEDIUM                                  |
| Framework              | Terraform, Terraform Plan               |

## Impact

This rule is verifying that alarm actions in AWS CloudWatch are enabled. AWS CloudWatch is a monitoring service that provides data and actionable insights for AWS applications, resources, and services. Alarm actions are essential functionalities that trigger specific automated responses based on predefined conditions, such as stopping an instance when CPU utilization is too high. If these are not enabled, AWS users may miss alerts on critical issues within their resources and services. Consequently, this could lead to performance degradation, service disruption, or even a security breach. Thus, it's considered a poor security practice not to have CloudWatch alarm actions enabled.

## How to Fix

*Resource:* aws\_cloudwatch\_metric\_alarm

* *Arguments:* actions\_enabled

## To fix the issue indicated by this rule, you will need to ensure that all your CloudWatch alarms have `actions_enabled` not set to `false`. \[source,go]

resource "aws\_cloudwatch\_metric\_alarm" "pass2" { alarm\_name = "alarmname" comparison\_operator = "LessThanThreshold" evaluation\_periods = 1 metric\_name = "HealthyHostCount" namespace = "AWS/NetworkELB" period = 60 statistic = "Average" threshold = var.logstash\_servers\_count alarm\_description = "Number of healthy nodes in Target Group"

* actions\_enabled = true alarm\_actions = \[aws\_sns\_topic.sns.arn] ok\_actions = \[aws\_sns\_topic.sns.arn] dimensions = { TargetGroup = aws\_lb\_target\_group.lb-tg.arn\_suffix LoadBalancer = aws\_lb.lb.arn\_suffix } }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/monitoring/appsec-aws-319.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.