> 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/monitoring/appsec-ali-37.md).

# Alibaba RDS instance has log\_connections disabled misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_ALI\_37           |
| Category - Subcategory | Monitoring - Unintegrated |
| Provider               | ALIBABA\_CLOUD            |
| Severity               | LOW                       |
| Framework              | Terraform                 |

## Impact

This rule ensures that the `log_connections` parameter is enabled for Alibaba Cloud RDS instances. Enabling this parameter logs connection attempts to the database, providing valuable information for monitoring, troubleshooting, and auditing. These logs can help detect unauthorized access attempts, investigate connection issues, and ensure better database management.

Failing to enable this parameter reduces visibility into connection activity, which may hinder security monitoring and operational diagnostics.

## How to Fix

*Resource:* alicloud\_rds\_instance

* *Arguments:* log\_connections

To mitigate this issue, ensure the `log_connections` parameter is set to `on` in the RDS instance configuration.

## Example: \[source,go]

resource "alicloud\_rds\_instance" "example" { ... parameter {

* name = "log\_connections"
* value = "on" } }

***


---

# 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/monitoring/appsec-ali-37.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.