Amazon Lightsail Pricing: Why the $3.50/Month Bundle Is Both a Steal and a Trap

Amazon Lightsail is AWS’s price-bundled VPS offering — compute, block storage, data transfer, and IP all rolled into flat monthly prices starting at $3.50/month for the smallest Linux instance. For the right workload, the bundling is dramatically cheaper than the equivalent EC2 + EBS + Data Transfer math; for the wrong workload, the bundle hides overage cliffs, scaling friction, and migration cost that compounds with time spent on the platform.

This post is the bill story. For the architectural decision of when Lightsail fits versus when EC2/ECS/Fargate is right, the EC2 vs serverless and ECS vs EKS guides cover the broader platform decisions.

The Lightsail Pricing Bundle Structure

Why Lightsail Bundles Look So Cheap (Because They Are)

For a workload that fits inside a bundle, the math is genuinely favorable. A $5/month Lightsail bundle delivers:

• 1 GB RAM, 2 vCPU
• 40 GB SSD storage
• 2 TB of outbound data transfer
• 1 static IP

The à la carte equivalent on EC2:

• t4g.micro instance: ~$6/month
• 40 GB gp3 EBS: $3.20/month
• 1 EIP (assuming attached and running): $3.60/month (new charge since Feb 2024)
• 2 TB data transfer at $0.09/GB: $180/month

à la carte total: ~$193/month vs $5/month Lightsail bundle. The data transfer line is the dominant differential. For workloads that consume meaningful bandwidth and fit in a bundle, Lightsail is genuinely better-priced than EC2.

The Overage Cliff

The mirror image of the bundle saving: overages. Data transfer above the bundle allowance bills at $0.09/GB — the same standard EC2 egress rate. A $5 bundle with 2 TB included that sees 3 TB actual usage costs $5 + (1000 × $0.09) = $95 for the month. The bundle that looked dramatically cheap becomes substantially more expensive than it appeared.

Bundle Scaling: The Lock-In Effect

Each Lightsail bundle is a fixed combination of compute, storage, and transfer. Scaling up means picking a larger bundle — and the bundle tiers double in size at each step (1 GB → 2 GB → 4 GB → 8 GB → 16 GB → 32 GB). There is no flexibility within a tier: if you need 6 GB RAM, you take the 8 GB bundle and pay for the 2 GB you don’t use.

On EC2, you can pick any instance type. On Lightsail, you pick the closest bundle and accept the gap. For workloads that genuinely fit at a bundle tier, this is fine. For workloads that consistently want the in-between sizes, EC2’s granularity is meaningfully more cost-efficient.

The Migration-to-EC2 Friction

The most consequential Lightsail cost lives outside the bill: the cost of migrating to EC2 when the workload outgrows Lightsail. Lightsail instances are not directly EC2 instances — they run in a parallel infrastructure. To move a Lightsail workload to EC2, you create a Lightsail snapshot, export it to an EBS snapshot in the same account (this is supported), then launch a new EC2 instance from that EBS snapshot.

The process works but requires:

• A planned migration window with downtime (or a parallel-run period with DNS cutover).
• Re-establishment of any infrastructure that was Lightsail-specific (load balancer, CDN, managed database — these don’t migrate; they need EC2/RDS/CloudFront equivalents created).
• Operational change for the team — different console, different APIs, different security model.

The implication: starting on Lightsail is a multi-year commitment for that specific workload. If you anticipate the workload growing beyond the largest bundle (32 GB RAM, 8 vCPU) within 12–24 months, starting on EC2 from day one is operationally simpler even if the early-month bill is higher.

Managed Database: Cheaper Than RDS Only for Small Tiers

Lightsail Managed Database starts at $15/month for 1 GB RAM, 40 GB storage, 100 GB transfer. The same workload on RDS at db.t4g.micro with 40 GB gp3 storage is ~$15/month base plus data transfer. At the smallest tier, the two are similarly priced.

The Lightsail managed database does not support:

• Multi-AZ with sub-minute failover (Lightsail offers high availability at $30+/month tier)
• Read replicas (RDS supports up to 15)
• IAM database authentication
• Performance Insights
• Aurora-tier scaling

For workloads that need any of these features, RDS is required regardless of the Lightsail option being available. For simple managed database needs (single instance, daily backups, occasional restore), Lightsail Managed Database is operationally simpler.

When to Use Lightsail vs EC2 / ECS / RDS

A 30-Day Lightsail Bill Cleanup Plan

Week 1 — Overage audit. Identify instances exceeding bundle data transfer allowance. Upgrade to a larger bundle (more transfer included) or migrate the high-bandwidth workload to EC2 + CloudFront.

Week 2 — Idle resource cleanup. Find unattached static IPs (billing at $3.65/month each). Delete unused instances and their snapshots. Review managed databases for usage; downgrade or terminate idle ones.

Week 3 — Snapshot hygiene. Snapshots at $0.05/GB-month accumulate. Apply a retention policy. Delete snapshots older than 30 days unless they are tagged for compliance retention.

Week 4 — Migration evaluation. For each Lightsail workload, evaluate whether it has outgrown bundles or will within 12 months. Plan migration to EC2 for workloads in the growth path; keep Lightsail for genuinely-stable small workloads.

What This Post Doesn’t Cover

• Lightsail for WordPress — common entry-point use case; bundled WordPress images are pre-configured but the underlying pricing is the same as Linux bundles.
• Lightsail Container Service deep comparison with ECS Fargate — covered in container-platform decision content.
• Multi-region Lightsail patterns — possible but limited; serious multi-region work belongs on EC2/ECS.
• Lightsail for SaaS deployments — workable for very small SaaS but limits become apparent at modest scale.

If You Only Do One Thing This Week

Audit data transfer per Lightsail instance via the Lightsail console (Metrics tab → Network out). For any instance consistently exceeding 70% of its bundle’s data transfer allowance, plan either a bundle upgrade or a migration to EC2 + CloudFront. Overages compound silently; catching them early prevents the bundle-cost-plus-overages bill that looks nothing like the headline bundle price.

For the broader compute decision — Lightsail vs EC2 vs ECS vs Lambda — the EC2 vs Lambda comparison covers the broader trade-offs that determine which compute primitive is right for the workload.