AWS Redshift enhanced VPC routing should be enabled¶
Ensure that AWS Redshift cluster has 'enhancedVpcRouting' enabled. The rule is non-compliant if 'enhancedVpcRouting' is not enabled or if the configuration.enhancedVpcRouting field is 'false'.
How to fix¶
Attribute enhanced_vpc_routing of aws_redshift_cluster must be true.
Implementation options¶
Choose the option that matches how you manage Terraform. All options satisfy this control.
Option 1: Compliance.tf module (recommended)¶
Use the compliance.tf registry module to get this control enforced by default. This control is mapped to the frameworks shown in the tabs above. To begin, see get started with compliance.tf.
module "redshift" {
source = "acscism2023.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "cfrpart11.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "ffiec.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "hipaa.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "nist800171.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "nist80053.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "nistcsfv11.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "nistcsf.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
module "redshift" {
source = "pcidss.compliance.tf/terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
}
Option 2: Open source module (terraform-aws-modules)¶
If you use terraform-aws-modules/redshift/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 "redshift" {
source = "terraform-aws-modules/redshift/aws"
version = ">=7.0.0,<8.0.0"
cluster_identifier = "abc123"
database_name = "mydb"
master_password_wo = "change-me-in-production"
master_username = "admin"
node_type = "dc2.large"
number_of_nodes = 1
subnet_ids = []
vpc_security_group_ids = []
enhanced_vpc_routing = true
}
Option 3: 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_redshift_cluster.
resource "aws_redshift_cluster" "this" {
automated_snapshot_retention_period = 7
cluster_identifier = "pofix-example"
master_password = "ChangeMe123!"
master_username = "admin"
node_type = "dc2.large"
skip_final_snapshot = true
enhanced_vpc_routing = true
}
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:
redshift_cluster_enhanced_vpc_routing_enabledAWS Config Managed Rule:
REDSHIFT_ENHANCED_VPC_ROUTING_ENABLEDCheckov Check:
CKV_AWS_321Powerpipe Control:
aws_compliance.control.redshift_cluster_enhanced_vpc_routing_enabled