Skip to main content

​
What this check does

Checks StorageEncrypted flag on all RDS instances. Passes when: All RDS instances have storage encryption enabled.

​
Why this matters

Encryption at rest protects database data.

​
How to fix

Encrypt RDS storage by migrating to an encrypted instance
  1. Sign in to the AWS Console, navigate to RDS → Databases, and select the unencrypted DB instance (storage encryption can only be set at creation, so existing instances must be migrated).
  2. Choose Actions → Take snapshot and wait for the snapshot to complete.
  3. Go to Snapshots, select the new snapshot, choose Actions → Copy snapshot, enable Encryption, and select your KMS key.
  4. Select the encrypted copy and choose Actions → Restore snapshot to create a new, encrypted DB instance.
  5. Update your application to use the new instance endpoint, verify connectivity, then delete the old unencrypted instance.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.