How to put an AWS certification on your CV (the right way)
Put your AWS certification in a dedicated Certifications section of your CV, written as the exact official name with its exam code and pass date, backed by the verifiable digital badge link — and, if you are targeting cloud roles, echo it once in your headline or summary so keyword screens catch it. That is the mechanical answer, and it takes ten minutes to do properly. The part most candidates get wrong is not placement but framing: a certification listed as though it were experience invites interview questions it cannot answer, while a certification presented honestly — as current, structured knowledge sitting alongside project and work evidence — does exactly the job it is designed for. Whether you call the document a CV (resume) or anything else, the principles below are the same. Here is where to put it, how to word it, how to handle LinkedIn, and how to make sure the credential helps rather than overreaches.
Where it goes: a Certifications section, echoed up top
Give certifications their own clearly labelled section — “Certifications” — rather than burying them under education or skills. Recruiters and applicant tracking systems both look for that section by name, and a dated, vendor-backed credential deserves better than a bullet in a skills list. Place the section according to its weight in your story: near the top if you are a career changer whose certification is the strongest cloud evidence you have, and below experience if you have real cloud work history, which should lead.
Then echo the credential once where the first glance lands. Many recruiters filter and search on certification names, and an automated screen may only weigh prominent fields — so a headline or summary line such as “AWS Certified Solutions Architect – Associate” earns its space, especially when the job advert names the certification explicitly. Once is enough; repeating a credential throughout a CV reads as padding, and padding is the impression you most want to avoid.
How to word the entry — exact name, code, date
Use AWS’s official certification title verbatim, not a paraphrase. “AWS Certified Solutions Architect – Associate” is searchable and unambiguous; “AWS Architecture Certificate” is neither, and may fail the exact-phrase matching some screens use. Alongside the name, include the exam code and your pass date. A clean entry looks like: AWS Certified Solutions Architect – Associate (SAA-C03) — Issued March 2026. The code matters because recruiters search on it, and because it tells a technical reader precisely which syllabus version you passed.
The date matters for a different reason: AWS certifications are valid for three years, and a dated entry signals both currency and honesty. If a certification has expired, either renew it or move it to a clearly marked line — listing an expired certification as current is exactly the kind of overstatement a verification check exposes. And if you are mid-study, “in progress” entries are acceptable only with a scheduled exam date; an open-ended “currently studying for” line carries almost no weight and is usually better omitted.
Add the badge link — verification is the credential’s superpower
Every AWS certification comes with a verifiable digital badge issued via Credly, and linking it is the single highest-value detail most candidates omit. The link lets a recruiter or hiring manager confirm in one click that the credential is real, current and yours — which matters in a market where unverifiable claims are common enough that verification itself is a differentiator. On a digital CV, hyperlink the certification name or add a short “verify” link; on LinkedIn the badge integrates directly.
This is also your protection. Certification claims do get checked — by automated background services and by sceptical hiring managers alike — and a candidate whose credential verifies instantly starts the conversation with earned trust. Keep your AWS Certification Account details current so the badge reflects your latest status, and claim the Credly badge promptly when you pass; it is issued to you, but it does not add itself to anything.
Don’t let the certification stand alone
A certification on a CV with no supporting evidence raises the exact question it cannot answer: fine, but what have you done? The fix is to pair it, deliberately, with the strongest hands-on material you have:
- Projects — a short Projects section with two or three finished, documented builds (a deployed application, an automated pipeline, a monitored workload) turns the certification’s theory into demonstrated practice. Free Tier projects count; our guide on AWS portfolio projects that get you hired covers what to build.
- Experience bullets that speak cloud — comb your existing work history for anything touching infrastructure, automation, cost, security or reliability, and word those bullets in the vocabulary the certification taught you.
- A skills section that matches the syllabus — list the specific services and practices you can actually discuss, not the entire AWS catalogue. Every skill you list is an interview question you are inviting.
- Honest framing everywhere — the certification proves organised, current knowledge; the projects and bullets prove application. Presented together, each makes the other more credible.
LinkedIn: the Licenses & Certifications section, done properly
On LinkedIn, add the credential under Licenses & Certifications with AWS (Amazon Web Services) as the issuing organisation, the exact official name, the issue and expiry dates, and the Credly credential URL — accepting the badge through Credly can add it near-automatically. Recruiters filter candidate searches on this section specifically, so a certification living only in your About text is invisible to the searches that matter.
Then let it appear naturally elsewhere: a mention in your headline if you are actively job-seeking in cloud roles, and a line in your About section connecting it to what you are building or aiming for. The same restraint applies as on the CV — one clear, verifiable listing beats scattered repetition, and pairing the credential with visible project posts or repositories does more than any amount of badge display.
The honesty line: what the keyword gets you, and what it doesn’t
Understand the two audiences a certification on a CV serves, because they read it differently. The recruiter screen — human or automated — is looking for the keyword: the exact certification name the role calls for. Your listing exists to pass that gate, which is why the official wording, the dedicated section and the headline echo matter. Past the gate, the hiring manager reads the same line as a claim about knowledge and probes for the experience behind it in the interview. The certification cannot answer those questions; your projects, work history and reasoning can.
So the honest strategy writes itself: present the certification precisely and verifiably for the screen, surround it with evidence for the interview, and never let the CV imply the credential is more than it is. A certification is knowledge, current and organised — a genuine asset when framed truthfully, and a liability the moment a CV inflates it into experience the interview then fails to find. Candidates who respect that line consistently get more from a modest, well-evidenced CV than others get from an inflated one.
Original practice questions, timed mock exams and revision notes. No card, nothing to pay.