- Newest
- Most votes
- Most comments
Hey Charles,
It sounds like there might be an Elastic IP still hanging around. AWS charges for those if they’re not in use, even if everything else is shut down.
Try checking the Elastic IPs section under VPC - look at the Allocation ID and see if it’s attached to anything. If it’s not, you can just release it to stop the billing.
answered a year ago
Hello, Pavan. I've checked and it says "No Elastic IP addresses found in this Region"
Hello.
Please try to find the public IPv4 in your AWS account using the method described in the following blog.
You can use Public IP Insights to find out which AWS resources are using public IPv4.
https://aws.amazon.com/jp/blogs/networking-and-content-delivery/identify-and-optimize-public-ipv4-address-usage-on-aws/
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated a year ago

Guys, I think I found the problem. The bills stem from EU (Frankfurt) but my region was set to us-east-1 the whole time, hiding the EC2 database instance I had running.