Nicole walks you through
terminating unneeded
EC2 resources


I’ve terminated all my Amazon EC2 instances, but the Billing and Cost Management console still shows that I’m being charged for EC2. Why?

Here are some reasons you might see EC2 charges on your bill after you terminated your instances:

  1. The charges you’re seeing might be for usage incurred earlier in the billing cycle. Most EC2 resources are billed as a function of the time they’re provisioned to your account, so if you ran an instance at the beginning of the month, your bill will include charges for the time that the instance was running.
  2. You terminated your instances, but you still have EC2 resources provisioned to your account. The Elastic Compute Cloud line item includes billing for resources other than instances. Commonly, EC2 instances are used in conjunction with other EC2 resources, such as Elastic IP addresses or EBS volumes. Expand the Elastic Compute Cloud line item in the Billing and Cost Management console to see the full breakdown of your EC2 usage by resource. If you have any billing line items related to resources other than EC2 instances, check the EC2 console for resources still provisioned to your account.
    Note: Stopped instances do not incur charges, but EBS volumes or Elastic IP addresses attached to those instances do.
  3. You terminated your instances in one region, but you also have instances running in another region. EC2, along with the EC2 console, is regional, meaning that it only shows one region at a time. Check the other EC2 regions to see if you have running resources in those regions, or expand the Elastic Compute Cloud line item in the Billing and Cost Management console to see which EC2 regions are generating the charges. If you no longer want or need those resources, terminate, delete, or release them in the EC2 console.
  4. New instances have launched on your account. Some services, depending on the way you configured them, can launch resources when certain conditions are met. For example, services like Auto Scaling and Elastic Beanstalk can launch instances on your behalf to meet a minimum number of instances, and Spot bids launch instances when a certain Spot bid price is met. Check that service’s documentation for more information on terminating these resources, or if you’re unsure which service or resource is launching instances on your account, contact AWS Support for help.
  5. You purchased a Reserved Instance. Reserved Instances are billed each month for each hour in a given month until the end of the Reserved Instance contract. If you’re no longer using the instance type that you purchased a Reserved Instance to cover, you might be able to modify your Reserved Instance to a size that suits your current use case, or sell your instance on the Reserved Instance Marketplace.

If none of these scenarios apply to you, or you’re not sure why you’re being billed, contact AWS Support.

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-07-21