Ensure EMR clusters are not publicly accessible
EMR clusters should be launched in private subnets without public IP addresses to prevent direct internet access.
Security Impact
Publicly accessible EMR clusters are vulnerable to unauthorized access, data exfiltration, and attacks on distributed processing frameworks.
How to Remediate
Launch clusters in private subnets. Use NAT gateways for outbound internet access. Remove public IP assignments.
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 Amazon EMR 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-emr-3
- Service
- Amazon EMR
- Category
- Network Security
- Severity
- CRITICAL
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon EMR Checks
View all checksEnsure EMR clusters have encryption at rest enabled
Ensure EMR clusters have encryption in transit enabled
Ensure EMR security groups restrict access appropriately
Ensure EMR clusters have Kerberos authentication enabled
Ensure EMR clusters have logging enabled to S3