Maximizing Database Durability with Amazon RDS Multi AZ with Two Standbys

Overview

This guide will walk you through setting up Amazon RDS with Multi-AZ and two standbys and how it manages failover in case of primary instance failure.

Introduction

By keeping many standby instances in various Availability Zones (AZs), this configuration is intended to offer automatic failover and enhanced performance.

What is Amazon RDS Multi-AZ with Two Standbys?

Amazon RDS Multi-AZ installations aim to increase your databases’ resilience and availability. Within an AWS Region, they automatically duplicate data across many Availability Zones. This configuration offers high availability and fault tolerance by guaranteeing that your database will continue functioning even in an AZ failure.

Adding a second backup instance improves reliability by improving the multi-AZ with two standby configurations. With this configuration, two standby replicas in separate AZs support your primary database instance. This additional redundancy lowers the chance of data loss and downtime for mission-critical applications that require the greatest availability levels.

Diagram of a multi-AZ DB cluster write path

Key Benefits

• Improved Availability: With two standby instances, failover is faster and more reliable.
• Data Durability: Synchronous replication ensures that your data is consistent across all instances.
• Automatic Failover: Amazon RDS automatically promotes one of the standbys as the new primary if the primary instance fails.

A Guide to Set Up Amazon RDS Multi-AZ with Two Standbys

To set up an Amazon RDS instance with multi-AZ and two standbys, follow these steps: 

Step 1: Access the RDS Console 

• Sign in to the AWS Management Console.
• Navigate to the Amazon RDS service.

Step 2: Launch a new Amazon RDS Instance 

• In the Amazon RDS dashboard, click on “Create database.”

• Choose a database creation method, usually “Standard create” for more configuration options.

• Select the database engine you want to use (e.g., MySQL, PostgreSQL, MariaDB, Oracle, or SQL Server).

Step 2.2: Configure Database Settings

• Choose Engine Version: Select the engine version that is compatible with your application.

• Template: Choose “Production” for the recommended settings, which include multi-AZ deployment options.

• DB Instance Class: Choose an instance type that meets your performance requirements.

Step 2.3: Enable Multi-AZ Deployment

• Under “Availability & durability,” select “multi-AZ DB Cluster.”

• Configure the additional settings according to your needs, such as storage type and allocated storage size.

Step 2.4: Configure Networking and Security

• Amazon VPC: Choose the Amazon VPC where your Amazon RDS instance will be deployed.
• Subnet Group: Select a DB subnet group that spans multiple AZs.
• Public Access: Decide if you want the database publicly accessible or restricted within your VPC.
• Amazon VPC Security Groups: Choose the security groups to control access to your database.

Step 2.5: Additional Configuration

• Database Authentication: Choose your preferred authentication method (password authentication or AWS IAM database authentication).
• Backup: Configure automatic backups to meet your RPO (Recovery Point Objective).

Step 2.6: Launch the Amazon RDS Instance

• Review your configurations in the summary section.
• Click on “Create database” to launch your Amazon RDS instance.

Step 3: Verifying Multi-AZ Deployment

• Once the instance is created, navigate to the “Databases” section in the Amazon RDS console.

• Click on your newly created database instance.
• Under the “Connectivity & security” tab, verify that the “multi-AZ deployment” shows “Yes.”
• Check the “Availability & durability” section to ensure that two standby instances are listed.

Step 4: Testing Failover

Testing failover ensures your application remains available if the primary database instance fails. To test failover:

• In the Amazon RDS console, select your multi-AZ Amazon RDS instance.
• Click on the “Actions” dropdown and choose “Failover.”

• Amazon RDS will promote one of the standby instances to become the new primary.

• Observe that the failover process is seamless and causes minimal downtime.

The database endpoint remains the same, so your application continues to connect to the primary instance without needing to change any configuration.

Step 5: Monitoring and Maintenance

• Monitoring: Amazon CloudWatch and Amazon RDS performance insights monitor database performance and health.
• Maintenance: Schedule maintenance windows during off-peak hours for updates and patching.

Conclusion

For your vital databases, Amazon RDS multi-AZ with two standbys is a reliable option for high availability and durability. You can ensure that your application is resilient to failures by setting up an Amazon RDS instance with two standbys and multi-AZ by following the instructions in this guide. For mission-critical applications, the automated failover mechanism offered by Amazon RDS helps to minimize downtime and ensure continuity.

Building a highly available database infrastructure in AWS requires utilizing multi-AZ with two standbys in Amazon RDS, whether executing production workloads or disaster recovery.

Drop a query if you have any questions regarding Amazon RDS multi-AZ and we will get back to you quickly.

About CloudThat

CloudThat is a leading provider of Cloud Training and Consulting services with a global presence in India, the USA, Asia, Europe, and Africa. Specializing in AWS, Microsoft Azure, GCP, VMware, Databricks, and more, the company serves mid-market and enterprise clients, offering comprehensive expertise in Cloud Migration, Data Platforms, DevOps, IoT, AI/ML, and more.

CloudThat is the first Indian Company to win the prestigious Microsoft Partner 2024 Award and is recognized as a top-tier partner with AWS and Microsoft, including the prestigious ‘Think Big’ partner award from AWS and the Microsoft Superstars FY 2023 award in Asia & India. Having trained 650k+ professionals in 500+ cloud certifications and completed 300+ consulting projects globally, CloudThat is an official AWS Advanced Consulting Partner, Microsoft Gold Partner, AWS Training Partner, AWS Migration Partner, AWS Data and Analytics Partner, AWS DevOps Competency Partner, AWS GenAI Competency Partner, Amazon QuickSight Service Delivery Partner, Amazon EKS Service Delivery Partner,  AWS Microsoft Workload Partners, Amazon EC2 Service Delivery Partner, Amazon ECS Service Delivery Partner, AWS Glue Service Delivery Partner, Amazon Redshift Service Delivery Partner, AWS Control Tower Service Delivery Partner, AWS WAF Service Delivery Partner and many more.

To get started, go through our Consultancy page and Managed Services Package, CloudThat’s offerings.