dms_replication_instance_encryption_enabled¶

How to fix¶

Attribute kms_key_arn of aws_dms_replication_instance must be non-empty.

Implementation options¶

Choose the option that matches how you manage Terraform. All options satisfy this control.

Option 1: Open source module (terraform-aws-modules)¶

If you use terraform-aws-modules/dms/aws, configure the required module inputs to satisfy this control. You can later migrate to the compliance.tf module with minimal changes because it is compatible by design.

module "dms" {
  source  = "terraform-aws-modules/dms/aws"
  version = ">=2.0.0"

  repl_instance_class                  = "dms.t3.micro"
  repl_instance_id                     = "abc123"
  repl_instance_vpc_security_group_ids = ["sg-12345678"]
  repl_subnet_group_subnet_ids         = ["subnet-12345678", "subnet-12345678"]

  repl_instance_kms_key_arn = "arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012"
}

Option 2: 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_replication_instance.

resource "aws_dms_replication_instance" "this" {
  replication_instance_class = "dms.t3.micro"
  replication_instance_id    = "pofix-example-repl"

  kms_key_arn = "arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012"
}

Tool mappings¶

Use these identifiers to cross-reference this control across tools, reports, and evidence.

• Compliance.tf (CTF) Control: dms_replication_instance_encryption_enabled