Q: Two EC2 instances in the same VPC can't communicate. What do you check?
1. Same VPC? — Confirm both are in the same VPC. Different VPCs require VPC Peering.
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When an interviewer asks how I troubleshoot this in AWS, I frame it through my hands-on production experience. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
- Same VPC? — Confirm both are in the same VPC. Different VPCs require VPC Peering.
- Security Groups — instance A's SG must allow inbound from instance B's IP or SG. And B's SG must allow outbound (usually default allows all outbound).
- NACL — both subnet NACLs must allow inbound and outbound traffic between them.
Remediation & Permanent Safeguards
Execute the resolution runbook and verify workload health:
- Route tables — both subnets must have routes to each other. In the same VPC, local routes (
10.0.0.0/16 → local) handle this automatically. - Are they in different VPCs with peering? — check the peering connection and route tables.
- Same VPC? — Confirm both are in the same VPC. Different VPCs require VPC Peering.
- Security Groups — instance A's SG must allow inbound from instance B's IP or SG. And B's SG must ...
- NACL — both subnet NACLs must allow inbound and outbound traffic between them.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Purging compromised IAM user credentials immediately prior to querying CloudTrail forensic event logs when configuring instances communicate check Deactivating a compromised key prevents abuse while preserving identity records for CloudTrail forensic queries to assess blast radius.
- Conflating local IAM Permissions Boundaries with organizational Service Control Policies (SCPs) when configuring instances communicate check SCPs define maximum permission guards at the AWS Organization level across accounts, whereas permission boundaries limit delegate privileges within a single account.
- Deploying single-AZ cloud infrastructure for production workloads without multi-AZ failover resilience when configuring instances communicate check Availability Zone hardware failures or localized network partitions cause complete service downtime when resources are not distributed across >=2 AZs.
- Jumping straight to SSH or instance restarts without reviewing CloudWatch metrics and AWS Systems Manager logs when configuring instances communicate check Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.