How Much Does AWS Web Hosting Cost? (w/Examples) + FAQs

Most small business sites hosted on AWS cost $5 to $50 a month. The exact price depends on which AWS service you pick, not on one fixed hosting fee. A single Lightsail server starts at $5, and Amazon's 2025 update now hands new accounts $200 in Free Tier credits to test that server for free.

That range hides a real trap. AWS never sells one hosting plan with one price tag; it sells dozens of separate services, and your bill grows with each one you add. A site that costs $8 in month one can turn into a $70 surprise once traffic spikes or a forgotten test server piles on extra charges.

What Determines Your AWS Hosting Bill

Every price in this article reflects AWS's published rates as of 2026. Cloud vendors change prices often, sometimes with little notice, so check AWS's own pricing pages before you commit to a plan. The AWS Pricing Calculator lets you model your setup before you sign up for anything.

AWS bills in four different ways, and knowing which one applies changes how steady your bill feels. Pay-as-you-go is the default: you pay only for the compute, storage, and requests you use, with no contract and no exit fee. This model rewards a quiet site and punishes a sudden traffic spike, because the meter tracks real use, not a flat cap.

Flat-rate plans bundle several services into one fixed monthly number with no overage charges. This is exactly how Lightsail and CloudFront's flat plan both work, and it is the closest AWS comes to normal web hosting. Savings Plans trade a one- or three-year usage promise for a lower hourly rate on compute, which only pays off if your traffic stays steady enough to forecast.

Volume pricing rewards scale directly instead of punishing it. S3 storage drops from $0.023 per GB to $0.022, then to $0.021 per GB, as your stored data crosses 50 TB and then 500 TB. Every plan's data transfer into AWS stays free no matter how much you send, which is a detail few new users notice.

A single website usually touches more than one of these billing shapes at once. A WordPress site on Lightsail pays one flat bundle for the server, but its CDN and storage add-ons carry their own separate flat fees on top. Knowing which piece of your bill is fixed and which one moves with traffic is what turns a confusing invoice into one you can predict. Even a mostly-flat setup can still surprise you if one part of it, like data transfer, is billed by the meter instead of by the bundle.

The AWS Free Tier, As It Works Today

AWS quietly dropped its old "12 months, 750 free hours" setup for new signups. The current Free Tier terms work on account credit instead. New customers get a starting credit and can earn more by trying key services, meant to cover roughly six months of testing AWS. AWS Amplify's own 2025 Free Tier update confirmed the new shape of this deal.

New accounts now get up to $200 in credits to use across eligible services, and a free plan stays open for six months after signup. Any credit left over rolls onto your bill once you switch to a paid plan. That rollover detail matters if you plan to upgrade partway through a project, since unused credit is not simply lost the day you add a card charge.

All of that credit expires 12 months after your account was created, whether you used it or not. This is not the old "forever free tier" that a lot of older blog posts and forum threads still describe. A site still leaning on that credit in month 14 gets a normal invoice with no extra warning built in.

Specific services also carry their own always-free allowances on top of the account credit. EC2's free-eligible instance types currently include T3.micro, T3.small, T4g.micro, T4g.small, C7i-flex.large, and M7i-flex.large, so a small test server can run at no cost if you stick to one of those types. CloudFront's flat-rate free tier costs $0 a month with no overage charges, and it throws in 5 GB of S3 storage credit every month too.

Free credit is a real head start, not a permanent hosting plan. Treat the six-month window as a runway to test your setup and learn its real cost. Once the credit and the free-tier clock both run out, budget for the Lightsail, EC2, or Amplify numbers later in this article. Write the expiry date down somewhere you will see it, since a credit that quietly lapses is the single easiest cause of an invoice that feels like it came out of nowhere.

Which AWS Hosting Path Fits Your Site?

AWS offers at least four ways to host a website, and the right one depends on your comfort with servers and how much your traffic swings. Match your situation to one of the paths below before you compare exact prices. Picking the wrong starting point costs more time than money, and switching later means real migration work.

The solo owner or small-business site

Say you run a single WordPress site, a portfolio, or a small store, and you do not want to manage servers by hand. Lightsail is the practical starting point for you. Its bundled pricing wraps compute, storage, and a data transfer allowance into one flat number starting at $5 a month, which reads like normal hosting instead of a menu of separate AWS charges.

