How to List AWS on Your Resume
Hiring managers don't care that you've heard of AWS. They want to know which services you've shipped against, how much infrastructure you've owned, and whether you've ever held a cloud bill in your hands.
Name the services you actually use
A useful AWS line names the services: "AWS (EKS, Lambda, RDS, S3, CloudFront, IAM)." This serves two audiences. Recruiters skim for keywords, and ATS systems search for them. "AWS" alone matches almost nothing.
Put certifications where people look
If you hold Solutions Architect, SysOps, or DevOps Engineer certs, put them in a Certifications block near the top of the resume, not buried in education or a sidebar. Recruiters search the ATS for the literal cert name. Bury it and you may not appear in the search at all.
Quantify what you ran
Good AWS bullets show scope. "Owned multi-region EKS deployment serving 80 services and 240 pods at peak; held 99.95% availability over four consecutive quarters." If you reduced cloud spend, lead with that. Cost wins read as senior because most engineers never get close to the bill.
Do this, not that
Cut AWS bill 28% (about $380k/yr) via Graviton migration and reserved-instance restructuring across 110 EC2 and RDS instances.
Worked on AWS infrastructure.
Apply this to your resume automatically
Upload your resume and the AI runs every tip in this guide against it, flags weak bullets, and rewrites them with quantified outcomes and the right ATS keywords.
Upload my resume