AWS Interview DropIntermediate TierScenario+25 XP on read

Your application suddenly can't connect to its RDS database. Walk through how you'd diagnose it.

Core Summary

Rule out the database's own health first, since that's a two-second check in the console, then work through the network path in order: security groups, subnet and public accessibility, DNS, and connection limits. A sudden failure that used to work points hardest at something that changed recently, not at a fundamentally broken setup.

Hints

Hint 1: Check instance status before touching a single network setting

Hint 2: A newly-failing connection usually means something changed, so check recent changes first

Hint 3: Max connections and CPU-starved instances fail in a way that looks identical to a network problem