Ensure EC2 instance IAM roles are used instead of access keys
EC2 instances should use IAM roles instead of hardcoded access keys. IAM roles provide temporary credentials that are automatically rotated.
Security Impact
Hardcoded access keys can be compromised and are difficult to rotate, leading to long-term credential exposure.
How to Remediate
Create an IAM role with required permissions and attach it to EC2 instances. Remove any hardcoded access keys from instances.
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 Elastic Compute Cloud (EC2) 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 CIS AWS v1.5.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ec2-19
- Service
- Elastic Compute Cloud (EC2)
- Category
- Identity Management
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial