Ensure EC2 instances do not have public IP addresses
EC2 instances should not have public IP addresses unless required. Use load balancers, NAT gateways, or bastion hosts for public-facing services.
Security Impact
Public IP addresses expose instances directly to the internet, increasing attack surface.
How to Remediate
Launch instances in private subnets. Use Application Load Balancers for web traffic and NAT gateways for outbound internet access.
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-5
- Service
- Elastic Compute Cloud (EC2)
- Category
- Network Security
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial