ECS services on regular Fargate — review for Fargate Spot
AWSCost optimizationFree planSeverity: medium
aws.ecs-serviceECS services on regular Fargate (launch type, or a capacity provider strategy without FARGATE_SPOT), not tagged as production, with 2+ desired tasks, created more than 7 days ago. Spot suitability depends on the workload and is not checked.
What LeftSize checks
Find ECS services using regular Fargate that could use Fargate Spot for 70% savings
Why it matters
Resources like this keep billing every hour while delivering little or no value, and nobody notices until the invoice arrives.
What you get in the GitHub issue
LeftSize runs this check from a scheduled GitHub Action with a read-only identity in your AWS account and opens one issue per scope, updated on every scan. The issue includes:
- The affected resources, grouped per subscription, resource group or account and region
- An estimated monthly cost where pricing data is available
- Background on why it was flagged and when it is a false positive
- Step-by-step remediation with safety checks
- Ready-to-run fix scripts (CLI, PowerShell or Terraform where available)
- Cost and operational impact of fixing it
- Alternative approaches and their trade-offs
- Snooze, ignore or report a finding with a comment on the issue
Install LeftSizeIncluded in the Free plan.