Other Articles

RDS DB Cluster – Encryption of Storage

Secure Configuration Checks > AWS

This check ensures that encryption at rest is enabled for the storage of Amazon RDS DB clusters, such as Amazon Aurora clusters. Encryption protects the data in the cluster volume, its automated backups, snapshots and read replicas. Without it, anyone who gets access to the underlying storage or a snapshot can read the data.

Check Details

  • Resource: RDS DB Cluster
  • Check: Encryption of RDS cluster storage (StorageEncrypted)
  • Risk: Data, backups and snapshots can be read in clear text if the storage or a snapshot is accessed or shared

Remediation via AWS Console

  1. Log in to the AWS Management Console and open the Amazon RDS console.

    Amazon RDS Console
  2. In the left navigation pane, click Databases, select the unencrypted DB cluster, and click Actions and then Take snapshot. Enter a snapshot name and click Take snapshot.
  3. In the left navigation pane, click Snapshots. Wait until the status of the snapshot is Available.
  4. Select the snapshot and click Actions > Copy snapshot. Under Encryption, select the default AWS-managed key (aws/rds) or a customer-managed KMS key, according to your security policy. Click Copy snapshot.

    Copy a snapshot with encryption enabled
  5. When the encrypted copy is Available, select it and click Actions and then Restore snapshot. Enter a new cluster name, choose the instance class, VPC, subnet group and security group, then click Restore DB cluster.

    Restore an encrypted DB cluster from a snapshot
  6. Point your applications to the endpoints of the new cluster and test them.
  7. When you have confirmed that the new cluster works, delete the old cluster and the unencrypted snapshots. They still hold the data without encryption.

Remediation via AWS CLI

  1. Log in to the AWS Management Console and click the CloudShell icon (>_) in the top-right corner.

    AWS CloudShell
  2. List the DB clusters where storage encryption is turned off. The output shows the cluster name, the engine and the engine version:

    aws rds describe-db-clusters \
    --query 'DBClusters[?StorageEncrypted==`false`].[DBClusterIdentifier,Engine,EngineVersion]' \
    --output text
    

    The command covers one region. Add --region <region> to each aws command to check another.

  3. Stop writes to the cluster, then take a snapshot and wait until it is available:

    aws rds create-db-cluster-snapshot \
    --db-cluster-identifier <cluster-name> \
    --db-cluster-snapshot-identifier <cluster-name>-unencrypted
    
    aws rds wait db-cluster-snapshot-available \
    --db-cluster-snapshot-identifier <cluster-name>-unencrypted
    
    
  4. Copy the snapshot with a KMS key to create an encrypted snapshot:

    aws rds copy-db-cluster-snapshot \
    --source-db-cluster-snapshot-identifier <cluster-name>-unencrypted \
    --target-db-cluster-snapshot-identifier <cluster-name>-encrypted \
    --kms-key-id <kms-key-id>
    
    aws rds wait db-cluster-snapshot-available \
    --db-cluster-snapshot-identifier <cluster-name>-encrypted
    
    
  5. Restore the encrypted snapshot as a new cluster and add an instance to it:

    aws rds restore-db-cluster-from-snapshot \
    --db-cluster-identifier <new-cluster-name> \
    --snapshot-identifier <cluster-name>-encrypted \
    --engine <engine> \
    --kms-key-id <kms-key-id> \
    --db-subnet-group-name <subnet-group-name> \
    --vpc-security-group-ids <security-group-id>
    
    aws rds create-db-instance \
    --db-instance-identifier <new-cluster-name>-1 \
    --db-cluster-identifier <new-cluster-name> \
    --engine <engine> \
    --db-instance-class <instance-class>
    
    aws rds wait db-instance-available \
    --db-instance-identifier <new-cluster-name>-1
    
    
  6. Verify that the new cluster is encrypted:

    aws rds describe-db-clusters \
    --db-cluster-identifier <new-cluster-name> \
    --query 'DBClusters[0].[DBClusterIdentifier,StorageEncrypted,KmsKeyId]' \
    --output text
    

    StorageEncrypted must be True.

  7. Point your applications to the endpoints of the new cluster and test them. When you have confirmed that it works, delete the unencrypted snapshot and then the old cluster:

    aws rds delete-db-cluster-snapshot \
    --db-cluster-snapshot-identifier <cluster-name>-unencrypted
    

    Delete the old cluster in the console, or with aws rds delete-db-cluster after its instances are deleted. Take a final snapshot only if you need one, and make sure it is encrypted.

Replace <cluster-name> with the identifier of the unencrypted cluster, and <new-cluster-name> with a name for the encrypted cluster. Replace <engine> with the engine of the cluster, for example aurora-mysql or aurora-postgresql, and <instance-class> with an instance class, for example db.r6g.large. Replace <kms-key-id> with the ID or ARN of your KMS key, <subnet-group-name> with the DB subnet group and <security-group-id> with the security group of the old cluster. Repeat steps 3 to 7 for each cluster that step 2 lists.

Updated on 05 November, 2026