1. Check whether tasks are spreading unnecessarily.
   • If a node only runs one task, and there are no placement constraints that require spreading, the node should be bin‑packed with other tasks.
     
     
2. Review placement constraints in the service.
   • A service without constraints looks like:
     

     "placementConstraints": [],
     "placementStrategy": []

1. • A service with constraints may include:
     

     "placementConstraints": [
       {
         "type": "memberOf",
         "expression": "attribute:nd.type == default"
       }
     ]

   • Make sure your constraints aren’t unintentionally forcing tasks onto separate nodes.
     
     
2. Review the portMappings in the task definition.
   • Port mappings let containers use ports on the host instance.
   • The hostPort value is usually left blank or set to 0 so ECS can choose an available port.
   • Example of a typical configuration:
     
     

     "portMappings": [
       {
         "protocol": "tcp",
         "hostPort": 0,
         "containerPort": 443
       }
     ]

3. Make sure hostPort isn’t restricting placement.
   • If hostPort is set to the same value as containerPort, each task requires a dedicated instance.
   • This prevents multiple tasks from running on the same node and causes underutilization.
   • Any pending tasks trigger scale‑ups, and the number of new instances equals the number of pending tasks.
     
     
4. Check all container definitions in the task.
   • A task definition can include multiple containers.
   • Review the portMappings section for each container to make sure none of them force unique host ports.

After updating port mappings or constraints, ECS can bin‑pack tasks onto fewer nodes, reduce scale‑ups, and lower costs.