Skip to content

I am being charged for $0.005 per In-use public IPv4 address per hour even after deleting all my resources

0

I have deleted my vpc Enter image description here I have no elastic ips Enter image description here and no ec2 instances Enter image description here this is my expanded billing and the Enter image description here I am still being charged for this kindly help me I have deleted all my resources and had released all elastic ips before deleting them but now I am being charged unnecessarily

asked 10 months ago172 views
2 Answers
0

I understand your frustration with being charged for public IPv4 addresses even after deleting your visible resources. This situation can occur due to a few reasons:

  1. Hidden or service-managed network interfaces: Some AWS services create network interfaces that are not immediately visible in the EC2 console. These can retain public IP addresses.

  2. Resources in other regions: Make sure to check all AWS regions for any remaining resources that might be using public IPs.

  3. Delayed billing updates: Sometimes, there can be a delay between resource deletion and the cessation of charges in the billing system.

To resolve this issue, I recommend the following steps:

  1. Use the EC2 Global View to check for network interfaces across all regions.

  2. Review your Usage Report or Cost and Usage Report (CUR) for detailed information. Look for entries related to "AssociateAddressVPC" or "DescribeNetworkInterfaces" operations.

  3. Utilize the Public IP Insights feature in Amazon VPC IP Address Manager. This tool can provide a comprehensive view of your public IP usage across services.

  4. Check for any load balancers or other services that might be using public IPs.

If you're still unable to locate the source of these charges after following these steps, it would be best to contact AWS Support. They can provide a more detailed analysis of your account and help identify any hidden resources that might be causing these charges. They can also assist with any potential billing adjustments if the charges are found to be erroneous.

Remember, while you may have deleted visible resources, some AWS services can create and manage network interfaces with public IPs that are not immediately apparent in the standard console views.
Sources
Unexpected $0.13 Charge for “In-use public IPv4 address” on Free Tier EC2 Instance | AWS re:Post
Why am I seeing charges for 'Public IPv4 addresses' when I am under the AWS free tier? | AWS re:Post
Unknown Billing | AWS re:Post

answered 10 months ago
AWS
EXPERT
reviewed 10 months ago
EXPERT
reviewed 10 months ago
0

Hello.

Follow the steps in the following article to find the public IPv4 addresses in your AWS account:
https://repost.aws/ja/articles/ARz98l8QOcSUar-_IIGgxGzA/vpc-ip-address-manager-s-public-ip-insights-a-free-and-simple-feature-for-customers-to-get-insights-on-their-public-ipv4-usage

Judging from the invoice image you shared, it seems likely that you forgot to delete the Elastic Load Balancer.
When you create an Elastic Load Balancer with Internet facing, a public IPv4 address is attached.

EXPERT
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.