---
title: Amazon Lightsail Pricing: Why the $3.50/Month Bundle Is Both a Steal and a Trap
description: Lightsail bundles compute, storage, and bandwidth into flat monthly prices starting at $3.50/month — dramatically cheaper than the equivalent EC2 + EBS + Data Transfer math for predictable small workloads. The trap: data transfer overages bill at $0.09/GB, scaling locks you into bundle tiers, and migration to EC2 is more disruptive than starting on EC2 from day one.
url: https://www.factualminds.com/blog/amazon-lightsail-pricing-bundles-vs-ec2-true-total-cost/
datePublished: 2026-06-13T00:00:00.000Z
dateModified: 2026-06-13T00:00:00.000Z
author: palaniappan-p
category: Cost Optimization & FinOps
tags: amazon-lightsail, lightsail-pricing, aws-pricing, cost-optimization, finops
---

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

> Lightsail bundles compute, storage, and bandwidth into flat monthly prices starting at $3.50/month — dramatically cheaper than the equivalent EC2 + EBS + Data Transfer math for predictable small workloads. The trap: data transfer overages bill at $0.09/GB, scaling locks you into bundle tiers, and migration to EC2 is more disruptive than starting on EC2 from day one.

import PricingHeroStats from '~/components/blog/PricingHeroStats.astro';
import PricingDimensionTable from '~/components/blog/PricingDimensionTable.astro';
import BillSurpriseCallout from '~/components/blog/BillSurpriseCallout.astro';
import PricingDecisionCard from '~/components/blog/PricingDecisionCard.astro';

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.

<PricingHeroStats
  stats={[
    { value: '$3.50', label: 'Smallest Linux bundle / mo', note: '512 MB RAM, 2 vCPU, 20 GB SSD, 1 TB transfer' },
    { value: '$0.09', label: 'Data transfer overage / GB', note: 'Same as EC2; lurks above bundle allowance' },
    { value: '$15', label: 'Smallest managed DB / mo', note: 'MySQL or PostgreSQL; 1 GB RAM, 40 GB storage' },
    { value: '$2.50', label: 'CDN distribution / mo', note: '50 GB transfer included' },
  ]}
  caption="us-east-1 list prices, June 2026. Verify against the AWS Lightsail pricing page for your region."
/>

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

<PricingDimensionTable
  title="Lightsail pricing breakdown — us-east-1, June 2026"
  intro="Bundles are the headline feature. Overages, managed services, and add-ons bill independently and can dominate at scale."
  region="us-east-1"
  dimensions={[
    {
      name: 'Linux instance — smallest bundle',
      unitPrice: '$3.50 / month',
      example: '512 MB RAM, 2 vCPU, 20 GB SSD, 1 TB transfer',
      monthly: '$3.50',
      note: 'Entry-level VPS pricing',
      highlight: true,
    },
    {
      name: 'Linux instance — mid bundle',
      unitPrice: '$10 / month',
      example: '2 GB RAM, 2 vCPU, 60 GB SSD, 3 TB transfer',
      monthly: '$10',
      note: 'Most common production tier',
    },
    {
      name: 'Linux instance — top bundle',
      unitPrice: '$160 / month',
      example: '32 GB RAM, 8 vCPU, 640 GB SSD, 7 TB transfer',
      monthly: '$160',
      note: 'Largest pre-bundled tier',
    },
    {
      name: 'Windows instance',
      unitPrice: 'Roughly 2× Linux equivalent',
      example: '2 GB RAM Windows bundle',
      monthly: '$20',
      note: 'Windows licensing premium',
    },
    {
      name: 'Data transfer overage',
      unitPrice: '$0.09 / GB',
      example: '500 GB over bundle',
      monthly: '+$45',
      note: 'Same as EC2 egress; quickly dominates',
      highlight: true,
    },
    {
      name: 'Additional block storage',
      unitPrice: '$0.10 / GB-month',
      example: '100 GB additional disk',
      monthly: '$10',
      note: 'Like EBS gp2 pricing',
    },
    {
      name: 'Object storage',
      unitPrice: '$1 / mo (5 GB, 25 GB transfer, 25K requests)',
      example: 'Smallest plan',
      monthly: '$1',
      note: 'Tiers up to $50/mo (5 TB)',
    },
    {
      name: 'Container service',
      unitPrice: '$7–$80 / mo per node',
      example: 'Small production container',
      monthly: '$7',
      note: 'Bundled compute, storage, load balancing',
    },
    {
      name: 'Managed database (MySQL/PostgreSQL)',
      unitPrice: '$15 / mo smallest',
      example: '1 GB RAM, 40 GB storage',
      monthly: '$15',
      note: 'Up to $470/mo top tier',
    },
    {
      name: 'CDN distribution',
      unitPrice: '$2.50 / mo (50 GB transfer)',
      example: 'Static content delivery',
      monthly: '$2.50',
      note: 'Tiers up to 12.5 TB',
    },
    {
      name: 'Load balancer',
      unitPrice: '$18 / month',
      example: 'HTTP/HTTPS load balancing',
      monthly: '$18',
      note: 'Includes free SSL cert via Lightsail',
    },
    {
      name: 'Static IP unattached',
      unitPrice: '$0.005 / hour = $3.65 / month',
      example: 'IP not attached to running instance',
      monthly: '$3.65',
      note: 'Free while attached and running',
    },
    {
      name: 'Snapshots',
      unitPrice: '$0.05 / GB-month',
      example: '20 GB instance snapshot',
      monthly: '$1',
      note: 'Same rate as EBS snapshots',
    },
  ]}
  footnote="Bundles are the appeal. Overages, additional services, and the cost of moving off Lightsail later are the considerations."
