How to use the AWS Free Tier to practise for certification
You can get most of the hands-on practice an AWS certification demands from the AWS Free Tier, without paying for a lab platform and — with a little care — without a surprise bill. Hands-on time matters more than it first appears: AWS exam questions are heavily scenario-based, and the difference between recognising a service’s name and having actually clicked through its console is often the difference between guessing and knowing. The Free Tier gives you a real account with real services, which beats any simulator for building that familiarity. It does come with rules you should understand before you create anything, and one safety habit — a billing alarm — that you should set up on day one. Here is how to use it well, which starter labs map to the concepts the exams actually test, and where to practise when you would rather not use your own account at all.
Why hands-on practice beats watching videos
Video courses and revision notes teach recognition; the exams test application. A typical associate-level question describes a small scenario — a company with a workload, a constraint, a problem — and asks which service or configuration solves it. If you have only ever read about S3 storage classes or IAM policies, every option looks plausible. If you have created a bucket, attached a policy, and watched a request get denied, the right answer tends to surface from memory of what actually happened.
There is also a plainer reason: doing something is a far stronger memory act than watching someone else do it. An hour spent launching, breaking and fixing a small setup will stick where three hours of passive video fade. The Free Tier exists precisely so you can have that hour without a bill, and treating it as your lab — alongside structured revision and practice questions — is the study pattern that reliably works.
What the AWS Free Tier actually gives you
Historically the Free Tier came in three broad flavours: always-free allowances that never expire (a monthly quantity of some services, such as a number of Lambda invocations), 12-month allowances that start when you open the account (limited monthly usage of services like EC2 and S3), and short free trials on specific services. In 2025 AWS moved new accounts to a credit-based free plan, which changes how the allowance is packaged for anyone signing up now.
The honest caveat: the exact terms, credits and time limits change, and any blog that quotes you specific amounts will eventually be wrong. Before you create an account, read AWS’s official Free Tier page and note which plan applies to you, what is included, and when it expires. The principle holds either way — a new personal account gives you enough free, real AWS to cover everything a foundational or associate exam expects you to have touched, provided you clean up after your labs and keep an eye on billing.
Five starter labs mapped to exam concepts
You do not need elaborate projects to start — you need small, finishable labs that each land a concept the exams test. Work through these in order, deleting what you create when you finish each one:
- Launch and terminate an EC2 instance — pick the smallest eligible instance type, connect to it, then terminate it. This lands compute fundamentals: instance types, key pairs, security groups, and why a stopped instance is not the same as a terminated one.
- Create an S3 bucket and upload a file — then explore permissions, try making an object public, and read the warnings AWS shows you. This lands object storage, bucket policies, and the access-control questions every exam includes.
- Create an IAM user with a minimal policy — sign in as that user and watch what it can and cannot do. Least-privilege access is one of the most heavily tested ideas in every AWS exam, and it only truly clicks once a permission denial has happened to you.
- Set a CloudWatch alarm — starting with the billing alarm described below, then one on an EC2 metric. This lands monitoring and alerting, the heart of the CloudOps syllabus and a recurring theme everywhere else.
- Write and invoke a Lambda function — the console’s hello-world template is enough. This lands serverless: triggers, permissions via roles, and why there is no server to manage — central to the Developer exam and present in all of them.
The billing alarm: set it up before anything else
The first thing to build in a new AWS account is not a server — it is the alarm that tells you if you are about to be charged. Enable billing alerts in your account settings, then create a CloudWatch billing alarm that emails you when your estimated charges exceed a small threshold, even one close to zero. It takes a few minutes and converts the Free Tier’s main anxiety — the surprise bill — into an early warning you will almost certainly never receive.
Pair the alarm with two habits. First, delete what you create: terminate instances, empty and remove buckets, and tear down anything a tutorial had you build, ideally in the same session. Second, glance at the billing dashboard once a week while you are studying; it shows your Free Tier usage against the allowance. Learners who follow these three practices — alarm, clean-up, weekly glance — overwhelmingly pay nothing, and the habit itself is exam-relevant: cost management is part of every AWS syllabus.
When you would rather not use your own account
If you are hesitant to attach a payment card to a personal account, or you want guided practice, AWS Skill Builder is the official alternative. Its free tier includes digital courses and learning plans aligned to each certification, and AWS Builder Labs and workshops provide sandboxed environments where you follow structured exercises in an AWS-provided account — nothing you do there can touch your own bill. Availability of specific labs varies between the free and paid tiers of Skill Builder, so check what is currently included.
A sensible combined approach: use Skill Builder or workshops for guided, safety-netted walkthroughs of unfamiliar services, and your own Free Tier account for the unscripted practice — building something without instructions, breaking it, and fixing it — that guided labs cannot give you. The unscripted kind is what interviewers probe for and what scenario questions reward, so do not let the sandbox become the only place you practise.
Fitting hands-on work into your revision plan
The pattern that works is study–do–test, in short cycles. Revise a topic, immediately do a small lab on it, then answer practice questions on the same area and notice how differently the scenarios read once you have touched the service. Do not front-load weeks of theory and save the console for the end — the hands-on time is most valuable interleaved, when it can anchor what you just learnt.
Keep the labs proportionate to your exam. For the Cloud Practitioner, the five starter labs above are genuinely enough — the exam assumes familiarity, not depth. For the associates, extend each lab in the direction of your exam’s syllabus: architecture trade-offs for Solutions Architect, deployment and code-adjacent services for Developer, monitoring and operations for CloudOps. And if you are turning labs into portfolio pieces for a job search, our guide on AWS portfolio projects that get you hired picks up where these starters leave off.
Original practice questions, timed mock exams and revision notes. No card, nothing to pay.