
Got the Badges and the Voucher. What's Next?
Everyone writes about earning the badges. Nobody writes about what to do the day after. Here's what to study next, by area, and how to make the voucher count.
Search "AWS Student Rewards" and you'll find plenty of roadmaps for earning badges. Complete your profile, publish, comment, keep the streak.
Almost nobody writes about the other half. You earned it. Now you're holding twelve months of premium learning access, some credits, and a $100 exam voucher, and the roadmap ends right where it starts to matter.
Take inventory first
Most people misjudge what they actually got.
Twelve months of premium AWS Skill Builder access is the biggest item, and the one people forget to use. 900+ courses, hands-on labs, and exam prep. The voucher is worth $100. The subscription is worth several times that.
Credits at 7 and 14 badges. Small by design. A tank of gas, not a car.
A foundational exam voucher at 21 badges.
Free sandboxes on Builder Center, available to everyone, not just students. You can request a free, time-limited sandbox straight from eligible workshops with no AWS account and no credit card. Eight hours each, automatic cleanup, one per week. If fear of a surprise bill is what's stopping you from touching the console, that's the fix.
So: spend the subscription, hold the voucher until you're ready, practice in sandboxes instead of your own account.
Which exam gets the voucher
Two foundational certifications, one voucher.
Cloud Practitioner is the broad one. Core services, security basics, billing, vocabulary. Choose it if you're new to cloud, want the widest recognition, or plan to go toward architecture or development next. It gives you the vocabulary every associate exam assumes you already have.
AI Practitioner is the focused one. Generative AI concepts, foundation models, responsible AI, prompt engineering. Choose it if you're already comfortable with cloud basics and your work leans toward data or ML.
Unsure? Take Cloud Practitioner. You can add the other later.
One thing to check: after you pass, look in your AWS Certification account for the discount benefit toward your next exam.
Courses by area
This is where the twelve months goes. Pick one track and finish it. Two half-finished tracks are worth less than one completed one. Search these by name on Skill Builder, since catalogs move.
Cloud and architecture - the default if you have no strong preference. Start with Cloud Practitioner Essentials, then AWS Technical Essentials. Cloud Quest if gamification keeps you consistent. Then the exam prep plan for Solutions Architect - Associate, the highest-leverage second certification for most people. Pick Developer - Associate instead if you write code and want Lambda, DynamoDB, and API Gateway depth.
AI and generative AI - the crowded track with the clearest demand. Generative AI Learning Plan for Developers (the version with labs), Foundations of Prompt Engineering, then Amazon Bedrock and AgentCore for building agents. Long term, AWS Certified Generative AI Developer - Professional now exists for production-grade GenAI work, but it targets 2+ years of AWS experience. Destination, not next step.
Data and analytics - less crowded, consistently hiring. SageMaker foundations and data engineering content, aiming at Data Engineer – Associate or Machine Learning Engineer – Associate.
Security - least competition among students, strongest long-term value. IAM, shared responsibility, encryption, detection, aiming at Security - Specialty. A hard first credential and a very strong second one.
DevOps - infrastructure as code and observability, toward DevOps Engineer - Professional.
Business and cloud literacy - cost optimization and GenAI-for-decision-makers content. Pairs well with Cloud Practitioner if you want cloud fluency, not a cloud job.
Spend the credits on something small and finished
The mistake is saving them for a big project that never happens. A working Bedrock prototype, a static site on S3, one Lambda that does one useful thing. Finished and small beats ambitious and abandoned. For anything longer, use a sandbox.
Then make it visible
A certification says you passed a test. A project says you can build. A written explanation says you understand. Employers weigh those roughly in reverse order of how much effort students put into them.
Publish what was hard and what you did about it, not another roadmap. Keep a public repo. Watch for AWS Community Builders applications early in the year. Answer someone's question in a Space, which takes ten minutes and often helps more than an article.
Three prompts worth keeping Find your blind spots.
Quiz me on [exam name], one question at a time, exam-style with plausible distractors. After each answer, tell me why the wrong options are wrong and keep a running tally of my weakest domain. Don't move on until I answer.
Turn a course into a project.
I finished [course]. Suggest three projects that prove I understood it. Each under 8 hours, free-tier or sandbox-friendly, producing something I can link to. List the services and the hardest part of each.
Pressure-test a decision.
Compare [cert A] and [cert B] for someone who is [year, degree, target role, region, experience]. Make the case for each, then commit to a recommendation and name the tradeoff I'm accepting.
Your turn
Program terms, catalogs, and exam versions all change. This reflects late August 2026, so confirm anything that costs you money or a voucher on the official pages first.
The badges were the easy part. So, for anyone further along: which certification did you spend your voucher on, and would you choose the same one again? I'm curious whether people who went straight to AI Practitioner regret skipping Cloud Practitioner, or the reverse.
If you're just starting the badge journey, my earlier article on AWS Students Rewards covers how the program works from the beginning.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article