AWS RDS
Explore Amazon RDS managed relational databases, supported engines, and the difference between Multi-AZ deployments and read replicas.
Amazon RDS is AWS’s managed relational database service. Instead of installing PostgreSQL, MySQL, MariaDB, Oracle, or SQL Server on your own servers, you ask AWS to run the engine, automate much of the patching, handle backups, and expose operational settings through APIs and the console. That removes a large amount of undifferentiated database administration while preserving the relational model most applications already understand.
RDS: Multi-AZ Architecture
Multi-AZ failover is automatic — endpoint stays the same, AWS updates DNS
RDS supports several engines, and the best choice often depends on team skill and application compatibility rather than raw feature lists. PostgreSQL is common for new greenfield apps, MySQL remains popular across web stacks, and Aurora offers AWS-optimized compatibility with MySQL or PostgreSQL. The managed service does not eliminate every database task, but it dramatically reduces routine effort around snapshots, maintenance windows, monitoring, and failover setup.
| Feature | Multi-AZ | Read replica |
|---|---|---|
| Primary goal | High availability | Read scaling |
| Replication type | Synchronous standby | Asynchronous copy |
| Accepts reads | No, standby is passive | Yes, on the replica |
| Failover use | Yes | Not the primary purpose |
Multi-AZ and read replicas solve different problems. Multi-AZ gives you a standby in another Availability Zone so AWS can fail over when the primary becomes unavailable. Read replicas give you extra database copies to offload reporting or heavy read traffic, but because replication is asynchronous, replicas may lag behind the source.
For DevOps teams, RDS is a productivity multiplier. Database backups, maintenance scheduling, encryption options, CloudWatch metrics, and parameter tuning live behind APIs that fit well into infrastructure as code. You still need to think about network placement, security groups, secrets handling, and cost, but you spend far less time replacing failed hosts or building custom replication plumbing.
Continue with AWS RDS Setup and AWS RDS Security.
aws rds describe-db-engine-versions --engine postgres --query 'DBEngineVersions[0:5].[EngineVersion]' --output table
aws rds describe-db-instances --output table
Operational note
Managed databases still need operational planning. Decide who owns schema changes, how backups will be tested, how failover will be validated, and where connection secrets live before production traffic arrives. RDS removes server care, but healthy database operations still depend on clear ownership and tested recovery paths. Shared standards like this make future environments easier to launch, review, and support.
RDS purpose
What is a primary benefit of Amazon RDS compared with self-managing a database on EC2?
Multi-AZ versus replicas
Which option is primarily used to improve availability through automatic failover?