You give up some fine-grained control, but you gain a bill you can predict before the month even starts, and that trade suits most small sites well. You rarely touch server settings once a small site is live, so the flexibility EC2 offers goes unused anyway. Pick Lightsail first, and only move off it once you have a concrete reason, like a database that needs its own failover.

The developer who wants full control

A developer who is comfortable with servers, load balancers, and manual setup usually reaches for EC2 instead, paired with separate S3 storage and CloudFront. Nothing here comes bundled: you pick your own instance size, attach your own storage, and pay for data transfer on its own separate scale. The total can run cheaper than Lightsail at low traffic, and pricier once you stack managed extras on top, so the math shifts with your exact setup.

This path suits anyone who wants to tune every setting by hand and is willing to read the EC2 pricing page closely first. It also suits a site with unusual needs, like heavy background processing, that a bundled plan was never built to handle. Expect to spend real setup time here in exchange for that control.

The team shipping a JavaScript app

Teams building a React, Next.js, or similar frontend, with frequent code deploys, tend to fit Amplify's pricing best. Amplify charges for build minutes, storage, and data served, instead of a flat server fee. A low-traffic app can cost a few dollars a month, and a busy one scales up in that same steady pattern. It also bundles in CI/CD and preview branches, which removes a separate deploy tool from your stack.

That alone can be worth the switch for a fast-moving team. A team that deploys code several times a day will feel the build-minute charge first. A team that deploys rarely will barely notice it at all, since the meter only runs when you ship new code. In both cases, the bill tracks your team's real habits instead of a server size you picked once and forgot about.

A Worked Example: Building an AWS Bill From Scratch

Numbers help more than a vague price range, so here is AWS's own published example for a real WordPress site delivered worldwide. It runs on a $5 Lightsail instance with 1 GB of memory, one core, a 40 GB disk, and 2 TB of transfer. The same setup adds a CDN distribution serving 50 GB and an object storage bucket holding 5 GB.

That $8.50 total only holds if the site stays inside its transfer allowance. AWS also publishes a second example. Two $5 instances share a combined 4 TB transfer allowance, and once real traffic pushes 100 GB past that limit, overage at $0.09 per GB adds $9 on top of the $10 base cost. The total comes to $19 a month.

The lesson repeats across almost every AWS service. The sticker price on the instance is rarely the whole bill. Storage, transfer, and any add-on each show up as their own separate line.

Scale the same idea up and the pieces multiply instead of changing shape. A small multi-tier app might run a Lightsail container, a managed database, and a load balancer. Add up $7 for the container, $15 for the database, and $18 for the load balancer, and the total is $40 a month before any traffic-based overage.

Use that same method to build your own bill. List every service you plan to use, and price each one from its own pricing page. Add the numbers up before you assume one low number tells the whole story.

A domain name is the one common line item this math tends to leave out. Registering or moving a domain to Route 53 carries its own separate yearly fee, and Route 53 also charges a small monthly amount to host your DNS records. Add that on top of whichever bundle you picked, since almost every real site needs a domain even when the hosting itself is nearly free.

Three Lessons From Real AWS Hosting Setups

These three cases each teach a different lesson about how AWS billing behaves once a real site is running. None of them repeats the bundled-Lightsail math above. Each one shows a different pattern in how the same underlying pricing rules play out in practice.

The freelancer who priced Lightsail against EC2

A freelance designer hosting a five-page client site compared a $5 Lightsail bundle against building the same site on EC2 with separate S3 storage and a Route 53 domain. The Lightsail bundle won on predictability, since its $5 covers compute, 40 GB of storage, and 2 TB of transfer in one number. The EC2 route means paying for the instance, the storage, and the transfer as three separate charges that can each grow on their own. The lesson here is about billing shape, not raw price: a bundle trades some savings potential for a bill you never have to reassemble by hand.

The startup that watched Amplify scale with traffic

A five-person startup team deploying a React app with 300 daily users tracked their Amplify bill for a full quarter. AWS's own worked math for that exact case comes to $6 in build minutes plus $2.08 in hosting charges, for $8.08 a month total. The same formula applied to a 10,000-daily-user app comes to $65.98 a month, once data served climbs past 439 GB.

The key point is that Amplify's cost scales with the traffic it serves, not with a fixed server size. A quiet app and a busy one on the same plan can pay very different bills. Remember that the next time your app's traffic doubles overnight, since your bill will follow it up almost exactly. No single instance size caps you here, so a launch-day spike raises the bill instead of crashing the site.

The engineer who automated shutdowns to control test costs

