DMS endpoints for MongoDB should have an authentication mechanism enabled¶
This control checks whether an AWS DMS endpoint for MongoDB is configured with an authentication mechanism. The control fails if an authentication type isn't set for the endpoint.
How to fix¶
Attribute mongodb_settings[0].auth_type of aws_dms_endpoint must be "password".
Implementation options¶
Choose the option that matches how you manage Terraform. All options satisfy this control.
Option 1: Terraform AWS provider resources¶
If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_dms_endpoint.
resource "aws_dms_endpoint" "this" {
endpoint_id = "pofix-example-endpoint"
endpoint_type = "source"
engine_name = "mysql"
redis_settings {
auth_type = "none"
port = 6379
server_name = "redis.example.com"
}
mongodb_settings {
auth_type = "password"
}
}
Which option should I choose?
- Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
- Open source module (
terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready. - Terraform AWS provider resources: manage Terraform resources directly.
Tool mappings¶
Use these identifiers to cross-reference this control across tools, reports, and evidence.
Compliance.tf (CTF) Control:
dms_endpoint_mongo_db_authentication_enabledAWS Config Managed Rule:
DMS_MONGO_DB_AUTHENTICATION_ENABLEDPowerpipe Control:
aws_compliance.control.dms_endpoint_mongo_db_authentication_enabled