AWS Public IPv4 Charges: What Each Address Costs and How to Cut It

Published by Rushikesh Dhule, LessBill · November 15, 2026 · Updated November 16, 2026
Here is a line item that surprises a lot of teams: public IPv4 addresses. Since February 2024, AWS bills every public IPv4 address at $0.005 per hour, whether it is attached to a running server or sitting idle. That sounds tiny. It works out to about $3.65 a month, or roughly $43 a year per address.
Now count them. Every NAT gateway has one. Every internet-facing load balancer has one per Availability Zone. Every EC2 instance launched in a public subnet with "auto-assign public IP" turned on has one. A startup with a few environments can easily hold 100 public IPs without anyone deciding to, and that is about $4,400 a year for addresses alone.
It is a good example of a wider pattern. Several 2026 cost analyses point out that bills are creeping up on flat traffic not because list prices rose, but because of small per-hour charges like IPv4, NAT gateways and cross-zone traffic that nobody owns. Here is how to find and cut the IPv4 part.
1. Find out how many public IPs you actually have
You cannot fix what you cannot see. On the bill, the charge shows up under Amazon VPC as "PublicIPv4:InUseAddress" and "PublicIPv4:IdleAddress". Most teams are surprised by the count.
Fix: Turn on Public IP Insights in Amazon VPC IP Address Manager (IPAM). It is free on the IPAM free tier and lists every public IPv4 address by Region, type and owner: EC2, load balancers, NAT gateways and Elastic IPs. Export the list and sort it by service.
2. Release idle Elastic IPs
An Elastic IP that is allocated but not attached to anything is pure waste. These pile up after migrations, deleted test servers and old failover setups.
Fix: In the EC2 console, filter Elastic IPs where "Associated instance" is empty and release them. Before you do, check that nothing (DNS records, partner allowlists) depends on that exact address. Then add a weekly check or a simple AWS Config rule so new idle IPs get flagged.
3. Stop giving every instance a public IP
Many VPCs were created with "auto-assign public IPv4" switched on for public subnets, so every instance gets an address by default, even backend workers that never need inbound internet traffic.
- Turn off auto-assign public IPv4 on subnets and launch templates.
- Move servers that only need outbound access into private subnets.
- Put anything that serves users behind a load balancer instead of exposing it directly.
Fix: Audit launch templates and Auto Scaling groups first. One template with public IPs turned on can create dozens of billable addresses every time it scales out.
4. Replace bastion hosts with keyless, IP-less access
A bastion host or "jump box" exists only to let engineers SSH in, and it usually carries a public IP that runs 24/7.
Fix: Use EC2 Instance Connect Endpoint or Systems Manager Session Manager. Both let engineers reach private instances without any public IP, and they also remove open SSH ports, which your security team will like.
5. Consolidate load balancers and NAT gateways
Each internet-facing Application Load Balancer uses a public IP in every zone it covers. Ten small ALBs across three zones means 30 addresses, about $1,300 a year, before any traffic or hourly load balancer charges.
Fix: Merge small services behind one ALB using host-based or path-based routing rules. For dev and test environments, one NAT gateway per VPC is usually enough instead of one per zone. Keep the extra redundancy only where uptime truly matters.
6. Start using IPv6 where it already works
IPv6 addresses on AWS carry no hourly charge. Support has improved a lot: Application Load Balancers can serve internet clients over IPv6 without public IPv4 addresses, Amazon ECS supports IPv6-only tasks, and an egress-only internet gateway gives private IPv6 instances outbound access with no NAT gateway at all.
Fix: Do not try to go IPv6-only everywhere at once. Start with new internal services and dev environments, enable dual-stack on your VPCs, and test which third-party APIs and tools still need IPv4. Teams that have moved Kubernetes clusters to IPv6-first report real savings, but also a list of tools that still assume IPv4, so plan for some gaps.
Worked example: what a small account pays
Take a typical small production account: 6 EC2 instances with public IPs, 2 load balancers spread over 3 zones (6 addresses), 3 NAT gateways (3 addresses) and 2 Elastic IPs nobody is using. That is 17 public IPv4 addresses.
AWS charges $0.005 per address per hour, in use or idle, so: 17 x $0.005 x 730 hours = $62.05 a month, or about $745 a year.
Now apply three fixes: move the 6 instances into private subnets and reach them with Session Manager (minus 6), release the 2 idle Elastic IPs (minus 2), and merge the two load balancers into one (minus 3). You are left with 6 addresses: 6 x $0.005 x 730 = $21.90 a month. That is a saving of about $40 a month, or $482 a year, for an afternoon of work.
To list Elastic IPs that are not attached to anything:
aws ec2 describe-addresses --query "Addresses[?AssociationId==null].[PublicIp,AllocationId]" --output tableWhen this does not apply: anything that must accept traffic directly from the internet over IPv4 (a public load balancer, a NAT gateway) still needs its addresses. The goal is to remove the ones doing no work, not all of them.
Related guides: 7 Zombie Cloud Resources Quietly Draining Your Bill (and How to Kill Them) and Cloud Data Transfer Costs: What You Pay For and How to Cut It.
The bottom line
Public IPv4 is a small charge that scales with sprawl, not with traffic. The quickest wins are releasing idle Elastic IPs, turning off auto-assign public IPs and removing bastion hosts. Most teams can do all three in an afternoon. Load balancer consolidation and IPv6 take longer but keep the number from growing back. And the same habit applies on Azure and Google Cloud, which also bill for public IP addresses.
How LessBill can help
Line items like idle IPs, forgotten NAT gateways and duplicate load balancers are exactly the quiet waste that is hard to spot in a raw bill. LessBill.org scans your AWS, GCP and Azure accounts, flags idle and unattached resources, and shows you which fixes save the most, so you can clean up in minutes instead of digging through Cost Explorer.
Sources and further reading
- AWS News Blog: public IPv4 address charge and Public IP Insights
- Amazon VPC pricing
- AWS Systems Manager Session Manager
Also drawn on: AWS News Blog; AWS Networking & Content Delivery Blog; AWS What's New; AWS Containers Blog; Rack2Cloud; RIPE Labs.
Comments
Post a Comment