> 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/logging/appsec-aws-324.md).

# RDS Cluster log capture is disabled misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_324              |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | AWS                           |
| Severity               | MEDIUM                        |
| Framework              | Terraform, Terraform Plan     |

## Impact

This rule is inspecting for the activation of log capture on RDS Clusters in AWS. Log capture is crucial for efficient diagnostics, security review and audit. It allows administrators to monitor activities and events that occur in the RDS clusters by capturing log data. If log capture is not enabled, it may compromise the ability to effectively troubleshoot issues or identify malicious activities, leaving the system vulnerable.

## How to Fix

*Resource:* aws\_rds\_cluster

* *Arguments:* enabled\_cloudwatch\_logs\_exports

To fix the issue, you should enable log exports for RDS cluster.

## The above Terraform code captures all RDS Cluster logs using the "enabled\_cloudwatch\_logs\_exports" argument. It makes the logs ("audit", "error", "general", "slowquery", "postgresql") available in CloudWatch Logs, making it secure and compliant with Cortex Cloud APPSEC\_AWS\_324 rule. \[source,go]

resource "aws\_rds\_cluster" "default" { engine = "aurora-postgresql" backup\_retention\_period = 5 preferred\_backup\_window = "07:00-09:00" enable\_http\_endpoint = true master\_username = "foo" master\_password = "bar" skip\_final\_snapshot = true

## enabled\_cloudwatch\_logs\_exports = \["audit", "error", "general", "slowquery", "postgresql"] }


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.