Ensure EC2 placement groups are used for high availability
Placement groups should be used for distributed workloads to ensure instances are spread across underlying hardware.
Security Impact
Without placement groups, instances may be placed on the same underlying hardware, creating a single point of failure.
How to Remediate
Create spread or partition placement groups for critical workloads. Use cluster placement groups for low-latency requirements.
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-26
- Service
- Elastic Compute Cloud (EC2)
- Category
- High Availability
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial