Ensure Glue connections are configured with VPC for database security
Connections to databases should use VPC endpoints or private subnets, not public internet connections.
Security Impact
Public database connections expose credentials in transit and increase attack surface.
How to Remediate
Configure Glue connections to use VPC, subnets, and security groups. Ensure databases are not publicly accessible.
Affected Resources
Compliance Frameworks
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 AWS Glue 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, NIST 800-53, Network Security compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-glue-13
- Service
- AWS Glue
- Category
- Network Security
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Glue Checks
View all checksEnsure Glue Data Catalog encryption at rest is enabled
Ensure Glue connection passwords are encrypted
Ensure Glue jobs have encryption for S3 data targets
Ensure Glue jobs have CloudWatch log encryption enabled
Ensure Glue jobs are configured with job bookmarks