The digital landscape is continuously evolving, and with it, the infrastructure demands of cloud services like Amazon Web Services (AWS). A significant development has recently emerged: AWS has started charging for the use of public IPv4 addresses. This change, effective from February 1, 2024, marks a pivotal shift in AWS billing and resource management, directly impacting businesses and developers relying on AWS services.
AWS has announced a new fee structure for public IPv4 addresses. The charge is set at $0.005 per IP per hour, applicable to all public IPv4 addresses, whether they are attached to a service or lying idle. This adjustment applies across the board to various AWS services, including but not limited to Amazon Elastic Compute Cloud (EC2), Amazon Relational Database Service (RDS), and Amazon Elastic Kubernetes Service (EKS).
| Public IP Address Type | Current Price/Hour (USD) | New Price/Hour (USD) |
| In-use Public IPv4 address (including Amazon provided and Elastic) | No charge | $0.005 |
| Additional (secondary) Elastic IP Address on a running EC2 instance | $0.005 | $0.005 |
| Idle Elastic IP Address in account | $0.005 | $0.005 |
Not all use cases will incur these new charges. The AWS Free Tier for EC2, for example, will continue to offer 750 hours of public IPv4 address usage per month for the first 12 months, a policy that remains unchanged since February 1, 2024. Additionally, addresses that users own and migrate to AWS through the Amazon Bring Your Own IP (BYOIP) feature will not incur these new costs.
In response to these new charges, AWS recommends several strategies to optimize the use of public IPs:
AWS’s decision isn’t merely about cost-recovery; it’s a push towards modernizing internet infrastructure. The finite pool of IPv4 addresses is rapidly depleting, a situation exacerbated by the exponential growth of the internet. AWS encourages users to adopt IPv6, offering long-term benefits and sidestepping the IPv4 scarcity issue.
The implementation of charges for public IPv4 addresses by AWS signifies a considerable shift in the cloud computing domain. While initially surprising, this move underlines the urgent need for more sustainable and efficient use of internet resources. By adopting the strategies outlined by AWS and considering the transition to IPv6, businesses can mitigate the impact of these new charges while positioning themselves for future technological developments. This transition period offers an opportune moment for AWS users to audit their current usage, implement cost-effective measures, and embrace the next generation of internet protocol.
Alexander Timokhin
COO
A Beginner’s Guide to Subnetting IPv4 and IPv6 Addresses Subnetting is a critical
Why IPv4 Leasing Is Becoming the Smart Choice for Businesses in 2025 1. Introduction
As CEO of InterLIR, I’ve witnessed firsthand how network isolation strategies
What is an ASN? ASN stands for Autonomous System Number. It is a unique identifier
Anycast DNS: A Leader’s Guide to Protecting Your Digital Infrastructure Executive
RPKI Certification: A Leader’s Guide to Internet Routing Security Executive
Executive Summary: What You Need to Know 🎯 Strategic Importance – Internet
When AWS DynamoDB failed in October 2025, thousands of businesses discovered that
Executive Summary: What You Need to Know 🎯 IP reputation directly impacts your
Mastering Subnetting and Routing for Modern Networks Why Subnetting Matters in Today’s
