AWS Learning Journey

Your Database Will Fail. Here's How RDS and Aurora Keep You Running

Engines, subnet groups, parameter groups, Multi-AZ, read replicas, backups, maintenance windows, RDS Proxy, Aurora, and Aurora Serverless — relational databases on AWS without the 3 a.m. pages.

8 min read · 1574 words
AWSAmazon RDSDatabasesPostgreSQLCloud Architecture
Your Database Will Fail. Here's How RDS and Aurora Keep You Running cover image

AWS from Zero to Production — Phase 5, Part 3 of 5 · See the full series roadmap


Running your own database server sounds manageable — until you list the jobs: installing, patching, backups, point-in-time recovery, replication, failover, monitoring, storage growth, encryption, and upgrades.

Every one of those is a chance for a 3 a.m. page.

Amazon RDS and Amazon Aurora take most of those jobs off your plate. But not all of them, and not automatically. You still choose the right settings — and the defaults aren’t always production-ready.

This article shows you what RDS does, what you still own, and how to configure a database that survives failure.

What you’ll walk away with


Amazon RDS in one paragraph

Amazon Relational Database Service (RDS) runs relational databases for you. You choose an engine, instance class, and storage; AWS handles provisioning, patching, backups, and failover. You connect with your normal database driver — it’s still PostgreSQL or MySQL underneath.

Database engines

Commercial engines may require license fees, either included in the price or bring-your-own.

Instances and storage


Where the database lives

DB subnet groups

A DB subnet group tells RDS which subnets it may use. Include private subnets in at least two AZs. In Phase 3, you built isolated data subnets for exactly this.

Security groups

The database security group should allow the database port only from the app’s security group:

db-sg   inbound 5432 from app-sg

Public accessibility

Set Publicly accessible = No. A production database never needs a public IP. Connect from your laptop through a bastion with Session Manager port forwarding, or a VPN — not the internet.

Encryption

Credentials

Let RDS manage the master password in Secrets Manager. RDS generates it, stores it, and rotates it — and the password never appears in your templates or terminal history:

aws rds create-db-instance ... --manage-master-user-password

Engineer’s note: Don’t let your application use the master user. Create an app user with only the privileges it needs.


Parameter groups and option groups

Some parameter changes apply immediately (dynamic); others need a reboot (static).


Backups and recovery

Automated backups

Manual snapshots

Restoring creates a new database

Every restore — from PITR or a snapshot — creates a new DB instance with a new endpoint. Your app must point to it. Plan for that in your runbook.

Watch out: When you delete a database, RDS offers a final snapshot. Take it. Automated backups can be deleted with the instance unless you choose to retain them.


Multi-AZ vs. read replicas

This is the most commonly confused topic in RDS.

Multi-AZ: for availability

Read replicas: for scaling reads

In short

Rule: Every production database should be Multi-AZ. A read replica is not a substitute.


Maintenance windows

RDS applies patches and minor version upgrades during a weekly maintenance window you choose.


RDS Proxy

Applications — especially Lambda functions and autoscaled containers — can open many short-lived connections. Databases handle that badly.

RDS Proxy sits between your app and the database:

Lambda (1,000 concurrent) -> RDS Proxy (pool) -> PostgreSQL (100 connections)

Amazon Aurora

Aurora is AWS’s cloud-native relational database, compatible with MySQL and PostgreSQL.

The big difference is storage:

Aurora clusters have endpoints: a writer endpoint, a reader endpoint that load-balances across replicas, and optional custom endpoints.

Extra features include Aurora Global Database for cross-Region replication with fast recovery, backtrack for MySQL, and fast database cloning for testing against production-like data.

Aurora Serverless v2

Aurora Serverless v2 scales capacity up and down in fine-grained increments, measured in Aurora Capacity Units (ACUs):

Good for variable workloads, dev and test, and multi-tenant apps with unpredictable load.

RDS or Aurora?


Database migration considerations

Moving an existing database to AWS? Think about:


Common mistakes


Key takeaways


Quick self-check

Test yourself before moving on:

  1. Does the standby in a Multi-AZ DB instance serve read traffic?
  2. You restore a database to 10:42 this morning. What’s the endpoint?
  3. Your Lambda functions exhaust database connections during traffic spikes. What do you add?
  4. How many copies of data does Aurora storage keep, and across how many AZs?

Answers

  1. No. It exists only for failover. Use read replicas, or a Multi-AZ DB cluster, for reads.
  2. A new endpoint — restores create a new DB instance.
  3. RDS Proxy.
  4. Six copies across three AZs.

What’s next

In Part 4, we go beyond relational: DynamoDB keys, indexes, capacity modes, streams, TTL, global tables, and transactions — plus caching with ElastiCache and MemoryDB.

RDS or Aurora — which does your team run, and why? Tell me in the comments.


Share this article

LinkedIn post draft