Idle Aurora Cluster, No Connections
An Aurora cluster bills for its instances for as long as they are running, no connections does not mean no 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: Delete the idle Aurora 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
- RDS Clusters on AWS
- The fix, by hand
- Confirm DatabaseConnections == 0 over the last 7+ days.
- Take a final snapshot: Actions → Take snapshot of the cluster. Wait for 'Available'.
- For dev/test: consider migrating to Aurora Serverless v2 (Modify → Serverless v2) so the cluster scales to 0 ACU during idle periods.
- To delete: Actions → Delete; 'Create final snapshot' = Yes; type the cluster ID to confirm.
- Validate billing drop in Cost Explorer 24h later.
These are the steps the finding carries in the product.
- Category
- Idle resources. Resources running but doing no useful work: zero invocations, no connections, no traffic.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-190- Full reference
Related checks
See the idle 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.