Guided architecture tour · 5–7 min
RDS architecture
Choose a relational database, keep it behind your application, and plan recovery before an accidental delete.
This tour teaches architecture decisions. Its services are not provisioned in the emulator.
Play this architecture tour1. Choose a relational store
Orders reference customers and line items. Your application needs joins and database transactions.
Which service is the best fit for this scenario?
An RDS PostgreSQL database.
RDS manages relational database engines. Objects and notifications serve different jobs.
The application stores related tables in a managed relational database.
Engine: "postgres"
Tables: customers → orders → order_items2. Repair broad network access
A proposed rule allows database connections from the entire internet. Only the application should connect.
Which change narrows the path?
Allow the application security group on the database port.
Network permission should match the application-to-database path. Credentials are still required separately.
Only the intended application path is allowed; authentication remains a separate requirement.
Database inbound rule:
TCP 5432 · source: application security group3. Plan for a mistaken deletion
An application bug deletes useful rows. High availability alone does not undo a logical deletion.
What should be planned and tested beforehand?
Backups and a tested point-in-time recovery procedure.
Availability and recovery solve different problems. Restore procedures need testing before an incident.
The recovery plan includes restoring to a separate database and validating the recovered data.
Recovery drill:
restore → validate rows → plan application cutoverPractice, then check your understanding
In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.
Read the official AWS documentation for service behavior and production details.