# 2.2.1 Ensure that encryption-at-rest is enabled for RDS instances

- Source: https://support.icompaas.com/support/solutions/articles/62000233093-2-2-1-ensure-that-encryption-at-rest-is-enabled-for-rds-instances
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS CIS V.4 Level 1 Benchmarks](https://support.icompaas.com/support/solutions/62000112671) › [CIS Control 2](https://support.icompaas.com/support/solutions/folders/62000169193)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

### Profile Applicability:

Level 1

## Description:

Amazon RDS Encryption helps protect sensitive data by encrypting databases, backups, and snapshots using the AES-256 encryption algorithm. Encryption is handled transparently without affecting database performance. Amazon RDS encryption applies to:

-   Database storage
    
-   Automated backups
    
-   Read replicas
    
-   Snapshots
    

## Rationale:

-   Protects confidential data from unauthorized access or data breaches.
    
-   Encryption at rest prevents attackers from reading stored data even if they gain access to the storage layer.
    
-   Helps meet compliance requirements such as GDPR, HIPAA, SOC 2, and PCI-DSS.
    
-   Ensures full data protection across RDS backups, snapshots, and replicas.
    

## Impact:

-   Cannot enable encryption for an existing RDS instance → Must create an encrypted snapshot and restore a new instance.
    
-   Slight performance impact (minimal, managed by AWS).
    
-   Cross-region replication restrictions (encrypted snapshots require the same KMS key).
    

## Default Value:

By default:

-   RDS does NOT enable encryption.
    
-   You must enable encryption when creating the database.
    
-   Existing RDS instances cannot be encrypted directly → Need a snapshot-based migration.
    

## Pre-Requisites:

1.  IAM permissions to modify RDS instance settings
    
    -   rds:DescribeDBInstances, rds:ModifyDBInstance, rds:CreateDBSnapshot, rds:RestoreDBInstanceFromDBSnapshot, kms:ListAliases
        
2.  AWS CLI installed (for automation)
    
3.  List of all RDS instances in the AWS account
    

## Remediation:

### Test Plan:

## Using AWS Console

Check Encryption Status for an RDS Instance

1.  Log in to the AWS Console → Open Amazon RDS Console: [RDS Console](https://console.aws.amazon.com/rds/)
    
2.  Click Databases
    

           ![](https://support.icompaas.com/assets/kb/3ec870631875e6bd.png)

3.  Select an RDS instance
    

            ![](https://support.icompaas.com/assets/kb/775fd0d8e97b3703.png)

4.  Click the Configuration tab
    

        ![](https://support.icompaas.com/assets/kb/d3eaba5f99ae9eed.png)

5.  Under Storage, check Encryption Enabled status:
    
    -   Enabled → Compliant
        
    -   Disabled → Not compliant      ![](https://support.icompaas.com/assets/kb/4ba7b7b978ab55b0.png)      
        

-   Repeat for all RDS instances.

## Using AWS CLI

Step 1: List All RDS Instances

aws rds describe-db-instances --query 'DBInstances\[\*\].DBInstanceIdentifier'

This will list all RDS instances in your AWS account.

Step 2: Check Encryption Status for Each Instance

aws rds describe-db-instances --db-instance-identifier <db-name> --query 'DBInstances\[\*\].StorageEncrypted'

 Expected Output (If encryption is enabled):

\[

    true

\]

Step 3: Check Encryption for All RDS Instances in a Region

aws rds describe-db-instances --query 'DBInstances\[\*\].\[DBInstanceIdentifier,StorageEncrypted\]'

This command will list all RDS instances along with their encryption status.

## Implementation Steps:

## Using AWS Console

Step 1: Create a Snapshot of the Unencrypted Database

1.  Log in to the AWS Console → Open RDS Console
    
2.  Click Databases → Select the unencrypted RDS instance
    

![](https://support.icompaas.com/assets/kb/7d2bee9143528c9f.png)

3.  Click Actions → Select Take Snapshot
    

           ![](https://support.icompaas.com/assets/kb/100502c27114aac1.png)

4.  Enter a Snapshot Name → Click Take Snapshot
    

            ![](https://support.icompaas.com/assets/kb/8237110f1cae97da.png)

Step 2: Copy the Snapshot with Encryption Enabled

1.  Open the RDS Console → Click Snapshots
    

                 ![](https://support.icompaas.com/assets/kb/4b2d0ad98c6f5f56.png)

2.  Select the snapshot you just created
    

               ![](https://support.icompaas.com/assets/kb/e8f4d393902efb6d.png)

3.  Click Actions → Select Copy Snapshot
    

             ![](https://support.icompaas.com/assets/kb/638d9682b3840331.png)

4.  In the New Snapshot Identifier, enter a name
    

                     ![](https://support.icompaas.com/assets/kb/820bcb134af97be8.png)

5.  Enable Encryption → Select AWS Default KMS Key (or a custom key)
    

            ![](https://support.icompaas.com/assets/kb/f35ea16806237ede.png)

6.  Click Copy Snapshot
    

                      ![](https://support.icompaas.com/assets/kb/200356e0620f7267.png)

Step 3: Restore the Encrypted Snapshot to a New Database

1.  Go to Snapshots → Select the encrypted snapshot
    

                    ![](https://support.icompaas.com/assets/kb/26883398bff2e514.png)

           ![](https://support.icompaas.com/assets/kb/7ddb10870d249104.png)

2.  Click Actions → Select Restore Snapshot ![](https://support.icompaas.com/assets/kb/c42ff41e9d155e0f.png) 
    
3.  Enter a new database identifier
    

           ![](https://support.icompaas.com/assets/kb/f7735190377bf083.png)

4.  Click Restore DB Instance              ![](https://support.icompaas.com/assets/kb/7a3a38a53e6c0bc2.png)              
    

-   Now, your new RDS instance is encrypted!
-   Update application configurations to point to the new encrypted RDS instance.

## Using AWS CLI

Step 1: Take a Snapshot of the Unencrypted Database

aws rds create-db-snapshot --db-instance-identifier <db-name> --db-snapshot-identifier <snapshot-name>

Creates a snapshot of the existing unencrypted RDS instance.

Step 2: Copy the Snapshot with Encryption

aws rds copy-db-snapshot --source-db-snapshot-identifier <snapshot-name> --target-db-snapshot-identifier <encrypted-snapshot-name> --kms-key-id <kms-id> --copy-tags

Copies the snapshot with encryption enabled using a KMS key.

Step 3: Restore the Encrypted Snapshot to a New Database

aws rds restore-db-instance-from-db-snapshot --db-instance-identifier <new-db-name> --db-snapshot-identifier <encrypted-snapshot-name>

Restores the encrypted snapshot to a new database instance.

Step 4: Verify That Encryption is Enabled

aws rds describe-db-instances --db-instance-identifier <new-db-name> --query 'DBInstances\[\*\].StorageEncrypted'

Expected Output: \[ true \]

##   

## Backout Plan:

If issues arise:

1.  Revert to the original unencrypted RDS instance.
    
2.  Ensure backups exist before making changes.
    
3.  Rollback application changes to point back to the old database.
    

## References:

-   [AWS RDS Encryption Best Practices](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Encryption.html)
    
-   [](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_CopySnapshot.html)[Copying an Encrypted Snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_CopySnapshot.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
