RDS and Database Backups
Create an RDS PostgreSQL instance with automated backups and Multi-AZ, take a manual snapshot, restore it to a new instance, and verify point-in-time recovery — the full backup-and-restore cycle on a managed database.
Prerequisites: An AWS account, AWS CLI v2 configured, the VPC from the EC2 project (with private subnets), and awareness that RDS instances incur hourly charges — delete when done.
Amazon RDS handles the operational heavy-lifting of running a relational database — patching, replication, automated backups, and Multi-AZ failover — so you can focus on schema design and queries instead of database administration. The tradeoff is that you're working within AWS's operational model rather than full control.
This project covers the backup-and-restore cycle end-to-end: automated backups for point-in-time recovery, a manual snapshot for a specific recovery point (like before a migration), and the restore process. This is the 'Backup and Restore' tier of the DR strategy spectrum — the cheapest and simplest, appropriate when hours of RTO is acceptable.
Create a DB Subnet Group and RDS instance
Take a manual snapshot and understand automated backups
Restore from a snapshot to a new instance
Test point-in-time recovery
Secret Mission: Simulate a Multi-AZ failover
Before You Go
Test what you just learned
Self-testing is one of the best ways to retain new skills. Unlock project quizzes to check your understanding.
Log in to unlock0 / 7 complete
