Idle Redshift Cluster
A provisioned cluster bills for every node continuously, and pausing it keeps the storage while dropping the compute charge.
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: Pause the idle Redshift cluster. 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
- Redshift on AWS
- The fix, by hand
- Snapshot the cluster: Clusters → select → Actions → Create snapshot. Wait for 'Available'.
- Audit downstream consumers (QuickSight datasets, Glue jobs, federated query references).
- Pause (reversible): Actions → Pause. Compute billing stops; storage continues.
- Or Delete (irreversible): Actions → Delete; choose 'Create final snapshot' = Yes.
- Validate billing impact in Cost Explorer the following day.
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-099- 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.