AWS - ECS and Fargate
You configured ECS service auto scaling but the service never scales out even when CPU is high. What is a likely cause?
You configured ECS service auto scaling but the service never scales out even when CPU is high. What is a likely cause?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze scaling limits
If max capacity equals min capacity, no room to scale out exists.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.Final Answer:
The maximum capacity is set equal to the minimum capacity -> Option DQuick Check:
Max equals min blocks scaling out = The maximum capacity is set equal to the minimum capacity [OK]
Quick Trick: 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
Master "ECS and Fargate" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes