- Newest
- Most votes
- Most comments
Hello.
Am I doing this wrong?
I think your method of setting the Elasitc IP address is correct.
How to correctly associate the Elastic IP (do I associate it with the instance or with the interface)?
When assigned to an EC2 instance, ElasitcIP is assigned to the primary ENI.
And finally, if I have the instance running, and I have associated the Elastic IP with the network interface, why am I being charged?
I think the charges are being incurred because AWS has started charging for public IPv4 since February.
https://aws.amazon.com/jp/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
With the introduction of charges for public IPv4 addresses, you will now be charged just for owning an Elasitc IP address.
This means that you will be billed even if Elasitc IP is configured on EC2.
If your AWS account was created less than a year ago, you have 750 free hours per month for 12 months.
https://aws.amazon.com/about-aws/whats-new/2024/02/aws-free-tier-750-hours-free-public-ipv4-addresses/?nc1=h_ls
Here is a snapshot of one day (11/03/24) of my cost and usage graph as reference for the question in the comments. Which one should be representing the cost of the Elastic IP?
As you know, each Public IPv4 address costs $0.005 per hour, meaning one day evaluates to $0.12 - this is the VPC item in your screengrab.
EC2 Instances charges are for the EC2 instances themselves, and EC2-Other is for other EC2-related items like EBS volumes, NAT Gateways, etc.
Hey Steve, thanks, this clarifies it!
you can to avail elastic ips free of charge aws charged for elastic ips how ever you can avail dynamic ip free of charge
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 22 days ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
Hello Riku Kobayashi, and thank you for answering on my question. I still don't understand why am I being charged so much, when the IPv4 are at a price of $0,005/h, this should be like $0,12 per day per IP. Am I right?
Please check AWS Cost Explorer or your bill to see which services have increased costs, as this could be due to a public IPv4 address other than ElasitcIP or other factors. https://docs.aws.amazon.com/cost-management/latest/userguide/ce-what-is.html
Alright, I updated my question and included a snapshot of my costs and usage for the 11 of march. Can you please point me out which of the elements represents the Elastic IP service cost?
As far as I can see from the image, it looks like there is a charge for EC2 rather than an IP address charge. As @Steve_M says, the cost of the public IP address is included in the VPC price.
Thanks for the updates, Riku! I have it under control now ;-)