AWS Free Tier and Pricing Basics

AWS doesn't charge one flat bill for "using AWS." Each service is billed on its own metered dimensions — compute time, amount of data stored, amount of data transferred, or number of requests made, depending on the service. Your total bill is the sum of every service you actually used, and — tying back to the previous lessons — some prices can vary by Region.

This is different from a traditional software licence or a flat hosting plan: the amount you pay tracks the amount you actually use, in both directions. Use less, pay less; use more, pay more.

The AWS Free Tier exists to let newcomers try services without charge, under specific conditions. Conceptually, free-tier offers on AWS tend to fall into a few shapes: some give a fixed amount of usage free for a limited trial period after account creation, some give an ongoing free allowance up to a limit for as long as you stay under it, and some are short trials tied to a specific new service.

This lesson deliberately doesn't quote exact numbers or dollar amounts — AWS changes Free Tier offers and pricing over time, so a specific figure taught today could be wrong by the time you read this. What matters is the model: Free Tier access is conditional and limited, not a blanket guarantee.

This is worth stating plainly: having Free Tier eligibility does not mean everything you create is free. Creating a resource that isn't Free Tier–eligible, or exceeding a Free Tier limit on one that is, starts real charges — often without any extra warning at the moment it happens.

Before creating anything, the responsible habit is to check the current Free Tier terms and limits for that specific service, precisely because those terms change over time and this lesson can't promise today's numbers will still be accurate later.

A few habits are worth starting before you ever create a real resource:

• Before creating something, check what you'll actually be billed for and how it's measured (per hour? per gigabyte? per request?).
• Keep track of what you've created, so you remember it exists and remember to remove it later.
• Expect that hands-on projects starting in Module 3 will include an explicit cleanup step for exactly this reason — removing a resource you no longer need is a normal, expected part of using AWS, not an optional afterthought.