Skip to main content

EC2 Fleet Bad Config Diagnostic Troubleshooter (Part 1)

Use the interactive troubleshooter below to identify your EC2 Fleet 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

#ScenarioKey Error SignalRoot CauseThe Fix
1JSON — EC2 Fleet Overrides mixing InstanceRequirements and InstanceType in same OverridesOverrides contains both InstanceRequirements and InstanceTypeThe Overrides structure contains both InstanceRequirements and InstanceType. For the Overrides, you can specify either InstanceRequirements or InstanceType, but not both.N/A
2JSON — EC2 Fleet Overrides mixing InstanceRequirements and InstanceType across different OverridesOverrides in different LaunchTemplateConfigs contain both typesThe Overrides structures contain both InstanceRequirements and InstanceType. You can specify either InstanceRequirements or InstanceType, but not both, even if they're in different Overrides structures.N/A
3JSON — EC2 Fleet duplicate InstanceRequirements with overlapping VCpuCount valuesTwo 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