# Aurora Global Database DuploCloud supports [Aurora Global Database](https://aws.amazon.com/rds/aurora/global-database/), a multi-region Aurora database that lets applications read from local copies if a region goes down. This setup improves application performance for global audiences and helps maintain availability during regional outages. ## Creating the Primary Aurora Cluster 1. In the DuploCloud Portal, navigate to **Cloud Services** → **Database.** 2. Select the **RDS** tab, and click **Add**. The **Create a RDS** pane displays.

3. Complete the required fields:


RDS Name	Enter a unique name for the primary cluster.
RDS Engine	Select Aurora MySQL or Aurora PostgreSQL.
RDS Engine Version	Select a compatible version that supports Global Aurora: Aurora MySQL: 5.7+ or 8.0+ Aurora PostgreSQL: 11+
RDS Instance Size	Select a supported instance size for Global Aurora (db.r5 or higher).
User Name	Enter the username for the cluster administrator.
User Password	Enter a password for the cluster administrator.

4. Complete any other optional fields to configure your database according to your needs (see the [RDS database](https://docs.duplocloud.com/docs/automation-platform/overview/aws-services/database/rds-database) page for optional field descriptions). 5. Click **Create** to provision the primary cluster. Allow 5–10 minutes for it to become available ## Adding a Secondary Region to Create a Global Aurora Cluster 1. Navigate to **Cloud Services** → **Database**. 2. Select the **RDS** tab. 3. Select the primary Aurora cluster you previously created in the **NAME** column. 4. Click **Actions** → **RDS Settings** → **Add Region**. The **Add Region** pane displays.

5. Complete the following fields:


Global Cluster Name	Enter a custom name for the global cluster name by adding a suffix or unique identifier. Do not remove or change the prefix. Each Aurora cluster can belong to only one Global Aurora cluster. Global cluster names must be unique within your account/region. Attempting to add a cluster to multiple global clusters will fail.
Tenant	Select the tenant in the secondary region where the read-only cluster will be created.
Secondary Cluster Name	Enter a unique name for the secondary (read-only) cluster by adding a suffix or unique identifier. Do not remove or change the prefix.

6. Click **Update** to provision the secondary cluster. 7. Once the secondary cluster is created, allow up to 40 minutes for it to become available, then follow the steps under **Viewing a Global Cluster** to verify the global setup. ## Viewing a Global Cluster 1. Navigate to **Cloud Services** → **Database.** 2. Select the **RDS** tab. 3. Select the the cluster you wish to view from the **NAME** column. 4. Select the **Global Cluster** tab. For each cluster in the global setup, the following information is shown:

Column	Description
Cluster Name	The name of the cluster.
Region	The AWS region where the cluster resides
Role	Indicates whether the cluster is the Primary (write) or Secondary (read-only replica)
Status	The current status of the cluster (e.g., Available, Created)

## Accessing Aurora Cluster Endpoints Each cluster in a global Aurora setup has a specific role: the primary cluster handles all writes, and secondary clusters handle reads in their respective regions. Follow the steps below to connect to each type of cluster. ### Connecting to the Primary Cluster 1. Select the appropriate tenant, go to **Cloud Services** → **Database** → **RDS**, and click on the primary cluster name. 2. Copy the **Writer** endpoint. 3. Use this endpoint for all write operations (`INSERT`, `UPDATE`, `DELETE`).

RDS details page for the primary Aurora database with the Writer endpoint highlighted

### Connecting to Secondary Clusters Each secondary cluster in a different region has its own reader endpoint. 1. Select the appropriate tenant, go to **Cloud Services** → **Database** → **RDS**, and click on the secondary cluster name. 2. Copy the **Reader** endpoint for that cluster. 3. Use this endpoint for all read operations (`SELECT` queries) in that region. ## Using Headless Aurora Clusters Enabling headless mode allows a secondary cluster to exist without any running DB instances while continuing to replicate data from the primary cluster. This is useful for cost optimization when read capacity in the secondary region is not required. For additional details, refer to the [Amazon Aurora Global Database documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-attach.console.headless.html). ### Making a Secondary Cluster Headless 1. Go to **Cloud Services** → **Databases** → **RDS**. 2. Select the primary Aurora cluster in the **NAME** column. 3. Click the **Global Cluster** tab to see all clusters in the global setup. 4. Click on the secondary cluster name to display the secondary cluster details page. 5. Click **Actions** → **RDS Settings** → **Make Cluster Headless**. {% hint style="info" %} **Note:** You can add a reader instance back to a headless cluster later if read capacity is needed. {% endhint %}

Actions menu with headless cluster options highlighted

#### Adding a Reader Instance Back to a Headless Cluster 1. Navigate to **Cloud Services** → **Databases** → **RDS**. 2. Select the primary Aurora cluster in the **NAME** column. 3. Click the **Global Cluster** tab to view clusters in the global setup. 4. Click on the secondary cluster name (the headless one) to display its details page. 5. Click **Actions** → **RDS Settings** → **Add RDS Instance**. 6. Configure the instance type, size, and any other required settings, then click **Add**. 7. Wait a few minutes for the instance to become available. After that, it will act as a **reader endpoint** for read operations in that region.