> 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-353.md).

# RDS instances have performance insights disabled misconfiguration detected in code

## Rule Details

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

## Impact

This rule is checking to verify if RDS instances have performance insights enabled. Performance insights allow for an advanced database monitoring feature that makes it easy to diagnose and solve performance issues on Amazon RDS databases. If this feature is not enabled, the user may struggle to identify the cause of issues impacting the performance of their RDS instances. Inadequate monitoring could lead to extended downtime, inefficient use of resources and potential loss of data, all of which may have significant impacts on a business's operations and profitability. Therefore, it's a bad practice not to enable performance insights on RDS instances.

## How to Fix

*Resource:* 'aws\_rds\_cluster\_instance', 'aws\_db\_instance'

* *Arguments:* performance\_insights\_enabled

## To fix the issue, you should enable Performance Insights for your RDS instance in your terraform file. Here is how you can do it: \[source,go]

resource "aws\_db\_instance" "default" { allocated\_storage = 10 engine = "mysql" engine\_version = "5.7" instance\_class = "db.t2.micro" name = "mydb" username = "foo" password = "foobarbaz" parameter\_group\_name = "default.mysql5.7"

* performance\_insights\_enabled = true }

***


---

# 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/appsec-aws-353.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.