Ensure EC2 instances are launched from approved AMIs
EC2 instances should be launched from approved, hardened AMIs to ensure consistent security configurations and patching.
Security Impact
Unapproved AMIs may contain vulnerabilities, malware, or non-compliant configurations.
How to Remediate
Maintain a list of approved AMI IDs. Use AWS Config rule 'approved-amis-by-id' or 'approved-amis-by-tag' for enforcement.
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 SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ec2-16
- Service
- Elastic Compute Cloud (EC2)
- Category
- Instance Configuration
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial