Aurora/RDS cluster storage is not encrypted at rest
- Severity
- High
- Service
- RDS
- Check ID
- RDS_CLUSTER_NOT_ENCRYPTED
What this check finds
The DB cluster has StorageEncrypted=false, so cluster volumes, automated backups, snapshots, and replicas are stored unencrypted. Anyone able to access the underlying storage or a snapshot can read the data. Cluster-level encryption is not reflected in per-instance checks.
Passing looks like: Aurora/RDS cluster encrypted at rest.
How to fix it
Encryption cannot be enabled in place. Take a snapshot, copy it with a KMS key to produce an encrypted copy, and restore a new encrypted cluster, then cut over.
AWS console
RDS → Snapshots → Copy (enable encryption) → Restore.
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 |
|---|---|
| CIS AWS Foundations Benchmark v5.0.0 |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| 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
- HighRDS automated backups are disabled
- HighRDS instance does not have automatic minor version upgrades enabled
- HighRDS instance has zero database connections for 7 days
- 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