Hacker News new | past | comments | ask | show | jobs | submit login

This post finally got my ass in gear to cancel an account that I thought I had closed but was still charging me a few dollars a month.

I spinned up an AWS instance to practice, and once I was done I thought I closed everything down.

Turns out I had just stopped my micro instances, and I didn't terminate them. I also hadn't released the my IP address. There was also a snapshot of the tiny db I had created still floating around. The documentation was a little confusing, so after I went through it I spent half an hour chatting with a support rep to make sure everything was completely good. After next month my last bill should go through and I should be free and clear. Unfortunately I have to wait for next months bill to go through as I can't just pay it all now.

This was mostly my fault for letting it go on for so long, but I hate how if you don't do some very specific steps you can still be charged. And I think if an account is closed, it should absolutely terminate all services that are still running on that account, and then send you the final bill.




If it happens again, you can try out the aws-nuke tool to help you destroy resources. (Because of course an open source tool is needed for this )


I've made the same mistake! Also check for EBS images which can be sneaky.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: