- Newest
- Most votes
- Most comments
To my understanding the computer free tier of 750 hours per month would account for the usage of one EC2-Instance in always-on state. If you had three EC2-Instances in an always-on state then this would be over 2,000 compute hours per-month which you would pay the hours above the free tier level.
You also have EC2-Other charges which are mostly data transfer, EBS volumes and Snapshots and these are not normally free.
I recommend using the Instance scheduler, turning the instances off when not in use, or consider removing the other two EC2-Instances.
You can find out more details by going into the Billing Dashboard and selecting Bills from the panel on the left, then about halfway down you'll see the Charges By Service tab which lists all the chargeable items that you've run in the current billing period.
I guess you're going to have a non-zero amount against Elastic Compute Cloud, so you can expand that section and find out exactly what it is you're being billed for, and additionally this is sorted by region.
Does this shed more light on where the charges have come from?
Effectively RWC, now it's all more clear and that explains why my EC2-Other charges are greater than EC2-intances charges, because of volume. I'll be more careful with this. Thank for your valuable information.
Relevant content
- asked 4 months ago
- asked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you David for your answer. Perhaps I read it, but didn't notice that the instance is in an always-on state, that makes much sense since the bill has increased with the second instance I launched, and much more with the third one. Thank you very much.