EC2 Heatmap-Based Schedule Opportunity
A running instance whose weekly usage shows a repeating idle window bills for every hour of it. A start and stop schedule recovers the hours nobody uses.
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: Schedule the EC2 instance off-hours. 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
- EC2 Instances on AWS
- The fix, by hand
- Open CloudWatch → Metrics → EC2 → CPUUtilization for this instance and switch to the Heatmap view for 30 days.
- Cross-check the idle window suggested by ZopNight against actual CPU under 5% bands.
- Open ZopNight → Schedules → Create. Match the recommended Stop/Start hours.
- Attach the schedule to this instance and any dependent resources that share the window.
- Track savings via the Recommendations dashboard for the first 30 days.
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-093
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.