The $30 AWS Bill I Didn’t Expect (And What It Taught Me)

Source: Dev.to

Background

One mistake many beginners make with AWS is assuming nothing will happen if they stop using it. In 2023 I opened an AWS account and deployed a small React app just to explore the console. After that, I left the account untouched for months.

What Happened

When I returned in 2024 to take cloud learning seriously, my Free Tier had already expired. I logged in and saw a $30 bill. The amount wasn’t huge, but the lesson learned was important.

I didn’t intentionally leave anything running; I simply didn’t understand which AWS services continue to cost money when you don’t turn them off. After reaching out to AWS support and explaining my situation, the issue was resolved. That experience changed how I approach cloud learning.

Lesson Learned

Cloud knowledge is not only about deploying services. It’s also about knowing what to stop, delete, and shut down. This lesson came from my own early mistakes while learning AWS, and it’s one that many beginners don’t realize until they see a bill.

Resources

• AWS Free Tier Explained: Services That Are Not Free
• AWS Services You Should Delete After Every Lab
• The Hidden Challenges of Building with AWS (article)

Habit to Save Money

After every lab or test, spend five minutes checking the following services before logging out:

• EC2
• RDS
• Lambda
• S3

That small habit can prevent surprise charges.

Key Takeaway

In AWS, learning what to turn off is just as important as learning what to deploy. Always review and clean up your resources after every experiment.

Discussion

Question: Which AWS service do you always double‑check before logging out, or which one worries you the most about unexpected costs?

Drop your answer in the comments.