EC2 Bad Config Diagnostic Troubleshooter (Part 2)
Use the interactive troubleshooter below to identify your EC2 bad configuration symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 5 | JSON — SpotFleet Overrides mixing InstanceRequirements and InstanceType | "Overrides" contains both InstanceRequirements and InstanceType | The Overrides structure contains both InstanceRequirements and InstanceType. For the Overrides, you can specify either InstanceRequirements or InstanceType, but not both. | N/A |
| 6 | JSON — SpotFleet duplicate InstanceRequirements with overlapping values | Two InstanceRequirements with "VCpuCount": {"Min": 0, "Max": 2} | The two InstanceRequirements structures each contain overlapping VCpuCount values, which will result in duplicate capacity pools. | N/A |
| 7 | INI/conf — PermitRootLogin enabled on public AMI | #PermitRootLogin yes | Using a fixed root password for a public AMI is a security risk that can quickly become known. Even relying on users to change the password after the first login opens a small window of opportunity for potential abuse. | PermitRootLogin without-password |
| 8 | INI/conf — UseDNS enabled causing login failures | #UseDNS yes | If you do not disable sshd checks, DNS resolution failures prevent all logins. | N/A |