Q: An EC2 instance is making unexpected outbound connections to unknown IPs. What do you do?
Isolate: change security group to block all outbound. 2) Take a snapshot (forensics). 3) Check VPC Flow Logs for the outbound connections. 4) Check GuardDuty findings. 5) Check running processes on instance. Likely compromised.
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."
Production Solution & Architecture
1) Isolate: change security group to block all outbound. 2) Take a snapshot (forensics). 3) Check VPC Flow Logs for the outbound connections. 4) Check GuardDuty findings. 5) Check running processes on instance. Likely compromised. Don't just terminate — preserve evidence first.
- Immediate Triage: 1) Isolate: change security group to block all outbound. 2) Take a snapshot (forensics). 3) Che
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
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 instance making unexpected 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 instance making unexpected 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 instance making unexpected 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 instance making unexpected Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.