EC2 Fleet Bad Config Diagnostic Troubleshooter (Part 2)
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
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 4 | JSON — Deny spot-instances-request resource in RunInstances not supported | "Sid": "DenySpotInstancesRequests - NOT SUPPORTED - DO NOT USE!" | The following policy is not supported for the spot-instances-request resource. This condition is not supported because Amazon EC2 does not evaluate the spot-instances-request resource in the RunInstances statement if the Spot Instance request is not tagged on create. | N/A |
| 5 | JSON — aws:RequestTag condition on spot-instances-request bypassed when untagged | "Sid": "RequestSpotInstancesOnlyIfTagIs_environment=production - NOT SUPPORTED - DO NOT USE!" | If no tags are specified for the Spot Instance request, Amazon EC2 does not evaluate the spot-instances-request resource in the RunInstances statement, which results in non-tagged Spot Instance requests being created by RunInstances. | N/A |
| 6 | JSON — create-fleet resource-level permissions unauthorized exception | "Resource": "arn:aws:ec2:us-east-1:111122223333:create-fleet/*" | We currently do not support resource-level permissions for the create-fleet resource. If you specify create-fleet as a resource, you will get an unauthorized exception when you try to tag the fleet. | Change "Resource" to "*" |