> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview/aws-services/database/rds-database/enable-or-disable-rds-logging.md).
# Enable or disable RDS logging
Turn logging on or off for an AWS RDS
You can enable or disable logging for an RDS database at any time, using the DuploCloud Portal.
## Prerequisites
To update logging for an RDS, you must select the **Enable Logging** option when you [create the RDS](/docs/automation-platform/overview/aws-services/database/rds-database.md).
## Update RDS logging
1. In the DuploCloud Portal, navigate to **Cloud Services** -> **Databases**.
2. In the **RDS** tab, from the **Name** column, select the database for which you want to enable or disable logging.
3. Click the **Actions** menu, select **RDS Settings**, and then **Update Logging**. The **Update Logging** pane displays.
Actions menu with Update Logging option
4. Select or deselect **Enable Logging** to turn logging on or off, respectively.
Update logging pane
5. Click **Update**.
View the status of the **EnableLogging** attribute in the **Details** tab.
Details tab with EnableLogging attribute
---
# 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://docs.duplocloud.com/docs/automation-platform/overview/aws-services/database/rds-database/enable-or-disable-rds-logging.md?ask=&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.
