How to List AWS Certification on a Resume: Format, Examples, and ATS Tips

The exact format (copy-paste examples)

AWS certifications belong in a dedicated Certifications section, written as the full official credential title, then the issuing body "Amazon Web Services," then the issue date with a "Valid through" date in parentheses. The "Valid through" date is the single most useful detail you can add, because AWS certifications expire exactly 3 years after the issue date, and showing currency proactively separates you from candidates listing a stale credential with no date. Start with the filled card below, then adapt the line that matches your tier.

Three formatting rules drive every example. First, always use the full official title (we cover the catalog below), never a bare acronym or a bare exam code. Second, always name the issuer as "Amazon Web Services" spelled out, because parsers use it to confirm the credential is real. Third, always include month and year for the issue date; year-only is acceptable but month and year parses more cleanly and lets a reader compute the expiry. The credential ID and verification line is optional but recommended for senior and enterprise roles, where it removes a step from the recruiter's verification path.

Where AWS certifications go on a resume

The dedicated Certifications section (or "Licenses & Certifications") is the default home for every AWS credential. Where that section sits depends on your experience. For early-career or cloud-focused candidates, place it near the top, just under the summary, so the credential is the first thing a recruiter sees. For senior candidates with a strong work history, place it below the Experience section, where it confirms rather than carries the application.

Full name vs abbreviation: use the official title

The most common AWS resume mistake is shortening the credential to an acronym or an exam code. List the full official title, "AWS Certified Solutions Architect – Associate," not the bare exam code "SAA-C03" and not a homemade acronym like "SAA" or "CSA." Recruiters search and filter on the title that AWS publishes, which is also the exact phrasing copied into job descriptions. The exam code is fine appended in parentheses when a posting references it, but it should never stand alone.

The current AWS catalog (use the official title)

AWS organizes its catalog into four levels, Foundational, Associate, Professional, and Specialty, with 12 active exams as of 2026 (Sailor.sh and course.careers AWS certification guides, 2026). There are exactly four official levels: invented tiers like "AWS Master Architect" or "AWS Certified Cloud Expert" do not exist and signal a fabricated credential. The table below pairs each common credential with its current exam code and the average salary reported in Skillsoft's 2026 IT Skills and Salary Report, so you can judge not just how to list a cert but which one signals the most value. Note one accuracy trap competitors still publish: the current Solutions Architect Associate code is SAA-C03, not the retired SAA-C02.

Demand follows the catalog. Solutions Architect – Associate is the most-requested AWS cert with 45,000+ job postings, Cloud Practitioner is second at 32,000+ and growing fastest, and the Machine Learning and Security Specialties are growing roughly 45% and 35% year over year (StudyTech "Most In-Demand AWS Certifications 2026," based on job-posting data). AWS also holds about 30 to 32% of the global cloud infrastructure market and is the most-mentioned cloud platform in 2026 tech job postings, ahead of Azure and GCP (codelabsacademy and practicetestgeeks, 2026), which is why an AWS credential carries more search weight than its rivals.

Dates, expiration, and the 3-year validity window

AWS certifications are valid for exactly 3 years and must be recertified before they expire (AWS Certification program; Sailor.sh AWS certification list, 2026). You recertify by passing the current version of the exam, and for many Foundational and Associate credentials by earning a qualifying higher-level certification. This is the single biggest gap in competing guides, and the easiest place to look more current than other candidates.

Never silently list an expired cert. An undated credential whose issue date is 3 or more years old reads as lapsed. If a cert has expired, the honest options are to recertify before applying, remove it, or, if it still provides useful context, label its status precisely rather than implying it is current. A soon-to-expire cert is fine to list with its real "Valid through" date; the date does the disclosing for you.

In-progress and "in pursuit" certifications

A certification you are studying for can absolutely appear on a resume, as long as you never present it as earned. Label it as in progress with a scheduled exam date or an expected completion date, and keep it in the Certifications section so it is clearly framed as a credential rather than an achievement.

What you must not do is list an in-progress cert with a "Valid through" date, an issue date, or a credential ID, because all three imply you already hold it. AWS maintains a public verification path, so an inflated claim is easily disproven and reads as a credibility problem the moment a recruiter checks.

Listing multiple AWS certs (stacking and order)

When you hold several AWS certifications, group them in one Certifications section and order them most advanced or most relevant to the target role first. A Professional credential outranks an Associate, which outranks the Foundational Cloud Practitioner. Once you hold a Professional cert, the underlying Cloud Practitioner is optional and can be dropped if space is tight, since the higher tier already implies the foundation.

If the role is specialized, lead with the matching Specialty cert even when you hold a Professional, because relevance beats raw tier for a hiring manager scanning for fit. For a security role, the Security Specialty belongs at the top; for an ML role, lead with the Machine Learning Specialty.

How parsers read AWS cert names (ROP parser callout)

Resume Optimizer Pro's parser matches certification credentials against the full canonical string, "AWS Certified Solutions Architect," because that is the exact phrasing recruiters paste into job descriptions and search filters. Bare acronyms ("SAA," "CSA," "SAP-C02") and informal phrasings ("AWS Architect cert") are frequently missed or mis-mapped, because they collide with unrelated tokens, for example SAP the software vendor. Parsers also expect certifications under a recognized heading such as "Certifications" or "Licenses & Certifications." A credential buried only inside a Summary paragraph or a comma-separated Skills line is parsed with lower confidence and may not populate the certifications field in the ATS profile at all.

The practical takeaway is that the placement rules in this guide are not stylistic preferences, they are parser requirements. Our free ATS checker flags AWS credentials that are missing the issuing body, sitting outside a recognized Certifications heading, or written as a bare code that will not match the title in a job description.

Before and after: a resume snippet

The fix is mechanical. The "before" snippet below buries an AWS credential in a Skills line as a bare acronym with no date. The "after" moves it into a dedicated Certifications section with the full title, the issuer, and a "Valid through" date.

Common AWS-specific mistakes to avoid

Frequently asked questions