AWS Lightsail Review 2026: Amazon's $5 VPS for People Afraid of AWS Billing

The AWS Billing Fear is Real. Lightsail Was Built to Fix It.

Every developer has the same AWS horror story. Maybe it's theirs, maybe it's a friend's, maybe they read it on Hacker News at 2 AM. Someone left a GPU instance running over a weekend. Someone forgot to delete a NAT Gateway. Someone's S3 bucket got scraped by bots. The bill arrived: $3,000. $8,000. One memorable Reddit post: $72,000.

That fear is the entire reason AWS Lightsail exists.

In 2016, Amazon was watching small developers flee to DigitalOcean and Vultr — providers with $5 plans, fixed monthly pricing, and control panels that didn't require a certification to navigate. The EC2 console had grown into a labyrinth of instance families (m5.xlarge? r6g.medium? What do these letters mean?), storage tiers, networking configurations, and a pricing calculator that needed its own tutorial. A freelancer who wanted a $10 WordPress server was not going to learn what a t3.micro is. Amazon was losing that market entirely.

So they built Lightsail: a separate console, a separate product, with fixed monthly prices printed in large friendly numbers. Pick a plan. Pick an OS. Click create. Your server is live in under a minute. The monthly price covers compute, SSD storage, bandwidth, and a static IP. No surprise bills. No pricing spreadsheets. No existential dread when you open the billing dashboard.

I signed up for Lightsail eight months ago with a specific question: where exactly does the simplicity end? Amazon promises the ease of DigitalOcean with the power of AWS behind it. That's a big promise. I wanted to find the seams — the moments where the friendly Lightsail console gives way to the full complexity of AWS, and whether that transition is graceful or painful.

The short answer: the simplicity is real for the first two months. Month three is when you start bumping into walls. And by month six, you've either committed to learning AWS properly or you've migrated to Vultr.

Here's everything I found.

Performance Benchmarks: What 8 Months of Data Actually Shows

Most VPS reviews benchmark a server once and publish the numbers. I ran tests monthly across my 8-month window, because Lightsail uses burstable CPU — and the difference between a fresh instance with full burst credits and a server that's been running a moderate workload for three weeks is significant enough to change your purchasing decision.

Here are the numbers from our standardized benchmark suite, tested on a $7/mo plan (1 vCPU, 1GB RAM) in US East (N. Virginia):

Now, look at that second row. CPU score of 3,800 with burst credits available, dropping to roughly 760 when credits are depleted. That is not a typo. That is an 80% performance cliff.

Lightsail uses the same T-class burstable CPU model as EC2. The $5 plan gives you a 5% CPU baseline — meaning sustained access to 5% of one vCPU core. You earn burst credits when running below that baseline, and burn them when running above it. For a typical web server that's idle 90% of the time and spikes during page loads, this model works surprisingly well. You'll never notice the burst mechanic.

But try to run a WordPress import, a database migration, or a sustained API workload, and the credits evaporate in minutes. When they're gone, your server crawls. I tested this deliberately in month four: ran a continuous CPU benchmark for 30 minutes. Performance started strong, held for about 12 minutes as credits burned down, then dropped off a cliff and stayed there. No warning in the Lightsail console. No alert. Just a server that suddenly felt like 2005.

The disk I/O story is less dramatic but still worth noting. At 40,000 read IOPS, Lightsail's EBS-backed storage is competent. It is not fast. Hetzner hits 58,000 IOPS on local NVMe. Hostinger reaches 65,000. If your application is database-heavy — WooCommerce with large catalogs, Nextcloud with many simultaneous users — you will feel the difference in page load times.

Where AWS infrastructure genuinely earns its reputation: networking. The 900 Mbps throughput and 1.1ms intra-region latency reflect decades of Amazon building the backbone that runs a significant chunk of the internet. Cross-region latency between Virginia and Oregon measured a consistent 62ms over my entire test period. No variance, no surprises. AWS does not have bad network days.

See how Lightsail stacks up against all 33 providers in our benchmark database →

Pricing Breakdown: Fixed Bills Until They Aren't

The pricing table is the best thing about Lightsail. Seriously. For a product from the company that invented cloud billing complexity, this is borderline revolutionary:

Clean. Simple. You know what you'll pay. That's the pitch, and for the base instance, it's true.

Now here's where the "predictable pricing" story gets complicated.

The Hidden Cost Stack

Your $5/mo instance is just the beginning. Here's what a realistic small production setup actually costs once you've been running for a few months:

