Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
redshift_cluster_enhanced_vpc_routingProvider: AWS
Service:
redshiftSeverity: MEDIUM
Categories:
trust-boundaries, internet-exposedResource type:
AwsRedshiftClusterWhat this check verifies
Amazon Redshift clusters are assessed for theEnhancedVpcRouting setting, which routes all COPY and UNLOAD traffic between the cluster and data repositories through the VPC, enabling use of VPC security controls and logging.
Risk
Without enhanced VPC routing,COPY/UNLOAD transfers can leave VPC oversight, reducing control and visibility.
- VPC egress filtering and endpoint policies can be bypassed (confidentiality)
- Limited flow-log telemetry (visibility)
- Higher risk of unauthorized exfiltration or tampering (confidentiality, integrity)
Recommendation
EnableEnhancedVpcRouting and enforce least privilege egress:
- Prefer private access with VPC endpoints and restrictive policies
- Constrain outbound paths via security groups, NACLs, and routing
- Monitor transfers with VPC Flow Logs
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws redshift modify-cluster —cluster-identifier <cluster-id> —enhanced-vpc-routing
References
- https://docs.aws.amazon.com/securityhub/latest/userguide/redshift-controls.html#redshift-7
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/Redshift/enable-enhanced-vpc-routing.html
- https://docs.aws.amazon.com/redshift/latest/mgmt/enhanced-vpc-routing.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = redshift_cluster_enhanced_vpc_routing. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks