What Is AWS and Can Learning It Make You Money?

Logeshwaran

AWS is rented computing. Amazon owns enormous buildings full of servers and rents you slices of them by the hour, the gigabyte or the request — you ask for a server, you get one in about a minute, and the meter runs until you switch it off. Can learning it make you money? Yes, but not from AWS. AWS never pays you; employers and clients do, and there are three routes to that money. The job route is the most reliable, the freelance route pays best and is hardest to start, and the certification route on its own pays nothing — a certificate is a syllabus and a signal, not an income.

⚡ Quick Answer

What it is → computing you rent instead of buy, billed by use. The rental analogy, and where it breaks.

What to learn first → IAM, EC2, S3, VPC, RDS, CloudWatch. Six services, and what each replaces.

⚠️ Free is not free → a spare IP address costs $0.005 an hour doing nothing. The six line items that bill beginners.

The money → job first, freelance second, certification third and only as a door opener. Ranked, with real timelines.

About to buy a course? Read what AWS will not do for you first.

The $41 that started this

Jake sells and repairs phones. Three months ago a customer mentioned that cloud people earn well, and Jake — quietly worried about where a phone shop is in ten years — opened an AWS account that evening, followed a tutorial, built a small site, and closed the laptop.

Six weeks later he got a bill for $41.

"It said free," he told Ethan, in the tone of a man who has been robbed. "I have the screenshot."

"What did you leave running?"

"Nothing. I turned the server off."

"You turned the server off," Ethan said. "Did you delete the disk? The address it was sitting on? The thing you set up so it could reach the internet?"

There was a pause of the kind that costs $41.

The two questions Jake asked next are the two everybody types into a search box. What is this thing? And is there real money in it, or is that just something people say?

What AWS actually is, in plain English

AWS stands for Amazon Web Services. It is the part of Amazon that has nothing to do with parcels.

Amazon owns data centers — buildings full of server racks, storage arrays, switches, generators and industrial cooling. Running one is a construction project. AWS rents you slices of it instead, by the hour, the gigabyte, or the individual request.

The rental analogy, and exactly where it breaks

Ethan's version, which Jake understood immediately: "You don't own the van you hire for a house move. You don't service it, insure it, or park it for the eleven months you don't need it. You pay for the two days, and if the gearbox fails that's their problem."

"So it's van hire for computers."

"For two days, yes. Here's where it breaks. The van company notices when you don't bring the van back. AWS doesn't. There is nobody at the counter. Rent a server and forget it, and it runs for four years and bills you every hour, and nothing feels like a mistake until the statement arrives."

Regions, zones, and the three meters

A region is a geographic area — Northern Virginia, Ireland, Mumbai, Sydney. You create everything in one, and things in different regions do not automatically see each other. An availability zone is one or more separate data centers inside a region, far enough apart that flooding one spares the other; spreading a system across two is the whole mechanism behind "highly available".

The console shows one region at a time, so anything running in a region you never look at is invisible and still billing.

And there are three meters. Confusing them is where beginners lose money.

  • Per hour, while it exists. Servers, load balancers, gateways, spare IP addresses. Bills whether or not anybody uses it. The dangerous meter.
  • Per gigabyte, per month. Storage. Cheap per unit, and it accumulates, because deleting things is nobody's favorite job.
  • Per request. Function calls, data transfer out. Individually trivial. This one surprises companies rather than beginners.

"So the trap isn't using it," Jake said. "The trap is owning it." Better phrased than most textbooks manage.

The handful of services that matter, and what each replaces

AWS has hundreds of services. That scares people off and it should not, because nobody knows them all. The catalog is a supermarket and you are shopping for six things. The useful question is not "what does it do" but "what did we do before it existed".

Service What it is What it replaced
IAM Who can do what. Free. The keys, and who has a copy
EC2 A virtual server, running by the hour The beige box humming in the cupboard
S3 Storage for files, per GB per month The shelf of external drives
VPC Your own private network inside AWS The office switch, cabling and firewall
RDS A managed database, patched and backed up A database server and its caretaker
CloudWatch Metrics, logs and alarms The colleague who noticed the disk was full
Lambda Run code on an event, no server A script on a machine left switched on

Learn the first six properly and you can read almost any architecture diagram in the industry. For the long version of the two that matter most, read what Amazon EC2 is in plain English, then what Amazon S3 stores and why it is not a hard drive.

"Seven," Jake said. "I was told there were two hundred."

"There are more than that. Most exist because one very large customer needed one very specific thing. Anyone telling a beginner to learn the catalog is not teaching, they are filling a course."

The one that gets skipped and should not

IAM — Identity and Access Management — is the boring one at the top of that table and the one to learn first. It decides which people, programs and services can touch which resources.

It gets skipped because it costs nothing and produces nothing visible. It matters because every serious cloud disaster is an identity story — somebody had permissions they should not have had, or a key ended up somewhere public. In the exams, security is the largest domain on the Solutions Architect Associate, at 30 percent.

Two things to do on day one, five minutes each: turn on multi-factor authentication for your root account, then stop using the root account and create yourself a normal user instead.

The free tier, and exactly how it bills you anyway

This is what the query is really asking, and almost nobody answers it honestly, because "here is how the free thing charges you" is a worse advert than "get started free today".

First: what changed, because the old advice is now the wrong advice

For years a new AWS account meant twelve months of free tier allowances, and every tutorial written before then assumed it — this page included. That was true then. AWS restructured new-account free access in 2025. A new account now picks one of two plans.

  • The Free plan. $100 in credits immediately and up to $100 more as you explore — up to $200 over six months. AWS states plainly that you will not see charges on your bill; credits cover anything past a free limit. The catch is the ending: the account closes on its own six months after you open it, or when the credits run out, whichever comes first. AWS keeps your data 90 days, and you can upgrade to keep everything.
  • The Paid plan. Full access, pay-as-you-go, also eligible for up to $200 in credits. Once credits are gone, anything outside the always-free limits lands on a real bill.

More than 30 services are always free within monthly limits on both plans — that part did not go away. And existing customers keep the old Free Tier benefits unchanged, but get no credits and no free plan. If you opened an account in 2021 and somebody mentions $200 of credits, that is not for you.

"Hang on," Jake said. "If the Free plan can't charge me, why did I get a bill?"

"Because you gave them a card and made an account that bills. Most people do, because most tutorials assume it. And a beginner often cannot tell which kind they made — which is why the next bit matters whichever plan you are on."

The six line items that bill beginners

Every one charges while doing nothing at all. That is the thing nobody says out loud: the bill is not driven by what you use, it is driven by what exists.

The thing Why it bills How it happens
A public IPv4 address $0.005 per hour, in use or idle, since 1 February 2024 You deleted the server, not the address
A NAT gateway $0.045 per hour plus $0.045 per GB processed A tutorial said to add one so private servers could update
An orphaned disk (an EBS volume) Per GB per month, indefinitely You terminated the server; the disk survived
A load balancer Per hour from the moment it exists A tutorial you stopped halfway through
An instance bigger than you meant Per hour, several times the small-instance rate The dropdown defaulted outside the allowance
Anything in another region Normally, and invisibly You switched region once and never switched back

Jake's $41 was three of these at once: a reserved address, the disk from the server he thought he had deleted, and — the one that hurt — a NAT gateway from a networking tutorial, charging $0.045 an hour for six weeks. Roughly $32 a month for plumbing he never used.

"That's the bit I object to," Jake said. "A gateway passing no traffic bills the same as one that is? If I open my fridge and the light comes on, I don't get charged for the light."

"You're not wrong to be annoyed. It's reserved capacity rather than consumption — you asked for a thing and it's standing there being available. It punishes beginners hardest, because a beginner is the person most likely to build something and walk away. I'm not defending the model. I'm telling you where the meter is."

⚠️ Stopped is not deleted — the one that catches everybody

Stopping a virtual server stops the per-hour charge for the server. It does not delete the disk, which keeps billing per gigabyte, or release the reserved address, which keeps billing per hour, or remove the gateway, load balancer or snapshots.

Finished with an experiment? Delete it, do not stop it, then check the billing console two days later. Stopping is for tonight. Deleting is for done.

The ten minutes that prevent all of it

  • Set a budget alert at $1. In AWS Budgets, a cost budget with an email alert. The point is not the money — it is finding out in hours instead of at month end.
  • Turn on multi-factor authentication for the root account, then stop using it. A compromised root account dwarfs that whole table.
  • Pick one region and stay in it. When something looks empty and the bill disagrees, the answer is another region.
  • Read the bill by service. The console breaks charges down by service name, and the name tells you what to delete. Beginners never open it.
  • Teardown pass after every tutorial. Instances, volumes, snapshots, addresses, gateways, load balancers, buckets. Seven things, two minutes.
  • Done entirely? Close the account. A dormant account with a card attached is a liability for no benefit.

Ethan is blunt: "Cost control isn't an advanced topic you get to later. It's lesson one, because it's the only mistake here that follows you home."

What genuinely is free, and stays free

Not everything is a trap. The always-free allowance we checked today, because beginners use it most: AWS Lambda includes one million requests and 400,000 GB-seconds of compute per month. For a hobby project that is effectively unlimited. IAM is free too.

So a serverless design is the cheapest way for a beginner to build something real: it inverts the dangerous meter, because nothing exists between requests and nothing bills between them.

The three money routes, ranked honestly

Start with the sentence the promotional material never says: AWS does not pay you. There is no revenue share and no mechanism by which knowing AWS produces money on its own. Employers pay you. Clients pay you. AWS skill is one input into what they will pay.

Route Time to first money Hardest part Verdict
1. Job 3–6 months if already in IT, 6–12 if not Getting past the first filter with no experience Most reliable, by a wide margin
2. Freelance 12 months plus, realistically The first client, trusting you with their business Best per hour, worst to start
3. Certification Never, on its own Believing the marketing A door opener for 1 and 2, not a route

Route 1: the job route, which wins and it is not close

Somebody else carries the risk and finds the clients, and you get paid while you are still learning. People underrate that.

The realistic entry points are cloud support, junior infrastructure roles and support-engineer jobs. Note what they share: they are operational. You start by keeping things running and working out why they broke, which is the fastest way to learn this.

What gets you through the door is not the study. It is having built something and broken it — an application you deployed, that fell over, that you fixed. That is a five-minute interview answer nobody can fake.

"Six to twelve months," Jake said. "The advert I saw said six weeks to a cloud career."

"The advert was selling a six-week course. I'd want to know how many of their students already worked in IT, and they won't tell you, because that number explains the testimonials. From a phone shop counter, six weeks gets you a vocabulary. Twelve months gets you employable, which isn't slow — it's a career change in a year."

Route 2: the freelance route, and the one job that works early

Freelance cloud work pays better per hour and is far harder to start, for a reason unrelated to technical skill: a client is handing a stranger the keys to their business. Trust is the product. So the realistic sequence is get the job first, do it two or three years, then take clients.

One exception works early, and Ethan is keen on it. Cost optimization. Small companies waste money on AWS constantly — oversized instances, disks belonging to servers deleted years ago, test environments running full size all weekend. Jake's mistakes, times a hundred.

"Want a first client? Offer to audit a small company's AWS bill for a flat fee, and if you don't find at least your fee in savings, they don't pay. You will find it. The invoice writes itself, because the value has a number on it: this cost you $380 a month, now it costs $90. Nothing else a beginner can sell has that property."

Unglamorous — and the only cloud work a beginner can sell where the buyer verifies the result on their own bill.

Route 3: the certification route, which is not a route

Here we part company with almost every other page answering this query. A certification is two useful things. It is a syllabus written by people who know the material, which solves the beginner problem of not knowing what to learn next. And it is a signal — a filter some employers use, and a requirement for firms in the AWS partner network, which is why an employer might pay for yours. What it is not is income.

"Now hang on," Jake said. "Every person I know who's done well in IT has a certificate on the wall. You're telling me it doesn't matter?"

"The order is backwards. They didn't get the certificate and then become good. They were doing the work, the certificate confirmed it, and the wall got one more frame. Take the exam first if you like — it structures six weeks of study. Just don't sit there afterwards waiting for the phone. The certificate isn't the qualification. It's the receipt."

"And building an app on AWS and selling it?"

"That's a business, and AWS is where it runs, the way a shop needs a lease. It answers how do I make money, not how do I make money from AWS — and the pages that blur the two are the pages selling something."

What the certifications cost, and which one to sit

If you decide the syllabus is worth having, here are the numbers, checked against AWS on 9 August 2026. AWS prices by level, one attempt each: foundational $100, associate $150, professional $300, specialty $300.

The Cloud Practitioner (CLF-C02) is the foundational one: 65 questions, 90 minutes, $100, valid three years, no prerequisites. AWS aims it at people new to the cloud, including non-IT backgrounds — which is to say, at Jake.

The Solutions Architect Associate (SAA-C03) is the one most job listings mention: 65 questions, 130 minutes, $150, valid three years. Your result is a scaled score from 100 to 1,000 and the pass mark is 720, scored compensatorily, so you need only pass overall. AWS recommends about a year designing on AWS and says it does not require deep hands-on coding.

The four domains tell you where to spend your evenings:

  • Secure architectures — 30%. The largest domain. The IAM material you were tempted to skip.
  • Resilient architectures — 26%. Availability zones, failover, backups, what happens when a thing dies.
  • High-performing architectures — 24%. Picking the right storage, database and compute.
  • Cost-optimized architectures — 20%. The exam agrees: cost is a design skill.

One rename to know before you buy a course

What older material calls the SysOps Administrator – Associate is now the AWS Certified CloudOps Engineer – Associate (SOA-C03) — same 720 pass mark, 50 scored questions plus 15 unscored. That was true then, AWS moved it since, and a course still using the old name is telling you when it was last updated. Ten seconds of checking, and it is the cheapest quality check you have.

How to prepare without spending anything extra

AWS gives away more preparation material than people realize. On AWS Skill Builder there are free official practice question sets of 20 questions, written by AWS, with feedback on each answer — the fastest honest read on whether you are ready. There is a free two-hour exam prep course per certification, and AWS Cloud Quest, a free game that teaches by making you build. The paid subscription starts at $29 a month, worth one month near the end and not before.

Use the free set before you book. A failed attempt costs the whole fee again — a $150 way of learning what twenty free questions would have told you in fifteen minutes.

🔬 How this was tested

Every price, exam number and free-tier rule here was read from AWS's own pages on 9 August 2026: the free tier page and FAQs for the two plans, the credits and the six-month closure; the VPC pricing page for the NAT gateway and public IPv4 rates; the Lambda pricing page; the certification policy pages for the $100 / $150 / $300 levels; and the exam guides for question counts, durations, domains and the 720 pass mark. Prices and free-tier terms do move, though, and they move quietly. Check the current page before you commit to anything, and if you find something here that has changed, tell us — you will be saving the next person a surprise on their card.

What we could not verify today, and therefore did not state: any salary figure. The earlier version of this page quoted a salary band and we have not repeated it, because we found no source we would stand behind today — check live listings in your own market. We also did not verify the always-free allowances beyond Lambda, the waiting period after a failed attempt, or a count of AWS services, so none appear here as numbers.

Prices and exam details change. Check the official page before you pay, and tell us if anything here has moved.

