Skip to main content
Compliance · Medium severity

EC2 Instance Has a Public IP: Review If Needed

The instance is directly addressable from the internet, so its exposure rests entirely on the security group being right.

Free to start. No card. The playground just needs your work email.

AWSprovider
Mediumseverity
Compliancewhere it shows up
Manualfix, steps written out

AWS

Found, explained, handed over.

Where the estate departs from your policies, frameworks and tagging rules.

01

Detect

ZopNight checks this automatically across AWS, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Remove the public IP from EC2 instance.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
EC2 Instances on AWS
The fix, by hand
  1. Confirm whether anything dials this instance directly from the internet (DNS records, monitoring probes, customer integrations).
  2. If inbound public access is required, terminate this instance and re-launch behind an Application Load Balancer in a public subnet, with the instance in a private subnet.
  3. If only outbound internet access is needed, move the instance to a private subnet with a NAT Gateway or VPC endpoints.
  4. If no internet access is needed, disable AssignIpv6 / public IPv4 on the network interface.
  5. Validate end-to-end (app smoke tests, monitoring probes) before the next prod release.

These are the steps the finding carries in the product.

Category
Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
Where it appears
The Compliance tab of Recommendations, with every affected resource listed.
Rule ID
RC-153
Full reference

EC2 Instance Has a Public IP -- Review If Needed

Related checks

See the compliance findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·