What to do after your first cloud certification
After passing your first cloud certification, the highest-value next moves are to convert it into evidence and momentum — build hands-on projects, update your CV and profiles, and decide deliberately whether your next step is a role-based associate, a second cloud, or a job search — not simply to book another exam. The pass itself is a milestone, but a certificate is a claim about knowledge, and what happens in the weeks afterwards determines whether that claim turns into interviews and opportunities or quietly fades into a line on a CV. There is some quick housekeeping worth doing immediately, one move that matters more than any other, and a genuine fork in the road about what comes next. Here is the honest sequence, whether your first pass was AWS Cloud Practitioner, Azure Fundamentals or something bigger.
First, the housekeeping: badge, CV, voucher
Within a few days of passing, do the small administrative things that make the credential visible and usable. Claim your digital badge — AWS issues one through Credly, Microsoft through Learn — and add it to your LinkedIn profile, where the verification link lets anyone confirm it is real. Put the certification on your CV (resume) with its full name and date; recruiters and filtering software search for the exact credential names, so “AWS Certified Cloud Practitioner” beats “AWS certified”.
If your pass was an AWS exam, log in to your AWS Certification Account and find your 50% discount voucher for a future exam — every AWS pass earns one, and it meaningfully cuts the cost of an associate exam if you continue. Azure works differently: there is no equivalent voucher scheme to hunt for, but note how renewal works instead — role-based Azure certifications renew free through an online assessment, while Azure Fundamentals never expires. Knowing your credential’s maintenance terms now saves a scramble later.
The most important move: build things that prove it
A certification implies skills, and interviewers will probe for them — so the single highest-value thing you can do after passing is build small projects that demonstrate the knowledge the exam certified. Host a static site, launch and secure a virtual machine, set up identity and least-privilege access, wire up a monitoring alert. None of these takes long on a free-tier account, and together they convert “I passed an exam about these services” into “I have used these services, and here is the repository”.
Document the projects publicly on GitHub with a short write-up of what you built and why. This is the evidence layer a certificate lacks: anyone can verify a badge, but a repository shows judgement, initiative and the ability to finish things. Our guide on how to build a cloud home lab covers the mechanics — the point here is sequencing. Projects built now, while the exam material is fresh, cost half the effort they will in six months and compound everything else on this list.
Choosing the next certification — if there is one
If you decide to certify again, choose role-first rather than badge-first. A role-based associate — AWS Solutions Architect Associate or Developer Associate on the AWS side, AZ-104 Azure Administrator on the Microsoft side — almost always beats collecting a second foundational badge, because associates map to jobs while foundationals map to vocabulary. Two foundational certificates say roughly the same thing twice; a foundational plus an associate says you went deeper, in a direction an employer can hire for.
The second cloud question deserves a deliberate answer too. Adding the other vendor’s foundational cert — AZ-900 after an AWS start, or Cloud Practitioner after an Azure one — is cheap breadth and genuinely useful in markets where both platforms are common, but it should complement depth, not substitute for it. Our post on how many certifications you actually need goes deeper; the short version is that depth in one cloud plus awareness of the other beats shallow coverage of both.
Or: stop certifying and start applying
The other branch of the fork is just as legitimate: decide that one certification is enough for now and put the effort into a job search instead. If your goal was a foothold — a support role, a junior cloud position, an internal move onto the infrastructure team — a foundational or associate certificate plus a few documented projects is a credible application today, and months spent accumulating further badges may simply delay it. Certifications have diminishing returns as signals; interviews, rejections and feedback teach you what the market in your area actually wants faster than any syllabus.
A practical test: read ten live job adverts for the role you want and see what they ask for. If your current certification plus demonstrable hands-on work meets the stated requirements, apply — the worst outcome is feedback. If the adverts consistently name a credential you lack, that is a data-driven reason to certify again, which is a far better reason than momentum.
Keep the credential current
Certifications are maintained, not just earned, and the two vendors handle it differently. AWS certifications are valid for three years, renewed by re-sitting the current version of the exam or by passing a higher-level one, which renews the lower automatically — so an associate pass down the line quietly extends your foundational. Azure role-based certifications expire after one year but renew free via an online, unproctored assessment on Microsoft Learn, available in the six months before expiry with unlimited attempts; Azure Fundamentals does not expire at all.
Put the relevant date in your calendar now, while it is fresh — an expired credential is an avoidable small embarrassment on a CV, and both vendors’ renewal routes are easiest when planned rather than rushed. Our posts on AWS recertification and on how Azure certification renewal works cover the mechanics of each; the only step needed today is knowing which model your certificate follows and when its clock runs out.
The honest close: experience compounds faster than badges
Finally, the framing to carry forward: after the first certification, experience compounds faster than certificates. The first badge opens the conversation — it gets a CV past filters and signals commitment credibly. But every badge after it adds less than a project shipped, a problem debugged in production or a role held for a year, because employers hire for demonstrated ability and certificates are, at best, promising claims about it. Collecting certifications can even read as a substitute for doing the work if nothing sits behind them.
So treat certificates as accelerants for a career built on doing, not as the career itself. Let your next certification — if there is one — follow from where your experience and your target roles lead, chosen off the back of live job adverts rather than momentum. The people a first certification serves best are the ones who convert it quickly: into projects, into applications, into a role where the learning continues on someone else’s systems. That conversion, not the next exam booking, is the actual assignment.
Original practice questions, timed mock exams and revision notes. No card, nothing to pay.