Ensure RDS instances use encrypted volumes

In AWS, you can only encrypt a database when you create it. However, you can create a snapshot of a database, encrypt that snapshot, and restore it as encrypted.

From the Console

Perform the following actions to create an encrypted database instance from the current one:

1. Open the security settings using the "Open in AWS" menu option
2. Select Actions, and then Take a snapshot
3. Give it a name and click Take snapshot
4. Select the newly created snapshot, and then Actions, Copy snapshot
5. Select the region and give it a name
6. Select a KMS key to encrypt the database with
7. After you created the copy, select it
8. Select Actions, and then Restore snapshot
9. Select the appropriate settings and click Restore DB Instance

Default Value

By default, encryption is turned on when creating a new database.

References

1. Encrypting Amazon RDS resources
2. Copying a DB snapshot

Multiple Remediation Paths

AWS

SERVICE-WIDE (RECOMMENDED when many resources are affected): Deploy centralized guardrails and remediation using AWS Config Conformance Packs and (if applicable) AWS Organizations SCPs.

aws configservice put-organization-conformance-pack --organization-conformance-pack-name <pack-name> --template-s3-uri s3://<bucket>/<template>.yaml

ASSET-LEVEL: Apply the resource-specific remediation steps above to only the affected assets.

PREVENTIVE: Add CI/CD policy checks (CloudFormation/Terraform validation) before deployment to prevent recurrence.

References for Service-Wide Patterns

• AWS Config Conformance Packs: https://docs.aws.amazon.com/config/latest/developerguide/conformance-packs.html
• AWS Organizations SCP examples: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps_examples.html

Operational Rollout Workflow

Use this sequence to reduce risk and avoid repeated drift.

1. Contain at Service-Wide Scope First (Recommended)

• AWS: deploy/adjust organization conformance packs and policy guardrails.

aws configservice put-organization-conformance-pack --organization-conformance-pack-name <pack-name> --template-s3-uri s3://<bucket>/<template>.yaml

2. Remediate Existing Affected Assets

• Execute the control-specific Console/CLI steps documented above for each flagged resource.
• Prioritize internet-exposed and production assets first.

3. Validate and Prevent Recurrence

• Re-scan after each remediation batch.
• Track exceptions with owner and expiry date.
• Add preventive checks in IaC/CI pipelines.