DMS endpoints for Redis OSS should have TLS enabled
Checks that a DMS endpoint for a Redis OSS target connects with TLS (SSL encryption rather than plain text), so the data DMS writes to the Redis OSS cluster is encrypted in transit and cannot be read or intercepted on the way.
- service
- DMS
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Can break clients: Tasks writing to this endpoint fail to connect if the Redis OSS cluster does not accept TLS, so run Test connection before restarting them.
In the console
Database Migration Service → Endpoints → the endpoint → Modify
- SSL security protocol
- SSL encryption
- SSL CA certificate
- Empty for ElastiCache, which uses the Amazon root CA; your CA's certificate for a self-managed Redis OSS
With the AWS CLI
aws dms modify-endpoint --endpoint-arn <endpoint-arn> --redis-settings ServerName=<server-name>,Port=<port>,AuthType=<auth-type>,SslSecurityProtocol=ssl-encryption --region <region>With Terraform
resource "aws_dms_endpoint" "this" {
endpoint_id = var.endpoint_id
endpoint_type = "target"
engine_name = "redis"
redis_settings {
auth_type = var.auth_type
server_name = var.server_name
port = var.port
ssl_security_protocol = "ssl-encryption"
}
}
See which of your accounts this check is failing on.
Book a live scan