AWS - ECS and Fargate
An ECS service auto scaling policy is not increasing tasks despite high CPU. What misconfiguration could cause this?
An ECS service auto scaling policy is not increasing tasks despite high CPU. What misconfiguration could cause this?
medium📝 Debug Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand max capacity effect
If max capacity equals current tasks, scaling out is blocked.Step 2: Evaluate other options
MinCapacity zero allows scale in, alarm on low CPU triggers scale in, and memory-based policy won't respond to CPU.Final Answer:
MaxCapacity is set equal to current task count -> Option BQuick Check:
MaxCapacity = current tasks blocks scale out [OK]
Quick Trick: MaxCapacity must be higher than current tasks to scale out [OK]
Common Mistakes:
- Setting max capacity too low
- Confusing alarm triggers
- Using wrong metric for scaling
Master "ECS and Fargate" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes