KMS key without automatic rotation
A customer-managed KMS key without automatic rotation uses the same cryptographic material indefinitely, so a single compromise exposes everything it ever encrypted.
Why it matters
Rotation limits the blast radius: if key material is ever exposed, only data encrypted since the last rotation is at risk, not all of it.
Yearly rotation is a common requirement in compliance frameworks and is effectively free to enable.
How to check for it
- KMS → the key → Key rotation tab shows whether automatic rotation is on (customer-managed symmetric keys only).
- aws kms get-key-rotation-status --key-id <id> — KeyRotationEnabled should be true.
How to fix it
- Turn on automatic yearly rotation (KMS → the key → Key rotation → Automatically rotate).
- AWS-managed keys rotate on their own and can't be changed — this check is about your customer-managed keys.
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
- Does rotation re-encrypt my data?
- No. KMS keeps old key versions so existing ciphertext still decrypts; new data uses the new material. There's no re-encryption to do.