Why it matters
Test databases, databases of retired applications and copies made for a one-off task often keep running for months after anyone last connected.How nOps finds it
This recommendation comes from AWS Compute Optimizer through Cost Optimization Hub, not from an nOps rule. AWS treats an instance as idle when it had no database connections over the lookback period (14 days by default). The saving is AWS’s estimate of what the instance costs.Before you start
Confirm with the owner that the database is not needed, including for month-end jobs, disaster recovery or audits.How to implement
- Check CloudWatch → DatabaseConnections for the instance over a longer period than the lookback.
- Find the owner from tags and confirm the database can go.
- If it must be kept but is rarely used, consider Aurora Serverless v2 with auto-pause instead (migrate with a snapshot restore).
- Otherwise delete it with a final snapshot (
aws rds delete-db-instance --db-instance-identifier DB_ID --final-db-snapshot-identifier DB_ID-final). - Remove it from Terraform or CloudFormation so it is not recreated.
Risks and considerations
- Deleting is permanent unless you keep a final snapshot. The snapshot keeps costing storage until you delete it.
- A database used only once a month or once a quarter can look idle in a 14-day window.
- To roll back, restore the instance from the final snapshot.
FAQs
Should I delete it or move it to Aurora Serverless?
Should I delete it or move it to Aurora Serverless?
Delete it if nobody needs it. Move it to Aurora Serverless with auto-pause if it is needed now and then, so you pay mostly for storage while it is idle.
Why not just stop it?
Why not just stop it?
RDS starts a stopped instance again after 7 days, so stopping only helps for short breaks.