What AWS will not do for you

1. A certification will not get you hired on its own. Worth repeating, because it sells the most courses. It gets a human to read your application a little longer.

2. It will not make you money passively. No configuration of AWS produces income while you sleep. Every route runs through somebody deciding to pay you.

3. It is not cheaper than a shared host for a small website. If Jake wants a five-page site for the shop, a $5-a-month shared host beats anything he builds on AWS on price and effort. AWS wins when you need to scale or fail over. For a brochure site it is the wrong tool.

4. It will not teach you the fundamentals you still need. Networking, Linux, DNS, how a database behaves under load. The cloud sits on top of those. People who skip them can follow a tutorial and cannot debug anything, and it shows in an interview immediately.

5. It will not protect you from your own mistakes. This is the shared responsibility model, worth learning by name because it is on every exam. AWS secures the cloud — buildings, hardware, hypervisor. You secure what you put in it — permissions, patches, data. Storage left open to the world is not an AWS failure. It is a setting you chose.

6. It will not stop billing because you stopped paying attention. The meter has no opinion about whether you are still interested.

🙋‍♂️ Jake's Reality Check

"Straight question. I'm thirty-eight, I run a phone shop, I have an hour most evenings. Is this a real option for me, or am I reading adverts written for other people?"

It is real, and an hour an evening is enough — but a year of it, not a month. Decide that going in rather than discovering it in week six. What you have that a graduate does not is a decade of handling people whose thing is broken and who are upset about it. That is most of what operations work is, and why support teams hire out of retail more often than people expect.

Two cautions. This is not more money for less work — on call at two in the morning is a real thing, and the first year is a pay cut for many career changers before it is a raise. And do not shut the shop to study. Learn on the shop's own problems: put the backups somewhere sensible, cost out running the till if the shop flooded.

And the honest version of the money question: the people doing well at this are not the ones who found the fastest route. They are the ones still doing it eighteen months later.

Questions people actually ask about this

What is AWS in simple terms?

AWS is Amazon Web Services, and it is rented computing. Amazon owns very large buildings full of servers, storage and networking, and rents you slices of them by the hour, the gigabyte or the request. You get a server in about a minute, and the meter runs until you switch it off.

Is AWS free to use?

Partly, and the free part changed shape in 2025. A new account picks a Free plan or a Paid plan. The Free plan gives 100 dollars in credits immediately and up to 100 more as you explore, and closes by itself six months after you open it or when the credits run out. More than 30 services stay free within monthly limits on both plans.

How do people get a surprise AWS bill on the free tier?

Almost always from something that charges by the hour while doing nothing. A public IPv4 address costs 0.005 dollars an hour whether in use or idle. A NAT gateway costs 0.045 dollars an hour plus 0.045 per gigabyte. A disk keeps billing after you terminate its server, and a load balancer bills from the moment it exists.

Which AWS services should a complete beginner learn first?

Six, in this order: IAM for permissions, EC2 for virtual servers, S3 for object storage, VPC for the network everything sits inside, RDS for managed databases, and CloudWatch for monitoring and alarms. Add Lambda once those make sense. Nobody knows the whole catalog anyway, including the people who work there.

Do I need to know how to code to learn AWS?

Not to start, and not for the entry-level certifications. AWS says outright that the Solutions Architect Associate exam does not require deep hands-on coding experience. What you need is comfort with a command line, an idea of how networks and Linux behave, and patience with error messages.

Can you really make money from AWS?

Yes, but not from AWS. AWS never pays you. Employers and clients pay you, and AWS skill is one input into what they will pay. The three routes are a job, freelance work, and a certification used as a door opener into either. The job route is the most reliable by a wide margin.

How long does it take to get a job with AWS skills?

Starting from no IT background, plan on six to twelve months of study plus something you have built and can talk through, not six weeks. If you already work in IT support or development, three to six months is realistic. What moves the timeline most is having built and broken something real.

