Skip to content

Hi, I keep getting billed but I don't know why exactly, need some assistance please!

0

Hi, I'm new on using AWS service, I used a EC2 instance for a pet project, trying to learn about networking, and cyber security and I got billed for about $25 ish for July.

I think this was because I didn't turn the instance off after using it, and I guess that kind of used data excelling the free tier usage, but I was kind of confused when I was getting billed at August, after I turned it off. (Turned the instance off at July)

So I took a look at the bill, and I am assuming

  1. For the EBS storing (like google drive charges stuff over 10gigs) storage of the instance data,
  2. and the VPC stuff is from the additional elastic IP I got allocated from Amazon for usage? (I had to use 2 IPs for this project)

I'm terribly sorry if this question is like the trillionth time asked question, but I am not familiar with AWS nor this re:Post community and wasn't sure where to ask. I just wanted to be sure, I will pay for what I've done, but do not want to get billed for stuff I didn't intend for D:

uploading some images to be more specific about my circumstance!

graph view of what is being billed currently details on the bill VPC screen When VPC deletion is selected

asked a year ago198 views

1 Answer
0

I understand your confusion about being billed after turning off your EC2 instance. This is a common issue for new AWS users, and I can help clarify what's happening.

When you "stop" an EC2 instance (rather than terminate it), AWS still maintains your instance configuration and any attached EBS volumes. You're not charged for the stopped instance compute time, but you are still charged for:

  1. EBS Storage: Yes, you're correct that you're being charged for the storage of your instance's EBS volumes. This is similar to how cloud storage services charge for data storage. Even when your instance is stopped, the EBS volumes are still maintained and you're billed for them.

  2. Elastic IP Addresses: Your assumption is also correct here. AWS charges for Elastic IP addresses that are allocated but not attached to running instances. Since you mentioned having two IPs for your project, if these are Elastic IPs that aren't currently attached to running instances, you'll be charged for them.

  3. VPC Components: Some VPC components like NAT Gateways are not included in the Free Tier and can lead to charges. Based on your screenshots, it appears you have some VPC resources that are generating charges.

To stop these ongoing charges, you would need to:

  1. Terminate (not just stop) any EC2 instances you're not using
  2. Delete any unneeded EBS volumes
  3. Release any Elastic IP addresses you're not using
  4. Check for and delete any NAT Gateways or other VPC components that might be incurring charges

For future reference, setting up AWS Budgets or Free Tier usage alerts can help you monitor your usage and avoid unexpected charges. Also, remember that the Free Tier has specific limits, and exceeding these will result in charges.
Sources
Getting billed for free tier ? | AWS re:Post
Why am I getting charged although I deleted my instances and volumes a few weeks ago? | AWS re:Post
Why have I been billed without running any instances? | AWS re:Post

answered a year ago

AWS
EXPERT

reviewed a year 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.