Not everyone will hit $75. But most production users end up somewhere between $25-50/mo once they add the pieces that turn a bare VPS into an actual hosting stack. That's still predictable — and still cheaper than equivalent EC2 infrastructure — but it's a long way from the $5 in the marketing headline.

The Bandwidth Trap

This is the one place where Lightsail's fixed pricing can genuinely break. Each plan includes a transfer allowance (2TB on the $5 plan, scaling up). Exceed it, and you're charged $0.09 per GB of overage. That doesn't sound like much until you do the math: 100GB of overage is $9 — nearly doubling a $10/mo plan. Serve a popular download or get scraped by aggressive bots, and you can discover the overage charge on your next billing statement with no warning.

Compare that to Contabo, which includes 32TB of transfer. Or Hetzner, which includes 20TB. Or BuyVM, which offers completely unmetered bandwidth. The bandwidth limits are where Lightsail's DigitalOcean-competitor positioning falls apart — DigitalOcean itself includes more transfer at every price tier.

The 3-Month Free Trial: Read the Fine Print

New AWS accounts get the entry-level Lightsail plan free for 3 months. This is genuinely useful for evaluation. But "free" has footnotes: you need a credit card on file, snapshot storage is billed from day one, managed databases aren't included in the trial, and unattached static IPs cost $0.005/hour. Set a calendar reminder for day 85 or you'll start paying on autopilot.

The AWS Gateway Trap: When Lightsail Stops Being Simple

This is the section no AWS Lightsail review wants to write honestly, because the truth makes Amazon's product strategy look a little too transparent.

Lightsail is a funnel. It exists to get you into the AWS ecosystem through a door that doesn't look scary. Once you're inside, the ecosystem starts making demands.

Here's the progression I observed over 8 months, almost like clockwork:

