📡 You're offline — showing cached content
New version available!
Quick Access
Tutorials AWS Solutions Architect RDS — Managed Relational Databases

RDS — Managed Relational Databases

5 min read Quiz at the end
Master the difference between Multi-AZ and Read Replicas, understand Aurora's advantages, and know when to use RDS versus DynamoDB.

RDS — Managed Relational Databases

RDS is a managed database service. AWS handles the undifferentiated heavy lifting: hardware provisioning, OS patching, database software updates, automated backups, and Multi-AZ failover. You focus on your data.

Teacher Note: Without RDS, a DBA spends 30-40% of their time on maintenance tasks: patching OS, upgrading database software, configuring backups, setting up replication. RDS handles ALL of this automatically so your team focuses on business logic.

Supported Database Engines

EngineBest For
MySQLWeb applications, WordPress, PHP apps
PostgreSQLComplex queries, GIS, advanced data types
MariaDBMySQL-compatible, community-driven
OracleEnterprise applications, legacy systems
SQL ServerMicrosoft stack, .NET applications
AuroraAWS-native — 5x MySQL, 3x PostgreSQL performance

Multi-AZ vs Read Replicas — Know the Difference!

FeatureMulti-AZRead Replicas
PurposeHIGH AVAILABILITY — automatic failoverREAD SCALABILITY — offload read traffic
ReplicationSYNCHRONOUS (zero data loss)ASYNCHRONOUS (small lag possible)
Standby readable?NO — standby is passive, not readableYES — each replica has its own endpoint
FailoverAutomatic, same endpoint, 60-120 secondsManual promotion required
Max replicas1 standby (Multi-AZ standard) or 2 (Multi-AZ cluster)Up to 5 (15 for Aurora)
Cross-regionNo (same region only)Yes — cross-region read replicas possible

RDS Aurora — The Best of Both Worlds

  • Shared distributed storage across 6 copies in 3 AZs — survives 2 AZ failures
  • Auto-grows from 10GB to 128TB — no storage planning needed
  • 15 read replicas with under 10ms lag
  • Aurora Serverless v2: auto-scales compute in 0.5 ACU increments within seconds
  • Aurora Global Database: replicates across 5 regions with under 1 second lag
Exam Tip: The MOST common exam trap: Multi-AZ is for AVAILABILITY (failover), NOT performance. Read Replicas are for PERFORMANCE (scaling reads). If the question says high availability or disaster recovery — think Multi-AZ. If it says too many read requests — think Read Replicas.
Topic Quiz · 2 questions

Test your understanding before moving on

1. An RDS MySQL database is getting too many SELECT queries and performance is degrading. What is the BEST solution?
💡 Read Replicas distribute read traffic across multiple database servers — each replica handles SELECT queries independently.
2. A company needs their database to automatically fail over to a standby in another Availability Zone with zero data loss. Which feature provides this?
💡 RDS Multi-AZ uses synchronous replication (zero data loss) and automatically fails over to the standby within 60-120 seconds.