Amazon AWS now char...
 
Notifications
Clear all

Amazon AWS now charging for each IPv4 Address

3 Posts
2 Users
0 Reactions
366 Views
Brandon Lee
(@brandon-lee)
Posts: 554
Member Admin
Topic starter
 

Amazon Web Services (AWS) has announced a new pricing structure for the use of public IPv4 addresses across its services, set to take effect on February 1, 2024. The rate will be $0.005 per hour for each public IPv4 address, regardless of whether it is actively attached to a service. This update extends an existing pricing policy to include charges for public IPv4 addresses allocated within an account but not linked to an EC2 instance.

Public IPv4 Address Charge Overview The decision to introduce this charge comes in response to the growing scarcity and rising acquisition costs of public IPv4 addresses, which have surged by over 300% in the last five years. AWS aims to reflect its operational costs through this pricing adjustment while encouraging users to adopt IPv6 addresses as a measure for modernization and resource conservation.

This pricing change affects all AWS services capable of allocating and attaching public IPv4 addresses, such as Amazon EC2, Amazon RDS, Amazon EKS, among others, across all AWS regions including commercial, AWS China, and GovCloud.

Pricing Details and AWS Free Tier Inclusion Under the new pricing scheme, in-use public IPv4 addresses, including those provided by Amazon and Elastic IPs assigned to resources, will incur a charge of $0.005 per hour. The rate for additional Elastic IPs on a running EC2 instance remains unchanged at $0.005 per hour, as does the charge for idle Elastic IPs. To mitigate the impact of this change, the AWS Free Tier for EC2 will cover 750 hours of public IPv4 address usage per month for the first year, starting from February 1, 2024. AWS customers using their own IPs through Amazon BYOIP will not face charges for these addresses.

AWS has updated its Cost and Usage Reports to include public IPv4 address usage and plans to integrate this data into AWS Cost Explorer for better visibility and management once the price change is implemented.

Encouragement towards IPv6 Adoption AWS is advocating for a quicker transition to IPv6, highlighting benefits such as avoiding the need for a public IPv4 address for each instance through alternative solutions like Elastic Load Balancers and NAT Gateways. Resources and guides are available to facilitate the adoption of IPv6 across various AWS services, including EC2, Amazon VPC, Amazon EKS, Elastic Load Balancing, and Amazon RDS.

Public IP Insights Launch To assist customers in monitoring and managing their public IPv4 address usage more effectively, AWS has introduced Public IP Insights as a new feature of Amazon VPC IP Address Manager. This tool, offered at no additional cost, aims to enhance the efficient use of public IPv4 addresses and provide insights into security postures. It features detailed breakdowns of public IP types and EIP usage with various filtering options.

image

Efficient Use of IPv4 Addresses AWS encourages customers to utilize the new Public IP Insights tool and follow its guidance to minimize the impact of the new charges. Additionally, AWS Direct Connect is suggested as a method to establish a dedicated network connection to AWS, potentially reducing the reliance on public IPv4 addresses for certain use cases.

https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/

 
Posted : 03/02/2024 5:55 pm
Brandon Lee
(@brandon-lee)
Posts: 554
Member Admin
Topic starter
 

Curious if this will affect the spend on major deployments out there? Looks like analysts are thinking another $1B in revenue for Amazon for charging for their IPv4 addresses...ouch. @t3hbeowulf curious if you guys have tons of IPs in AWS that will be charged or just a few?

 
Posted : 03/02/2024 10:09 pm
(@t3hbeowulf)
Posts: 27
Eminent Member
 

Coincidentally, this came up in a sort of "all hands DevOps" meeting we do every week and the general consensus was "negligible impact". I couldn't begin to know what every public IP was for all AWS services and endpoints we have but I do know what the general infrastructure aims to minimize public IPs in favor of VPCs and direct connect endpoints. 

I don't think we use anywhere near 1,000 public addresses but setting that as a rough back-of-the-napkin calculation; 1,000 public IPs would amount to approximately $3,650/mo or so? Considering the current company-wide EKS spend, that is drop in the bucket.

 
Posted : 03/02/2024 10:57 pm