Why ECS service auto scaling in AWS? - Purpose & Use Cases

The Big Idea

What if your app could instantly grow and shrink on its own to handle any number of users without you doing a thing?

The Scenario

Imagine you run a busy online store using containers on ECS. When many customers visit, your service slows down because it can't handle the load. You try to add more containers manually, but by the time you do, customers are already frustrated.

The Problem

Manually adjusting container numbers is slow and tiring. You must watch traffic constantly and react quickly. Mistakes happen easily, causing downtime or wasted resources. It's like trying to add more checkout lanes only after long lines have formed.

The Solution

ECS service auto scaling automatically adds or removes containers based on real-time demand. It watches your service's health and traffic, then adjusts capacity instantly. This keeps your app fast and cost-efficient without you lifting a finger.

Before vs After

✗ Before

aws ecs update-service --cluster myCluster --service myService --desired-count 5

✓ After

aws application-autoscaling register-scalable-target --service-namespace ecs --resource-id service/myCluster/myService --scalable-dimension ecs:service:DesiredCount --min-capacity 2 --max-capacity 10

What It Enables

You can deliver smooth, reliable service that grows and shrinks with your users automatically, saving time and money.

Real Life Example

A food delivery app uses ECS auto scaling to handle lunch rush hours by instantly adding containers, then scales down during quiet times to save costs.

Key Takeaways

Manual scaling is slow and error-prone.

Auto scaling adjusts container count automatically based on demand.

This ensures better performance and cost savings without manual effort.

Practice

1. What is the main purpose of ECS service auto scaling?

easy

A. Store container logs for analysis

B. Manually start and stop containers

C. Automatically adjust the number of running containers based on demand

D. Create new ECS clusters automatically

Solution

1. Step 1: Understand ECS service auto scaling function

   ECS service auto scaling changes the number of containers automatically to match workload.

2. Step 2: Compare options to this function

   Only Automatically adjust the number of running containers based on demand describes automatic adjustment of container count based on demand.

3. Final Answer:

   Automatically adjust the number of running containers based on demand -> Option C

4. Quick Check:

   Auto scaling adjusts container count = Automatically adjust containers [OK]

Hint: Auto scaling means automatic container count changes [OK]

Common Mistakes:

• Confusing auto scaling with manual container management
• Thinking auto scaling creates clusters
• Believing auto scaling stores logs

2. Which of the following is the correct way to specify a target tracking scaling policy for CPU utilization in ECS service auto scaling?

easy

A. "TargetValue": 50, "PredefinedMetricSpecification": {"PredefinedMetricType": "ECSServiceAverageCPUUtilization"}

B. "TargetValue": "high", "PredefinedMetricSpecification": {"PredefinedMetricType": "CPUUsage"}

C. "TargetValue": 100, "MetricName": "MemoryUtilization"

D. "TargetValue": 30, "PredefinedMetricSpecification": {"PredefinedMetricType": "NetworkIn"}

Solution

1. Step 1: Identify correct metric type for CPU utilization

   The predefined metric for ECS CPU is "ECSServiceAverageCPUUtilization" with a numeric target value.

2. Step 2: Check option syntax and metric correctness

   "TargetValue": 50, "PredefinedMetricSpecification": {"PredefinedMetricType": "ECSServiceAverageCPUUtilization"} uses correct metric type and numeric target value 50, which is valid.

3. Final Answer:

   "TargetValue": 50, "PredefinedMetricSpecification": {"PredefinedMetricType": "ECSServiceAverageCPUUtilization"} -> Option A

4. Quick Check:

   Correct metric and numeric target = "TargetValue": 50, "PredefinedMetricSpecification": {"PredefinedMetricType": "ECSServiceAverageCPUUtilization"} [OK]

Hint: Use numeric target and correct predefined metric name [OK]

Common Mistakes:

• Using string instead of number for TargetValue
• Using wrong metric names like CPUUsage
• Mixing memory or network metrics for CPU scaling

