AWS Free Tier and Billing Overview
How the AWS Free Tier works since July 2025, from credits to free and paid plans, and how to track spend with budgets, tags and Cost Explorer.
Most people’s first AWS bill is either zero or a surprise. The difference is rarely the services they used. It is whether they understood what the Free Tier actually covers, and whether anything was watching the account when it stopped covering it.
The Free Tier changed substantially in July 2025, so a lot of advice online, including older versions of this article, describes a program that new accounts no longer get. This article explains how the current Free Tier works, how it differs from the legacy one, and how AWS billing fits around it: where charges come from, which tools show them, and the small set of guardrails worth setting up on day one.
How the Free Tier works now
For accounts created on or after July 15, 2025, the Free Tier is built around credits rather than a 12-month list of free allowances. Every new account receives $100 in AWS credits at sign-up. You can earn up to $100 more by completing a handful of getting-started activities, such as launching an EC2 instance, creating a database in Amazon RDS, building a Lambda function, trying a model in Amazon Bedrock and setting up a budget in AWS Budgets. Each activity adds $20.
At sign-up you also choose an account plan:
- Free plan. Meant for learning and proofs of concept. Your usage draws from your credits, and you are not charged. Some services are unavailable, mainly those that would burn through the credit balance immediately or that involve buying hardware or Marketplace products.
- Paid plan. A normal AWS account with access to every service. Credits still apply to eligible usage, and anything beyond them is billed to your payment method.
The free plan ends after six months or when your credits run out, whichever comes first. At that point AWS closes the account. You then have 90 days to upgrade to a paid plan and get your resources and data back; after that, the account and its content are deleted. You can upgrade at any time before then, and unused credits stay valid for up to 12 months from sign-up.
flowchart TD
A["Sign up"] --> B["$100 credits"]
B --> C{"Choose a plan"}
C -->|Free plan| D["Usage draws from credits"]
C -->|Paid plan| E["Credits first, then billed"]
D --> F["Activities add up to $100"]
E --> F
D --> G{"6 months passed or credits gone?"}
G -->|No| D
G -->|Yes| H["Account closed"]
H --> I{"Upgrade within 90 days?"}
I -->|Yes| E
I -->|No| J["Account and data deleted"]
The important property of the free plan is that it cannot produce a bill. That makes it a good fit for a student account or a weekend experiment. It is a poor fit for anything you want to keep running past six months, because the deadline is fixed and the account closes whether or not you are still using it.
Always Free offers
Alongside the credits, a set of services has monthly allowances that never expire and apply to every account, old or new, on either plan. Two well-known examples:
- AWS Lambda: 1 million requests and 400,000 GB-seconds of compute per month.
- Amazon DynamoDB: 25 GB of storage, plus 25 provisioned read and 25 provisioned write capacity units. The capacity allowance applies to provisioned mode, not on-demand.
The full list is longer and changes over time, so check the AWS Free Tier page for current offers and limits rather than relying on a copy of it.
EC2 instances that count as free tier eligible
On new accounts, the EC2 instance types covered by the Free Tier are t3.micro, t3.small, t4g.micro, t4g.small, c7i-flex.large and m7i-flex.large. The EC2 console marks them as “Free tier eligible” in the launch wizard, and the CLI can list them for your Region:
aws ec2 describe-instance-types \
--filters Name=free-tier-eligible,Values=true \
--query "InstanceTypes[].InstanceType" \
--output text
The old rule of thumb, “750 hours a month of t2.micro”, belongs to the legacy program and doesn’t apply to accounts created after the change.
You opened an account on the free plan in March 2026 and still have $60 in credits in September. What happens next?
Correct! The free plan ends at six months or when credits run out, whichever comes first. Upgrading keeps the account and the remaining credits.
The legacy Free Tier, for older accounts
Accounts created before July 15, 2025 stay on the legacy Free Tier. It had three kinds of offer:
- 12 months free: allowances that started at sign-up and ended a year later, such as 750 hours a month of t2.micro or t3.micro on EC2 and 5 GB of S3 Standard storage.
- Always Free: the same non-expiring allowances described above.
- Trials: short free trials of individual services, starting when you first used them.
Because those 12-month windows began at sign-up, every legacy account has now passed them. If your account dates from before the change, assume the Always Free allowances are all that is left, and that everything else is billed at normal rates.
| Legacy Free Tier | Free plan | Paid plan | |
|---|---|---|---|
| Applies to | Accounts created before July 15, 2025 | New accounts | New accounts |
| Main benefit | 12 months of per-service allowances | Credits, no charges | Credits, then normal billing |
| Always Free offers | Yes | Yes | Yes |
| Service access | All services | Restricted subset | All services |
| Can produce a bill | Yes | No | Yes |
| What ends it | 12-month window per offer | 6 months or credits used up | Nothing; credits expire after 12 months |
If you are setting up accounts on several clouds at once, Setting Up Free Accounts on AWS, GCP and Azure walks through the sign-up steps, and the GCP and Azure free tier articles cover the other two providers.
How AWS billing works
AWS bills monthly in arrears for what you used. Each service meters its own dimensions: compute by the second or hour, storage by GB-month, requests by count, data transfer by GB. Prices usually differ by Region. Credits are applied to eligible charges before anything reaches your payment method.
A few properties of the model explain most surprise bills:
- Resources cost money while they exist, not while you use them. A stopped EC2 instance stops compute charges, but its EBS volumes are still billed. An idle load balancer or NAT gateway is billed by the hour whether or not traffic flows.
- Some costs are attached to other resources. Public IPv4 addresses are charged hourly, including the one AWS assigns automatically to an instance. Snapshots outlive the volumes they came from.
- Data transfer out is charged separately. Data coming into AWS is generally free; data leaving to the internet, and in many cases between Regions or Availability Zones, is not.
- Resources live in Regions. A forgotten instance in a Region you rarely look at is still running. Cost Explorer shows spend across all Regions, which the console’s resource pages do not.
None of this is specific to the Free Tier, but it matters most there: on a paid plan, once credits run out, these small hourly charges are the first thing to appear on a bill.
Where to see charges
All of the billing tools live in the Billing and Cost Management console. The ones you will use most:
| Tool | What it shows or does | Cost |
|---|---|---|
| Bills | Charges for each month, by service and Region | Free |
| Credits page | Remaining credit balance and expiry | Free |
| Cost Explorer | Spend over time, filtered and grouped by service, Region, tag or account | Console free; API calls are charged per request |
| AWS Budgets | Alerts when actual or forecast spend crosses a threshold | Monitoring budgets are free; action-enabled budgets beyond the first two are charged |
| Cost Anomaly Detection | Machine-learning alerts on unusual spend patterns | Free |
| CloudWatch billing alarm | Alarm on the account’s estimated charges | Standard CloudWatch alarm pricing |
Check the AWS Budgets pricing and Cost Explorer pricing pages for current rates.
Billing access is controlled by IAM like everything else. By default only the root user can see it, and you need to enable IAM access to billing before an administrator role can use these pages. If you haven’t set up IAM users or roles yet, AWS Identity and Access Management (IAM) covers why daily work shouldn’t happen as root.
You stop an EC2 instance at the end of a lab. Which charge continues?
Correct! A stopped instance keeps its EBS volumes, and those are billed per GB-month until you delete them or terminate the instance.
Guardrails to set up on day one
Billing tools only help if they run before the problem. On a free plan account the worst case is losing the account early; on a paid plan or legacy account it is an unexpected charge. Either way, these steps take a few minutes and cover most mistakes.
flowchart LR
R["Resources"] -->|"tags"| CE["Cost Explorer"]
R -->|"usage"| BL["Billing data"]
BL --> B["AWS Budgets"]
BL --> AD["Cost Anomaly Detection"]
BL --> CW["CloudWatch billing alarm"]
B -->|"threshold crossed"| N["Email or SNS"]
AD -->|"unusual spend"| N
CW -->|"alarm"| N
N --> Y["You act"]
Create a budget with forecast alerts
AWS Budgets is the single most useful guardrail. A monthly cost budget with two alerts covers most cases: one when actual spend passes 80 percent of the limit, and one when forecast spend is expected to pass 100 percent. The forecast alert matters because it can warn you mid-month, before the money is spent.
You can create it in the console, or with the CLI. First describe the budget:
{
"BudgetName": "monthly-cap",
"BudgetLimit": { "Amount": "10", "Unit": "USD" },
"TimeUnit": "MONTHLY",
"BudgetType": "COST"
}
Then the two notifications:
[
{
"Notification": {
"NotificationType": "ACTUAL",
"ComparisonOperator": "GREATER_THAN",
"Threshold": 80,
"ThresholdType": "PERCENTAGE"
},
"Subscribers": [{ "SubscriptionType": "EMAIL", "Address": "you@example.com" }]
},
{
"Notification": {
"NotificationType": "FORECASTED",
"ComparisonOperator": "GREATER_THAN",
"Threshold": 100,
"ThresholdType": "PERCENTAGE"
},
"Subscribers": [{ "SubscriptionType": "EMAIL", "Address": "you@example.com" }]
}
]
And create both in one call:
aws budgets create-budget \
--account-id 111122223333 \
--budget file://budget.json \
--notifications-with-subscribers file://notifications.json
Setting up a budget is also one of the activities that earns extra credits on a new account.
A budget alerts; it does not stop anything. Budget actions can apply an IAM or service control policy, or stop specific EC2 and RDS instances, when a threshold is crossed, but for a personal account an email you actually read is usually enough.
Turn on Cost Anomaly Detection
Cost Anomaly Detection learns your normal spending pattern and alerts on departures from it, such as a service you’ve never used suddenly costing money. It is free, and for a small account a single monitor covering all AWS services with a daily or immediate email summary is a sensible default.
Add a CloudWatch billing alarm if you want a second signal
Before Budgets existed, the standard advice was a CloudWatch alarm on the EstimatedCharges metric. It still works and gives you an independent check. Enable billing alerts in the Billing preferences first, and create the alarm in US East (N. Virginia), because billing metrics are only published in that Region.
Which AWS Budgets alert is most likely to warn you in time to prevent an overspend?
Correct! A forecast alert fires when the projected month-end total crosses the limit, often days or weeks before actual spend does.
Tagging resources for cost allocation
Once an account runs more than one project, the bill’s breakdown by service stops being enough. Tags let you answer “what did the blog cost this month?” instead of “what did EC2 cost?”.
A tag is a key-value pair on a resource, such as project=blog or env=dev. Tagging alone isn’t enough for billing: you have to activate the tag key as a cost allocation tag in the Billing console before it appears in Cost Explorer and cost reports. Activate them early: you can request a backfill of earlier months, but it is simpler when the tag data is there from the start.
# Tag an instance
aws ec2 create-tags \
--resources i-0abcd1234example \
--tags Key=project,Value=blog Key=env,Value=dev
# Activate the tag key for cost allocation
aws ce update-cost-allocation-tags-status \
--cost-allocation-tags-status TagKey=project,Status=Active
A tag key only shows up for activation after AWS has seen it on at least one resource, so create the tags first. AWS also generates some tags itself, such as aws:createdBy, which can be activated the same way.
Keep the scheme small. Two or three keys used consistently, such as project, environment and owner, are worth more than a dozen applied at random.
A cleanup habit
Most surprise charges come from resources left behind after a tutorial. A short routine after each experiment prevents them:
- Terminate instances you no longer need, rather than stopping them, and check that their EBS volumes were deleted.
- Release Elastic IP addresses and delete load balancers and NAT gateways.
- Delete snapshots and AMIs you created along the way.
- Look at Cost Explorer grouped by Region for the last few days. Anything in a Region you weren’t working in deserves a look.
If you’re about to launch your first server, Creating Your First AWS EC2 Instance goes through the launch and the cleanup step by step. For billing questions you can’t resolve yourself, account and billing support cases are included with every support plan, including Basic; AWS Support and Documentation Resources covers the options.
Further reading
- AWS Free Tier and its FAQs
- Using the AWS Free Tier in the Billing user guide
- Managing your costs with AWS Budgets
- Organizing and tracking costs using cost allocation tags
- AWS News Blog: Free Tier update with up to $200 in credits
Key takeaways
- Accounts created on or after July 15, 2025 get $100 in credits, plus up to $100 more for completing getting-started activities, and choose a free or paid plan.
- The free plan never bills you, but it restricts some services and closes the account after six months or when credits run out, with 90 days to upgrade before deletion.
- Accounts created before that date stay on the legacy Free Tier, whose 12-month offers have now expired; only Always Free allowances remain.
- Always Free offers, such as Lambda’s 1 million monthly requests, apply to every account and never expire.
- Charges accrue for resources that exist, not just ones in use: EBS volumes, public IPv4 addresses, NAT gateways and data transfer are the usual surprises.
- Set up a monthly budget with a forecast alert and Cost Anomaly Detection on day one, and activate cost allocation tags before you need them.
Part 5 of 7 · Getting to Know AWS