Idle RDS instances are different from over-provisioned RDS: over-provisioned findings apply to databases that are receiving connections but have more compute capacity than they need. Idle instances have near-zero database connections over the last 14 days — a signal the database may no longer be in use.
Before you delete or stop
- Confirm no applications, cron jobs, or reporting tools still connect to this database (including from other VPCs or via VPN).
- Check for read replicas, RDS Proxy endpoints, or EventBridge rules that reference this instance.
- Review automated backups and retention — deleting the instance removes automated backups; create a manual snapshot first if you need a recovery point.
- Remember that stopping an RDS instance still incurs storage charges; deleting with a final snapshot removes compute cost but snapshot storage is billed until you delete the snapshot.
Paid plans include remediation scripts that create a final snapshot and delete the instance. AWS does not support --dry-run for RDS delete — review commands carefully before running them.
What triggers this finding
An available RDS database instance older than 14 days with fewer than 0.5 average database connections over the last 14 days.
Typical fix
Create a final snapshot, then delete the instance if the database is no longer needed. Confirm applications and backups no longer depend on it.
Example savings
100% of instance compute charges — typically $15–$500+/month depending on instance class.
See also: Severity and savings estimates for how Parsivex calculates figures on your report.