Help! Accidental AWS Charges and What to Do Next

0
2
Asked By TechWanderer93 On

I'm a beginner with AWS, diving into some courses on YouTube, and I've accidentally racked up over $300 in charges. Despite ensuring that all my instances were closed, it turns out the charges came from the EKS clusters I had created. It's a lot of money for me to handle right now, and I've noticed that my projected costs for February are already over $400, despite having deleted everything related to EKS. I've opened a support ticket with AWS but haven't heard anything back yet. What options do I have to resolve this? I'd really appreciate any guidance!

3 Answers

Answered By CloudyDayDreamer On

That’s rough! Sorry to hear about the unexpected costs. Since you've opened a support case, make sure to give it some time for AWS to get back to you. Meanwhile, I recommend checking out this article on tracking and avoiding unexpected charges: http://go.aws/resources-unexpected-charges. It has some good tips! And remember, projections can change, so keep an eye on them as the month progresses.

Answered By CuriousTechie On

Don’t stress too much! Just keep monitoring your costs over the next week. Projections are not always accurate, and I’ve found that actual costs can adjust as the month goes on. If it doesn’t drop after a week, definitely follow up with support again.

Answered By LoneCoder42 On

I totally get where you’re coming from. I've been in that exact situation before! When I reached out to AWS about similar charges after I accidentally left some services running, they were understanding and waived the charges after I explained everything. Make sure you explain your situation clearly in the support ticket, and they might be willing to help you out.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.