- Amazon RDS overview: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Welcome.html
- Multi-AZ deployments: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html
- Read replicas: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html
- Amazon Aurora: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html
1 — Open the RDS console and start a new database
In the AWS Console, search for RDS (Relational Database Service) and open the RDS / Amazon Aurora service. The console lists Amazon Aurora alongside the other RDS engine options.
2 — Choose the engine and creation method
Select the database engine that matches your workload—this demo uses PostgreSQL. Choosing PostgreSQL tailors the subsequent options in the wizard.

3 — Enable Multi-AZ for high availability
Under Availability and durability select the Multi-AZ DB instance deployment option. This creates a primary instance and a synchronous standby in a different Availability Zone to provide automatic failover and improved durability.
- Writes are synchronously replicated to a standby instance in another AZ for data durability.
- The standby is not a readable endpoint; it exists only for failover/HA.
- RDS automatically fails over to the standby if the primary becomes unhealthy.

4 — Credentials, networking, and public access
For this demo we used a self-managed username and password to keep the steps straightforward. In production environments, integrate with AWS Secrets Manager for managed, rotated credentials. Decide whether the DB should be publicly accessible:- For demos, enabling public access gives an easy endpoint for testing.
- For production, avoid public exposure—use private subnets, VPC security groups, and IAM/Secrets Manager integration.
Enabling public access exposes the DB endpoint to the Internet and can be a security risk. For production, prefer private subnets, VPC security groups, and Secrets Manager for credentials.
5 — Create and wait for the instance
Create the database and wait for provisioning. The console will show the instance transitioning from Creating to Available.
6 — Read replicas: when and how to add them
Read replicas are different from Multi-AZ: Multi-AZ provides availability (standby, synchronous replication), while read replicas provide read scaling (usually asynchronous replication and readable endpoints).Multi-AZ = high availability (synchronous replication, standby not readable). Read replicas = read scaling (typically asynchronous replication, readable endpoints).
- Select the source database in the console.
- Choose Actions → Create read replica.
- Set a DB instance identifier (for example
database-1-readreplica). - Keep most settings at defaults; the demo used a Single-AZ replica to reduce cost and complexity.


- Standard RDS read replicas (MySQL, MariaDB, PostgreSQL) generally use asynchronous replication — expect replication lag.
- Aurora replicas use a different, storage-based replication design that offers faster scaling and lower lag.
- Read replicas are readable and can serve application read traffic. They are not automatically promoted on primary failure unless you manually promote them or implement failover automation.
- Use Multi-AZ for automatic failover/availability. Use read replicas to scale read capacity horizontally.
7 — Wait for the replica and verify
Create the read replica and wait until its status is Available. The console will list the primary as Primary and the replica(s) as Replica(s).
Quick comparison: Multi-AZ vs Read Replica
Best practices and cleanup
- Use Secrets Manager for credentials and rotate them regularly.
- Keep DB instances in private subnets and control access with VPC security groups.
- Monitor replication lag, CPU, memory, and disk I/O on primary and replicas.
- When tearing down test resources: delete read replicas first, then the primary. Decide whether to take a final snapshot—skip for throwaway demos, but keep snapshots for production or important data.
Links and references
- Amazon RDS documentation
- RDS Multi-AZ deployments
- RDS Read Replicas
- Amazon Aurora documentation
- AWS Secrets Manager
- VPC security groups