ECS Service Auto Scaling Not Enabled
The task count is fixed, so the service cannot absorb a traffic increase and pays for peak capacity at quiet times.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable auto scaling on ECS service.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- ECS Services on AWS
- The fix, by hand
- ECS → Services → the resource → Update service → enable Service Auto Scaling.
- Pick scaling policy type. Target tracking is the simplest: pick a metric (CPUUtilization, MemoryUtilization, ALBRequestCountPerTarget) and a target value (typically 60-70%).
- Set Min capacity (covers off-peak floor) + Max capacity (caps run-away cost).
- Save. Watch CloudWatch alarms (auto-created) trigger scale-out / scale-in.
- Load-test in staging to confirm scaling is responsive enough for your traffic pattern.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-160- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.