AWS Pricing, Free Tier, and the $200 Credit Explained: What Beginners and Builders Must Know Before Going Pay-As-You-Go

Scenario

A new AWS builder needs to understand Free Tier credits, plan transitions to pay-as-you-go, and avoid common billing surprises early in a project.

Scope

This guide covers AWS pricing mechanics, Free Plan versus Paid Plan behavior, the $200 credit model, cost traps, and operational cost controls.

How to use this guide

Use this as a cost-readiness checklist before account upgrades and before deploying any workload that can run continuously.

AWS is powerful because it lets you build almost anything: a tiny static website, a production SaaS app, a data pipeline, a game backend, an AI API, a Kubernetes cluster, or a global enterprise platform. But AWS is also intimidating because every service has its own pricing model. One service charges by seconds, another by requests, another by gigabytes stored, another by data transferred, another by provisioned capacity, and another by model tokens.

The Free Tier exists to reduce that fear. It gives new users a way to explore AWS without committing money immediately. Since AWS updated the Free Tier program in July 2025, new customers can receive up to $200 in AWS credits: $100 at sign-up and up to another $100 by completing AWS exploration activities. The newer Free Tier model also introduces a clearer distinction between the Free Plan and the Paid Plan, and this distinction is extremely important. AWS says the Free Plan lets new users experiment for up to six months without charges, while the Paid Plan gives full service access and charges standard pay-as-you-go prices beyond available credits.

This article explains AWS pricing from shallow to deep: what “pay-as-you-go” really means, what the Free Tier covers, what the $200 credit is, what happens when you upgrade to pay-as-you-go, what remains with you, what disappears, and how to avoid surprise bills.

1. The Simple Idea: AWS Is Not One Product, It Is a Metered Utility

The easiest way to understand AWS pricing is to compare it to electricity. You do not buy “AWS” as one fixed product. You consume small units of many different services. A virtual machine consumes compute time. A database consumes storage, memory, I/O, backups, and sometimes CPU credits. An API consumes requests. A CDN consumes data transfer. A machine learning model consumes tokens or inference units.

AWS describes its general pricing model as pay-as-you-go for most services: you pay only for the individual services you use, for as long as you use them, without long-term contracts or complex licensing. AWS also explains that when you stop using a service, there are generally no additional termination fees for that stopped usage.

That sounds simple, but the real challenge is that “use” means different things depending on the service.

For example:

This is why Free Tier matters: it gives you a credit pool and selected free usage limits, but it does not change the fact that AWS is metered underneath.

2. The Three Core Cost Drivers: Compute, Storage, and Outbound Data

Most AWS bills can be explained by three big categories: compute, storage, and outbound data transfer. AWS’s pricing documentation identifies these as fundamental cost drivers. Compute is usually charged by time, storage by GB-month, and data transfer by the amount of data leaving AWS or crossing certain network boundaries.

This diagram is important because beginners often think, “I only launched one server, so why am I paying?” The answer is usually that the server is only one part of the bill. The disk, snapshots, public IP address, logs, load balancer, NAT gateway, and outbound traffic may continue to generate cost even when the application feels small.

A stopped EC2 instance does not charge for compute runtime, but its attached EBS volume still stores data. A deleted database may leave final snapshots. A private subnet may require a NAT Gateway, and NAT Gateway charges can continue as long as it is provisioned. AWS notes that NAT Gateways are charged both for each hour they are available and for each gigabyte of data they process.

3. What Is the AWS Free Tier Today?

The modern AWS Free Tier has three major ideas:

1. Free Tier credits
2. Always Free offers
3. Short-term trials or selected free usage offers

For new customers under the current model, AWS says users can receive up to $200 in credits: $100 at sign-up and up to $100 more by completing activities. New customers can also access more than 30 Always Free services with monthly free usage limits.

The important word is eligible. Credits do not mean “everything is free forever.” They are a temporary balance that AWS applies to eligible charges. Some services, regions, taxes, marketplace products, or special arrangements may not be covered the way you expect. AWS’s Paid Plan documentation says that when usage exceeds credit balance, or when you use services where credits do not apply, you pay standard pay-as-you-go pricing.

