Elastic Compute cloud billing

Question

I was noticed via my emails about an exceeding budget and I instantly went to view the service i was being charged for immediately I stopped my instance from running when I received  an exceeding budget, unfortunately I got another email and I was charged again but my instance isn’t running no more. Please how do I go about this and what do I do to avoid incurring cost.

Answer

You shouldn't be charged for a stopped instance.

Try using [AWS Cost Explorer](https://aws.amazon.com/aws-cost-management/aws-cost-explorer/) to see the details of your charges. Cost Explorer is free when you use the console with out of the box settings the only billable features are hourly & resource granularity & direct API requests.

Initially Cost Explorer will group the costs by Service, making it easy to see which service is responsible for the cost. You can also switch the Group By dimension to Usage Type, which will show you the next level of detail: the specific units by which your charges are being metered.

Some examples of items that you might find:

EBS:SnapshotUsage - EBS Snapshots that need to be deleted
ElasticIP:IdleAddress - unused elastic IPs

Answer

Apart from above, could be related to attached EBS volumes may generate costs for you: https://repost.aws/knowledge-center/ebs-volume-charges

Answer

Check [this guide](https://repost.aws/knowledge-center/ec2-billing-terminated) for more info about being charged with no instances running.

If you have provisioned other resources some could be causing this extra billing. For a detailed info of your current cost use the [AWS Cost Explorer](https://aws.amazon.com/es/aws-cost-management/aws-cost-explorer/).

Elastic Compute cloud billing

Relevanter Inhalt