> 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/aws-extension/aws-extension/policy-model/databases/rds.md).

# RDS

Amazon RDS provides managed relational databases. The AWS Extension supports provisioning both single RDS instances and multi-node Aurora clusters inside an Environment.

## Spec

{% tabs %}
{% tab title="RDS Instance" %}
A single database instance. Suitable for MySQL, PostgreSQL, MariaDB, SQL Server, Oracle, and non-Aurora deployments.

| Field                | Description                                                                                      |
| -------------------- | ------------------------------------------------------------------------------------------------ |
| **Engine**           | Database engine: MySQL, PostgreSQL, MariaDB, SQL Server, Oracle, Aurora MySQL, Aurora PostgreSQL |
| **Engine Version**   | The database engine version                                                                      |
| **Instance Class**   | The compute and memory capacity (e.g. `db.t3.medium`)                                            |
| **Storage**          | Allocated storage size in GB and type (gp2, gp3, io1)                                            |
| **Multi-AZ**         | Deploy a standby replica in a different AZ for high availability                                 |
| **Database Name**    | The initial database name                                                                        |
| **Username**         | The master username                                                                              |
| **Backup Retention** | Number of days to retain automated backups (0 to disable)                                        |
| **Encryption**       | Enable encryption at rest using the Environment's KMS key                                        |
| {% endtab %}         |                                                                                                  |

{% tab title="Aurora Cluster" %}
A multi-node Aurora cluster with a writer endpoint and one or more reader endpoints.

| Field                   | Description                                  |
| ----------------------- | -------------------------------------------- |
| **Engine**              | Aurora MySQL or Aurora PostgreSQL            |
| **Engine Version**      | The Aurora engine version                    |
| **Instance Class**      | The instance class for cluster nodes         |
| **Number of Instances** | Total number of instances (writer + readers) |
| **Database Name**       | The initial database name                    |
| **Backup Retention**    | Days to retain automated backups             |
| **Encryption**          | Enable encryption at rest                    |
| {% endtab %}            |                                              |
| {% endtabs %}           |                                              |

## Dependencies

RDS resources require an **Environment**. The Environment's Network Baseline must have RDS subnet groups available (created automatically during network provisioning).


---

# 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:

```
GET https://docs.duplocloud.com/docs/aws-extension/aws-extension/policy-model/databases/rds.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.