ECS Auto Scaling groups with a minimum of 3+ instances — review for idle capacity
AWSCost optimizationFree planSeverity: medium
aws.asgAuto Scaling groups tagged as ECS capacity (AmazonECSManaged) with MinSize of 3 or more, created more than 14 days ago. Flags configuration for review; does not measure ECS utilization.
What LeftSize checks
Find ECS capacity-provider Auto Scaling groups with a minimum of 3 or more instances. A high minimum keeps container instances running even when no tasks need them. This flags the configuration for review; it does not measure ECS utilization.
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
- Cost and operational impact of fixing it
- Alternative approaches and their trade-offs
- Step-by-step remediation with safety checks
- Ready-to-run fix scripts (CLI, PowerShell or Terraform where available)
- Snooze, ignore or report a finding with a comment on the issue
Install LeftSizeIncluded in the Free plan.