> 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-ali-25.md).

# Alibaba Cloud RDS Instance SQL Collector Retention Period is less than 180 misconfiguration detected

## Rule Details

|                        |                     |
| ---------------------- | ------------------- |
| Cortex AppSec Rule ID  | APPSEC\_ALI\_25     |
| Category - Subcategory | Logging - Retention |
| Provider               | ALIBABA\_CLOUD      |
| Severity               | LOW                 |
| Framework              | Terraform           |

## Impact

This rule ensures that Alibaba Cloud RDS (Relational Database Service) instances have the SQL collector enabled and its retention period set to 180 days or more. Enabling the SQL collector and setting an adequate retention period helps in tracking and analyzing the SQL queries made to the database, which can be useful for performance tuning, troubleshooting, and security analysis.

Failing to enable the SQL collector or setting a short retention period may result in insufficient data for analysis, making it difficult to identify performance issues or security threats.

## How to Fix

*Resource:* alicloud\_db\_instance

* *Arguments:* sql\_collector\_status, sql\_collector\_config\_value

To mitigate this issue, ensure that the `sql_collector_status` attribute is set to `Enabled`, and the `sql_collector_config_value` attribute is set to `180` or more in the `alicloud_db_instance` resource.

## Example: \[source,go]

resource "alicloud\_db\_instance" "example" { ...

* sql\_collector\_status = "Enabled"
* sql\_collector\_config\_value = 180 }

***


---

# 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-ali-25.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.