/>

## 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.

<BillSurpriseCallout
  variant="surprise"
  title="Lightsail instance hosting a viral content moment"
  amount="Bundle + $0.09/GB on every TB above allowance"
>
  A small site on a $10 Lightsail bundle (3 TB transfer included) that goes viral and consumes 20 TB in a week incurs 17
  TB × $0.09 = $1,530 in overages on top of the $10 bundle. The bundle pricing was designed for predictable workloads;
  viral traffic patterns blow through the included transfer immediately. For variable-traffic workloads, CloudFront +
  EC2 with optimized caching and the right price class is the better architecture.
</BillSurpriseCallout>

## 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

<PricingDecisionCard
  headline="Lightsail for predictable small workloads that won't outgrow bundles; EC2/ECS/RDS for everything else, including workloads with growth uncertainty."
  useWhen={[
    'Personal sites, blogs, portfolios with predictable low-to-moderate traffic',
    'Small-business websites where the operational simplicity of bundled pricing justifies the lower flexibility',
    'Development sandboxes where you want a clean per-month cost without tracking EC2 + EBS + Data Transfer separately',
    'Simple internal tools (wiki, ticketing) within a small organization',
    'Static-content sites where Lightsail bundle + CDN distribution is operationally simpler than S3 + CloudFront',
    'Container services for simple production workloads (one or two services, predictable scale)',
  ]}
  avoidWhen={[
    'Workloads with variable or viral traffic — overages dominate the bill',
    'Workloads anticipated to grow beyond the 32 GB / 8 vCPU largest bundle within 1–2 years',
    'Workloads requiring Spot, Reserved Instances, or Savings Plans economics',
    'Multi-instance architectures requiring autoscaling — Lightsail lacks autoscaling primitives',
    'Workloads requiring RDS-specific features (read replicas, Multi-AZ with sub-minute failover, IAM auth)',
    'Anything intended to remain on AWS long-term that will eventually need EC2 features — start on EC2',
  ]}
  footnote="Lightsail is the right answer for the narrow band of workloads that genuinely fit bundles forever. For everything else, the migration cost outweighs the early-month bundle saving."
/>

## 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](/compare/aws-ec2-vs-lambda/) covers the broader trade-offs that determine which compute primitive is right for the workload.

## FAQ

