AWS carries the largest share of cloud infrastructure postings in the United States, which makes "AWS cloud engineer" one of the most searched job titles in American technology and one of the hardest to research honestly. Every salary figure published for it is an estimate built from self-reported submissions, and the two most commonly quoted averages contradict each other. This guide covers what is specifically true of AWS work: what the pay figures actually are, why federal AWS roles set two completely different eligibility bars that are constantly described as one, and the certification sequence that catches people out precisely because nothing stops them.
If you are still deciding between platforms, start with our cloud engineer jobs in USA guide, which covers the occupation as a whole. This page assumes you have picked AWS.
The Two Salary Averages That Cancel Each Other Out
Guides on this subject typically quote both of these figures, usually in consecutive sentences: a national cloud engineer average of $136,050, and an AWS-specific average of $130,802. They then argue that AWS is the premium platform.
Read those together. The AWS-specific number is lower than the general one. If AWS commanded a premium, that figure would be the higher of the two. Nobody is lying; the two numbers are drawn from different sample sizes, different job titles and different self-reported submissions, and the gap between them is measurement noise rather than a finding about AWS pay.
The same applies to the wider range you will see quoted, roughly $88,973 to $208,034, and to city averages like Seattle at $160,429, New York at $146,578 and Washington DC at $142,475. They are directionally useful — the expensive cities do pay more, and the top of the market is genuinely near $200,000 — and they are not measurements.
The measured figures come from the Bureau of Labor Statistics, which has no cloud engineer occupation at all. The work is counted under three others:
- Network and computer systems administrators — a $99,130 median, the highest tenth above $155,050. Running the estate.
- Computer network architects — a $134,050 median, the highest tenth above $202,680. Designing it.
- Software developers — a $135,980 median, the highest tenth above $214,670. Building platform tooling as software.
So the useful question at offer stage is not what AWS engineers earn. It is which of those three the role is. Read the requirements: provisioning and maintaining pays like administration, designing environments pays like architecture, building internal platform software pays like development. The word AWS in the title moves the number far less than which of those verbs the job is.
GovCloud and a Security Clearance Are Two Different Bars
This is the most consequential thing on the page, and almost every guide flattens it into one sentence about federal work.
A large share of US AWS postings — concentrated around Washington DC, Northern Virginia and Columbia, Maryland — are federal, defence or intelligence work. Those advertisements ask for two different things, and they are not the same requirement.
AWS GovCloud (US) requires a US Person. AWS restricts GovCloud access to customers who are US Persons and who comply with US export control law, because the regions exist to hold ITAR and export-controlled data. Under those rules a US Person is a US citizen or a lawful permanent resident — a green card holder. Working on a GovCloud environment does not, by itself, require citizenship.
A security clearance requires US citizenship. It also cannot be applied for independently: you need an employer with a contract who is willing to sponsor the investigation, and the process takes months. No amount of AWS skill substitutes for it.
Why this matters practically: if you hold a green card, the cleared postings are closed to you and a meaningful number of GovCloud postings are not. If you are on a work visa, both are generally closed, and the commercial market is where your time is better spent — it is larger, better paid at the top end, and far more remote-friendly.
Read the eligibility line before you read anything else in a federal posting. Our cybersecurity analyst guide covers the clearance process in full.
AWS Removed the Certification Gate, and That Is the Trap
AWS certifications carry real weight in this market, because the platform changes fast enough that a current certificate signals current knowledge. The planning mistake is about order.
AWS removed prerequisites for its Professional exams in 2018. Nothing stops you booking the AWS Certified DevOps Engineer – Professional or Solutions Architect – Professional exam tomorrow with no prior certification at all. What AWS publishes instead is a recommendation: two or more years of hands-on experience provisioning, operating and managing AWS environments before you sit the Professional papers.
A recommendation is easy to skip and an empty gate looks like permission. It is not. The Professional exams are written for people who have operated production estates, and the exam fee is payable again on a retake.
It is worth knowing that this is an AWS-specific rule rather than an industry norm, because the two adjacent certification paths do enforce order:
- Azure gates its Expert certifications. AZ-305 requires the Azure Administrator Associate certification first, and AZ-400 requires either the Administrator or Developer Associate. Covered in our Azure cloud engineer guide.
- Kubernetes gates its security exam. The Linux Foundation will not register you for CKS without an active CKA. Covered in our cybersecurity engineer guide.
The sensible AWS sequence is Solutions Architect – Associate, or SysOps Administrator – Associate if your work is operational, backed by a project you can describe in detail — then Professional once you have the experience AWS is describing. An associate certificate with real work behind it interviews better than a professional one with nothing, because the conversation goes straight to what you actually did.
Being the Biggest Platform Cuts Both Ways
AWS holding the largest share of US cloud postings is usually presented as a reason to choose it. It is, but the same fact has a second edge that nobody mentions: the largest pool of postings attracts the largest pool of applicants. Every bootcamp, every career-change course and every certification mill defaults to AWS, which means the associate-level AWS certificate is the most common single credential in the pile.
That does not make it worthless — it makes it the baseline rather than the differentiator. What separates applications in an AWS-heavy market is the thing that is scarce: production operational experience, IAM design you can reason about, and a cost story with a number attached.
It also means the narrower specialisms are worth more here than they are elsewhere. GovCloud eligibility, EKS at scale, and cost engineering all shrink the applicant pool sharply, and all three appear constantly in senior postings.
The Services That Actually Recur in Postings
- EC2, S3, VPC and IAM — the four that appear in nearly every advertisement. IAM is the one candidates underprepare and the one interviews probe hardest.
- Lambda and event-driven patterns, increasingly assumed rather than listed as a specialism.
- EKS on container-heavy teams, along with what a cluster costs to run.
- Terraform above CloudFormation in most postings, treated as code that gets reviewed rather than as scripts.
- CI/CD — GitHub Actions, GitLab CI or CodePipeline — and the discipline to keep pipelines boring.
- Python and Bash for automation, with enough software practice to write code others maintain.
- Cost management — last on their requirements list, first on your promotion case, because it is the only part of the job with a dollar figure attached.
- Hybrid and multi-cloud, usually AWS alongside Azure or an on-premise estate that is not going anywhere.
The Roles You Will Actually Meet
- AWS Cloud Engineer. The general title: provisioning, automation and maintenance of AWS environments.
- Senior or Lead AWS Cloud Engineer. Architecture decisions and mentoring. Reads and pays like the architect occupation.
- Cloud DevSecOps Engineer. AWS infrastructure with security-first automation, frequently cleared work. See our DevOps engineer guide for the delivery half.
- AWS Migration Engineer. Moving legacy systems and data into AWS. Often contract, and often the best exposure available to someone crossing over from systems administration.
- Cloud Platform or Infrastructure Engineer. Broader infrastructure with heavy AWS reliance. Closest to the network engineering side.
One correction worth making, because it appears in role lists on this subject: "AWS Hardware Engineer" is not a cloud engineering job. Those are data centre and hardware roles inside Amazon itself — server design, racks, physical infrastructure. It is a different occupation with a different skill set, and applying to it from a cloud engineering background is a mismatch on both sides.
Where the Jobs Are
Postings concentrate in Seattle, New York, Washington DC, Northern Virginia, Santa Clara and Columbia, Maryland. The DC, Virginia and Maryland cluster is where the federal and intelligence work sits, which is why the eligibility lines matter more there than anywhere else.
AWS engineering is also among the more remote-friendly technical specialisms, particularly at mid and senior level with commercial employers. Cleared work is the exception and is rarely remote. Expect an on-call rotation on most platform teams wherever you sit, and ask how often it comes round and whether it is paid before you accept.
Frequently Asked Questions
How much do AWS cloud engineers make in the USA?
There is no federal figure for the title. Job boards quote averages around $130,000 to $136,000, but those are self-reported estimates that disagree with each other. The measured medians are $99,130 for network and computer systems administrators, $134,050 for computer network architects and $135,980 for software developers — and which one the role resembles matters more than the platform.
Do AWS GovCloud jobs require a security clearance?
Not necessarily, and this is the distinction that matters most. GovCloud requires US Person status, which includes lawful permanent residents. A security clearance is a separate, higher bar requiring US citizenship and an employer to sponsor the investigation. Read which one a posting is actually asking for.
Can a green card holder work on AWS GovCloud?
Generally yes. A lawful permanent resident is a US Person under the export control rules GovCloud exists to satisfy. Cleared roles are a different matter and require citizenship.
Which AWS certification should I take first?
Solutions Architect – Associate, or SysOps Administrator – Associate if your work is operational. AWS removed exam prerequisites in 2018, so nothing stops you booking a Professional exam, but AWS recommends two or more years of hands-on AWS experience before those papers.
Is an AWS certification enough to get hired?
It gets your application read. In the largest and most certified platform market in US cloud, an associate certificate is the baseline rather than the differentiator. Production operational experience is what is scarce.
AWS or Azure for a US job search?
Whichever appears in the postings you want. AWS carries the largest overall share; Azure is stronger inside enterprises already committed to Microsoft. Depth in one beats familiarity with both.
Are AWS cloud engineer jobs remote?
Many commercial ones are, especially at mid and senior level. Cleared and GovCloud work is far more likely to be on-site. Expect an on-call rotation either way.
Can I get an AWS cloud engineer job with no experience?
Rarely straight away. Terraform and the AWS services are learnable in months; judgement about systems under load is not. This is usually a second job, reached from support, systems administration, networking or development.
People Also Search For
AWS cloud engineer salary USA
Board averages cluster around $130,000 to $136,000 and contradict one another. The measured medians are $99,130, $134,050 and $135,980 depending on which occupation the role belongs to.
AWS GovCloud jobs
Federal and defence work requiring US Person status — citizens and green card holders. Not the same thing as a cleared posting.
Remote AWS engineer jobs
Common with commercial employers past entry level, rare in cleared work. Ask about the on-call rotation before offer stage.
AWS Solutions Architect jobs
The design end of this work, and the band that reads like the $134,050 architect occupation rather than the $99,130 administrator one.
Entry level AWS cloud engineer jobs
Scarce as a first job. The realistic entry is a role with operational responsibility, learning AWS alongside it.
Terraform AWS jobs
The most requested infrastructure-as-code tool in these listings, and the easiest part of the job to learn.
AWS DevOps engineer jobs
Infrastructure plus the delivery pipeline, with both owned by the same person. See our DevOps guide for the four measures senior interviews run on.
AWS EKS and Kubernetes jobs
A narrower pool than general AWS work, which is exactly why it pays better. Note the CKA before CKS ordering if you are certifying.
More Job Guides
Comparing platforms and routes? These cover them:
- Cloud Engineer Jobs in USA — the occupation as a whole, and the declining job title that feeds it.
- Azure Cloud Engineer Jobs in USA — the other major platform, its gated certification path, and the Microsoft 365 work bundled into a lot of those postings.
- DevOps Engineer Jobs in USA — the delivery half of platform work, and the four measures senior interviews run on.
- Network Engineer Jobs in USA — the $34,920 between running a network and designing one.
- Cybersecurity Engineer Jobs in USA — the security specialisation, and the Kubernetes certification ordering trap.
- Cybersecurity Analyst Jobs in USA — the clearance rules in full.
- Software Developer Jobs in USA — the best-paid of the three occupations this work is counted under.
- Python Developer Jobs in USA — the automation language that carries most of this job.
This article is for general informational purposes and is not legal, immigration or careers advice. Wage data, employment projections, certification requirements, export control rules and clearance policy change, and posting counts on any job board are a moving figure rather than a statistic. Confirm the current position with the Bureau of Labor Statistics, AWS and the employer's own advertisement before applying or paying for any course.
