RDS instance has zero database connections for 7 days
- Severity
- High
- Service
- RDS
- Check ID
- RDS_IDLE_INSTANCE
What this check finds
An RDS instance with no connections over 7 days is running with no active workload. RDS instances incur charges for instance hours, storage, and I/O regardless of activity. An idle instance is a strong signal it can be deleted or converted to a snapshot.
Passing looks like: No idle RDS instances.
How to fix it
Create a final snapshot then delete the instance if it is no longer needed: aws rds create-db-snapshot then aws rds delete-db-instance --skip-final-snapshot (or omit flag).
AWS console
RDS → Databases → select → Actions → Delete.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More RDS checks
- HighAurora/RDS cluster storage is not encrypted at rest
- HighRDS automated backups are disabled
- HighRDS instance does not have automatic minor version upgrades enabled
- HighRDS instance storage is not encrypted at rest
- HighRDS security group allows broad CIDR ingress (broader than /16)
- HighRDS snapshot is public
- MediumAurora/RDS cluster has automated backups disabled
- MediumNo RDS event subscription configured for this account