Blog

When a cloud instance is stopped, users often ask about the ongoing cost. The main cost drivers are EBS storage for attached volumes and any persistent resources tied to the instance. This guide provides practical pricing in USD with low–average–high ranges and clarifies what you actually pay when EC2 instances are not running.

Overview Of Costs

Cost when an EC2 instance is stopped is mostly driven by persistent storage and any associated backups. The compute portion drops to zero, but the attached EBS volumes continue to incur storage fees. If the instance uses additional resources such as Elastic IPs, these may have small ongoing charges when not attached to running instances. For most users, the annual impact of stopped instances centers on storage costs rather than compute.

Cost Breakdown

A detailed view helps avoid surprises. Below is a practical breakdown with representative ranges and clear assumptions. The table blends total project implications with per-unit costs to show what a typical stopped-state bill looks like.

What Drives Price

Storage type and volume size are the largest price levers. gp3 and io1 volumes cost more per GB than gp2, with higher IOPS or throughput requirements driving the per-GB price up. The number and age of snapshots also scale the monthly bill.

Factors That Affect Price

Regional differences matter: storage pricing varies by AWS region, and some regions have higher snapshot and data-transfer charges. Availability of cheaper storage classes or reserved backups can shift costs. Additionally, the lifetime of a stopped-state deployment can influence when to delete unused volumes or consolidate snapshots.

Price Components

Assumptions used for examples include standard gp3 volumes, no allocated IOPS beyond baseline, and a modest set of backups. The exact costs shift with region, data growth, and backup policy. The mini-formula below highlights a typical ongoing charge if storage remains constant: data-formula=”monthly_storage_gb × storage_rate_per_gb”>.

Regional Price Differences

Regional contrasts can swing costs by 10–40% depending on region and storage class. In the U.S., a common delta occurs between Northern Virginia, Ohio, and Oregon for EBS volume pricing and snapshot storage. Expect higher costs in high-demand regions and lower costs in newer or less-populated zones. These deltas apply to both storage and backup charges, while data-transfer costs remain a smaller, variable component.

Local Market Variations

Local market impact arises from region-specific pricing and tax treatment. For a withdrawn-volume setup, the choice of region and backup strategy can create meaningful differences in monthly spend. Users should compare the per-GB-month rate for volumes and per-GB-month rate for snapshots across regions to optimize ongoing costs.

Labor & Deployment Time

Administration time has a cost, even when idle. Routine tasks such as resizing, detaching, or pruning unused volumes require staff hours. If a team spends 2–4 hours per month managing stopped resources, estimate labor cost at $40–$120 per month based on internal rates. This is often small relative to storage spend but matters for small teams or tight budgets.

Extra & Hidden Costs

Hidden charges can creep in with untracked backups. Unneeded snapshots accumulate, and old volumes left attached or orphaned resources can generate ongoing fees. Regular audits to delete unused volumes and prune snapshots help control costs. In some cases, cross-region backup replication or lifecycle automation introduces additional per-month costs.

Cost Compared To Alternatives

Review other options to minimize ongoing spend. If a stopped instance is rarely used, consider deleting the volume or converting to a smaller snapshot plan, or using lifecycle policies to remove obsolete backups. Alternatively, keep a minimal standby state with a single small volume for quick restoration, trading off restoration time against ongoing storage costs.

Real-World Pricing Examples

Three scenario cards illustrate typical setups and monthly ranges. Each scenario assumes a single stopped instance with varying storage needs and backup practices.

Note: All figures are illustrative ranges and depend on the exact region, volume type, snapshot policy, and data-transfer patterns. The primary ongoing cost for a stopped EC2 instance is storage and backups, not compute, and small changes in policy can yield meaningful savings over time.