---
title: Multi-AZ Aurora Cluster
url: https://www.tines.com/docs/self-hosted/best-practices/multi-az-aurora-cluster/
updated: 2026-03-18T11:09:18+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt) › [Self-Hosted](https://www.tines.com/llm/docs/self-hosted.md) › [Best Practices](https://www.tines.com/llm/docs/self-hosted/best-practices.md)*

# Multi-AZ Aurora Cluster

*[View on tines.com](https://www.tines.com/docs/self-hosted/best-practices/multi-az-aurora-cluster/)*

> **NOTE:**
> ### Prerequisites
> 
> -   Ensure you have an Aurora PostgreSQL database cluster already set up with one instance. This step is covered [here](https://www.tines.com/docs/self-hosted/deploying-tines/aws-fargate/deployment-guide/#step-4-create-a-postgres-database).
> -   Retrieve the **db-cluster-identifier** of your previously created aurora cluster.

## Configuration Steps

### Step 1. **Verify Current Aurora Cluster Configuration**

Ensure that your current Aurora PostgreSQL cluster is correctly set up:

```bash
aws rds describe-db-clusters --db-cluster-identifier <your-cluster-identifier>
```

### Step 2. **Create a Second Instance in a Different Availability Zone**

- Identify the current Availability Zone (AZ) of your existing instance.
- Choose a different AZ for the new instance to enable Multi-AZ deployment.

```bash
aws rds create-db-instance \
  --db-instance-identifier <new-instance-identifier> \
  --db-cluster-identifier <your-cluster-identifier> \
  --engine aurora-postgresql \
  --db-instance-class db.t4g.large \
  --availability-zone <new-availability-zone> \
  --db-subnet-group-name tines-db
```

### Step 3. **Enable Automatic Failover**

- Verify that the new instance is part of the cluster and located in a different AZ.
- Ensure the cluster is set to automatically failover to the secondary instance in case of a failure.

```bash
 aws rds modify-db-cluster \
  --db-cluster-identifier <your-cluster-identifier> \
  --apply-immediately \
  --multi-az-enabled 
```

### Step 4. **Configure Cluster Parameters for High Availability**

- Modify the cluster parameter group to optimize settings for high availability.

```bash
 aws rds modify-db-cluster-parameter-group \
  --db-cluster-parameter-group-name <your-cluster-parameter-group> \
  --parameters "ParameterName=auto_failover_enabled,ParameterValue=1,ApplyMethod=immediate"
```

### Step 5. **Verify Multi-AZ Configuration**

- Ensure the cluster is now Multi-AZ with automatic failover enabled.

```bash
 aws rds describe-db-clusters --db-cluster-identifier <your-cluster-identifier>
```