When traffic to your application spikes, how quickly auto scaling responds determines whether users see fast responses or timeouts. Amazon Elastic Container Service (Amazon ECS) service auto scaling handles this by adjusting the number of tasks in a service to meet demand. It includes predictive scaling for recurring patterns, scheduled scaling for known events, and target tracking. With target tracking, you set a target value for a metric such as average CPU or memory utilization. Many teams rely on target tracking to keep their services responsive as demand rises and falls.

By default, ECS publishes CPU and memory utilization every 60 seconds, a resolution well suited to steady, gradual traffic. For applications that experience sudden spikes, the default 60-second resolution might not be responsive enough, and a service can take several minutes to detect the change and add capacity. This leads some teams to over-provision to stay ahead of demand. Amazon ECS now detects and responds to load changes faster with high-resolution (20-second) CPU and memory utilization metrics for target tracking, in addition to the default 60-second resolution.

With higher-resolution metrics, capacity arrives much closer to when demand rises. Your service spends less time serving slow or failing requests during a spike, and you have less need to over-provision for headroom you rarely use. ECS also optimized the metric publishing path for high-resolution metrics, so each measurement reaches the scaling policy sooner. In the AWS benchmarking published with the launch announcement , time to trigger scale-out fell 76 percent, from 363 seconds to 86 seconds. The time from triggering a scale-out to placing the new tasks fell 72 percent, from 386 seconds to 109 seconds.

The first number is how long the service takes to decide to add capacity. The second is how long until the new tasks are running. Reacting faster on both counts can mean lower latency during a spike, fewer failed requests, and less capacity sitting idle as a safety margin. Target tracking is the most straightforward scaling policy to set up. You choose a target for a metric, such as 60 percent average CPU utilization, and ECS adds or removes tasks to keep the service near it. Because it’s fully managed, you don’t configure alarms or maintain step-scaling rules, and it works well for most workloads.