Unexpected VPC Costs Despite Stopped EC2 Instances

Question

Hi Suppor Team,

Although my EC2 instances are stopped, I am still incurring costs related to the VPC. However, I have never set up a VPC myself. Where are these costs coming from?
![Enter image description here](/media/postImages/original/IMfv0Ra9SPQGiAp7f9J_zjbQ)

Answer

Hello.

Please check the breakdown of costs in your VPC from Cost Explorer by following the steps in the answer at the URL below.  
https://repost.aws/questions/QUelBAhchWSm-9IcmSv3IybQ/how-to-break-down-vpc-costs#AN1WQakXDeSOG4GPT9WAPj1g

VPC costs include ElasticIP, public IPv4, NAT Gateway, etc.  
https://aws.amazon.com/vpc/pricing/?nc1=h_ls

Answer

Thank you for providing the instructions on how to break down the costs. I can now see they were incurred due to idle ipv4 addresses.
![Enter image description here](/media/postImages/original/IMwS4NQbyfQSuvDxC5NId0Fg)
I created an elastic IP for one of my EC2 instances. Looks like the free-tier usage only covers an in-use EC2 instance but not an idle one?
![Enter image description here](/media/postImages/original/IMLN1IqSO7S2SWouQuXq71xQ)

Unexpected VPC Costs Despite Stopped EC2 Instances

Relevant content