Why am I being billed for Elastic IP addresses when all my Amazon EC2 instances are terminated?

2 minute read

I terminated all my Amazon Elastic Compute Cloud (Amazon EC2) instances, but I'm still billed for Elastic IP addresses. The Amazon EC2 On-Demand pricing page says that Elastic IP addresses are free. I want to know why I was billed.


An Elastic IP address doesn't incur charges as long as all the following conditions are true:

  • The Elastic IP address is associated with an EC2 instance.
  • The instance associated with the Elastic IP address is running.
  • The instance has only one Elastic IP address attached to it.
  • The Elastic IP address is associated with an attached network interface. For more information, see Network interface basics.

Note: If the address is from a BYOIP address pool, then you're never charged for that address.

You're charged by the hour for each Elastic IP address that doesn't meet these conditions. For pricing information, see Elastic IP addresses on the Amazon EC2 pricing page.

To see the Elastic IP addresses that are provisioned to your account, open the Amazon EC2 console, and then choose Elastic IPs in the navigation pane.

If you don't need an Elastic IP address, you can stop the charges by releasing the IP address.

Note: When you release the IP address, it might be provisioned automatically by another AWS account. You might be able to recover that same Elastic IP address again later, but only if no one else is using it.

If you receive an error when you try to release an Elastic IP address from your Amazon EC2 instance, see How do I resolve the error "The address with allocation id cannot be released because it is locked to your account" when trying to release an Elastic IP address from my Amazon EC2 instance?

Related information

Elastic IP addresses

AWS OFFICIALUpdated 2 years ago

Does this mean that if I create an Elastic IP address, for the purpose of keeping a the same IP address of a REST API service running in my single EC2 instance (free tier), I have to keep that EC2 instance running, in order not to incur charges for that Elastic IP address?

replied a year ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

profile pictureAWS
replied a year ago

Hi. I think you have to review the scope of this answer, based on https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/

replied 9 months ago