Ensure Systems Manager managed instances use IMDSv2
Instance Metadata Service v2 requires session tokens for metadata access, preventing SSRF attacks from accessing instance credentials.
Security Impact
IMDSv1 is vulnerable to SSRF attacks that can steal instance role credentials and escalate privileges.
How to Remediate
Use State Manager or automation to enforce IMDSv2 on all instances. Set HttpTokens=required in instance metadata options.
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 Systems Manager 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, Security Best Practices compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ssm-15
- Service
- AWS Systems Manager
- Category
- Instance Security
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Systems Manager Checks
View all checksEnsure Systems Manager managed instances are compliant with patch baselines
Ensure Systems Manager Session Manager is used instead of SSH/RDP
Ensure Session Manager has logging enabled to S3 and CloudWatch
Ensure Systems Manager Parameter Store uses SecureString for sensitive data
Ensure Systems Manager documents do not contain hardcoded credentials