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

# AWS RDS database instance not configured with encryption in transit misconfiguration detected in cod

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_69                           |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | AWS                                        |
| Severity               | MEDIUM                                     |
| Framework              | CloudFormation, Terraform, Terraform Plan  |
| Mapped CSPM/KSPM Rule  | 4ea6de73-a950-4d1b-95ba-84a5d9f4b5d4       |

## Impact

This rule detects whether an Amazon RDS database instance is not configured to use data-in-transit encryption, potentially exposing sensitive data to unauthorized access through unencrypted data transmission between the database and other services or clients. A lack of encryption in transit increases the risk of data interception and unauthorized access, leading to potential data breaches. Implementing encryption in transit is crucial for maintaining data integrity and confidentiality in cloud environments."

## How to Fix

*Resource:* AWS::RDS::DBInstance, AWS::RDS::DBParameterGroup

* *Arguments:* Parameters

## This example shows how to configure SSL enforcement for a DB2 instance using an AWS RDS DBParameterGroup in a CloudFormation template. \[source,go]

## Resources: DB2PassParam: Type: "AWS::RDS::DBParameterGroup" Properties: Description: "My DB2 parameter group" Family: "1db2-ae1" Parameters: db2comm: "SSL"


---

# 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/storage/appsec2-aws-69.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.