Month 1-2: Everything lives inside the Lightsail console. You deployed an instance, set up a static IP, maybe pointed a domain via Route 53 (which Lightsail's DNS management handles natively). Life is simple. You're thinking: "Why does everyone complain about AWS? This is easy."

Month 3: You want to store user uploads in S3 instead of on the instance disk. Lightsail can do this — but configuring the IAM role requires visiting the main AWS console. You create a policy, attach it to the Lightsail instance's role, and suddenly you're reading IAM documentation. The simple console didn't prepare you for this.

Month 4-5: Traffic grew. You want CloudFront in front of your application. Lightsail has a built-in CDN feature, but it's limited. For custom cache behaviors, you need the full CloudFront console. Now you're configuring origin groups, cache policies, and distribution settings in the regular AWS interface. The Lightsail tab is open in one browser window and the AWS console in another.

Month 6-8: You need monitoring beyond what Lightsail's basic metrics show. CloudWatch is the answer, but it's an entirely separate AWS service with its own learning curve. You want email notifications, so you set up SNS. You want log aggregation, so you look at CloudWatch Logs. Each service is individually rational but collectively overwhelming. Your "simple VPS" now has tendrils into six different AWS services, each with its own console page, its own pricing model, and its own documentation.

This isn't a bug. It's the product strategy. Amazon built Lightsail knowing that successful projects outgrow it. The snapshot-to-EC2-AMI export path exists because Amazon wants you to graduate, not leave. Every AWS service you integrate during your Lightsail phase becomes a reason you can't easily switch to Vultr or Hetzner later. The switching cost accumulates quietly.

Is that malicious? No — it's smart business, and the services genuinely add value. But you should walk in with your eyes open. Lightsail isn't cheap hosting. It's AWS's customer acquisition tool priced like cheap hosting.

US Datacenter Coverage: 4 Regions, Multiple Availability Zones

Lightsail is available in four US AWS regions:

Four regions is adequate for coast-to-coast coverage but thin compared to competitors. Vultr offers 9 US locations including Miami, Dallas, Chicago, Atlanta, and Seattle. If you need a server physically close to users in the Southeast or Mountain West, Lightsail leaves a geographic gap.

What Lightsail offers that most VPS providers cannot: multiple availability zones within each region. You can deploy redundant instances across AZs for genuine fault tolerance — if one physical datacenter has an issue, your second instance in another AZ stays up. This is table stakes in the AWS world but genuinely unusual in the VPS market. If high availability matters to your use case, this architectural option is worth the tradeoff of fewer total locations.

For choosing the right region for your specific use case, our US Datacenter Location Guide covers latency maps and best practices.

What You Actually Get (and What's Suspiciously Missing)

The Ecosystem: This Is the Product

Strip away the AWS ecosystem, and Lightsail is an overpriced, average-performing VPS. I mean that literally — run a Lightsail instance in isolation and you're paying 3-5x more than Hetzner for comparable specs with worse disk I/O. The value proposition is entirely in what sits behind the VPS: native integration with S3 for storage, RDS for databases, CloudFront for CDN, Route 53 for DNS, SES for email, CloudWatch for monitoring, and roughly 200 other services.

My staging environment on Lightsail stores uploads in S3, sends transactional emails through SES, and caches static assets on CloudFront. Setting that up took about 45 minutes because everything lives in the same AWS account with the same IAM permissions. Replicating that stack across three different providers — a VPS here, Mailgun there, Cloudflare in front — would take a full day and ongoing maintenance to keep the credential rotation working. That integration tax is what you're actually paying to avoid with Lightsail.

Snapshots and the Golden Handcuffs

Both automatic and manual snapshots work well. Automatic snapshots capture your instance daily, retained for 7 days. Manual snapshots persist indefinitely. Storage costs $0.05/GB/month — not free, but reasonable. The feature that makes Lightsail genuinely clever: snapshots can be exported to EC2 AMIs. When your project outgrows Lightsail, you don't migrate to another provider. You stay in AWS and step up to EC2. Amazon designed the exit ramp to lead deeper into their ecosystem, not out of it.

Managed Databases: Worth It at Small Scale

MySQL and PostgreSQL starting at $15/mo with automated backups, failover, and maintenance windows. Is $15/mo for a managed database expensive? Compared to running your own — no. Compared to DigitalOcean's managed database at $15/mo — identical. Compared to just putting MySQL on the same Lightsail instance — yes, but you'll thank yourself when the instance crashes and your data is still intact on the separate database server.

Container Services: Simplified Docker (Emphasis on "Simplified")

Push a container image, get an HTTPS endpoint. For a single containerized app that needs to be publicly accessible, this works. For anything with service discovery, custom networking, or multi-container orchestration, you're back to ECS or EKS — which means the full AWS console and a sharp jump in complexity.

What's Missing (And Why It's Missing)

No auto-scaling. No custom instance types. Limited OS selection (no Arch, no FreeBSD, fewer distro versions than Vultr). No placement groups. No GPU instances. These aren't oversights — they're deliberate constraints. Every feature Lightsail lacks is a feature EC2 has. The absence is the upgrade path.

Who This Is Actually For (Be Honest With Yourself)

After 8 months, I've identified exactly four groups of people for whom Lightsail makes genuine sense:

Teams already deep in AWS. If your application already touches S3, CloudFront, and Route 53, adding a Lightsail compute instance is seamless. No cross-provider API bridging, no credential juggling, no firewall exceptions. Everything lives in the same account with the same billing. This is Lightsail's unbeatable use case.

Developers learning AWS for career reasons. AWS certifications matter on resumes. The 3-month free tier gives you a playground to learn IAM, VPC basics, and service integration without the EC2 complexity overhead. Lightsail is the training ground; EC2 is the exam. If your goal is AWS fluency, starting here is rational.

Small projects that will grow into AWS. Building an MVP that might eventually need auto-scaling, managed queues, or machine learning services? Starting on Lightsail means you're already inside the ecosystem when that day comes. The snapshot-to-AMI export is your predetermined upgrade path. Starting on Vultr and migrating to AWS later is significantly harder.

Windows VPS users who want simplicity. Lightsail's Windows Server blueprints with licensing included and pre-configured RDP access are among the least painful Windows VPS setups available. If you need a Windows VPS and you're already in the AWS ecosystem, this is the path of least resistance.

Who Should Stay Far Away

Anyone who doesn't need AWS services. This cannot be stated strongly enough. Without the ecosystem, Lightsail is a mediocre VPS at premium pricing. Hetzner gives you 4x the resources for less money. Vultr gives you better performance with 9 US locations. If your server runs in isolation — no S3, no CloudFront, no RDS — you are paying an ecosystem tax for an ecosystem you're not using.

Budget-conscious users. If you're hunting for the best VPS under $5, Lightsail's entry plan is a poor value compared to Contabo, RackNerd, or Hetzner at similar price points. The specs-per-dollar math doesn't even come close.

CPU-intensive workloads. Video encoding, CI/CD pipelines, data processing, machine learning training — anything that sustains high CPU utilization will burn through burst credits and hit the performance cliff. I watched a WordPress database migration that should have taken 5 minutes stretch to 40 minutes after credits depleted. Use Kamatera's dedicated CPU plans or Hetzner's CCX instances instead.

High-traffic sites without CDN discipline. The bandwidth overage at $0.09/GB means a traffic spike can generate a bill that dwarfs your instance cost. One client's small marketing site got featured on a popular newsletter — 200GB of extra transfer in three days, $18 in overage on a $10 plan. On Hetzner, that same traffic wouldn't have registered against the 20TB allowance.

People who need human support. If your production server goes down at 2 AM and you need a human being to help, the free tier gives you documentation links and nothing else. The $29/mo Developer plan offers email-only support during business hours. Phone access starts at $100/mo. For a $10 server. That ratio is hard to justify.

Lightsail vs DigitalOcean vs Vultr: The $5 VPS Showdown

These three are the most common comparison set for Lightsail, and it's the comparison Amazon explicitly designed Lightsail to compete in. So let's be thorough:

Lightsail vs DigitalOcean: If you handed me $5 and said "get me a VPS for a personal project with no AWS dependencies," I'd choose DigitalOcean every time. Faster NVMe storage, better documentation, included support, and a community ecosystem of tutorials that dwarfs Lightsail's. DigitalOcean wins on pure VPS merit. Lightsail only wins when the project needs AWS services — and then it wins decisively, because no amount of DigitalOcean add-ons replaces native S3 + CloudFront + SES integration.

Lightsail vs Vultr: Vultr's advantage is geographic coverage (9 US locations vs 4) and flexibility (more OS options, bare metal available, AMD and Intel choices). Vultr doesn't try to be a cloud platform — it's a fast, flexible VPS provider. If latency to specific US cities matters to your application, Vultr's location density is unbeatable. Lightsail's AZ redundancy within regions is a counter-argument, but for most users, being closer to their users beats being redundant within a region.

For a deeper comparison of these providers with more benchmarks, check our head-to-head comparison pages.

Final Verdict: 4.1/5 — A Good AWS Product, an Average VPS

After 8 months, here's what I know: Lightsail's 4.1 rating is almost entirely carried by the AWS ecosystem. If I rated the VPS in isolation — the compute, the storage, the pricing against competitors — it would land around 3.2. The CPU is burstable with a vicious performance cliff. The disk I/O is average. The support model is actively hostile to small users. Mid-range plans cost 3-5x what Hetzner charges for identical specs.

But the VPS doesn't exist in isolation, and that's the point. Lightsail is the on-ramp to the most comprehensive cloud platform in existence. The native access to S3, CloudFront, RDS, SES, Route 53, and hundreds of other services is something no standalone VPS provider can replicate, no matter how fast their NVMe or how cheap their plans. For teams building applications that will grow into AWS services, that on-ramp has genuine, measurable value.

The question you need to answer before signing up is simple: Does your project need AWS, or does it need a VPS?

If the answer is AWS — if you're already using S3, if you'll eventually need CloudFront, if your employer runs on AWS and you're building skills — Lightsail is a smart entry point. Accept the performance ceiling, appreciate the fixed pricing, and know that the snapshot-to-EC2 export is waiting when you outgrow it.

If the answer is just a VPS — just a server, running your code, as fast and cheap as possible — Lightsail is a bad deal. Get a Hetzner instance for a quarter of the price. Get a Vultr instance with NVMe storage and 9 US locations. Get a DigitalOcean droplet with included support and a better community. You'll have more resources, more flexibility, and fewer hidden constraints.

Lightsail is a 4.1 because it does exactly what Amazon designed it to do: make AWS accessible to people who were afraid of the billing page. That it does this while being a mediocre VPS is the tradeoff. For the right user, it's a tradeoff worth making. For everyone else, the VPS market has better options at every price point.

Frequently Asked Questions

Is AWS Lightsail really simpler than EC2?

Yes, but only up to a point. Lightsail gives you a separate, cleaner console with fixed monthly pricing, pre-built blueprints, and no need to understand instance families, EBS volume types, or security group configurations. You can deploy a WordPress server in 60 seconds. But the moment you need VPC peering, custom IAM policies, or integration with services not exposed in the Lightsail console, you're dumped into the full AWS Management Console — which has a learning curve measured in weeks, not hours. Lightsail delays the complexity; it doesn't eliminate it.

What happens when I exceed my Lightsail bandwidth limit?

Lightsail charges $0.09 per GB for outbound data transfer that exceeds your plan's monthly allowance. The $5 plan includes 2TB, scaling up from there. Inbound transfer is always free. For context: if you exceed by 100GB, that's an extra $9 on a $5 plan — nearly doubling your bill. A single viral blog post serving large images could push you well beyond the limit. This is the main area where Lightsail's "predictable pricing" promise breaks down.

Can I migrate from Lightsail to EC2 without downtime?

Not with zero downtime, but close. The process is: create a Lightsail snapshot, export it as an EC2 AMI (takes 15-30 minutes depending on disk size), launch an EC2 instance from the AMI, then swap your DNS or Elastic IP. Total downtime can be under 5 minutes if you pre-stage everything. The snapshot export preserves your entire disk state — OS, applications, data, configurations. It's one of Lightsail's genuinely well-designed features and the clearest proof that Amazon built Lightsail as an EC2 on-ramp.

How does Lightsail pricing compare to DigitalOcean and Vultr?

At the entry level ($5/mo), Lightsail gives you 1 vCPU and 1GB RAM — identical to DigitalOcean and Vultr's $5 plans. But as you scale up, the relative value shifts. The 4GB RAM tier costs $20/mo on Lightsail vs $24/mo on DigitalOcean and Vultr — Lightsail is actually cheaper on paper. Where Lightsail really loses is against Hetzner ($4.59/mo for 4GB) and Contabo. You're paying an AWS ecosystem tax, and whether that's worth it depends entirely on how many AWS services your application touches.

Is Lightsail good for running WordPress?

It's decent, not great. Lightsail has a 1-click WordPress blueprint (Bitnami-based) that deploys in under a minute with Apache, MySQL, and phpMyAdmin pre-configured. The $10/mo plan with 2GB RAM handles a WordPress site with moderate traffic (up to 50,000 monthly visitors). The main advantage over other VPS providers is pairing WordPress with CloudFront CDN and S3 for media storage — all within the same AWS account. The main disadvantage is that Bitnami's stack has a non-standard directory structure that can confuse WordPress developers used to standard setups. For WordPress-specific hosting, our WordPress VPS guide covers more options.

Does AWS Lightsail include free technical support?

No. The free Basic Support tier only covers billing questions and service health dashboards. If your Lightsail instance is unreachable and you need a human to help troubleshoot, you need at minimum the Developer Support plan at $29/month (email only, business hours, 12-24 hour response). Business Support with 24/7 phone access starts at $100/month. For a $5-12/mo VPS, paying $29/mo just to email someone about it is a hard sell. Compare this to DigitalOcean (24/7 chat included) or Hostwinds (24/7 phone included at no extra cost).

What are Lightsail's burstable CPU limits and how do they affect performance?

Lightsail instances use the same T-class burstable model as EC2. You get a baseline CPU allocation (varies by plan) and accumulate burst credits when running below baseline. When you need more CPU, you burn credits to burst above baseline. If credits run out, you're throttled to baseline — which is noticeably slow. The $5 plan has a 5% baseline (meaning sustained access to 5% of one vCPU core). The $10 plan bumps to 20%. For web serving and moderate PHP workloads, bursting is fine. For sustained CPU tasks like video encoding, CI/CD builds, or data processing, you'll hit the ceiling fast. There's no option to pay for unlimited burst like EC2's unlimited mode.

Can I use Lightsail for a production e-commerce store?

You can, but I'd only recommend it if you're already committed to the AWS ecosystem. A WooCommerce store on the $10-20/mo plan works for small catalogs (under 500 products) with moderate traffic. Pair it with Lightsail's managed database ($15/mo) to separate compute from data, and CloudFront for static asset delivery. The total cost ($25-35/mo) is competitive with managed WooCommerce hosting. However, the burstable CPU will struggle during traffic spikes (flash sales, viral social posts), and the bandwidth limits mean high-traffic stores risk overage charges. For pure e-commerce hosting without AWS dependencies, Cloudways or a dedicated Vultr instance offers better price-to-performance.

Is the 3-month free trial on AWS Lightsail actually free?

The entry-level Lightsail plan is free for the first 3 months for new AWS accounts — that part is real. But "free" has footnotes. You still need a credit card on file. If you add a static IP and don't attach it to an instance, you're charged. If you create snapshots, you're charged for storage ($0.05/GB/month). If you spin up a managed database alongside your free instance, that's $15/mo from day one. And critically, if you forget to cancel or downgrade before month 4, billing starts automatically. Set a calendar reminder for day 85. The trial is genuinely useful for evaluation — just don't assume everything in the Lightsail console is covered by it.