ECS task definition allocates 4+ vCPU — review utilization

What it checks

ECS task definition allocates 4+ vCPU — review utilization

Where it applies

Terraform: aws_ecs_task_definition

CloudFormation: AWS::ECS::TaskDefinition

How to fix it

1. Review task and container utilization, sidecars, CPU reservations, memory and memoryReservation. Inspect opaque container definitions rather than assuming totals.
2. Choose a measured size compatible with the launch mode: Fargate requires supported CPU/memory pairs; EC2, Managed Instances and EXTERNAL have different placement and charging models. Windows containers ignore task-level CPU/memory limits; review container-level requirements. No fixed CPU or memory value is recommended.

Frameworks

• AWS Well-Architected COST.6

These mappings are advisory, not an attestation of compliance.

Vendor documentation

All rules