Q: EC2 instances in an ASG aren't launching due to `InsufficientInstanceCapacity`.
Spot capacity issue or that AZ/region is out of that instance type. Mitigate: use multiple instance types in the ASG (mixed instances policy), use multiple AZs, configure capacity rebalancing.
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: "AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. 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
Spot capacity issue or that AZ/region is out of that instance type. Mitigate: use multiple instance types in the ASG (mixed instances policy), use multiple AZs, configure capacity rebalancing.
- Immediate Triage: Spot capacity issue or that AZ/region is out of that instance type. Mitigate: use multiple inst
- 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 instances launching InsufficientInstanceCapacity 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 launching InsufficientInstanceCapacity 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 launching InsufficientInstanceCapacity 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 launching InsufficientInstanceCapacity Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.