Ensure Systems Manager automation documents have appropriate IAM roles
Automation documents should use least privilege IAM roles specific to required actions, not overly permissive admin roles.
Security Impact
Overly permissive automation roles increase blast radius if automation is compromised or misconfigured.
How to Remediate
Create specific IAM roles for each automation use case. Grant only required permissions. Avoid using AdministratorAccess.
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, Least Privilege, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ssm-10
- Service
- AWS Systems Manager
- Category
- Access Control
- Severity
- MEDIUM
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