1. Classic 3-tier web app layers are…
- S3, Lambda, CloudFront only
- Web (ALB) → App (EC2) → Database (RDS)
- IAM, KMS, SSO
- Git, GitHub, GitLab
Route53, ALB, RDS Stack
Source: doonops-curriculum/aws-three-tier--route53-rds-stack.md
Doonops lesson
Goal
Full app: DNS name → ALB → EC2 → database.
Simple explanation
User types domain → Route53 phonebook → ALB door → EC2 waiter → RDS storage room.
Technical view
User types domain → Route53 phonebook → ALB door → EC2 waiter → RDS storage room.
Think of it like
User types domain → Route53 phonebook → ALB door → EC2 waiter → RDS storage room.
Steps
- Read simple section
- Read analogy + diagram
- Copy project files
- Do local lab
Deep explanation
Layman words first, then technical detail — read slowly
DB passwords never plain in Git. RDS in DB subnets — no public IP.
Expensive lab — destroy same day.
Example (Doonops)
Modern HCL — names are examples, not from any third-party course
Example HCL
# see project files
Terraform runs on your computer — copy this HCL into a folder, then follow the local lab steps below.
Quick check
- Explain topic to a friend in 2 sentences
- Did local lab steps
Project files for this lab
Full implementation folder — copy all files, then run terraform commands
Lab project files (full folder)
Copy every file below into one folder — same as a real repo module. Then run the local lab steps.
Suggested folder: Suggested path: ~/doonops-terraform/16-three-tier/
versions.tfSee file purpose in the code belowterraform {
required_version = ">= 1.9.0"
}
Module check — did you get it?
2–3 quick questions before the next module
3-tier — quick check
Quick check — did this module stick?