Where do I put AWS on a resume?

Put it in three places: a skills line naming the services you have used (for example Compute: EC2, Lambda. Data: S3, RDS), a certifications section if you hold any, and experience bullets that say what the services did. Recruiters skim the skills line, but they read the bullets.

Should I put AWS on my resume if I only have basic experience?

Yes, if you have really used it and the job asks for it. Label it honestly, for example 'AWS (basic: EC2, S3)', and back it with a small project or a task you did. Expect a practical question about it in the interview.

How do I show my AWS skill level?

Describe what you have built or operated instead of writing 'expert'. A service you deployed, a permission problem you fixed, or an environment you designed each say more than a label. Name the services and, where you can, what changed because of your work.

Do I need an AWS certification to get a cloud job?

Not always. A certificate shows you studied the platform, but employers still look for bullets proving you used the services. If you have no certificate yet, strong project work and clear bullets can carry a CV, and a certificate then adds to it.

How do I check if my CV shows the AWS skills a job ad asks for?

Paste the job ad and your CV into NextCV's free job match tool at /en/job-match. It is deterministic, needs no signup, and lists the keywords from the ad that your CV is missing, with a 0-100 overlap score. For a general score without a job ad, /en/cv-check rates your CV out of 100 across 8 categories, with no AI.

How to Put AWS on a Resume (With Examples)

Q: How do I list an AWS certification on a resume?

Write the exact official name and the year you passed, for example 'AWS Certified Solutions Architect – Associate, 2026'. AWS says its certifications are valid for 3 years, so the year tells a recruiter whether yours is current. Check the name on the AWS certification page before you copy it.

AWS goes in three places on a resume: a skills line that names the specific services you have used (EC2, S3, RDS, Lambda, IAM), a certifications section with the exact certificate name and the year you passed, and experience bullets that show those services running real work. State your level by describing what you built or operated, not with "expert". Cloud support, DevOps and architect roles each expect a different depth, so match the services to the job ad.

Where AWS Goes on a Resume

Skills section. Do not write "AWS" on its own. Group the services you have used by purpose: "Compute: EC2, Lambda, ECS. Data: S3, RDS, DynamoDB. Security: IAM, KMS. Tooling: Terraform, CloudFormation". Keep the list to services you could talk about for five minutes.

Certifications section. Give each certificate its own line with the exact official name and the year, covered below.

Experience bullets. This is where the claim becomes believable. Put the service name inside a bullet with what it did and what changed. A skills line says you have heard of Lambda; a bullet says what you did with it.

A skills line that works

Compare these two versions of the same line (illustrative example):

Weak: AWS, cloud, DevOps, infrastructure

Better: AWS: EC2, ECS Fargate, Lambda, S3, RDS (PostgreSQL), IAM, CloudWatch. IaC: Terraform. CI/CD: GitHub Actions

The second version tells a recruiter what you can be asked about, and it gives the applicant tracking system real service names to match against the ad. If you used a service only in a course, leave it off or mark it as such.

Not sure your CV shows the AWS keywords a job ad asks for? Paste both into the free job match tool. It compares your CV to the ad, lists the keywords you are missing and gives a 0-100 overlap score. It is deterministic and needs no signup.

How to Show Your AWS Level Honestly

Interviewers tend to pick one service from your CV and ask how you used it, so describe the work and not a label.

Basic: You have used the console or CLI to launch an instance, store files in S3, or follow a tutorial project. Write "AWS (basic: EC2, S3)" and link a small project if you have one.
Working: You deploy and maintain services on AWS as part of your job, with IAM roles, a database and some monitoring. Name the services and what they ran.
Advanced: You design the setup, write the infrastructure as code, and own security, reliability or cost. Give a bullet that shows a decision you made.

How to Write AWS Certifications on a Resume

Use the exact name AWS gives the certificate, then the year you passed. Do not use abbreviations like "SAA" in place of the name; keep it to the name an employer can look up.

AWS Certified Solutions Architect – Associate, 2026

