AWS Free Tier in 2026: Build, Learn, and Avoid Surprise Charges
A practical guide to the new AWS Free Tier, the $200 credit model, free offers, monitoring, alerts, and building portfolio projects while keeping spending under control
Key idea: the AWS Free Tier is not simply “$100 of free AWS.” New customers receive $100 in credits and can earn up to another $100 through activities. Credits are a balance, not a universal spending cap.
What changed?
AWS changed the Free Tier for new customers on July 15, 2025. New customers receive USD $100 at signup and can earn up to another USD $100 through activities in the AWS Console, for up to USD $200 in credits. The Free account plan is designed for exploration and proof-of-concept work for up to six months.
The Free account plan ends after six months or when the credits are fully used, whichever comes first. AWS says the Free plan does not incur charges until the customer upgrades to the Paid plan. Credits themselves expire 12 months after account creation.
Do not confuse the six-month Free plan with the 12-month credit validity. They are different clocks.
The four things beginners should understand
$200 is not a monthly allowance
The credits do not reset every month. Eligible usage consumes the balance. They also do not make every AWS service free. On a Paid plan, once credits are exhausted or expire, standard pricing can apply.
Think of the credits as a prepaid learning budget. The Free plan provides stronger protection because AWS says you will not be charged unless you upgrade.
How to earn the extra $100
The current activities appear in the Explore AWS widget on the AWS Console Home. AWS currently lists activities such as launching an EC2 instance, using a foundation model in Bedrock, setting up an AWS Budgets cost budget, creating a Lambda web app, and creating an RDS database. The exact activities and deadlines can change, so the console is the source of truth.
Earning credits does not necessarily mean the activity itself costs zero. AWS explicitly notes that some activities incur service charges that are deducted from your Free Tier credits.
Services that are useful for a low-cost portfolio
Do not memorize every offer. Check the current Free Tier page before launching a resource. The following services are particularly useful for small projects:
Example MVP: S3 + CloudFront for the frontend, API Gateway + Lambda for the API, DynamoDB for data, and Cognito only if authentication is needed. This gives you real AWS experience without keeping a VM and database running 24/7.
The classic beginner mistake: leaving resources running
EC2 is billed while running even if you are not connected to it. Stopping an EBS-backed instance stops instance usage and data-transfer charges, but EBS volumes remain and continue to incur storage charges. Stopping is not the same as deleting.
Public IPv4 addresses are another common surprise. AWS currently charges USD $0.005 per hour for an in-use or idle public IPv4 address. An automatically assigned public IPv4 is released when an EC2 instance is stopped, while an Elastic IP can remain associated and billable.
EC2: a safe learning routine
① Work on the project → ② stop the instance when finished → ③ remove unused Elastic IPs and other resources → ④ review EBS volumes/snapshots → ⑤ terminate the instance when the project is finished.
RDS: stopping is not complete cleanup
Stopping an RDS instance can stop instance-hour charges, but storage and backup-related charges can continue. AWS states that to stop all RDS-related charges, you need to delete the DB instances and snapshots that are generating charges.
For a tutorial, plan the cleanup before creating the database. RDS is excellent for learning, but it is easy to forget that the database and its stored data are separate billable components.
Cost traps worth knowing
Monitor your Free Tier usage
The Billing and Cost Management console has a Free Tier page where you can review current usage by service, usage type, and Region. AWS also provides Free Tier usage alerts for active offers. Check the page regularly instead of assuming a resource is free.
AWS Budgets: your first line of defense
AWS Budgets can alert on actual or forecasted cost/usage. For a Paid plan used for learning, a low monthly cost budget such as $1, $5, or $10 can give you an early warning. You can also create service-specific budgets.
Budgets do not automatically shut down every resource. They are monitoring and alerting tools.
CloudWatch billing alarms
CloudWatch can monitor estimated AWS charges. Billing metrics are stored in US East (N. Virginia) and represent worldwide charges. The alarm triggers when the current estimated billing amount crosses your threshold; it does not forecast future charges.
Console path: Billing preferences → enable billing alerts → switch CloudWatch to US East (N. Virginia) → Alarms → Create alarm → Billing → Total Estimated Charge → choose a threshold → configure an SNS notification.
Budgets vs CloudWatch: Budgets can use actual and forecasted values; the CloudWatch billing alarm is based on the estimated charge metric.
A practical monitoring setup
A portfolio architecture with minimal infrastructure
Frontend: S3 + CloudFront
API: API Gateway + Lambda
Database: DynamoDB
Authentication: Cognito when needed
Monitoring: CloudWatch
This kind of serverless portfolio project lets you demonstrate storage, CDN, APIs, compute, databases, identity, logging, and monitoring without keeping EC2 and RDS running all day.
What I would avoid in a first lab
Avoid creating a NAT Gateway just because a tutorial does. Avoid leaving RDS running when you are not using it. Avoid unnecessary load balancers, large EBS volumes, public IPv4 addresses, high volume logging, and third-party Marketplace software until you understand their pricing.
The goal is not to avoid every paid service forever. The goal is to know exactly what you are creating, why you need it, what the pricing dimensions are, and how you will clean it up.
Free Tier first: a simple workflow
Final checklist
- I know when my Free plan ends.
- I know when my credits expire.
- I check the Free Tier offer before launching a service.
- I have an AWS Budget.
- I have a billing alert.
- I stop unused EC2 instances.
- I review EBS, snapshots and Elastic IPs.
- I delete RDS resources when the lab is finished.
- I avoid unnecessary NAT Gateways and always-on infrastructure.
- I check the Billing dashboard before upgrading.
The takeaway
The new AWS Free Tier makes learning easier by combining credits, free offers, and a dedicated Free account plan. But “free” does not mean “ignore the bill.” Understand the offer behind every service, monitor usage, build small projects, and clean up what you no longer need. Build small. Measure often. Clean up aggressively. Scale when you actually need to..
Official AWS references
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article