4 documented AWS ECS cost inefficiencies, each with how to detect it and how to fix it.
AWS ECSCER-0139
When ECS clusters are configured with an Auto Scaling Group that maintains a minimum number of EC2 instances (e.g., min = 1 or higher), the instances remain active even when there are no tasks scheduled. This leads to idle compute capacity...
AWS ECSCER-0340
Amazon ECS tasks on Fargate must declare CPU and memory at the task level, chosen from a fixed set of valid combinations, and Fargate bills for that configured size for as long as each task runs. What the containers actually consume does...
AWS ECSCER-0341
An Amazon ECS service keeps its desired count of tasks running indefinitely: if a task stops, the scheduler starts a replacement. When the application behind a service is retired, replaced by a new service, broken, or simply no longer...
AWS ECSCER-0360
When Amazon ECS runs tasks on EC2 container instances, the placement strategy decides which instance each task lands on. Services default to spreading tasks across Availability Zones, and many teams also spread by instance ID or use random...
