Scenario Labs

10 Real-world Scenarios

Labs mein har click bataya gaya tha. Yahan tumhe ek business problem aur requirements milenge — jaise job pe ticket milta hai. Pehle khud design karo aur banao; atak jao toh hints dekho; phir guided solution se compare karo. Har scenario ke end mein verification tests, Break & Fix aur cleanup.

Kaise karein
  1. Story + requirements padho aur kagaz pe architecture diagram banao (subnets, routes, SGs).
  2. Khud banao — console ya CLI, jo aata ho. 20–30 min atko toh Hints kholo.
  3. Verification tests chalao — sab pass? Tabhi solution kholo aur apne approach se compare karo.
  4. Break & Fix + cleanup same din.

Shell: solutions ke scripts bash ke liye likhe hain — macOS pe terminal mein pehle bash type karo (zsh mein kuch syntax alag hai). Variables usi terminal mein rehte hain, isliye ek scenario ek hi terminal mein poora karo.

Prerequisites: Labs 1, 2 aur 4 (CLI setup, deepdive-ec2-role with Session Manager, deepdive-key key pair, VPC basics). Region: us-east-1 (Scenario 3 aur 10 mein ap-south-1 bhi).

Scenario 01Beginner → Intermediate · 2–2.5 hours

3-tier app: EC2 se EC2 communication

Web EC2 → App EC2 → DB EC2. Har tier sirf apne pados wale tier se baat kare — security groups se layered access.

Scenario 02Intermediate · 1.5–2 hours

Do VPCs ki baat-cheet: peering + private DNS

Orders team ki VPC Payments team ki VPC ke internal API ko naam se call kare — internet ke bina.

Scenario 03Intermediate · 1.5 hours

Cross-region VPC peering (Virginia ↔ Mumbai)

US aur India ke do VPCs private network pe jodo, latency naapo, aur inter-region limits samjho.

Scenario 04Intermediate → Advanced · 2 hours

Overlapping CIDRs? PrivateLink se service share karo

Do VPCs dono 10.0.0.0/16 — peering impossible. Ek service ko bina network jode share karo.

Scenario 05Intermediate · 2 hours

Private EC2 access: bastion host vs Session Manager

Private servers tak pahunchne ka purana tareeka (bastion + SSH) aur naya (Session Manager, zero open ports).

Scenario 06Intermediate · 1.5–2 hours

NAT instance vs NAT Gateway (cost vs reliability)

Startup ka NAT bill zyada hai — khud ka NAT instance banao, NAT Gateway se compare karo, trade-offs likho.

Scenario 07Intermediate · 1–1.5 hours

S3 sirf VPC ke andar se: endpoint-locked bucket

Sensitive bucket: EC2 VPC endpoint se hi padh sake — credentials leak ho jaayein tab bhi bahar se nahi.

Scenario 08Intermediate · 2.5–3 hours

Highly available auto-scaling web app + blue/green

Load test se auto-scaling trigger karo, ek AZ 'gira' do, aur zero-downtime blue/green release karo.

Scenario 09Intermediate → Advanced · 1.5–2 hours

Troubleshooting: tooti hui network theek karo

CloudFormation ek jaan-boojh ke broken network banata hai. 5+ faults dhoondo aur fix karo — bina hints ke try karo.

Scenario 10Intermediate · 1.5–2 hours

Disaster recovery: EC2 ko doosre region mein wapas lao

us-east-1 'down' ho gaya — server ko Mumbai mein backup se khada karo aur RTO/RPO naapo.