- Newest
- Most votes
- Most comments
To find out what is that VPC charge, you can use Cost Explorer;
- Use filter to view only VPC charges
- Group by API operation
- Components of VPC charges are show in chart
I accept that AWS has started charing for VPC related items (Elastic IP associations). But there are other items incurring much higher cost for me, and I cannot find documentation on how to reduce these and how to estimate future costs.
One would think that when new (auto-applied) costs are introduced, the responsibility lies with the vendor to bring more-than-sufficient clarity on the impact and mitigation options.
How do I reduce:
- RunInstances
- DescribeNetworkInterfaces
Also seeing an unexpected charge for VPC usage. I am using 3 EIPs (across 4 instances in the VPC), but my expectation was to be charged $0.005/hr x ~695hrs (for Feb '24) x 3 EIPs = +$10.43/m for EIP usage.
But in Cost Explorer, the total charges are $24.38, broken down as:
DescribeNetworkInterfaces $10.45 AssociateAddressVPC $10.44 RunInstances $3.49
The breakdown seems to show double the expected charges for DescribeNetworkInterfaces and AssociateAddressVPC. Not sure what RunInstances refers to.
Seems like a money grab to me...
Thanks for adding to this question. It seems there are a few people who are unhappy about this.
I can also already see that the VPC charges are continuing in March 2024.
Hello.
The charges listed on your bill are monthly charges.
Although it is impossible to say exactly without comparing the details of the bill, the charges may vary depending on the amount of communication of EC2.
Also, If you are using public IPv4, billing started in February, so it is possible that the charge for public IPv4 has increased compared to last month.
https://aws.amazon.com/jp/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
https://aws.amazon.com/vpc/pricing/?nc1=h_ls
https://aws.amazon.com/ec2/pricing/on-demand/?nc1=h_ls
Please follow the steps in the document below to view your invoice.
Please check the VPC price column for January and February to see what has been added.
https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/getting-viewing-bill.html
Thanks @Kallu - here are my February 2024 VPC charges: Now I'm really confused. Four thousand hours in one month on four EC2 instances, only one of which has been changed in any way. To be clear: if I select January 2024, the VPC cost is zero.
Starting from Feb 1st you will be charged for all public IPs you use or have allocated. Here is more details https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
I have a similar problem too. Suddenly, AWS charged me for something I've never been charged for. why ??
I believe the fix is to use IPv6 for your servers and turn off your public IPv4 addresses. https://aws.amazon.com/vpc/ipv6/ (I haven't done it yet, I have been too busy) I really don't think this was very well publicised by AWS.
After my February invoice, I released one of my 3 EIPs in early March in order to reduce my VPC charges. Now that April's invoice has been generated, I see that releasing one of my EIPs has made no difference in terms of my VPC charges for March. I must not be understanding how these VPC charges are being calculated on a per EIP basis. Anyone have any insight on why my costs did not go down in March with one less EIP?
After some correspondence with AWS billing support, I now have a better understanding of how the new VPC charges were calculated. My assumption was that the new charges were only applicable to EIP usage, of which I have 2 in use. But actually, the fees are calculated based on EVERY public IP address that is being used within the VPC. In my environment, I have a total of 7 public IP addresses associated with: Elastic Load Balancers (2 public IP's), RDS instances (2 public IP's) and EC2 service (3 public IP's)
For EACH public IP address (including EIPs), the charge is $0.005/hr. If the month has an average of 720 hours, that is $3.60/month PER public IP. That equates to about $25.20/month under the new fee structure started in February 1st.
The new fee sucks! As such, I'll be looking into ways to convert to IPv6 where possible.
Hi Riku - thanks for your quick response.
Here is a bit more information:
I would really like to understand why the red box has suddenly appeared for Feb 2024. If it is a new charge for everyone with any EC2 then I expect a lot of people will be asking a similar question.
I do not recall selecting any optional VPC services. if I have accidentally selected any then I would really like to understand what I have changed.
I am happy with EC2 costs and I often create and delete new instances - but they comprise the light blue box.
Please let me know if any more info about my account will help, or if there is any other way to understand this additional charge. Thanks,
I also have the above issue. Has anyone got a response from AWS on this?
Relevant content
- asked 8 days ago
- asked 2 years ago
- asked 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
Thanks for this. In my case the graph shows zero cost to last month (Jan 2024). I have since rebuilt one of my servers selecting the default VPC and it seems to be working fine. So a solution may be to rebuild all of the other servers with the same default VPC option selected. Hopefully that will avoid further VPC charges.
What it shows for Feb VPC charges?