# AWS public IPv4 address pricing explained

AWS pricing explained · Updated 17 November 2026

**Short answer:** AWS charges $0.005 per hour for every public IPv4 address, in use or idle, in us-east-1 at the time of writing: about $3.65 a month per address. That covers Elastic IPs, public IPs auto-assigned to EC2 instances and ENIs, and the public addresses behind NAT gateways, internet-facing load balancers and publicly accessible databases.

## Pricing dimensions

| Address state | Unit | us-east-1 price |
|---|---|---|
| In use (attached to a running resource) | hour | $0.005 |
| Idle (Elastic IP not associated, or on a stopped instance) | hour | $0.005 |
| Bring-your-own (BYOIP) addresses | Not charged | |
| IPv6 addresses | Not charged | |

From the AWS Price List API at the time of writing. The charge appears under Amazon VPC, not EC2, even when the address is on an instance.

## Worked examples

**1. A fleet with public IPs.** 20 instances with auto-assigned public addresses: 20 × 730 × $0.005 = **$73.00** a month, often for instances that never accept inbound internet traffic.

**2. A standard three-AZ VPC.** An internet-facing ALB with a node in each of three AZs and three NAT gateways: six addresses, 6 × 730 × $0.005 = **$21.90** a month.

**3. At organisation scale.** 200 addresses across accounts cost 200 × 730 × $0.005 × 12 = **$8,760.00** a year.

## What counts as a public IPv4 address

- Elastic IP addresses, associated or not.
- Public IPs auto-assigned at launch, including on ECS tasks in public subnets and on EKS nodes.
- NAT gateway Elastic IPs.
- Load balancer nodes for internet-facing ALBs and NLBs.
- RDS and other managed resources set to be publicly accessible.

## Reading the bill

Cost Explorer shows the charge under Virtual Private Cloud with usage types `USE1-PublicIPv4:InUseAddress` and `USE1-PublicIPv4:IdleAddress`. VPC IP Address Manager (IPAM) has a free Public IP Insights view that lists every public IPv4 address in a Region and what it is attached to. From the CLI:

```
aws ec2 describe-addresses --query 'Addresses[?AssociationId==null].PublicIp'
aws ec2 describe-network-interfaces \
  --query 'NetworkInterfaces[?Association.PublicIp].{eni:NetworkInterfaceId,ip:Association.PublicIp,type:InterfaceType}' --output table
```

The first command lists unassociated Elastic IPs, which are pure waste; the second shows every ENI with a public address and its type (instance, NAT gateway, load balancer).

## Cutting the number of addresses

Most addresses can go without changing how anything works. Instances that only make outbound calls can sit in private subnets behind a shared NAT gateway or use IPv6 egress through an egress-only internet gateway. Administrative access works through Systems Manager Session Manager or EC2 Instance Connect Endpoint instead of public SSH. ECS tasks and EKS nodes rarely need their own public address once image pulls go through VPC endpoints. Keep public addresses for load balancers, NAT gateways and the few hosts that must accept inbound traffic directly.

## Things that are easy to miss

- **Subnet setting "auto-assign public IPv4"** left on in default VPCs, so every instance gets an address.
- **Stopped instances holding Elastic IPs**, billed as idle.
- **Free-tier allowances** for public IPv4 on EC2 apply only to eligible new accounts and only for a limited period.
- **Dual-stack does not remove the charge**: an instance keeps paying while it still has a public IPv4 address.

Cutting it: [the public IPv4 charge on your bill](https://cloudconsole.dev/aws-pricing/public-ipv4-pricing).

## Questions

### How much does a public IP cost on AWS?

$0.005 per hour per public IPv4 address, about $3.65 a month, in us-east-1 at the time of writing.

### Do I pay for an Elastic IP that is in use?

Yes. Since February 2024 in-use and idle public IPv4 addresses are both charged at the same hourly rate.

### Are IPv6 addresses charged?

No. There is no charge for IPv6 addresses, which is one reason to move internal and outbound traffic to IPv6 where you can.

## When this happens away from your desk

Idle Elastic IPs are a small but steady leak. CloudConsole is being built to show resources and costs on a phone, which makes a quick audit easier.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Amazon VPC pricing](https://aws.amazon.com/vpc/pricing/)
- [Elastic IP addresses](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html)

## Related

- [NAT gateway pricing explained](https://cloudconsole.dev/aws-pricing/nat-gateway-pricing)
- [ALB and NLB pricing explained](https://cloudconsole.dev/aws-pricing/alb-pricing)
- [EC2 pricing explained](https://cloudconsole.dev/aws-pricing/ec2-pricing)
- [VPC endpoint pricing explained](https://cloudconsole.dev/aws-pricing/vpc-endpoint-pricing)
- [How to find an EC2 instance by IP address](https://cloudconsole.dev/how-to/find-ec2-instance-by-ip)
- [AWS Amplify pricing explained](https://cloudconsole.dev/aws-pricing/amplify-pricing)

---

Source: https://cloudconsole.dev/aws-pricing/public-ipv4-pricing

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
