Ensure EC2 stopped instances are reviewed and terminated
Stopped EC2 instances may still incur costs for EBS volumes and reserved IPs. They should be reviewed and terminated if no longer needed.
Security Impact
Stopped instances continue to incur costs for attached EBS volumes and may contain outdated, vulnerable configurations.
How to Remediate
Review stopped instances regularly. Create snapshots of volumes if data retention is needed, then terminate 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 SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-ec2-25
- Service
- Elastic Compute Cloud (EC2)
- Category
- Cost Optimization
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial