The IPv4 line item
Every public address on your AWS bill now costs $43.80 a year, attached or not. The ten-minute audit, and the three fixes priced.
Release your idle public IPs today. The rest of this page is arithmetic.
Since February 2024 AWS bills every public IPv4 address at $0.005 an hour, attached or not, in use or not. That is $3.65 a month and $43.80 a year per address, as of September 2026. One address is noise. The 40 to 60 that a mid-sized account accumulates, one per forgotten load balancer and long-terminated instance, is $1,750 to $2,600 a year for numbers nobody dials.
The audit takes ten minutes because AWS built the tool when it built the charge: Public IP Insights, free inside the VPC console, lists every public address in the account with what it is attached to. Sort by "unattached". That column is pure refund.
The fixes, in order of effort:
- Release unattached Elastic IPs. Zero risk, ten minutes, and the finding on every account we have checked this year: 8 to 20 of them, $350 to $875 a year.
- Count addresses per workload. A service behind a load balancer does not also need public IPs on each instance behind it; that pattern is usually left over from before the load balancer existed. Same money, actual work.
- IPv6 for anything that talks only to modern clients, and private subnets plus one NAT gateway for egress-only fleets. Do the math first though: a NAT gateway runs about $32 a month standing, so it beats the address charge at roughly nine addresses, not at two.
The pattern rhymes with the unattached volume audit: the cloud's smallest line items are the ones nobody owns. This one at least comes with its own free report. Ten minutes. Go sort the column.