RDS database not encrypted at rest
RDS encryption at rest protects the database storage, automated backups, read replicas and snapshots. It can only be enabled when the instance (or a snapshot restore) is created.
Why it matters
An unencrypted RDS snapshot that is copied or shared exposes the whole database; encryption at rest closes that path.
It's a standard audit requirement, and because it can't be toggled on in place, an unencrypted instance needs a planned migration.
How to check for it
- aws rds describe-db-instances --query "DBInstances[?StorageEncrypted==\`false\`].DBInstanceIdentifier".
- Check snapshots too: aws rds describe-db-snapshots --query "DBSnapshots[?Encrypted==\`false\`]".
How to fix it
- Take a snapshot, copy it with encryption enabled, and restore a new encrypted instance; then cut over.
- Set encryption (with a KMS key) at creation for all new databases, and encrypt replicas.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Can I encrypt an existing RDS instance in place?
- No. You create an encrypted copy via an encrypted snapshot and migrate to it — plan a short cutover window.