- Newest
- Most votes
- Most comments
I understand your confusion about being billed after turning off your EC2 instance. This is a common issue for new AWS users, and I can help clarify what's happening.
When you "stop" an EC2 instance (rather than terminate it), AWS still maintains your instance configuration and any attached EBS volumes. You're not charged for the stopped instance compute time, but you are still charged for:
-
EBS Storage: Yes, you're correct that you're being charged for the storage of your instance's EBS volumes. This is similar to how cloud storage services charge for data storage. Even when your instance is stopped, the EBS volumes are still maintained and you're billed for them.
-
Elastic IP Addresses: Your assumption is also correct here. AWS charges for Elastic IP addresses that are allocated but not attached to running instances. Since you mentioned having two IPs for your project, if these are Elastic IPs that aren't currently attached to running instances, you'll be charged for them.
-
VPC Components: Some VPC components like NAT Gateways are not included in the Free Tier and can lead to charges. Based on your screenshots, it appears you have some VPC resources that are generating charges.
To stop these ongoing charges, you would need to:
- Terminate (not just stop) any EC2 instances you're not using
- Delete any unneeded EBS volumes
- Release any Elastic IP addresses you're not using
- Check for and delete any NAT Gateways or other VPC components that might be incurring charges
For future reference, setting up AWS Budgets or Free Tier usage alerts can help you monitor your usage and avoid unexpected charges. Also, remember that the Free Tier has specific limits, and exceeding these will result in charges.
Sources
Getting billed for free tier ? | AWS re:Post
Why am I getting charged although I deleted my instances and volumes a few weeks ago? | AWS re:Post
Why have I been billed without running any instances? | AWS re:Post
Relevant content
- AWS OFFICIALUpdated 3 years ago
