ElastiCache replication groups should be encrypted in transit
Checks that ElastiCache (Redis OSS or Valkey) replication groups have encryption in transit enabled, so traffic between clients and nodes, and between the nodes, is TLS encrypted. A group in the Preferred transit encryption mode passes, although it still accepts unencrypted connections until the mode is Required.
- service
- ElastiCache
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Replaces the resource: Redis OSS below 7 cannot turn this on in place (Terraform replaces below 7.0.5): upgrade the engine, or restore a backup into a new group with it on, repoint clients, delete the old.
- Can break clients: Once the mode is Required, every client that does not connect with TLS is refused, so keep it at Preferred until all of them do.
In the console
ElastiCache → Valkey caches or Redis OSS caches → the cache → Actions → Modify → Security
- Encryption in transit
- Enable
- Transit encryption mode
- Preferred first; Required once every client connects with TLS
With the AWS CLI
aws elasticache modify-replication-group --replication-group-id <replication-group-id> --transit-encryption-enabled --transit-encryption-mode preferred --region <region>With Terraform
resource "aws_elasticache_replication_group" "this" {
replication_group_id = var.replication_group_id
description = var.description
transit_encryption_enabled = true
transit_encryption_mode = "preferred"
}
See which of your accounts this check is failing on.
Book a live scan