AWS Builder Center
AWS Free Tier 2026: What's Free and How to Start

AWS Free Tier 2026: What's Free and How to Start

Breaks down AWS's post-2025 free tier: the $200/6-month credit clock for new accounts vs. the always-free service list that never expires. Walks through securing the account, setting real budget alerts, and deploying inside the always-free list, plus the billing traps that catch beginners.

What's Actually Free on AWS Right Now

The first time I created an AWS account, I stared at the "Launch Instance" button for a solid two minutes before clicking it, convinced my card was about to get charged for something I didn't understand yet. It wasn't, that time. But the free tier everyone keeps recommending to beginners quietly stopped being the same free tier in 2025, and almost none of the guides floating around have noticed. Here's what's actually true right now, explained without assuming you already know what half these services do.

Two different free tiers exist at the same time

If you created your AWS account before July 15, 2025, you're on the legacy structure:
Service
Legacy free allowance
Duration
EC2
750 hours/month of a t2.micro or t3.micro
12 months
S3
5 GB storage, 20,000 GET, 2,000 PUT requests, 100 GB transfer out
12 months
RDS
750 hours/month of a db.t2.micro or db.t3.micro, 20 GB storage
12 months
API Gateway
1M REST + 1M HTTP API calls, 1M WebSocket messages, 750K connection minutes
12 months
Plus a separate list of "Always Free" services that never expire, covered below.
If you're signing up today, you're on a different plan. New accounts get $200 in total credits: $100 the moment you sign up, and up to $100 more for completing five onboarding tasks worth $20 each: launching an EC2 instance, trying a foundation model in the Amazon Bedrock playground (AWS's AI service), building a small app on AWS Lambda, creating an RDS database, and setting up a cost budget. That whole $200 pool expires in 6 months or when it hits zero, whichever happens first.
Here's the part that surprises people. EC2, RDS, S3, and API Gateway, the services most beginner tutorials lean on, are no longer on a "runs forever for free" list for new accounts. All four are covered by your $200 clock now. On the legacy structure none of them were permanent either, they ran for exactly 12 months from sign-up, then started billing. So the free tier isn't one single thing anymore. It's a shrinking pot of credit (or, for legacy accounts, a ticking 12-month clock) for anything server-, database-, storage-, or gateway-like, plus a separate, permanent list of lighter services that never touch either one.

What never touches your credits

These services run on their own monthly allowance and don't draw from your $200 pool or your 12-month clock, on any account, new or old:
Service
What it does
Free every month
AWS Lambda
Runs your code on demand, no server to manage
1,000,000 requests + 400,000 GB-seconds of compute
Amazon DynamoDB
A managed NoSQL database
25 GB storage + 25 provisioned read/write units
Amazon SNS
Sends notifications (push, SMS, email)
1,000,000 publishes + 100,000 HTTP notifications
Amazon SQS
A message queue for connecting services
1,000,000 requests
CloudWatch
Monitoring, metrics, and alarms
10 custom metrics, 10 alarms, 1,000,000 API requests
CloudFront
Content delivery network (CDN)
1 TB data transfer out + 10,000,000 HTTP/HTTPS requests
Lambda and DynamoDB are the two truly indefinite building blocks here, and that combination alone is enough to run a useful backend: a function with a real database behind it, no server rental required. Worth flagging a correction to how this table usually gets drawn, and how it was drawn in an earlier version of this one: it should not include S3 or API Gateway. Both are 12-month-free for legacy accounts and credit-draining for new accounts, same bucket as EC2 and RDS, not permanent allowances. If you want a REST endpoint in front of Lambda that stays free indefinitely on any account, skip API Gateway and use a Lambda Function URL instead, an HTTPS endpoint attached directly to the function, billed as part of Lambda's always-free requests rather than as a separate line item. It's less feature-rich than API Gateway (no built-in usage plans or API keys), but for a beginner project it's the difference between "free forever" and "free until month 13."

Hosting a static site, mostly for free

This is probably the first thing most beginners actually want to do, and it's worth being upfront about scope: this method is for a static site only, a portfolio, a resume page, a React or Vite build with no backend server, nothing that needs to run code or talk to a database on the server side. If that's what you're building, S3 is still the easiest way to get there. It's just not free indefinitely the way Lambda or DynamoDB are:
  1. Create a bucket. Any valid, globally unique name works.
  1. In the bucket's Properties tab, turn on Static website hosting and set index.html as the index document.
  1. Under Permissions, turn off Block all public access, then add a bucket policy that allows s3:GetObject to everyone (AWS's own S3 hosting tutorial has the exact JSON to paste in).
  1. Upload your index.html and the rest of your files.
  1. Your site is now live at a URL shaped like  http://your-bucket-name.s3-website-<region>.amazonaws.com .
For a small static site, the S3 storage and request costs are tiny, well under a dollar a month even after your free window ends, so this isn't a trap the way an idle NAT Gateway is. It's just not the "never expires" kind of free the always-free list gives you.
That URL only speaks plain HTTP though, no padlock icon in the browser, and no custom domain. Put Amazon CloudFront (AWS's content delivery network) in front of the same bucket to get both. CloudFront's free allowance is genuinely permanent, on both account types, and doesn't touch your $200 credit or your 12-month clock at all: 1 TB of data transfer out and 10 million HTTP/HTTPS requests every month, forever. So the part of this setup that scales with traffic (transfer and requests) stays free forever through CloudFront, even though the storage sitting in S3 behind it eventually starts billing at a few cents a month.
If your site isn't static, if it needs a backend, server-side rendering, or a full Next.js app that isn't just a static export, this whole section doesn't apply. That's a different job (AWS Amplify Hosting or an EC2-backed setup), and it draws from your credit pool instead of the free-forever list too.

The walkthrough: lock the account down, then build

Step 1: secure the account, and don't hand yourself a permanent admin key. The very first login is your "root" account, and it has unrestricted power over everything, including billing. Turn on MFA for it under Account settings > Security credentials > Assign MFA device, preferably with a passkey or hardware security key rather than an app-based code, and never generate access keys for root.
For everyday work, AWS's current guidance is to avoid a long-lived IAM user with AdministratorAccess and static keys, that's exactly the kind of credential that ends up pasted into a public GitHub repo. Two options that hold up better:
  • IAM Identity Center (formerly AWS SSO): sign in through it and it hands you short-lived, temporary credentials instead of a permanent access key. This is what AWS itself recommends for human users, even solo beginners.
  • If you specifically need an IAM user with programmatic access (some CLI tools still expect one), scope its policy to what you're actually doing, S3 and Lambda for this walkthrough, for example, instead of AdministratorAccess, and rotate or delete the access key once you're done experimenting.
Either way, the goal is the same: nothing long-lived and unrestricted sitting around waiting to leak.
Step 2: set a budget alert before you deploy anything. From the console's "Explore AWS" widget, choose Set up a cost budget using AWS Budgets, then pick Use a template (simplified) > Monthly cost budget. Name it, set the amount to $100 (your credited amount), and enter your email. AWS will now email you automatically at 50%, 25%, and 10% of your remaining credits, and again at 15, 7, and 2 days before your 6-month window closes.
The same thing from the command line, if you'd rather script it:
aws budgets create-budget \
--account-id <your-account-id> \
--budget file://budget.json \
--notifications-with-subscribers file://notifications.json

Step 3: build inside the always-free list first. For most beginner projects, that means Lambda and DynamoDB, with a Lambda Function URL standing in for API Gateway and no EC2 server involved at all. A minimal function deploy from the CLI looks like this:
aws lambda create-function \
--function-name my-first-function \
--runtime python3.12 \
--handler app.handler \
--zip-file fileb://function.zip \
--role arn:aws:iam::<account-id>:role/lambda-basic-execution

aws lambda create-function-url-config \
--function-name my-first-function \
--auth-type NONE

If your project actually needs a full server (a Node/Express app, something that has to run continuously), that's exactly what your $200 credit exists for. Just watch the burn rate weekly in the Billing console. It disappears faster than "6 months of casual use" makes it sound, especially the moment you leave an instance running overnight instead of stopping it.

The $6 mistake that taught me to actually check the dashboard

A while back I set up a NAT gateway (a component that lets private servers reach the internet without being exposed to it) just to see how it worked, then forgot about it over a weekend. I came back to a small charge sitting on my bill, about $6, for two days of a gateway nobody was using. Not a disaster, but exactly the kind of charge that shows up with zero warning if you're not actually looking.
The same handful of things catch almost everyone starting out:
Trap
Cost
Why it sneaks up on you
Idle Elastic IP
~$3.60/month
Bills the moment it's detached from a running instance
NAT Gateway left running
~$32/month
Charges just for existing, before it moves a single byte
EBS volume on a stopped instance
Varies by size
Keeps billing even while the attached server is off
Data transfer past 100 GB/month
~$0.09/GB
Adds up fast serving images or video straight out of S3 instead of through CloudFront
The fix for all four is the same single habit: open the Billing and Cost Management console once a week during your free window, not just when the alert email shows up.

What's next

Getting a project to live inside the always-free list is the easy half of this. The half that actually burns people is what happens later, when a teammate pastes an AWS access key into a public GitHub repo at 1 AM before a hackathon deadline, and a bot finds it in under two minutes and starts mining crypto on someone else's dime. I'll be writing about that next: IAM done properly, before it turns into a $400 lesson instead of a free one.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article