Unexpected charge for VPC

To find out what is that VPC charge, you can use Cost Explorer;

1. Use filter to view only VPC charges
2. Group by API operation
3. 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...

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

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.

I have a similar problem too. Suddenly, AWS charged me for something I've never been charged for. why ??

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?

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,

Unexpected VPC charges starting in Feb 2024. Any reason.

I also have the above issue. Has anyone got a response from AWS on this?