4. The New $200 Credit: What It Really Means

The phrase “$200 AWS Free Tier” can be misleading. You do not necessarily receive $200 instantly in cash-like value on day one.

The structure is:

AWS states that new customers receive $100 in credits upon sign-up and can earn up to an additional $100 by completing activities in the Explore AWS widget. AWS also says these activities must be completed within six months from the account creation date, and earned credits expire 12 months from the date the AWS account was created.

So the correct mental model is:

“I start with $100. I may earn another $100. The maximum is $200. The credits are time-limited. The Free Plan itself is also time-limited.”

This matters because many beginners assume the Free Tier is still mainly the old “12 months of specific service limits” model. AWS says accounts created after July 15, 2025 follow the newer Free Tier plan model, while accounts created before that date remain under the previous Free Tier program.

5. Free Plan vs Paid Plan: The Critical Difference

AWS now asks new users to choose between a Free account plan and a Paid account plan during sign-up. Both can receive the Free Tier credits, but they behave differently.

AWS’s Free Tier comparison says the Free Plan has no charges during usage and closes when credits are depleted or plan duration ends, while the Paid Plan pays for charges that exceed the credit balance and does not close when credits are depleted. AWS also states the Paid Plan gives access to all AWS services and features.

This is the first strategic decision: choose Free Plan if your goal is learning safely. Choose Paid Plan if you need production services, full AWS access, Organizations, Control Tower, or scaling beyond the protected environment.

6. Does the $200 Credit Remain When You Flip to Pay-As-You-Go?

Yes — with important exceptions.

AWS says that when you upgrade from Free Plan to Paid Plan, your remaining Free Tier credits automatically apply to future AWS bills until they expire. AWS also says Free Tier credits expire 12 months after account creation.

So if you create an account, receive $100, earn another $100, spend $40 while experimenting, and then upgrade to the Paid Plan, your remaining credit balance should continue to apply against eligible future AWS bills until expiration.

But there are two dangerous exceptions:

1. If you upgrade by joining or creating an AWS Organization, your Free Tier credits expire immediately.
2. If you set up an AWS Control Tower landing zone, your Free Tier credits expire immediately.

AWS explicitly says that when an account joins an AWS Organization or sets up Control Tower, Free Tier credits expire immediately, the account becomes ineligible to earn more Free Tier credits, and the Free Plan automatically upgrades to Paid Plan.

This is probably the most important part of the article. If you are a beginner, do not join an AWS Organization just because a tutorial tells you to, unless you understand that it can destroy your remaining Free Tier credit eligibility.

7. What Happens When the Free Plan Ends?

The Free Plan is not permanent. AWS says the Free Plan expires at the earlier of two events: six months from account creation or when Free Tier credits are exhausted. AWS also says that when the Free Plan expires, AWS closes the account, access to resources and data is lost, and AWS retains the data for 90 days. During those 90 days, you can upgrade to a Paid Plan to reopen the account and restore access; after 90 days without upgrade, AWS permanently erases the account and content.

This creates a practical timeline:

For serious builders, the lesson is simple: if you build anything valuable, upgrade deliberately before the Free Plan expiration creates operational risk. But do it with cost controls already configured.

8. Existing AWS Customers: Do They Get the New $200?

No. AWS says existing customers keep the benefits of the previous Free Tier program, but existing customers are ineligible for the new Free Tier credits and the Free Plan. AWS also says users are ineligible for Free Plan or Free Tier credits if they have an existing AWS account or had one in the past.

This matters because creating multiple accounts to repeatedly claim credits is not a legitimate cost strategy. AWS uses payment methods, identity verification, account history, and abuse controls. The correct strategy is not “farm free accounts”; the correct strategy is to learn AWS pricing, design low-cost architecture, and use credits as a temporary launchpad.

9. Why “Free” Still Requires a Payment Method

AWS requires a valid payment method even for the Free Plan. AWS explains that the payment method is used to verify identity and prevent abuse, and says it will not charge the payment method until the user upgrades to Paid Plan.

This is a trust mechanism, but it also means you must treat the account seriously. Turn on MFA, secure the root account, set budget alerts, and avoid deploying random templates from the internet.