Is the AWS Cloud Practitioner certification worth it?

It is worth it as a syllabus and as a signal, and not as a plan. For 100 dollars you get a structure written by people who know the material, a deadline that makes you finish, and vocabulary you can use without hedging. It will not put you at the front of a queue.

How much do AWS certification exams cost?

AWS prices by level: foundational exams at 100 US dollars, associate at 150, and both professional and specialty at 300, with the price valid for one attempt. So the Cloud Practitioner is 100 dollars and the Solutions Architect Associate is 150. A failed attempt costs the full fee again.

What is the passing score for the AWS Solutions Architect Associate exam?

Results come back as a scaled score from 100 to 1,000 and the minimum passing score is 720. Scoring is compensatory, so you need only pass the exam overall, not each section. It is 65 questions in 130 minutes for 150 US dollars, across four domains weighted 30, 26, 24 and 20 percent.

Can I freelance with AWS as a beginner?

Not easily, because a client is handing a stranger the keys to their business and trust is the product. The exception that works early is cost work: small companies routinely pay for idle resources, and finding those and switching them off produces a number you can put on an invoice.

Will an AWS certification alone get me hired?

No, and this is the most oversold claim in the subject. A certification gets a human to read your application a little longer. What gets you hired is describing something you built, what broke, and how you worked out why. An interviewer can tell the difference within two questions.

Is AWS better than Azure for getting a job?

Look at the actual job listings in your own city and count. Whichever name appears more often is your answer, and it varies by region and industry. The concepts transfer anyway: virtual machines, object storage, identity, networking and managed databases exist on both under different names.

How do I stop AWS from charging me?

In this order. Set a budget alert at a dollar or two so you find out in hours rather than at month end. Read the bill by service in the billing console, because the service name tells you what to hunt. Check every region. Then delete rather than stop, because stopped servers keep their disks.

Where to go from here

The order that works is boring. Set the budget alert. Turn on multi-factor authentication and stop using the root account. Learn EC2 and S3. Deploy one small thing, break it, fix it, delete it, do it again. The map for the rest is where this free AWS series starts and what it covers.

If your interest is the AI side rather than the infrastructure side, the path forks here. Start with AI, machine learning and generative AI explained as one nested ladder, which also costs out which AI exam is worth sitting. Then what Amazon SageMaker is in plain English is the service that route runs through, and problem formulation — does your business even need machine learning stops people building something nobody needed. If you would rather work with data than models, data fundamentals, ingestion and transformation is the entry point.

What Jake did with the $41

He deleted the gateway, released the address, found two disks he did not know he owned, and set a budget alert at one dollar. Eleven minutes. Then he wrote the $41 on a sticky note and stuck it on the monitor.

"Tuition," he said. "Cheapest lesson in the shop this year. So — honest answer. Can I make money at this?"

"Yes. Not quickly, not passively, and not by buying a certificate and waiting. A year at an hour an evening and you'd be employable. And you already know something plenty of certified people don't: what a NAT gateway costs when nobody's watching."

AWS is not magic and it is not a scam. It is rented computing with a meter that never sleeps, and the money in it is real and slower than advertised.

Revision note. Originally published 19 April 2022 as the opening post of our free AWS series, lightly updated in October 2024, rewritten on 9 August 2026. Two things drove the rewrite. AWS restructured free access for new accounts in 2025 — the twelve-month free tier every tutorial written before then assumed, ours included, is not what a new account gets today, so that section was rebuilt around the two plans and the credits, checked against AWS on the day of writing. And the exam lineup moved: the operations associate certification is now the CloudOps Engineer Associate. We also dropped the salary band the original quoted, because we could not verify a figure we would stand behind, and a number we cannot check is worse than none. If something here does not match what you see in your own console or when you book an exam, please write in through the contact page. And if you have had your own $41 lesson, do tell us. It helps more people than you would think.

Related