Choose the networking type before comparing prices

Scope: US East (Ohio), Linux/Unix, General Purpose, the five smallest sizes. The rows pair the published IPv4 and IPv6-only cards; they are not the entire Lightsail catalog. The last column is our twelve-full-month price difference, assuming each displayed rate stays unchanged.

MemoryvCPUsSSDTransferIPv4 USD/moIPv6-only USD/mo12-month difference
0.5 GB / 512 MB (page labels)220 GB1 TB$5$3.50$18.00
1 GB240 GB2 TB$7$5$24.00
2 GB260 GB3 TB$12$10$24.00
4 GB280 GB4 TB$24$20$48.00
8 GB2160 GB5 TB$44$40$48.00

Data from AWS official Lightsail pricing → Virtual servers → Bundles with public IPv4 address / Bundles with IPv6 address only → Linux/Unix → General Purpose, first five cards in each section. Checked 2026-11-13 04:06 UTC. Memory labels on the smallest pair are preserved as printed. Formula for the last column: (IPv4 monthly card − IPv6-only monthly card) × 12. The transfer allowance shown applies to Ohio; some other Regions have reduced allowances.

First year and second year: a paid-service budget, not a free-credit promise

Model one 1 GB IPv4 instance, a 32 GB attached disk, and a total of 40 GB of billable manual snapshot storage for twelve complete billed months. The quantities are our assumptions. The monthly resource subtotal is $7 + (32 × $0.10) + (40 × $0.05) = $12.20. First year = $12.20 × 12 = $146.40. With unchanged resources and rates, second year = $146.40; the modelled change is $0. This is not a prepaid annual product or a guaranteed future renewal quote.

For the IPv6-only 1 GB alternative, the same storage assumptions give $5 + $3.20 + $2 = $10.20/month, or $122.40 for twelve complete months. The networking choice changes this model by $146.40 − $122.40 = $24/year. That comparison only applies if your clients and dependencies can use IPv6; a static IPv4 cannot be attached to an IPv6-only instance.

Do not subtract a fixed first-year promotion from this budget. The official Billing FAQ says previous short-term trial offers were replaced by the AWS Free Tier, while already-started trials have their own remaining periods. Your eligible credit, expiry and a guaranteed future tariff were Not obtained. Check the account's actual entitlement instead of assuming an old free-trial article is a current offer.

Evidence: the two 1 GB official bundle cards; Block storage, opening pricing sentence; Instance and disk snapshots, rate card; Billing and account management → What happened to Lightsail's free trial offers?; What if I am already on a free trial?; What do Lightsail static IPv4 addresses cost?. Snapshot size means billable stored data, not a claim that every snapshot equals the whole allocated disk.

Transfer and extra storage: two separate meters

For our Ohio scenario, assume the transfer report has already identified 40 GB of chargeable outbound overage after allowances and free traffic are accounted for. This is not 40 GB of all inbound-plus-outbound traffic. Keep the 32 GB extra disk and 40 GB billable snapshot storage from the annual model.

Chargeable transfer = 40 GB × $0.09/GB = $3.60. Added disk = 32 GB × $0.10/GB-month = $3.20. Snapshot storage = 40 GB × $0.05/GB-month = $2. Resource subtotal = $7 + $3.60 + $3.20 + $2 = $15.80. The extra disk is provisioned capacity, not an automatic penalty for exceeding the root disk. A separately metered automatic root-disk-overflow price was Not obtained.

Both inbound and outbound traffic can consume an instance allowance, but only qualifying excess outbound traffic is billed. Allowance aggregation is tied to bundle and Region, not a universal account-wide bucket. Creating a new instance does not erase overage already accrued. These distinctions determine which GB enter the formula; the unit price alone cannot calculate your invoice.

Evidence: Data transfer in Lightsail → What types of data transfer do I get charged for with instances?, US East (Ohio) bullet; How does my data transfer allowance work for instances?, paragraphs 1–3 and Example 6. Storage rates: the official Block storage and Instance and disk snapshots cards linked above. Traffic, disk and snapshot quantities are our scenario.

When a larger bundle can cost less than transfer overage

Compare choosing the $5 IPv4 bundle with 1 TB transfer versus the $7 IPv4 bundle with 2 TB before a new billing period. The extra plan cost is $2/month. At Ohio's $0.09 per chargeable GB, $2 ÷ $0.09 = about 22.22 GB is the compute-price break-even point.