10. How AWS Applies Credits

Think of credits as a coupon balance that AWS applies after usage is measured. The infrastructure still produces normal line items internally. The difference is whether credits absorb those charges before you pay real money.

AWS says credits apply automatically to bills, and Free Tier usage is calculated across regions. The credits are in USD and apply to participating services across global regions, except where the Free Tier program is not available, such as China regions and generally GovCloud account-plan availability limitations.

11. The Most Common Beginner Cost Traps

Trap 1: Leaving compute running

Compute is often charged for runtime. AWS pricing guidance says compute resources are generally charged by the hour or second from launch until stop or termination, unless covered by reservations or another pricing model.

The beginner mistake is launching an EC2 instance “just for testing,” then forgetting it for weeks. Even small instances cost money when left running 24/7. The professional pattern is automation: tag temporary resources, schedule shutdown, and use Infrastructure as Code so environments are reproducible instead of permanently running.

Trap 2: Keeping storage after deleting compute

Deleting a server does not always delete every disk, snapshot, backup, or log group. EBS volumes, RDS snapshots, S3 buckets, and CloudWatch logs can remain. Storage costs are usually less explosive than compute, but they accumulate silently.

Trap 3: NAT Gateway

NAT Gateway is production-grade, but not beginner-cheap. AWS says a NAT Gateway is charged per hour while available and per gigabyte processed.

For tiny experiments, a public subnet, VPC endpoints, IPv6 egress-only design, or a carefully managed NAT instance may be cheaper depending on the architecture. For production, NAT Gateway is often worth the cost because it is managed and highly available, but it should never be added blindly.

Trap 4: Public IPv4

AWS charges for all public IPv4 addresses, including addresses associated with running instances and Elastic IP addresses.

This catches beginners because old tutorials often imply that an EC2 public IP is basically free. That assumption is no longer safe. Prefer private subnets, load balancers, CloudFront, IPv6 where possible, and minimize unnecessary public IPv4 exposure.

Trap 5: Logs

CloudWatch logs are useful, but verbose debug logs can become real cost. The safe approach is to set retention periods, avoid unbounded debug output in production, and export/archive only what you need.

Trap 6: Data transfer out

AWS says outbound data transfer is one of the fundamental cost drivers. Inbound data transfer is usually free, but outbound transfer and certain cross-boundary transfers can cost money.

This is why video hosting, file downloads, game assets, and AI-generated media can become expensive even if compute looks small.

12. Cost-Control Setup for a New AWS Account

Before deploying anything, configure your financial guardrails. The right setup is not complicated, but it must happen early.

AWS Budgets lets you create budgets that alert you when cost or usage exceeds, or is forecasted to exceed, your budgeted amount.

A good beginner budget configuration is:

AWS also provides Cost Explorer for visualizing, understanding, and managing cost and usage over time. Cost Explorer can filter and group spending, identify cost drivers, and forecast costs. AWS says Cost Explorer data is updated at least once every 24 hours after it is enabled.

For Free Tier usage specifically, AWS provides the GetFreeTierUsage API, which returns Free Tier usage objects including actual usage, forecasted usage, limit, service, region, and usage type.

13. Pricing Calculator: Estimate Before You Build

The AWS Pricing Calculator is one of the most important tools for avoiding surprise bills. AWS says the in-console Pricing Calculator helps estimate planned cloud costs using discounts and purchase commitments, while the public calculator can be used without creating an AWS account. AWS also warns that calculator results are estimates, not final bills, and do not include applicable taxes.

Use it before deploying anything with:

• EC2 always-on instances
• RDS databases
• NAT Gateways
• Load balancers
• High log volume
• AI inference
• Multi-AZ production architecture
• Cross-region replication
• Large file downloads

A clean cost formula looks like this:

Estimated monthly cost =
  compute runtime
+ storage
+ database runtime
+ backups/snapshots
+ requests
+ logs/metrics
+ networking
+ public IPv4
+ support plan
+ taxes
- eligible credits

Most beginners estimate only compute. Professionals estimate the whole architecture.

