The AWS cleanup checklist I wish someone had given me when I was starting out with cloud.

I talk to computer science students regularly. There’s one fear that comes up more than almost anything else: “I am worried about spinning up stuff in the cloud and charges getting out of control.”

I used to feel this. Some time ago, I set up a relational database on RDS, some virtual machines as EC2 instances, an S3 bucket to upload some data. After I was done, I deleted everything on the AWS console. Deleted my database. Terminated my instances. Then I got a bill I wasn’t expecting.

Didn’t everything get deleted? Literally AWS told me “deleting” in the console. I didn’t think anything was running. What happened?

That experience stuck with me. As I work with students building on AWS, I see the exact same thing happen to them. Last semester alone, I heard some version of this story from students.

I’m gonna walk us through what’s actually going on and give you a checklist to eliminate this fear when building out on AWS.

What’s Actually Charging You After You “Delete Everything”

Here’s an example. You delete your RDS instance at the end of a semester project. Makes sense. Project’s done. But during deletion, AWS offers to create a final snapshot of your database. It’s a checkbox. You probably don’t even register that it’s there. You click through, the database goes away, and that snapshot sits in your account quietly costing you money.

Same thing with EC2. You terminate your instances and depending on how your volumes were configured, the EBS volumes that were attached don’t always get deleted with the instance. They’re still there, billing. Invisible unless you know where to look.

And then there’s this one that gets people: Elastic IPs. When you terminate an instance, the Elastic IP doesn’t get deleted with it. It just sits there, unattached, costing you a few dollars per month. Not huge, but it adds up when you forget about it. That one catches people off guard.

None of this is hidden. It’s all documented. But nobody tells you to look for it when you’re learning, and the console doesn’t wave a red flag that says “hey, you still have billable resources over here.”

Why This Frustrates Me

Here’s the part that actually gets to me as a Developer Advocate. When a student gets a surprise bill, they don’t usually think “I missed a step in my cleanup.” They think “AWS secretly charges you even after you delete stuff.” They tell their classmates and that becomes the narrative. I’ve heard it in person, on discord, etc. “Be careful with AWS, they’ll charge you for nothing.” It’s not cool because it can scare people away from learning skills that would genuinely help their careers.

AWS doesn’t charge you in mysterious ways. It charges you in specific, predictable ways that nobody taught you to look for. That’s a knowledge gap. The purpose of this post is to shed some light on this.

There’s a Better Way Now

Here’s something I wish existed when I was starting out. AWS now has a free account plan where you get $100 in credits just for signing up, and you can earn up to $200 total by completing activities like launching an EC2 instance or creating a budget. The key part: you literally cannot be billed. There’s no scenario where you wake up to a surprise charge. When your credits run out or six months pass, whichever comes first, your account just closes. That’s it. No bill.

If you want more flexibility — say you’re working on a longer project or you don’t want to risk your account closing mid-semester — you can choose the paid account plan instead. You still get the same $200 in credits, but your account stays open after they’re used up. The tradeoff is that you can be billed beyond your credits, which is exactly why the billing alarm later in this post matters. Set that up on day one and you’re covered.

I’ve been guiding more students toward these options lately and it keeps coming up enough that I’ll probably write a dedicated post about it soon.

The Cleanup Checklist

This is what I share with every student I work with now. I tell them to bookmark it and come back to it at the end of every project.

Start With Your Bill, Not Your Console

Before you click around trying to find leftover resources, go to AWS Billing Dashboard from the AWS console. Look at the current month’s charges broken down by service. This tells you exactly which services are costing money right now.

If you see a charge for RDS, go check RDS. If you see a charge for EC2, go check EC2. Let this be your map.

Use Resource Explorer

Looking for an exhaustive list of everything going on in your AWS account across all regions?

Instead of clicking through every service console in every region hoping you didn’t forget something, Resource Explorer gives you a single search interface across your entire account. All services. All regions. One view.

That last part matters more than you’d think. I’ve seen students create resources in us-east-1 for a tutorial and us-west-2 for a class project, then only check one region during cleanup and assume everything’s gone. Resource Explorer solves that completely. Resource Explorer in the console. If your account is truly clean, you’ll see very little. If it’s not, you’ll see exactly what’s still hanging around.

Check the Usual Suspects

Even with Resource Explorer, it helps to know the specific things that catch people. These are the ones I see come up a lot:

Snapshots (EBS and RDS) Check EC2 -> Snapshots and RDS -> Snapshots. Common silent cost I see among students. They get created automatically, often during deletion workflows, and nobody thinks to look for them. These snapshot costs can add up - something like 100 GB could be $5/month.

Unattached EBS Volumes Go to EC2 -> Volumes and filter by state: “available.” If a volume shows “available,” it’s not attached to anything. It’s just sitting there being billed.

Elastic IPs Check EC2 -> Elastic IPs. If any are listed and not associated with a running instance, release them.

NAT Gateways If you followed a VPC tutorial with public and private subnets, check VPC -> NAT Gateways. These run about $32/month whether you’re pushing traffic through them or not. If you don’t need it, delete it.

Set Up a Billing Alarm

This takes two minutes and it’s the single most important thing you can do on a new AWS account.

1. Go to Billing -> Budgets
2. Create a low budget, say $5 or $10
3. Set an alert at 80% of that threshold
4. Add your email

What I Tell Students Who Are Afraid to Start

Every time I meet a student who communicates to me in a way that signals “I’m scared of cloud billing getting out of control,” I tell them the same thing. That fear is valid. Every dollar matters when you’re a student. Once you understand where surprise charges actually come from, which is a pretty short list, the fear goes away.

The students who get burned are the ones who don’t know about snapshots, orphaned volumes, and unattached Elastic IPs. Now you do.

I tell students these three things:

• If you want zero billing risk, choose the free account plan when you sign up. You get up to $200 in credits and you cannot be charged. The tradeoff is that your account closes when credits run out or after six months. If you’d rather keep your account open longer, go with the paid plan — you get the same credits, just set up a billing alarm so nothing sneaks past you.
• Set up a billing alarm no matter which plan you pick
• Bookmark this checklist and come back to it at the end of every project

Start the account. Build the project. Learn the skills. And when the semester ends, come back to this checklist.

Quick Reference

Or to avoid any billing entirely, choose the free account plan when signing up. You still get credits, but you are never billed. Note: when you run out of credits (or 6 months pass, whichever comes first), AWS closes your account.

Click here for more info on AWS Free Tier.

The best time to set up a billing alert was when you created your account. The second best time is right now.