Skip to content
FinOps workspace
COST LEDGER / DECISION GUIDE

EBS pricing: AWS volume, IOPS and snapshot cost review

Updated: 6 November 2026

Review EBS pricing for capacity, performance and snapshots. Compare the complete bill before changing storage settings.

Request a quote
Server cabinets in the mint and dark green Cost Ledger visual style
Define the workload before comparing its cost.

If snapshot protection is orchestrated through Backup, the AWS Backup storage and retention review adds vault ownership, copy routes and lock constraints to the EBS cost boundary.

EBS pricing: separate storage, IOPS and throughput

The official EBS pricing page bills gp3 provisioned storage until release. The gp3 technical specification includes 3,000 IOPS and 125 MiB/s of throughput; provisioned performance above that baseline is charged separately. gp2 includes I/O in its storage charge, while io2 adds provisioned IOPS charges. Use the current rate for your Region and volume type.

Cost lineEstimate fromReview question
Volume storageProvisioned capacity, applicable regional rate and billed durationDoes the application need this capacity?
gp3 additional performanceIOPS and throughput provisioned above their included baselineWhich peaks justify the settings?
io2 performanceProvisioned IOPS and the applicable pricing tiersDoes the workload need this volume type?
Snapshots and related servicesSnapshot storage and separately used featuresWhich recovery points and services remain necessary?

Provisioned capacity is different from used filesystem space. A sparsely used volume can still incur its provisioned storage charge. Keep the capacity decision separate from the performance decision, and validate both with the application owner.

Compare gp2 and gp3 against the same workload

AWS allows gp3 performance to be provisioned separately from storage capacity, subject to volume-size, IOPS and throughput limits and ratios. Compare the candidate's full settings with measured demand and the attached instance's constraints. A lower storage rate alone does not establish the total saving. Write down the target settings and the rollback test.

  1. Export volume type, size, provisioned performance, attachment and owner.
  2. Match each billing line to the current configuration and applicable rate.
  3. Validate the candidate using application latency and peak I/O evidence.
  4. Review the next bill with snapshots and other retained resources still included.

Reconcile the storage review with EC2 compute and stopped-instance costs, the RDS cost optimization sequence and the AWS cost audit boundary. Carry implementation costs into the TCO scenario comparison when a change requires migration work.

AWS EBS cost: provisioned capacity and performance

The EBS pricing page describes charges for provisioned capacity and the performance dimensions applicable to each volume type. Billing does not depend only on how much application data is currently stored. Record volume type, provisioned size, Region and performance settings to explain an EBS AWS cost entry.

ItemEvidenceQuestion
Volume capacityProvisioned size and filesystem useIs the current capacity needed?
PerformanceConfigured IOPS and throughput, measured demandDoes the application use the purchased performance?
AttachmentInstance association and resource ownerIs an unattached volume intentionally retained?
SnapshotsOwner, age and retention purposeDoes this recovery point remain required?

Read EC2 cost drivers alongside the storage review. A stopped instance can leave storage that still incurs charges. The AWS audit scope should therefore retain the volume lines when it measures a compute change, rather than assuming that stopping an instance removes the entire workload cost.

Investigate detached volumes with the owner

The EBS deletion documentation explains that a volume is retained rather than immediately deleted when it matches a Recycle Bin retention rule. Otherwise, deletion removes its data; create a snapshot beforehand if the data must be retained. Have the owner confirm the volume purpose and required recovery point. A detached state is a review signal, not a deletion instruction.

  • Map each volume to its owner, environment and last known application.
  • Identify deliberate retention, migration and recovery use cases.
  • Confirm the restoration path and any snapshot requirement.
  • Obtain approval for deletion and keep an audit record of the decision.

Delete only after the retention decision is settled. The review can expose resources with no apparent owner, but engineering or the data owner must decide what can be removed. Keep investigation work separate from implementation permissions. That makes the finding useful without granting an auditor unnecessary write access.

Evaluate a performance or type change

For AWS EBS cost optimization, compare the measured I/O requirement with provisioned settings. Review peaks, latency and throughput as well as average IOPS. Ask the application team to identify the workload constraint and select a candidate configuration that preserves it. Record the expected financial effect using the rate for the actual volume type and Region.

  1. Capture the current volume settings and performance evidence.
  2. Define the application acceptance criteria and recovery boundary.
  3. Test or validate the proposed setting through the approved change process.
  4. Measure storage and performance charges after the change.

A recommendation should explain how the application will move to the new configuration, which work your team must carry out and what happens if performance deteriorates. Treat a capacity reduction as an engineering task with a documented migration path. Do not assume a volume can be made smaller simply because the filesystem has free space.

The S3 storage guide covers object lifecycle choices, while the RDS cost guide addresses managed database storage within its own service boundary. Use those reviews to avoid double-counting a database or an archive as an EBS opportunity. For a quote, provide the inventory and billing lines, performance measurements and retention policy. Ask for editable calculations and a finding status for each volume.

Server cabinets in the mint and dark green Cost Ledger visual style
Keep the data retention decision beside every storage finding.

Questions before a cost review

What does EBS gp3 pricing include?

The storage price includes a baseline of 3,000 IOPS and 125 MiB/s of throughput, as specified in the gp3 technical documentation. Additional provisioned IOPS and throughput are separate charges. Apply the rate for your Region and include any snapshot services used.

Does EBS pricing depend on used disk space?

Volume storage charges use provisioned capacity, rather than only the application data stored on the filesystem. Snapshot storage has its own billing basis, so review it separately.

Is a gp2 to gp3 change always cheaper overall?

Compare the actual Region, provisioned capacity and required performance, including additional gp3 performance charges. Validate application behavior and implementation effort before accepting a savings estimate.

Does an unattached EBS volume still cost money?

Provisioned EBS storage remains billed until it is released. Confirm ownership and data retention before deleting an unattached volume, and review any snapshots retained afterward.

Related workload decisions

Continue the review with aws data transfer costs, aws ec2 cost. Each guide addresses a separate decision within the same cloud cost boundary.

Get my FinOps quote