ASG Floor Lock Detected
The group's minimum size holds instances running that the scaling policy would otherwise remove, so the floor, not demand, is what is setting the bill.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Lower the auto scaling group's minimum size. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Auto Scaling Groups on AWS
- The fix, by hand
- EC2 Console → Auto Scaling Groups → select the resource.
- Edit → Group details. Review MinSize / Desired / MaxSize.
- Decide the new MinSize. Prod web tier: MinSize ≥ 2 (one per AZ) to preserve redundancy. Non-prod / batch: MinSize = 0 or 1.
- Save. The ASG immediately becomes eligible for scale-in based on its scaling policies.
- Confirm scaling policies (target tracking / step scaling) exist; without them the ASG won't actually scale.
These are the steps the finding carries in the product.
- Category
- Scheduling. Resources running 24x7 with a clear off-hours usage pattern, ready for start and stop scheduling.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-054- Full reference
Related checks
See the always-on resources 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.