14. A Practical Example: Small Web App on AWS

Imagine a small FastAPI + Angular web app. The naive AWS design might be:

This architecture may be production-friendly, but not necessarily Free Tier-friendly. It can include multiple cost sources:

A more cost-sensitive beginner version might be:

This version leans serverless and removes always-on compute, RDS runtime, NAT Gateway, and load balancer cost. It is not always the best architecture, but it is often better for low-traffic experiments.

15. The Smart Way to Use the $200 Credit

The worst way to use the $200 credit is to spend it randomly on large EC2 instances, forgotten databases, and NAT Gateways. The best way is to use it as a controlled learning and validation budget.

A good learning path:

1. Week 1: IAM, budgets, billing, Cost Explorer, S3, CloudFront.
2. Week 2: Lambda, API Gateway, DynamoDB.
3. Week 3: EC2, EBS, security groups, public/private subnets.
4. Week 4: RDS, backups, snapshots, parameter groups.
5. Week 5: ECS/Fargate, ECR, ALB.
6. Week 6: CloudWatch alarms, logs, dashboards.
7. Week 7: Bedrock or AI services, but with strict quotas and daily review.
8. Week 8: Infrastructure as Code cleanup and cost report.

The goal is not to “consume the credit.” The goal is to learn which AWS services map to real business value and which ones are expensive defaults.

16. When Should You Upgrade to Paid Plan?

Upgrade to Paid Plan when at least one of these is true:

• You need services blocked under the Free Plan.
• You are building something real and cannot risk Free Plan expiration.
• You need production-scale workloads.
• You need AWS Organizations, but understand the credit consequence.
• You need short-term trials available under Paid Plan.
• You already implemented budgets and cost monitoring.

Do not upgrade just because a tutorial says “click upgrade.” Upgrade when your architecture and billing guardrails are ready.

The key reassurance is that a normal manual upgrade does not automatically delete your remaining Free Tier credits. AWS says remaining Free Tier credits apply to future AWS bills until expiration when you upgrade to Paid Plan.

17. Advanced Topic: Pricing APIs and Automation

For DevOps engineers and serious builders, manual billing review is not enough. AWS provides APIs for price and Free Tier visibility.

AWS Price List APIs let you query AWS service, product, and pricing information programmatically. AWS says the Price List Query API can be used to build cost-control and scenario-planning tools, reconcile billing data, forecast spend, and compare workloads. AWS also warns that if there is a difference between the price list file and a service pricing page, AWS charges the prices on the service pricing page.

The Free Tier API gives actual and forecasted Free Tier usage objects.

A mature setup could run a daily script that:

This is how you turn AWS pricing from fear into observability.

18. The Final Mental Model

AWS Free Tier is not a magic free cloud. It is a controlled onboarding system. The $200 credit is not a lifetime grant. It is a temporary exploration balance. The Free Plan is not the same as the Paid Plan. Upgrading to pay-as-you-go can preserve remaining credits, but joining AWS Organizations or setting up Control Tower can immediately expire those credits. Credits expire 12 months after account creation. The Free Plan ends after six months or when credits are exhausted, whichever comes first.

The professional way to use AWS is:

The beginner asks: “Is AWS free?”

The professional asks: “Which meter is running, what is its unit, what limit protects me, what alert catches drift, and what happens when credits expire?”

That second question is how you avoid surprise bills and build confidently on AWS.

References

• Free Cloud Computing Services - AWS Free Tier
• AWS Product and Service Pricing | Amazon Web Services
• Key principles - How AWS Pricing Works
• Pricing for NAT gateways - Amazon Virtual Private Cloud
• Free Tier FAQs
• Choosing an AWS Free Tier plan - AWS Billing
• Explore AWS services with AWS Free Tier - AWS Billing
• Amazon EC2 instance IP addressing - Amazon Elastic Compute Cloud
• AWS Budgets Documentation
• Cloud Cost Report - AWS Cost Explorer - AWS
• GetFreeTierUsage - AWS Billing and Cost Management
• Generating estimates with Pricing Calculator - AWS Cost Management
• Calling AWS services and prices using the AWS Price List - AWS Billing