> 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/appsec2-aws-30.md).

# AWS Postgres RDS have Query Logging disabled misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_30              |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | AWS                           |
| Severity               | LOW                           |
| Framework              | Terraform, Terraform Plan     |

## Impact

This check ensures that you have enabled query logging set up for your PostgreSQL database cluster. A cluster needs to have a non-default parameter group and two parameters set - that of *log\_statement* and *log\_min\_duration\_statement*, these need to be set to *all* and *1* respectively to get sufficient logs. *Note* Setting querying logging can expose secrets (including passwords) from your queries, - restrict and encrypt to mitigate.

## How to Fix

You will need to have a resource aws\_rds\_cluster\_parameter\_group that is referred to your aws\_rds\_cluster\_parameter\_group

attribute: db\_cluster\_parameter\_group\_name.

With that in place the following parameters need to be set:

## For more details see the aws docs here: <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER\\_LogAccess.Concepts.PostgreSQL.html> \[source,go]

resource "aws\_db\_parameter\_group" "examplea" { name = "rds-cluster-pg" family = "postgres10"

* parameter {
* name="log\_statement"
* value="all"
* }
* parameter {
* name="log\_min\_duration\_statement"
* value="1"
* } }

***


---

# 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/logging/appsec2-aws-30.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.