Quiz
Warm-up from lesson 5-2: why does a database belong in a private subnet?
You could run it yourself. Should you?
You know how to run PostgreSQL in a Docker container, so you could launch an EC2 instance and do exactly that. Now you own the 3 a.m. problems: applying security patches, taking backups and testing they restore, growing the disk before it fills, and failing over to a replica when the AZ has a bad night.
RDS (Relational Database Service) is AWS running that database for you. You pick an engine (PostgreSQL, MySQL, MariaDB, and others), an instance size (the same t3/m5 types from lesson 3-1, prefixed db.), and RDS handles:
- Automated backups: daily snapshots plus a continuous change log, so you can restore to any minute within the retention window (up to 35 days).
- Patching during a maintenance window you choose.
- Multi-AZ failover: a hot standby copy in another AZ, promoted automatically if the primary dies, usually within a minute or two.
The trade: it costs more than raw EC2 (roughly $13/month for the smallest instance versus $7.50), and you give up root access to the box. For nearly every team, that is a bargain.
Code exercise · bash
Backup storage is free only up to the size of your database, and overflow is billed. A 20 GB database changes 2 GB per day and keeps 7 days of backups. Run the estimate of how much backup storage exceeds the free allowance.
Code exercise · bash
Your turn. A production database is 50 GB, changes 3 GB per day, and compliance requires 14 days of retention. Update the variables and compute the billable backup storage.
Quiz
Multi-AZ RDS keeps a standby copy in a second availability zone. Which earlier idea is this the payoff of?