Lightsail bundles data into a fixed plan; EC2 bills per component and takes discounts. Which is cheaper at your size?
For small teams and individuals picking a server on AWS, the first question is usually: Lightsail or EC2?
The common answer — "Lightsail for beginners, EC2 for professionals" — is useless, because it describes how hard it is to start, while what actually affects your wallet is the billing model.
And there is a dividing line almost nobody mentions: Lightsail cannot use Reserved Instances or Savings Plans. So past a certain size, its cost curve is overtaken by EC2 — even though EC2 looks more expensive and more complex. That is the character of the second layer: commitment discounts are not available on every product. All five compared in cloud discount mechanisms compared.
Not two sizes — two billing models
Compressed to one line: Lightsail sells you a plan; EC2 sells you parts.
| Lightsail | EC2 | |
|---|---|---|
| Billing shape | Fixed monthly plan (instance + storage + data allowance bundled) | Priced per component (instance, disk, snapshots, transfer separately) |
| Data transfer | Plan includes an outbound allowance | Outbound transfer billed by usage |
| Commitment discounts | No (no Reserved Instances / Savings Plans) | Yes (RI / Savings Plans / Spot) |
| Elasticity | Change plan manually; no autoscaling | Auto Scaling groups, load balancing, full networking |
| Good for | One machine, predictable traffic, no networking wanted | Several machines, elasticity, VPC/network detail |
The most useful judgement: Lightsail's value is turning the least predictable item — data transfer — into a fixed cost; EC2's value is that once you have scale, commitments push the unit rate down. Which you pick depends on which of those you need more.
Plans and sizes are whatever the official page says (no price lists here — they change); details of the lightweight option are on using Lightsail.
Lightsail: a fixed plan with a data allowance
Lightsail prices like this: pay a fixed monthly fee and get a machine of fixed size, a disk of fixed size, and a fixed outbound data allowance.
Its real appeal is three things:
- The bill is predictable. The number barely moves month to month; no watching the console to see how much traffic ran.
- Transfer is bundled. Data transfer out is the item most likely to run away on an AWS bill (see AWS discounts beyond EC2), and Lightsail folds part of it into the monthly fee.
- No networking to run. VPC, subnets, routing and security groups are simplified away — for someone who just wants a website, that saves learning time and misconfiguration risk.
⚠️ The allowance is not infinite: beyond the bundled outbound allowance, excess is normally billed by usage. So the "fixed monthly fee" holds only within the allowance. If traffic can spike (a share, a scrape), that excess becomes a surprise. Estimate monthly outbound traffic before choosing a plan.
One more: Lightsail also has a trial period (duration and eligible plans per the official page), useful for validating an idea — but decide before it ends, otherwise it converts to a paid plan automatically.
EC2: priced per component, but it earns discounts
EC2 works the other way: instances bill per hour (or second), and disks, snapshots, public IPs and outbound transfer each bill separately. The unit rate looks higher and the bill is more complex — but that buys two things.
- Discounts are available. Reserved Instances, Savings Plans and Spot all apply to EC2, so a long-running steady instance can come in well below on-demand. This is the key to EC2 overtaking Lightsail at scale.
- It can be tuned finely. Separate components mean you optimise each: change disk type, set snapshot lifecycles, put transfer behind a CDN, change CPU architecture (see how much Graviton saves). Lightsail bundles all of that, leaving little room to optimise.
The price is complexity: you break the bill down yourself, configure the network yourself, and compute the commitment baseline yourself (how to buy is on how to buy AWS Reserved Instances). For one small site, that effort is not worth it.
An often-missed combination: EC2's elastic portion can run on Spot, and Lightsail has no such option. So "baseline on reserved/on-demand + peaks on Spot" only exists on EC2 — another reason EC2 wins once you have scale.
The dividing line nobody mentions: Lightsail cannot use commitment discounts
This is the point this page most wants to land, and the root of most wrong choices.
AWS commitment discounts (Reserved Instances, Savings Plans) apply to EC2-class compute. Lightsail is a separate bundled product and is not covered. The consequence:
| Stage | Lightsail | EC2 |
|---|---|---|
| Just starting (one machine, low traffic) | Cheaper: allowance bundled, bill predictable | On-demand is high and transfer bills separately |
| Settled (1–3 machines for a full year) | Still a fixed fee with no room to fall | Commitments cut the unit rate substantially |
| Scaling (several machines plus peaks) | Bigger plans, cost rises linearly | Baseline commitment + Spot elasticity keeps unit cost falling |
⛔ So the real dividing line is not "do you know the technology" but "will this workload keep running steadily". Long-lived → EC2 commitments eventually win. Temporary or experimental → Lightsail's simplicity and predictability are worth more.
A rough self-check: if you have paid for the same machine for three consecutive months with no plan to retire it, it is time to price EC2. Staying on Lightsail means paying an undiscounted fixed fee for convenience.
When Lightsail is cheaper, when EC2 is
Condensed into one decision table. Note the criteria are workload shape, not skill level:
| Your situation | Choose | Why |
|---|---|---|
| A blog / brochure site / small tool, predictable traffic | Lightsail | Allowance bundled, predictable bill, no networking |
| Temporary validation, campaign page, gone in weeks | Lightsail | Delete it any time; no commitment, no need for discounts |
| One or two services, definitely running a year | EC2 (start on demand) | Run a month, get a baseline, then consider commitments |
| Steady for 3+ months with no retirement plan | EC2 + RI / Savings Plans | Commitment discounts are unavailable on Lightsail |
| Clear peaks and troughs, needs autoscaling | EC2 | Lightsail has no autoscaling and no elastic Spot |
| Custom networking, subnets, peering | EC2 | Lightsail's networking is deliberately simplified |
| Heavy outbound traffic (media, downloads, image hosting) | EC2 + CDN | The allowance will be exceeded and billed; only CDN reduces it structurally |
Two boundaries people cross by mistake:
- "I will start on Lightsail and deal with it later" usually means staying forever. Migration means redeploying; the later you do it, the more it costs. If you already know it is long-lived, start on EC2.
- Conversely, do not jump to EC2 "in case we scale". A tiny site on EC2 pays on-demand rates and handles transfer and networking by hand — work for nothing.
In one line: Lightsail buys peace of mind and predictability; EC2 buys room to optimise. The larger and steadier the workload, the more the latter is worth.
Moving up smoothly as you grow
There is no one-click upgrade from Lightsail to EC2 — they are separate products, so it means deploying again. A few things make it smooth:
- Externalise state first. Move the database to a managed service, files to object storage, sessions to a cache. Once the machine only runs code, migration is just a deployment.
- Switch with DNS. Deploy and validate fully on EC2, then point the domain over (lower the TTL beforehand to shorten the cutover).
- Run both for a while. Keep both environments live until the new one is proven, then retire the old. That overlap costs far less than a rollback after a bad cutover.
- Buy discounts only after you arrive. Run on demand for a month on EC2, get a real baseline, then decide how much to commit — the reverse order locks in a wrong number (see how to buy AWS Reserved Instances).
A cheaper route is to deploy for portability from day one: install the environment from a script or image rather than configuring a machine by hand. A hand-configured machine cannot be moved — the most common trap for Lightsail users.
If migration cost is what worries you: hand the discount question to the channel instead — settling through a reseller lowers what you actually pay, and does not change whether you run Lightsail or EC2. That layer does not conflict with official discounts; they stack — see AWS discounts and reseller pricing.
Common questions
What happens when the Lightsail allowance runs out?
Excess outbound transfer is normally billed by usage, so the "fixed monthly fee" holds only inside the allowance. Workloads whose traffic can spike (shared, scraped, media files) should watch this closely. If outbound transfer is the main cost, the fix is a CDN, not a bigger plan — see AWS discounts beyond EC2.
Can Lightsail use Reserved Instances or Savings Plans?
No. Those commitment discounts cover EC2-class compute; Lightsail is a separate bundled product and is out of scope. This is the single most important cost difference: once a workload is steady, EC2 can cut the unit rate with a commitment, while Lightsail's monthly fee has no room to fall.
I am already on Lightsail — is moving to EC2 painful?
There is no one-click upgrade; it means redeploying. How painful depends on whether state is externalised: with database, files and sessions outside, it is "deploy on EC2 + switch DNS"; if the environment was configured by hand on that machine, it is essentially a rebuild. Use a script or image from day one.
EC2 on-demand looks much more expensive — is it worth it?
Depends on the horizon. For something you may retire, no — on-demand plus separately billed transfer genuinely costs more short-term. But for anything you know will run a year or more, EC2 plus a commitment usually overtakes it. Simple test: three months of paying for the same machine with no retirement plan — price the EC2 option.
Can I use both?
Yes, and it is common: keep a steady, predictable public site on Lightsail and put compute that needs elasticity or commitments on EC2. They are separate products and do not conflict. Just remember — whatever sits on Lightsail will never earn a commitment discount.
How much does choosing wrong cost?
Two main leaks: leaving a steady long-lived workload on Lightsail, which means paying an undiscounted fixed fee for convenience; and putting a temporary workload on EC2 and buying a commitment, locking a year you will not use. The second is more expensive — commit only after the workload is steady (see how to buy AWS Reserved Instances).