A widely read AWS learning guide is built entirely around cost discipline. It makes a bold claim: a determined learner can rebuild and tear down a full set of practice projects for under $50 total, by using Free Tier credits and shutting resources down between sessions. Treat that specific number with some doubt, since it depends on which services you leave running and for how long. The underlying habit is still worth copying, and it costs nothing to try.

A separate reply in the same discussion explained why cloud billing feels different from renting a physical server. The real payoff, this user argued, is that you can script and tear down roughly 95% of your setup between sessions. Idle test resources rarely sit around long enough to rack up real charges when you automate that teardown.

Students get an extra lever worth checking, too. One user in the same thread mentioned that the GitHub Student Developer Pack has offered somewhere around $110 in AWS credit for enrolled students. Program terms change often, so confirm the current offer directly with GitHub Education before you count on it. The mistake this lesson heads off differs from the first two: it is not about which service you pick, but about leaving something running when nobody needs it.

Lightsail vs EC2 vs Amplify: How the Costs Differ

These three services are not true competitors. They are three different shapes of the same underlying AWS infrastructure, and the table above is a quick reference, not a ranking. What matters more than the shape itself is the specific signal that tells you when to move from one to another.

Lightsail's ceiling is a real dollar figure, not only a feature limit. Its largest general-purpose bundle tops out around $2,344 a month, and once your traffic or your database needs push past what that tier offers, the bundle stops being an advantage and starts being a wall. That is the actual point most teams graduate to EC2 or a mix of managed services, not some vague sense that they have "outgrown" Lightsail. Few small sites ever come close to that ceiling, which is exactly why Lightsail works for most of them for years without a single upgrade.

EC2 earns its extra complexity once your usage is steady enough to make a Savings Plan pay off, since a flat Lightsail bundle can never capture that kind of discount. Add a second instance for redundancy, or a bigger disk for a growing database, and each change shows up as its own new line on the bill. That transparency is the real trade-off: more lines to track, in exchange for control over every one of them and a shot at a lower rate once your usage pattern is predictable.

Amplify's real difference shows up when your site sits idle. A Lightsail or EC2 instance keeps billing by the hour whether a single visitor shows up or not, but Amplify's usage-based meters can shrink close to zero for a truly quiet app. That makes it the one option of the three built to cost almost nothing between traffic spikes, though it still fits a frontend-heavy app far better than a traditional server-rendered one with heavy backend processing.

Mistakes to Avoid With AWS Hosting Costs

• Leaving test instances running. A forgotten EC2 or Lightsail instance keeps billing every hour it exists, free-tier eligible or not, and a weekend-long oversight can add real dollars to a bill nobody meant to spend.
• Assuming the Free Tier lasts forever. The current model gives new accounts about six months of free-plan access, plus a 12-month credit expiry, not an endless free ride, so a site still leaning on that credit later gets a real invoice with no warning.
• Ignoring data transfer OUT charges. Data moving into AWS stays free, but data served to visitors does not, and a site that suddenly goes viral can rack up transfer overage charges even while its compute costs hold steady.
• Picking EC2 for a project that needed Lightsail. A simple site rarely needs instance-by-instance setup, and the time spent managing EC2's separate pieces often costs more in effort than Lightsail's flat bundle would have cost in dollars.
• Forgetting that storage and snapshots keep billing after deletion. Detached storage volumes and old snapshots keep adding their own per-GB charge even after the instance that made them is gone, quietly padding a bill long after a project ends.
• Stacking add-ons without checking their flat fees. A Web Application Firewall in front of an Amplify app adds its own $15-a-month charge per app, and a load balancer or managed database each add a separate flat fee, so a multi-service setup's true cost is always a sum, never one number.
• Not setting a billing alert before experimenting. AWS's own console supports budget alerts, and skipping this step is the single most avoidable mistake on this list, since a five-minute setup would have caught nearly every other mistake here before it became a real charge.

Do's and Don'ts for Keeping Your AWS Bill Predictable

Do

• Do set a billing alert the same day you create your AWS account, before you deploy anything.
• Do start with Lightsail for a simple site, since its flat bundle is easier to forecast than EC2's separate-charge pricing.
• Do check the AWS Pricing Calculator before you commit to a specific instance size or plan tier.
• Do shut down or delete test resources the moment you finish a learning session or experiment.
• Do read the current Free Tier terms before you assume any service is free without limit.

Don't

