Ensure EMR clusters use IMDSv2 for instance metadata
Instance Metadata Service v2 prevents SSRF attacks from accessing instance role credentials on EMR nodes.
Security Impact
IMDSv1 is vulnerable to SSRF attacks that can steal instance role credentials and escalate privileges.
How to Remediate
Configure EMR clusters to require IMDSv2 by setting HttpPutResponseHopLimit and HttpTokens in launch configurations.
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 Security Best Practices, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-emr-7
- Service
- Amazon EMR
- Category
- Instance Security
- Severity
- HIGH
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 clusters are not publicly accessible
Ensure EMR security groups restrict access appropriately
Ensure EMR clusters have Kerberos authentication enabled