Will It Vibe?Instance assigned a public IP address
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
associate_public_ip_address = true puts the instance directly on the public internet, widening its attack surface beyond a private subnet with a NAT or load balancer in front.
Why it matters
associate_public_ip_address = true gives the instance a routable public address, so it is reachable from the internet and every open security group port is exposed to the world. Most workloads should sit in a private subnet and reach the internet through a NAT gateway, with inbound traffic arriving via a load balancer.
How to fix it
Set associate_public_ip_address = false and place the instance in a private subnet. Route outbound traffic through a NAT gateway and put a load balancer in front for any inbound service. Reserve public IPs for hosts that genuinely must be directly reachable, such as a bastion, and lock those down tightly.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo