Follow-up · depth 7
What would you monitor for AWS VPC, Subnets, and Security Groups on-call?
What would you monitor for AWS VPC, Subnets, and Security Groups on-call?
Answers use simple, clear English.
Quick interview answer
On-call for AWS VPC, Subnets, and Security Groups: alert on lag/latency, error spikes, and saturation — with runbooks. Baseline: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
Detailed answer
On-call monitoring for AWS VPC, Subnets, and Security Groups: • Golden signals: latency, traffic, errors, saturation • AWS VPC, Subnets, and Security Groups-specific gauges (queue delay, pool wait, cache miss, etc.) • Alerting: burn-rate / multi-window so pages are actionable • Runbook: mitigate → diagnose → escalate Parent context: Baseline: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
Full explanation
Tie each alert to a user-visible or SLO impact for AWS VPC, Subnets, and Security Groups. Baseline: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — AWS VPC, Subnets, and Security Groups
Baseline: VPC CIDR, public/private subnets, IGW/NAT, route tables. Security groups stateful allow-lists; NACLs stateless.
View full parent question →