### Is Lightsail really cheaper than EC2 for small workloads?
For workloads that fit within a bundle, yes — significantly. A Lightsail $5/month bundle includes 1 GB RAM, 2 vCPU, 40 GB SSD, and 2 TB of data transfer. The equivalent on EC2 would be a t4g.micro (~$6/month) plus 40 GB gp3 EBS ($3.20) plus the 2 TB data transfer at $0.09/GB = $180. Pre-bundled, the Lightsail offering is ~$5; built à la carte on EC2, the same resources cost ~$190 because of the data transfer line. The economics only flip when the workload outgrows the bundle or needs EC2-only features (Spot, Reserved Instances, autoscaling groups, custom AMIs).

### What happens when traffic exceeds the bundled data transfer allowance?
Overages bill at $0.09/GB for outbound traffic — the same rate as standard EC2 internet egress. A bundle that includes 2 TB of transfer with actual usage of 3 TB costs the bundle price plus 1000 GB × $0.09 = $90 in overage. On a $5 instance, overage can be 20× the base price. The mitigation: monitor data transfer per instance via the Lightsail console; if monthly usage consistently exceeds the bundle allowance, either upgrade to a larger bundle (more transfer included) or migrate to EC2 + CloudFront where transfer can be optimized differently.

### Why is migration from Lightsail to EC2 so painful?
Lightsail instances run in a separate AWS account boundary internally — you cannot snapshot a Lightsail instance and launch it as an EC2 AMI directly. Migration paths involve creating a Lightsail snapshot, exporting it (which creates an EBS snapshot in the same account), and launching a new EC2 instance from that. The process works but requires downtime and a one-time migration effort. The decision to start on Lightsail versus EC2 effectively commits you to the platform for the workload lifetime; switching later is non-trivial. For workloads that may grow beyond bundles within 12 months, starting on EC2 from day one is operationally simpler.

### How does Lightsail managed database pricing compare to RDS?
Lightsail managed databases (MySQL, PostgreSQL) start at $15/month for the smallest tier (1 GB RAM, 40 GB storage, 100 GB transfer) and go up to ~$470/month for the largest. The equivalent RDS instance at db.t4g.micro with 40 GB gp3 storage is ~$15/month base plus data transfer. For small managed-database workloads, Lightsail and RDS are similarly priced. For workloads that need RDS-specific features (read replicas, Multi-AZ with sub-minute failover, IAM database authentication, Performance Insights, Aurora-tier scaling), RDS is required regardless of the Lightsail option being cheaper.

### When is the Lightsail CDN distribution cheaper than CloudFront?
Lightsail CDN distributions start at $2.50/month for 50 GB of transfer, up to $215/month for 12.5 TB. CloudFront is pay-as-you-go at standard CDN rates (~$0.085/GB for the first 10 TB in North America). For predictable static-content workloads at sub-12 TB volumes, Lightsail CDN is simpler and often cheaper. For variable or higher-volume workloads, CloudFront with appropriate caching and the right price class is more flexible. Lightsail CDN is appropriate for the same audience as the rest of Lightsail: predictable, small-to-medium workloads where bundled pricing is operationally simpler than à la carte.

### Is Lightsail Container Service cheaper than ECS Fargate?
For consistent steady-state container workloads, sometimes. Lightsail Container Service bundles compute, storage, and load balancing for $7–$80/month per node. The equivalent on ECS Fargate is per-vCPU-hour and per-GB-hour rates that vary with workload. At low scale (one or two small containers running 24/7), Lightsail Container Service is often cheaper. At any scale that benefits from Fargate Spot (70% discount) or that needs autoscaling, Fargate becomes cheaper. Use Lightsail Container Service for development environments, internal tools, or simple production workloads with no autoscaling requirement.

### What about Lightsail Object Storage vs S3?
Lightsail Object Storage starts at $1/month for 5 GB storage, 25 GB transfer, 25K requests — the smallest "I just need somewhere to put a few files" tier. Pricing scales up to ~$50/month for 5 TB / 5 TB / 5M requests. S3 with similar storage and transfer is comparably priced at low volume but offers a much richer API surface (versioning, lifecycle, replication, intelligent tiering, etc.) that Lightsail Object Storage does not match. For applications that need any S3-specific feature, use S3 directly; Lightsail Object Storage is appropriate only for the simplest "bucket of files" use cases inside a Lightsail workload.

---

*Source: https://www.factualminds.com/blog/amazon-lightsail-pricing-bundles-vs-ec2-true-total-cost/*