Follow-up · depth 3
What are common failure modes of AWS VPC, Subnets, and Security Groups?
What are common failure modes of AWS VPC, Subnets, and Security Groups?
Answers use simple, clear English.
Audio N/AQuick interview answer
Common failures around AWS VPC, Subnets, and Security Groups: blocking the hot path, ignoring backpressure, and weak timeout/retry design. 0.0.0.0/0 on SSH SG; databases in public subnets.
Detailed answer
Failure modes for AWS VPC, Subnets, and Security Groups: Known pitfalls: 0.0.0.0/0 on SSH SG; databases in public subnets. • Missing timeouts / unbounded retries • No backpressure when downstream slows • Assuming ordering/guarantees the runtime does not provide How seniors prevent them: Least privilege SG; VPC endpoints for S3/ECR; flow logs. Parent context: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
Full explanation
Name concrete failure modes and the mitigation for each — that scores higher than a vague “it can fail.” VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless. Private workloads without public IPs.
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — AWS VPC, Subnets, and Security Groups
VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
View full parent question →