
21 AWS Badges Are Easier Than You Think
Part 2 of my aricle working towards the 21 AWS Student Rewards badges π Iβm sharing what Iβm learning about consistency, meaningful comments, useful Wishes, better articles, community engagement, and why helping other builders matters just as much as working on your own progress.
Connect. Learn. Share. Grow. πππ¬
This is Part 2 of my article working towards the 21 AWS Student Rewards badges, where Iβm sharing what Iβm learning along the way.
When I first saw that AWS Student Rewards requires 21 badges to unlock the $100 AWS Foundational Certification voucher, it sounded like a lot.
But after spending more time on AWS Builder Center, I started realizing that the individual activities are actually quite achievable.
The real challenge is consistency and contributing something useful to the community. π
I am still working toward the 21 badges myself, so this is not a "I completed everything, copy my strategy" article. These are the things I am currently trying and learning while working toward the milestone.
And there is one important point I want to make right at the beginning:
The goal should not be to trade likes, replies, or comments just to unlock badges.
An AWS employee recently made this distinction very clear in a Builder Center discussion: these badges are intended to recognize comments that genuinely help other builders, not coordinated like or reply exchanges.
That actually makes the strategy simpler.
Do not ask:
"How can I get someone to like my comment?"
Ask:
"How can I write a comment that someone genuinely finds useful?"
That is the mindset behind everything below.
Start Early and Stay Consistent π
Some activities can be completed relatively quickly.
Long streaks cannot.
If you are working toward badges that require weeks or even months of activity, there is no shortcut that turns 90 days into one weekend.
So start early.
Visit Builder Center regularly, read what other builders are publishing, explore different communities, check Wishes and contribute when you actually have something useful to add.
Think of the longer streaks as something that runs in the background while you learn and work on the other badges.
The individual actions are not necessarily difficult.
The challenge is doing them consistently.
Don't Write "Great Article!" Just to Leave a Comment π¬
There is a huge difference between leaving a comment and contributing to a discussion.
This:
"Great article!"
does not really teach anything.
It does not share an experience.
And it gives the author almost nothing interesting to respond to.
Instead, add something.
For example:
"I'm currently learning Lambda too. What made you choose Lambda instead of ECS for this use case? Was simplicity the main reason?"
Or:
"I tried something similar and ran into problems with cold starts. Did you experience that as well, or was it irrelevant for your workload?"
Or:
"I initially thought Multi-Region was always the better option, but for a student project the extra complexity seems huge. Would you start with Multi-AZ instead?"
These comments work better because they contribute something to the article.
They share an experience.
They introduce another perspective.
They ask a real question.
That is much more likely to create organic engagement.
Answer Questions Before Asking Another One
If somebody asks you a question under your article, actually answer it.
Do not immediately reply with another question just because you want to keep the comment chain going.
If somebody asks:
"Why did you choose Lambda instead of Fargate?"
give your actual reasoning first.
Then, if it makes sense, continue:
"For my use case, I preferred Lambda because I wanted something simple and event-driven without managing containers. I'm still curious though, would you have chosen Fargate here?"
Now you have actually helped the person and created an opportunity for further discussion.
That feels very different from manufacturing replies.
Engage With Other Articles, Not Just Your Own π
Publishing your article is only one part of Builder Center.
Read what other people are publishing too.
If somebody writes about a service you are currently learning, contribute your experience.
If somebody asks a question you can answer, help.
If somebody introduces an AWS service you have never used before, ask how they are using it.
If you disagree with something, explain why respectfully.
And when people interact with your own articles, return and continue those discussions too.
Over time, you start recognizing the people who regularly interact with your work.
You can see who comments, who contributes useful ideas and who is interested in similar topics.
And the same works in the other direction.
Other builders can also recognize whether you only appear when you want engagement on your own content or whether you actually participate in their discussions too.
That is where Builder Center becomes much more valuable than simply collecting badges.
You start building a network.
Connect. Learn. Share. Grow. π
Likes Should Be Earned Through Value β
Likes are naturally harder because you cannot control whether somebody likes your contribution.
And that is exactly the point.
Instead of trying to coordinate likes, write something that people independently think deserves one.
Teach something.
Share an experience.
Correct a misunderstanding.
Explain how you solved a problem.
Ask a question that improves the discussion.
And when you see another builder doing the same thing, support that contribution because you genuinely found it valuable.
You can also use different filters, categories and communities to discover discussions you might otherwise miss.
Look at new content.
Explore older discussions.
Move between topics.
Discover people outside your normal feed.
But the principle stays the same:
Do not like something because you expect a like back.
Like it because it helped you, taught you something or improved the conversation.
If that happens consistently across the community, engagement-based badges become a natural result of good participation.
Publish 1 to 2 Useful Articles a Day βοΈ
If you have enough genuinely useful ideas, publishing one or two interesting articles per day can be a good way to stay active.
But frequency should not replace quality.
Your articles can be simple.
Share something you recently learned.
Write a short guide.
Explain a mistake you made.
Compare two AWS services.
Share your certification preparation.
Discuss a current AWS or AI topic.
Document a small experiment.
Ask the community for another perspective.
You do not need every article to be a massive technical deep dive.
The important thing is that readers get something from it.
Make the Article Look Worth Opening π¨
Content matters most, but presentation matters too.
Create a good thumbnail.
It does not need to be overloaded with ten AWS icons and huge amounts of text.
A clean thumbnail with one strong visual idea can make your article much easier to notice.
The thumbnail should match the topic immediately.
AWS costs?
Make that visible.
AI agents?
Communicate AI and automation.
Certification?
Make the learning or certification theme obvious.
The same applies to the title.
Make it interesting, but make sure the article actually delivers what the title promises.
Attention gets the reader in. Value makes them stay.
Use Tags That Actually Fit π·οΈ
Tags should help the right people discover your article.
Do not simply choose whatever tag seems popular.
If your article is about Amazon Bedrock, use relevant AI and Bedrock topics.
If it is about cost optimization, use cost-related topics.
If it is about certification preparation, use learning and certification-related tags.
If it is about Serverless, use Serverless topics.
Good tags help your article reach the people who are actually interested in that topic.
And those are the people most likely to add something meaningful to the discussion.
Wishes Should Solve Something Real π‘
Wishes are another place where usefulness matters.
Do not create a random Wish just because you want another activity on your profile.
Think about something that could genuinely improve AWS Builder Center for other people.
Maybe there is a missing feature.
Maybe something is confusing.
Maybe an existing feature could work better.
Or maybe you found a bug.
My own Wish, for example, is about a bug that I would like to see fixed.
The bug affects me, but it is likely that other builders can experience the same issue too.
That is what makes it worth reporting.
Before submitting a Wish, ask:
Would implementing or fixing this help other builders too?
Also search existing Wishes first.
If somebody already reported your problem, supporting the existing Wish may be more useful than creating a duplicate.
Join Other Communities π
Do not stay in the same topic forever.
Join communities around areas you actually want to learn.
Generative AI.
Serverless.
Security.
DevOps.
Data.
Cloud architecture.
Certifications.
Different communities expose you to different people, projects and perspectives.
You might discover someone preparing for the same exam.
Someone might be building something with the service you are currently learning.
Or you might discover a completely new AWS service because of one discussion.
That is the part of Builder Center I think becomes more valuable over time:
You start for the badges, but you stay because you keep discovering new things and new people.
Follow People You Actually Want to Learn From
Following people should work the same way.
Do not follow random users simply because you want activity.
Follow somebody because their content is relevant to you.
Maybe they consistently write about Bedrock.
Maybe they are preparing for the same certification.
Maybe they keep answering questions you are interested in.
Maybe you already had a useful discussion with them.
Then the next interaction becomes a continuation instead of starting from zero again.
That is how you gradually build connections around your actual interests.
Use Conversation Starters That People Can Genuinely Answer π¬
Questions are still a great way to invite people into an article.
The difference is that they should exist because you actually want to hear the answers, not because you are trying to generate a specific number of replies.
Try questions such as:
Which AWS certification are you currently aiming for, and why did you choose it?
Which AWS service are you currently learning?
What are you currently building or experimenting with?
Which AWS concept took you the longest to understand?
What was one mistake that taught you something useful about AWS?
What AWS topic do you think more students should learn?
Which service looked simple until you actually started using it?
What would you like AWS Builder Center to improve?
What AWS or AI topic should I explore next?
These questions work well for students because you do not need professional production experience to answer them.
Everyone has something they are learning. π
Why You Cannot Really Do This Alone π
AWS Builder Center is community-driven.
That means some progress depends on more than simply publishing your own articles and waiting.
If you only focus on your own profile, your own content and your own badges, you are missing a huge part of how the platform works.
People notice who participates.
When you publish regularly, you start recognizing the same names in your comments. You see who answers questions, who shares useful experiences, who joins discussions and who keeps coming back.
And other builders see the same thing about you.
They can see whether you only show up when you want attention on your own article or whether you also read, discuss and contribute to other people's content.
That does not mean:
"I helped you, so now you owe me a like."
It means building genuine relationships inside the community.
If somebody writes a useful article, read it and contribute something meaningful.
If someone asks a question you can answer, help them.
If you learn something from a comment, show that it was useful.
If someone publishes a Wish that solves a real problem you also have, support it.
If another student is preparing for the same certification, talk about how you are both approaching it.
Over time, people remember useful interactions.
Someone you helped understand Lambda today might recognize your Bedrock article next week and genuinely want to join that discussion.
Someone whose article you contributed to might later see your name and remember that you had an interesting conversation before.
That is not coordinated engagement.
That is how communities work. π
And I think this is one of the biggest mistakes you can make when trying to reach 21 badges:
Thinking you can do everything by yourself.
Some activities are individual.
Community engagement is not.
If everybody only publishes and waits for other people to help them, nothing happens.
Someone has to answer the questions.
Someone has to share the useful experience.
Someone has to read the article.
Someone has to improve the discussion.
So instead of asking:
"How can the community help me reach 21 badges?"
I think the better question is:
"What can I contribute that makes another builder want to interact with me naturally?"
That is where the badges, networking and actual learning start coming together. π
What I'm Currently Doing π
I am still working toward the 21 badges myself.
Right now, I am focusing on:
- Starting long streaks as early as possible. π
- Visiting Builder Center consistently.
- Publishing one or two useful articles when I have good topics. βοΈ
- Writing about my experiences, guides and things I am currently learning.
- Creating clean and relevant thumbnails. π¨
- Choosing tags that genuinely match each article. π·οΈ
- Writing comments that teach, help or add another perspective. π¬
- Answering questions properly.
- Returning to my own articles and continuing useful discussions.
- Reading and engaging with other people's articles too.
- Exploring different communities and topics. π
- Creating Wishes that solve genuine problems. π‘
- Supporting existing Wishes that I actually agree with.
- Following builders I genuinely want to learn from.
- Learning from the people I meet instead of treating them as another badge requirement.
I am sure I am still missing things.
And that is why I want to hear from people who are also working toward the same goal.
Connect. Learn. Share. Grow. π
If you are also participating in AWS Student Rewards, tell us:
- How many badges do you currently have? π
- Which certification are you aiming for, and why? π
- Which badge are you finding the hardest?
- Which AWS service are you currently learning? βοΈ
- What are you currently building or experimenting with?
- Have you submitted a meaningful Wish? What problem does it address? π‘
- Which Builder Center communities have you found useful? π
- What have you learned from another builder recently?
- What is one thing I should add to this strategy?
And if you find an interesting answer, continue the conversation because you are genuinely interested in it.
Ask how they are preparing.
Compare what you are learning.
Share something that could help them.
That is much more valuable than coordinating a certain number of likes or replies.
I started looking at AWS Student Rewards because of the 21 badges.
But the more I use Builder Center, the more I think the badges are only part of the opportunity.
21 badges might get you the reward. The people you learn from along the way might be worth even more. π
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article