DMS endpoints should use SSL
Checks that the DMS endpoint's SSL mode is require, verify-ca or verify-full, so the connection between the replication instance and the database is encrypted; the verify modes also check the server certificate. Endpoints whose engine has no SSL mode, such as Kinesis, DynamoDB and Redshift, report none and fail here although AWS documents their connections as encrypted.
- service
- DMS
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Can break clients: Tasks using this endpoint fail to connect if the database does not accept SSL or the CA certificate does not match, so run Test connection before restarting them.
In the console
Database Migration Service → Endpoints → the endpoint → Modify
- SSL mode
- verify-full where the engine supports it, otherwise verify-ca or require; AWS's SSL page lists each engine's modes
- CA certificate
- The certificate bundle that signed the database's server certificate, needed for verify-ca and verify-full
With the AWS CLI
aws dms modify-endpoint --endpoint-arn <endpoint-arn> --ssl-mode <ssl-mode> --certificate-arn <ca-certificate-arn> --region <region>With Terraform
resource "aws_dms_endpoint" "this" {
endpoint_id = var.endpoint_id
endpoint_type = var.endpoint_type
engine_name = var.engine_name
ssl_mode = var.ssl_mode
certificate_arn = var.ca_certificate_arn
}
See which of your accounts this check is failing on.
Book a live scan