Our concrete case assumes 23 GB would be chargeable overage on the smaller bundle, while the same traffic fits the larger bundle's allowance. The smaller choice costs $5 + (23 × $0.09) = $7.07 before other resources; the larger one costs $7 with no overage in this case. That is $0.07 less, with more memory and disk included. This is a conditional plan-selection calculation, not a promise that upgrading after the event cancels $2.07 of fees.

Evidence: the first two IPv4 General Purpose cards and their 1 TB / 2 TB Transfer labels; Ohio outbound rate, allowance aggregation and Example 6. The 23 GB excess and the larger bundle fully covering the workload are our assumptions. Check the actual bundle, timing and quota before applying this threshold.

After deletion: inspect the disk, snapshot and static IP separately

This models a later full month, not the month in which you click Delete. Keep a 32 GB attached disk and 40 GB of billable manual snapshot storage. For any detached static IP, assume 720 chargeable hours after the documented grace condition; this is an assumed chargeable-hour count, not an extra monthly bundle cap.

State for the modelled period1 GB IPv4 instanceExtra diskManual snapshotsStatic IPResource subtotal
Running or stopped; IP stays attached$732 × $0.10 = $3.2040 × $0.05 = $2No separate attached-static-IP charge$12.20
Instance deleted; disk, snapshots and detached IP retainedNo further instance charge$3.20$2720 × $0.005 = $3.60$8.80
Detached IP released; disk and snapshots retainedNo further instance charge$3.20$2No further charge for that released IP$5.20
All modelled resources deleted or releasedNo further chargeNo further chargeNo further chargeNo further charge$0 going forward for these resources

Data from AWS official Lightsail pricing and documentation, checked 2026-11-13 04:06 UTC. Formulas use the 1 GB IPv4 card, allocated-disk rate, snapshot-storage rate and the Billing FAQ's unattached-static-IP rate. Every subtotal is our scenario, not a measured invoice. Charges already incurred are not refunded by this table.

Rules: When am I getting charged for a plan?, paragraph 1; What do Lightsail static IPv4 addresses cost?, paragraph 1; Instances → What is the difference between stopping and deleting my instance?, deletion paragraph; Block storage → Does my disk need to be attached to an instance?, paragraph 1; Manual and automatic snapshots → How long can I store snapshots?, manual-snapshot paragraph.

Automatic snapshots have different retention behavior when their source instance is deleted. This table deliberately uses retained manual snapshots; it does not assume that every automatic snapshot survives. Releasing or deleting resources can lose data and addresses. Verify what you need to retain before carrying out cleanup.

A forgotten IP can erase the IPv6 price saving

For the 1 GB shape, the networking-price gap is $7 − $5 = $2 per full billed month. At $0.005 per chargeable unattached-IP hour, $2 ÷ $0.005 = 400 chargeable hours consumes that entire saving. With our assumed 720 chargeable hours, a $5 IPv6-only bundle plus a forgotten IP is $5 + $3.60 = $8.60, exceeding the $7 IPv4 bundle by $1.60 before other resources.

The orphan IP is a separate retained resource, not an address attached to the IPv6-only instance. The official FAQ says unattached addresses are chargeable after more than one hour, and IPv6-only instances cannot take static IPv4 addresses. The calculation uses chargeable hours after that condition, so it does not invent how AWS rounds the initial grace period. Rates: the two 1 GB cards and What do Lightsail static IPv4 addresses cost?, paragraph 1.

Who should choose this, and what was not obtained?

Use the IPv4 column when your users or integrations require public IPv4 connectivity. Consider IPv6-only only after checking that connectivity and any added network-service costs. The price comparison does not include a proxy, load balancer or migration service to bridge missing IPv4 access. If you need a different operating system or a Research instance, use its own cards and stopped-state rules.

  • Account-specific Free Tier eligibility, credit expiry and guaranteed future renewal rate: Not obtained; no fixed introductory discount is deducted.
  • Tax-inclusive total and actual billable snapshot GB for your workload: Not obtained; quantities in the examples are stated assumptions.
  • Automatic root-disk-overflow price: Not obtained; only separately allocated block disks are priced.
  • A consistent plan-by-plan hourly quote for all ten networking variants reviewed: Not obtained; monthly cards are shown without back-calculating hourly rates.
  • Other-Region overage rates and any extra IPv4-bridging service quote for an IPv6 deployment: Not obtained for this guide; Ohio is the scope.

Official sources and check date

Official sources checked 2026-11-13 04:06 UTC: bundle, disk and snapshot pricing; billing, static IP and trial rules; data transfer; independent attached disks; manual and automatic snapshots. All worked usage patterns are our assumptions; rates are official page observations.

Home · Compare published plans · AWS Lightsail source index