AWS Builder Center
I Earned the AWS Badges. Now What Do I Build?

I Earned the AWS Badges. Now What Do I Build?

How to turn AWS learning into something you can actually show ?

Series: Free-AWS-Certifications (5 articles)

  1. …
  2. 4
    I Earned the AWS Badges. Now What Do I Build? This article
You finish a course.
Another badge appears.
Then another.
Eventually you start wondering:
"I've learned all this stuff. What am I actually supposed to do with it?"
In my previous article, AWS Student Rewards: My Fastest Route to 21 Badge , I talked about using AWS Student Rewards to structure my learning and work towards the available badges.
But badges are only one part of the journey.
Learning something and being able to use it are two different things.
That's where projects come in.

Don't Start With a Huge Project

When someone says "build an AWS project," it's easy to think you need some massive architecture with ten services.
You don't.
Your first project can be:
  • A file uploader
  • A simple task tracker
  • A static portfolio
  • An image processor
  • A serverless API
The goal isn't to build the next big startup.
The goal is to take something you've learned and actually use it.
A simple rule I like:
1 problem + 2–3 AWS services + 1 weekend.
That's enough to get started.

Use What You Already Learned

Don't wait until you've mastered AWS.
Look at the services you've already encountered.
For example, if you've learned Amazon S3, build something with S3.
Then take it one step further.
S3 → Lambda
A file gets uploaded to S3, which triggers a Lambda function to process it.
Now you've gone from:
"I know what Lambda does."
to:
"I used Lambda with S3 to automatically process uploaded files."
That's a much better thing to talk about in an interview.
And if you learned DynamoDB, try building something that actually stores data in it.
The project doesn't need to be complicated. It just needs to make you use what you learned.

Let Something Break

This is probably the most valuable part of building.
Your first attempt might not work.
Maybe your Lambda function doesn't trigger.
Maybe your permissions are wrong.
Maybe your application can't access your database.
Don't just fix it and forget about it.
Document it.
What did you think was wrong?
What did you try?
What was actually wrong?
How did you fix it?
That can become your next Builder Center article.
And unlike a generic tutorial, it's something you actually experienced.
In my first article, NEW TO AWS? BUILDER CENTER IS WHERE YOU SHOULD START , I talked about using Builder Center to learn, build and connect.
This is where those pieces start coming together:
Learn → Build → Break → Fix → Explain

Turn a Workshop Into Your Own Project

You don't even have to start from a blank page.
AWS workshops and learning resources can give you the foundation.
Follow the workshop.
Get it working.
Then change something.
Add a feature.
Try a different service.
Change the architecture.
Or intentionally break something and figure out why it stopped working.
The moment you start experimenting instead of simply following instructions, you've turned a tutorial into your own learning experience.

Your Project Becomes More Than a Project

Once you've built something, don't leave it sitting on your laptop.
Put the code on GitHub.
Write about what you learned.
Share the article.
Add the project to your portfolio.
Now one small project has become several things you can show:
AWS knowledge + GitHub project + Builder Center article + something to discuss in an interview.
And that's why I think the best progression is:
Badge → Project → Article
Your badge shows that you learned something.
Your project shows that you used it.
Your article shows that you understood it well enough to explain it.

So, What Should You Build?

Don't overthink it.
Look at the last AWS concept you learned and ask:
"What's the smallest useful thing I could build with this?"
Give yourself a weekend.
Build it.
Let something break.
Fix it.
Then write about what happened.
You don't need 20 projects.
Start with one.
And if you're already working through AWS Student Rewards, maybe your next badge shouldn't be the only thing you take away from the next course.
Take a project out of it too.

Series: Free-AWS-Certifications (5 articles)

  1. …
  2. 4
    I Earned the AWS Badges. Now What Do I Build? This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article