The three-tier workhorse
This is the architecture behind an enormous share of production software, and it is nothing but this course assembled:
- An ALB (lesson 5-2) in the public subnets of two AZs owns the public address and the TLS certificate.
- Two or more EC2 instances (unit 3) run your app, in private subnets, one per AZ. They wear
sg-app, which admits port traffic only from the ALB's security group. - RDS Multi-AZ (unit 6) holds the data, in private subnets, wearing
sg-db, which admits 5432 only fromsg-app(lesson 6-2's chaining). - Each instance carries an IAM role (lesson 2-3) for whatever AWS access the app needs, such as presigning S3 URLs (lesson 4-3) for user uploads.
Trace a request: browser → ALB (public) → app instance (private) → database (private), and each arrow is permitted by exactly one security-group rule. Everything else is default-deny (lessons 2-2, 3-3, 5-1).
Code exercise · bash
What does this minimal version of the architecture cost per month? The values are rough list prices in cents: two small app instances, the smallest Multi-AZ database, disks, and the ALB's fixed hourly charge. Run the sum and note which line is biggest.
Quiz
In the cost sum you just ran, the single most expensive line was the ALB (~$16/month before any traffic). For a hobby project, what is the honest takeaway?
Problem
One component in this architecture is the reason the app survives an entire availability zone going dark, because it notices dead servers and routes around them (lesson 5-2). Which component? (Its three-letter abbreviation or full name.)