Verifies that Amazon Redshift clusters are encrypted at rest using KMS to protect sensitive data.
Rule | Redshift clusters should be encrypted at rest |
Framework | AWS Foundational Security Best Practices |
Severity | ✔ Medium |
Rule Description
Redshift clusters should be encrypted at rest to comply with AWS Foundational Security Best Practices. Encrypting data at rest provides an added layer of security by ensuring that sensitive information is protected from unauthorized access.
Troubleshooting Steps
If encryption at rest is not enabled for your Redshift clusters, you can follow the steps below to enable it:
Necessary Codes
If encryption at rest is not enabled for your Redshift clusters, you can use the AWS Command Line Interface (CLI) to enable it by modifying the cluster using the
modify-cluster
command with the --encrypted
parameter.aws redshift modify-cluster --cluster-identifier <cluster-identifier> --encrypted
Step-by-Step Guide for Remediation
Open the AWS CLI or AWS Management Console.
Check the encryption status of your Redshift clusters by running the following command:
aws redshift describe-clusters --query "Clusters[*].[ClusterIdentifier,Encrypted]"
Identify the Redshift clusters that are not encrypted at rest.
Enable encryption at rest for a specific Redshift cluster by running the following command:
aws redshift modify-cluster --cluster-identifier <cluster-identifier> --encrypted
Verify that encryption at rest is enabled for the cluster by checking the encryption status again:
aws redshift describe-clusters --query "Clusters[*].[ClusterIdentifier,Encrypted]"
Repeat the above steps for any other Redshift clusters that are not encrypted at rest.
By following these steps, you can ensure that your Redshift clusters are encrypted at rest to align with AWS Foundational Security Best Practices.