Redshift cluster must not be publicly accessible
Critical
AWS
General
aws-redshift-cluster-no-public-access
Applies to
AWS::Redshift::Cluster
What CGPulse checks
A resource passes this rule when publiclyAccessible must equal false. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Disable public accessibility and restrict access to VPC-internal connections. In AWS Console: Redshift > Clusters > Modify > set Publicly accessible to No. See: https://docs.aws.amazon.com/redshift/latest/mgmt/managing-clusters-vpc.html
Terraform
resource "aws_redshift_cluster" "{name}" {
publicly_accessible = false
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled