Connections to Amazon Redshift clusters should be encrypted in transit

How to fix it

• Interrupts service: Neither the new value nor a newly associated parameter group applies until the cluster reboots, so schedule the reboot for a quiet period.
• Can break clients: Clients that connect without SSL are refused once this applies, so check drivers and connection strings first.

In the console

Redshift → Configurations → Workload management → the cluster's parameter group → Parameters → require_ssl

require_ssl

true

Cluster parameter group

A custom group with require_ssl true, if the cluster is on a default group, which cannot be edited

With the AWS CLI

aws redshift modify-cluster-parameter-group --parameter-group-name <parameter-group-name> --parameters ParameterName=require_ssl,ParameterValue=true --region <region>

With Terraform

resource "aws_redshift_parameter_group" "this" {
  name   = var.parameter_group_name
  family = "redshift-2.0"

  parameter {
    name  = "require_ssl"
    value = "true"
  }
}