AWS Free Tier: The 12-Month Clock Is Ticking – Here’s What You Actually Keep

The two faces of AWS Free Tier

When you sign up for AWS, you don’t get a universal “free” pass. You get two distinct tiers:

1. **Always Free**: A limited set of services that remain free forever, within strict usage limits.

2. **12-month Free Tier**: A generous trial that gives you access to a broader set of resources for the first 12 months after your initial sign-up.

The problem? New users often conflate the two and assume that everything they spun up in month three will keep running for free after month twelve. That’s how you get the infamous $1,200 surprise email.

What’s always free (and what isn’t)

Services like AWS Lambda, DynamoDB, and Amazon SQS offer a perpetual free allowance. Lambda, for example, grants 1 million requests and 400,000 GB-seconds of compute per month—forever. Similarly, DynamoDB’s 25 GB of storage and 25 read/write capacity units won’t expire.

But EC2? Only a single `t2.micro` or `t3.micro` instance is included *for 12 months*. After that, you’re charged standard on-demand rates. RDS, with its 750 hours of `db.t2.micro` usage, vanishes the same way. The list of services with an expiration date is long, and it’s easy to forget what’s temporary.

The expiration clock

The 12-month clock starts the moment your AWS account is created—not when you first launch a resource. If you signed up in January, waited until June to deploy your side project, your free EC2 hours will dry up in December, not the following June.

AWS sends multiple email reminders (via the root account email) about the approaching expiration, but many developers miss them because they land in spam or a shared admin inbox. The service itself does not hard-block your resources; it switches them to standard billing automatically. Your instance keeps running. The bill just starts rising.

How to avoid the bill

**1. Terminate or downsize before day 366.**

If you don’t need the `t2.micro` instance anymore, stop it completely. For data, consider migrating tables from RDS to DynamoDB if the workload fits the Always Free limits.

**2. Set a zero-spend budget with alerts.**

AWS Budgets can send an alert when your costs exceed a threshold. Create a budget for $0.01 and attach it to your root account email. It’s a blunt instrument, but it’s better than silence.

**3. Use the AWS Free Tier usage dashboard.**

Hidden inside Billing and Cost Management, the dashboard shows your actual consumption against free-tier limits. It’s not real-time, but it highlights which services have breached the threshold.

**4. Tag everything from day one.**

Good tagging hygiene helps you understand which resources belong to your “free experiment” phase. You’ll be able to bulk-delete them when the trial ends without wondering if you still need something.

Where a monitoring tool makes the difference

Manual checks don’t scale when you’re building with multiple environments. At Sapior, we built a lightweight monitoring layer that hooks into your AWS billing data and sends a Slack alert 24 hours before any 12-month Free Tier entitlement is about to flip to chargeable. Instead of calendar reminders, you get actionable notifications tied to the actual resources that matter.

> “Sapior turns AWS billing signals into a developer-friendly feed. You see exactly what’s expiring, what’s costing, and what you can safely kill.”

The fine print that saves you

The AWS Free Tier is generous, but it’s also a marketing funnel. Learn to treat it as a 12-month sandbox with an off-switch. The always-free services are still fantastic for prototype workloads and event-driven apps. Everything else should have an explicit decommissioning date.

Read the [official AWS Free Tier documentation](https://aws.amazon.com/free/) and, if you’re building in a team, make “free tier expiry” a standing item in your sprint planning. A five-minute review can save thousands.

_This article was produced by Sapior, the developer-tools platform that keeps your cloud costs predictable._