Redshift cluster has a public IP address

Severity: Medium
Service: Redshift
Check ID: REDSHIFT_PUBLIC_IP

What this check finds

Redshift databases should be in private subnets. Databases should not have public IPs. You should additionally check if the Security Groups associated with this are allowing it to be publicly accessible.

Passing looks like: Redshift not publicly accessible.

How to fix it

Disable public accessibility on the Redshift cluster.

AWS CLI

aws redshift modify-cluster --cluster-identifier CLUSTER_ID --no-publicly-accessible

Names in capitals are placeholders for your own resource. Review a command before you run it.

AWS console

Redshift → Clusters → select cluster → Actions → Modify → Network and security → disable Publicly accessible.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to Redshift cluster has a public IP address
Framework	Controls
PCI-DSS v4.0.1	1.3 Network access to and from the cardholder data environment is restricted
NIST SP 800-53 Rev5 (Moderate)	SC-7 Boundary Protection
NIST Cybersecurity Framework 2.0	PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
ISO/IEC 27001:2022 Annex A	A.8.20 Networks security

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More Redshift checks

All Redshift checks