Cleaning up AWS waste is a great first step, but it also teaches you where your
cloud knowledge is thin.
When you find an unattached EBS volume, an idle NAT gateway, an unused Elastic
IP, or old snapshots, you are not just saving money. You are seeing real
infrastructure decisions that someone forgot to finish.
This post is a practical path for what to learn next.
Disclosure: Some links may be affiliate links. I only include tools or resources
that fit the topic.
Start With the Bill
Most AWS learning paths start with service names:
- EC2
- S3
- IAM
- VPC
- Lambda
- DynamoDB
That is useful, but the bill shows you what matters in production.
If a small account has a surprising monthly cost, the cause is often something
concrete:
- a NAT gateway left running
- an Elastic IP that is no longer attached
- old EBS volumes
- old snapshots
- oversized storage
- logs or backups retained forever
Those are better learning prompts than abstract tutorials because they connect
AWS services to operational behavior.
Resource 1: A Cost Cleanup Scanner
Before studying more AWS, scan your own account in read-only mode and make a
short list of things to understand.
I built AWS Waste Finder for this exact loop:
python3 aws_waste_finder.py --profile default --all-regions --format html --output report.html
It checks common AWS waste signals and generates Markdown, JSON, or HTML
reports.
Paid starter bundle:
https://basilian1.gumroad.com/l/aws-waste-finder?utm_source=devto&utm_medium=post&utm_campaign=product2_learning_resources
Use the report as a study guide. For each finding, ask:
- Why does this resource exist?
- What other resources depend on it?
- What would break if it disappeared?
- How would I verify that safely?
That is how AWS stops being a list of icons and starts becoming a system.
Resource 2: The Cloud Resume Challenge
If you want a structured AWS project after cleanup work, the Cloud Resume
Challenge is a good next step.
It usually touches several real-world pieces:
- static hosting
- DNS
- HTTPS
- serverless functions
- databases
- CI/CD
- IAM permissions
The paid guidebook is here:
https://forrestbrazeal.gumroad.com/l/cloud-resume-challenge-book?a=93367907
Why I like this kind of project: it forces you to build something small but
complete. That is much better than clicking around one AWS service at a time.
Resource 3: IAM and Least Privilege
After you scan for waste, learn IAM next.
Cost cleanup is full of permission questions:
- Can this scanner run read-only?
- Which API calls does it need?
- Who is allowed to delete resources?
- Should cleanup be manual, automated, or approval-based?
For your first pass, learn:
- users vs roles
- managed policies vs inline policies
- read-only policies
sts get-caller-identity- CloudTrail basics
Do not start by giving every tool admin access. A boring read-only role is a
better habit.
Resource 4: VPC Basics
NAT gateway findings are a signal that you should understand VPC networking.
Learn:
- public vs private subnets
- route tables
- internet gateways
- NAT gateways
- security groups
- network ACLs
Before deleting a NAT gateway, always check route table usage and traffic. A
quiet NAT gateway might still support a private workload that only runs once a
day.
Resource 5: Terraform or OpenTofu
Once you understand the resources, learn infrastructure as code.
The useful idea is not just "write Terraform." The useful idea is that your
cloud should have a reviewable source of truth.
Start with:
- variables
- outputs
- state
- modules
- importing existing resources
-
planbeforeapply
This also makes cost cleanup safer because you can see whether a resource was
created intentionally or by accident.
Resource 6: DynamoDB or One Managed Database
Do not try to learn every AWS database at once.
Pick one managed database and go deeper.
DynamoDB is a good choice for AWS developers because it teaches:
- access patterns
- partition keys
- sort keys
- indexes
- capacity modes
- backups
- operational limits
Even if you do not use DynamoDB every day, learning one AWS database deeply
will make the others easier to reason about.
A Simple 7-Day Path
If you want a practical sequence:
- Run a read-only cost scan.
- Pick one finding and understand every dependency around it.
- Learn the IAM permissions needed to inspect it.
- Learn the VPC or storage concept behind it.
- Build one small AWS project.
- Put that project in GitHub.
- Write down what you would monitor and what could cost money.
That path is small enough to finish, but real enough to matter.
Final Thought
AWS cost cleanup is not separate from AWS learning.
It is one of the fastest ways to learn what real infrastructure is doing,
because every wasted dollar points back to a resource, a dependency, and a
decision.
Start with the bill, then learn the system behind it.
Top comments (0)