• Don't assume a $5 Lightsail instance is your whole bill once you add a CDN, storage, or a database on top.
• Don't leave detached storage volumes or old snapshots sitting around after you delete the instance that used them.
• Don't pick EC2 by default if you have never set up a server before; Lightsail or Amplify will cost you less time.
• Don't ignore data transfer pricing because your storage and compute costs look small.
• Don't wait for a surprise invoice to learn how your setup bills; test it with real traffic first.

Pros and Cons of Hosting a Website on AWS

Pros

• You pay only for what you use, with no long contract locking you into a fixed plan you have outgrown.
• Your setup scales without a full migration, since the same account can grow from a $5 Lightsail bundle to a multi-region EC2 setup.
• Free Tier credit removes the first-dollar risk for anyone testing a new project before real budget is on the line.
• Volume pricing rewards growth instead of punishing it, with storage costs dropping once your usage crosses set thresholds.
• One provider covers compute, storage, database, and CDN, so you are not stitching together three separate vendors' bills.

Cons

• The unbundled services are genuinely confusing for anyone who has only used flat-rate hosting before.
• A misconfigured resource can bill without limit until someone notices and shuts it down.
• Free Tier credit runs out on a fixed schedule, not when you finish needing it, so the clock keeps ticking even during a slow project.
• Data transfer OUT charges are easy to underestimate until a site's traffic spikes.
• Comparing total cost across services takes real effort, since no single page shows Lightsail, EC2, and Amplify pricing side by side.

What to Do Next

1. Pick your hosting path first, using the persona guide above, before you look at a single price.
2. Set a billing alert in the AWS console the same day you create your account.
3. Price every service you plan to use separately, then add the numbers up as the worked examples above do.
4. Test your setup inside the Free Tier window so you learn its real cost before the credit expires.
5. Compare your total against a WordPress-specific host if your site is a simple content site rather than a custom app.
6. Revisit your setup every few months, since AWS pricing and your own traffic both change over time.

Frequently Asked Questions

Is AWS free for hosting a website?

Only for a limited window. New accounts get account credit and roughly six months of free-plan access on select services, plus a few always-free allowances like CloudFront's $0 flat-rate tier. Nothing on AWS stays free forever once the credit and the free-tier clock both run out.

What's the lowest-cost option for AWS hosting?

A Lightsail bundle starting at $5 a month. It wraps compute, storage, and a transfer allowance into one flat charge, which is the least expensive predictable option AWS sells for a simple site.

Is AWS cheaper than other web hosts?

It depends on the comparison. AWS can undercut a traditional host at very low or very high traffic, but its separate-charge pricing makes mid-range comparisons harder than checking a flat hosting plan elsewhere.

Does AWS charge for a domain name?

Yes, separately from hosting. A domain bought or moved to Route 53 carries its own registration fee. Route 53 also charges a small monthly amount to host your DNS records, on top of whatever you pay to host the site.

How much does it cost to run a small WordPress site on AWS?

About $8.50 a month. That figure comes from AWS's own published example, combining a $5 Lightsail instance, a $2.50 CDN distribution, and a $1 object storage bucket for a site delivered worldwide.

Can my AWS bill go up unexpectedly?

Yes, and it is the most common complaint about AWS pricing. Traffic spikes, forgotten test instances, and leftover storage volumes are the usual causes, which is why a billing alert matters more than any single pricing choice.

What's the real difference between Lightsail and EC2 pricing?

Lightsail bundles; EC2 does not. Lightsail charges one flat number for compute, storage, and transfer together, while EC2 bills each of those as its own separate, usage-based line.

Do I need a credit card to try AWS?

Yes, even to use Free Tier credit. AWS asks for payment details at signup so it can bill you automatically once your credit or free-plan window runs out.

Is Amplify a good option for a simple content site?

Not usually. Amplify's build-and-deploy pricing suits a JavaScript frontend with frequent code changes far better than a plain content site, which will almost always cost less on Lightsail.

How do I avoid a surprise AWS invoice?

Set a billing alert on day one. Pair that with shutting down test resources you are not actively using, since idle compute and forgotten storage cause most unexpected charges.

Does data transfer cost extra on AWS?

Only outbound data, and only past your plan's allowance. Data moving into AWS stays free, and Lightsail bundles a transfer allowance into its flat price, but data served past that allowance bills separately per GB.

Can I switch from Lightsail to EC2 later without starting over?

Yes, though it takes real migration work. Many teams start on Lightsail for its steady pricing and move to EC2 once they need finer control over instances, storage, or networking than the bundle allows.