AWS - ECS and Fargate
An ECS service is configured with auto scaling, but the number of tasks does not increase despite sustained high CPU usage. What is a probable cause?
An ECS service is configured with auto scaling, but the number of tasks does not increase despite sustained high CPU usage. What is a probable cause?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Identify why scaling does not occur
If CPU is high but tasks don't scale out, the scaling policy might not be linked properly.Step 2: Evaluate other options
Too many tasks or CPU below target would not cause lack of scaling with high CPU. Minimum task count limits scale in, not scale out.Final Answer:
The scaling policy is not attached to the ECS service -> Option BQuick Check:
Scaling policy must be attached to trigger scaling [OK]
Quick Trick: Scaling policy must be linked to ECS service [OK]
Common Mistakes:
- Confusing min task count with max task count
- Assuming CPU metric is low when it's high
- Ignoring policy attachment
Master "ECS and Fargate" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes