HIGH

Ensure RDS instances are deployed in private subnets

RDS instances should be deployed in private subnets without internet gateway routes.

Security Impact

RDS instances in public subnets with public accessibility are directly exposed to the internet.

How to Remediate

Deploy RDS instances in DB subnet groups containing only private subnets. Remove internet gateway routes.

Affected Resources

AWS::RDS::DBSubnetGroupAWS::RDS::DBInstance

Compliance Frameworks

SOC 2PCI-DSSHIPAANIST 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 Relational Database Service (RDS) 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 SOC 2, PCI-DSS, HIPAA compliance

  • Drift Detection

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

Check Details

Check ID
aws-rds-18
Service
Relational Database Service (RDS)
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 Relational Database Service (RDS) Checks

View all checks
aws-rds-1critical

Ensure RDS instances are not publicly accessible

aws-rds-2high

Ensure RDS instances have encryption at rest enabled

aws-rds-3medium

Ensure RDS instances use KMS customer managed keys

aws-rds-4high

Ensure RDS instances have automated backups enabled

aws-rds-5medium

Ensure RDS backup retention is at least 7 days