HIGH

Ensure Redshift clusters are deployed in VPC

Redshift clusters should be deployed in VPC for network isolation, security group controls, and integration with other VPC resources.

Security Impact

Non-VPC clusters lack network isolation and modern security controls available in VPC environments.

How to Remediate

Deploy new Redshift clusters in VPC. Migrate EC2-Classic clusters to VPC using snapshot restore method.

Affected Resources

AWS::Redshift::ClusterAWS::EC2::VPC

Compliance Frameworks

AWS Best PracticesNIST 800-53

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Amazon Redshift resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for AWS Best Practices, NIST 800-53 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-redshift-10
Service
Amazon Redshift
Category
Network Security
Severity
HIGH

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Amazon Redshift Checks

View all checks
aws-redshift-1critical

Ensure Redshift clusters are not publicly accessible

aws-redshift-2high

Ensure Redshift clusters have encryption at rest enabled

aws-redshift-3high

Ensure Redshift clusters have encryption in transit enabled

aws-redshift-4high

Ensure Redshift clusters have audit logging enabled

aws-redshift-5medium

Ensure Redshift clusters have automated snapshots configured