AWS Certified Developer – Associate, 2025

AWS says its certifications are valid for 3 years, and you renew by passing the latest version of the exam. So the year matters: a recruiter can tell at a glance whether yours is current. If a certificate has lapsed, either renew it or leave it off, because an expired line invites a question you do not want.

The AWS certification page lists these, among others:

Foundational: AWS Certified Cloud Practitioner, AWS Certified AI Practitioner
Associate: AWS Certified Solutions Architect – Associate, AWS Certified Developer – Associate, AWS Certified CloudOps Engineer – Associate, AWS Certified Data Engineer – Associate, AWS Certified Machine Learning Engineer – Associate
Professional: AWS Certified Solutions Architect – Professional, AWS Certified DevOps Engineer – Professional
Specialty: AWS Certified Security – Specialty

Pick the ones that fit the role you are applying for. A certificate does not replace experience: put it next to bullets that show the same services in use. If you hold a certificate under an older name, write the name printed on your credential.

Example AWS Bullets by Level

The bullets below are made up to show the pattern. Use your own work, and only numbers you can explain.

Junior or cloud support (illustrative example):

Resolved customer tickets on EC2, S3 and IAM permissions, using CloudWatch logs to find the cause; wrote three runbooks for the most common access errors so other agents could close them without escalating.

DevOps or cloud engineer (illustrative example):

Moved a containerised API from a single server to ECS Fargate behind an Application Load Balancer, with the infrastructure in Terraform and deploys through a CI pipeline; releases changed from a manual evening task to a merge-triggered job.

Senior or architect (illustrative example):

Designed the account structure for a growing product team using AWS Organizations with separate dev, staging and production accounts, least-privilege IAM roles and Service Control Policies; wrote the cost-tagging rules that let each team see its own AWS spend.

Notice the pattern: the service, what you did with it, and what changed. Add a number only where you can defend it in an interview.

What Hiring Managers Look For

"AWS" matches a keyword filter. The services around it tell a recruiter which kind of work you do:

Compute and containers: EC2, Lambda, ECS, EKS.
Data and storage: S3, RDS, DynamoDB, SQS.
Security: IAM, KMS, CloudTrail. Least-privilege access is a common interview topic.
Infrastructure as code: Terraform, CloudFormation or CDK. Name the tool you used.
Cost: budgets, tagging, right-sizing. If you have owned any of it, say so.

Mirror the wording of the job ad where it is true. If the ad asks for Lambda and you have used Lambda, that word should appear in your bullets, not only in a skills list.

Common Mistakes That Weaken AWS CVs

"Experience with AWS" as a standalone bullet. It is too vague to be useful. Follow it with service names and what they did.

Listing every service you have ever touched. Forty service names read as padding. Keep the ones you used on real work.

Certificates with no matching experience. A Professional-level credential next to tutorial-level bullets raises more questions than it answers.

No year on a certificate. The recruiter cannot tell whether it is current.

Not naming the infrastructure tool. If you manage AWS through code, say Terraform, CloudFormation or CDK. If you mostly use the console, be honest about it.

See how NextCV tailors your CV to match the job posting

Closing

AWS is everywhere, but most AWS CVs look the same: a list of service acronyms and a certification or two with nothing behind them. The candidates who consistently land strong cloud roles are the ones who connect their AWS choices to real outcomes — cost savings quantified, reliability metrics held, security posture validated, architecture decisions explained. Every bullet you write about AWS work should answer: which services, at what scale, and what did it enable or improve?

NextCV reads the AWS job description you are targeting and restructures your CV to surface your most relevant service experience, IaC work, and production outcomes — the specifics that distinguish an AWS practitioner from an AWS certificate holder.

Ready to put this into practice? Build your AWS Cloud CV with NextCV →

Three related guides round out the picture: the guide to startup CVs, the AI PM guide, and the Prompt Engineer CV guide. Much of this advice transfers — the container skills guide and the DevOps Engineer CV guide show how it plays out elsewhere.