> 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/public-exposure/appsec2-aws-49.md).

# AWS Database Migration Service endpoint do not have SSL configured misconfiguration detected in code

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AWS\_49                           |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | AWS                                        |
| Severity               | LOW                                        |
| Framework              | Terraform                                  |
| Mapped CSPM/KSPM Rule  | 61764822-555e-4492-b9d6-0b5210e11ee4       |

## Impact

This rule identifies Database Migration Service (DMS) endpoints that are not configured with SSL to encrypt connections for source and target endpoints.

It is recommended to use SSL connection for source and target endpoints; enforcing SSL connections help protect against 'man in the middle' attacks by encrypting the data stream between endpoint connections.

NOTE: Not all databases use SSL in the same way.

An Amazon Redshift endpoint already uses an SSL connection and does not require an SSL connection set up by AWS DMS. So there are some exclusions included in policy RQL to report only those endpoints which can be configured using DMS SSL feature. For more details <https://docs.aws.amazon.com/dms/latest/userguide/CHAP\\_Security.html#CHAP\\_Security.SSL\\[see> here.]

## How to Fix

## \[source,go]

## resource "aws\_dms\_endpoint" "pass\_source\_1" { certificate\_arn = "arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012" database\_name = "test" endpoint\_id = "test-dms-endpoint-tf" endpoint\_type = "source" engine\_name = "aurora" extra\_connection\_attributes = "" kms\_key\_arn = "arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012" password = "test" port = 3306 server\_name = "test" ssl\_mode = "require" username = "test" }


---

# 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/public-exposure/appsec2-aws-49.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.