Enable encryption in Amazon Redshift to protect data at rest and enforce SSL in transit.
Encrypting the cluster protects sensitive customer, order, and payment data stored on disk and in automated snapshots. SSL ensures data in flight remains private.
No. You must create a new encrypted cluster or restore an encrypted snapshot. Plan migration time.
At-rest: AWS‐managed KMS key or customer KMS key (CMK).
In-transit: Force SSL by setting require_ssl parameter to true.
Use AWS CLI, SDK, or Console. Specify --encrypted true and an optional --kms-key-id. See syntax below.
Create a snapshot of the old cluster, restore it with encryption, or unload to S3 and reload with COPY.
Modify the cluster parameter group: set require_ssl to true, then reboot.
Use server-side encryption (SSE) on S3 objects and specify the aws_kms_key_id in the COPY command.
Rotate CMKs regularly, enforce SSL in connection strings, block unencrypted ports in security groups, and use IAM roles rather than access keys.
The COPY example below shows loading encrypted order CSVs into the Orders table.
Minimal. Redshift uses hardware-accelerated AES, so most workloads see negligible impact.
Yes. Pass its ARN via --kms-key-id during cluster creation or snapshot restore.
No native feature exists. Use client-side encryption before loading or Amazon S3-side encryption on files.