Encryption at rest secures all data blocks stored in Amazon Redshift by automatically encrypting the cluster s disks and backups with AWS KMS or a customer-managed key.
Protect PII, financial records, and sensitive business metrics from unauthorized disk access. Meet GDPR, HIPAA, and PCI-DSS compliance without application changes.
New RA3 clusters default to AWS-owned KMS keys. For precise control, create a cluster or snapshot copy grant with a customer-managed key (CMK).
Use the AWS Console, CLI, or CloudFormation. Supply --encrypted true and --kms-key-id when calling create-cluster.Redshift encrypts system tables, user tables like Customers, Orders, and automatic backups.
No direct toggle exists. Snapshot the cluster, then restore it with encryption parameters. Point applications to the new endpoint.
Encryption uses AES-256 with hardware acceleration. Benchmarking shows <2% overhead on most analytical workloads.
Enable automatic KMS key rotation or manually create a new CMK and re-encrypt snapshots.Restore snapshots with the new key.
Query SVL_ENCRYPTED_COLUMNS or use AWS Config rules (redshift-cluster-kms-enabled). CloudTrail logs CMK usage for compliance audits.
Store CMKs in separate AWS accounts, enable automatic rotation, restrict kms:Decrypt to Redshift service role, and always back up CMKs.a0
Forgetting to create snapshot copy grants stops cross-region encrypted backups. Also, missing CMK IAM permissions causes create-cluster failures.a0
.
Yes. Pass your CMK ARN in --kms-key-id. Redshift then encrypts data and snapshots with that key.
No. Spectrum relies on the S3 object s encryption. Configure S3 SSE-KMS or client-side encryption separately.
AWS charges $1 per CMK per month plus $0.03 per 10,000 KMS requests. Redshift performance impact is minimal.