3. Given this ECS service auto scaling configuration snippet:

{"MinCapacity": 2, "MaxCapacity": 5, "TargetValue": 60}

What happens when CPU utilization stays at 70% for a long time?

medium

A. The service scales up to 5 containers to reduce CPU load

B. The service scales down to 2 containers to save cost

C. The service keeps running 2 containers without change

D. The service crashes due to high CPU

Solution

1. Step 1: Understand scaling triggers from CPU target

   TargetValue 60 means ECS tries to keep CPU near 60%. If CPU is 70%, it needs more containers.

2. Step 2: Apply min and max capacity limits

   Min is 2, max is 5. Scaling up is allowed up to 5 containers to reduce CPU load.

3. Final Answer:

   The service scales up to 5 containers to reduce CPU load -> Option A

4. Quick Check:

   CPU above target scales up containers = The service scales up to 5 containers to reduce CPU load [OK]

Hint: CPU above target scales up, below scales down [OK]

Common Mistakes:

• Thinking service scales down when CPU is high
• Ignoring max capacity limit
• Assuming service crashes on high CPU

4. You configured ECS service auto scaling but the service never scales out even when CPU is high. What is a likely cause?

medium

A. The service has no load balancer attached

B. The target CPU utilization is set to 100%

C. The ECS cluster has no running tasks

D. The maximum capacity is set equal to the minimum capacity

Solution

1. Step 1: Analyze scaling limits

   If max capacity equals min capacity, no room to scale out exists.

2. Step 2: Check other options

   Target 100% means scaling triggers only at max CPU, but scaling can still happen. No running tasks or load balancer affect service but not scaling limits directly.

3. Final Answer:

   The maximum capacity is set equal to the minimum capacity -> Option D

4. Quick Check:

   Max equals min blocks scaling out = The maximum capacity is set equal to the minimum capacity [OK]

Hint: Max capacity must be greater than min capacity to scale out [OK]

Common Mistakes:

• Ignoring max and min capacity settings
• Assuming load balancer affects scaling triggers
• Confusing target CPU with scaling limits

5. You want to configure ECS service auto scaling to keep container count between 3 and 10, scaling based on memory usage targeting 70%. Which configuration is correct?

hard

A. MinCapacity: 10, MaxCapacity: 3, TargetValue: 70, PredefinedMetricType: ECSServiceAverageMemoryUtilization

B. MinCapacity: 3, MaxCapacity: 10, TargetValue: 70, PredefinedMetricType: ECSServiceAverageMemoryUtilization

C. MinCapacity: 3, MaxCapacity: 10, TargetValue: 70, PredefinedMetricType: ECSServiceAverageCPUUtilization

D. MinCapacity: 3, MaxCapacity: 10, TargetValue: 30, PredefinedMetricType: ECSServiceAverageMemoryUtilization

Solution

1. Step 1: Set correct min and max container counts

   MinCapacity must be less than MaxCapacity, so 3 and 10 is valid, 10 and 3 is invalid.

2. Step 2: Use correct metric and target value for memory

   Memory scaling uses ECSServiceAverageMemoryUtilization with target 70% to trigger scaling.

3. Step 3: Verify options

   MinCapacity: 3, MaxCapacity: 10, TargetValue: 70, PredefinedMetricType: ECSServiceAverageMemoryUtilization matches all requirements: correct min/max, target 70, memory metric.

4. Final Answer:

   MinCapacity: 3, MaxCapacity: 10, TargetValue: 70, PredefinedMetricType: ECSServiceAverageMemoryUtilization -> Option B

5. Quick Check:

   Correct min/max and memory target = MinCapacity: 3, MaxCapacity: 10, TargetValue: 70, PredefinedMetricType: ECSServiceAverageMemoryUtilization [OK]

Hint: Min < Max and match metric to resource (memory or CPU) [OK]

Common Mistakes:

• Setting max less than min capacity
• Using CPU metric for memory scaling
• Setting wrong target value for scaling