Amazon EBS Costs: Volumes, Snapshots and gp3 Moves

The EBS meter never pauses

AWS charges EBS volume storage by the GB you provision per month until you release it. Additional IOPS and throughput above a volume type’s baseline are charged by what you provision, not what you use. Snapshots bill by the space the data consumes, and each incremental snapshot stores only the changed blocks. None of this depends on the instance being up, so EBS cannot be scheduled: stopping the attached instance leaves the volume charge exactly where it was.

What to look for instead

• Unattached volumes left behind after an instance was terminated.
• gp2 volumes that would cost less as gp3.
• Provisioned IOPS set well above what the workload draws.
• Snapshots that outlived the volume or the reason they were taken.

ZopNight’s EBS rules

• Orphaned EBS Volume fires on volumes in the available state for at least seven days and prices the full volume cost. It skips volumes created by Kubernetes storage, because deleting those would strand the pod that asked for them.
• EBS gp2 to gp3 Migration prices the real per-GB rate difference, netted against any IOPS or throughput charge the volume would inherit.
• EBS Provisioned IOPS Over-Allocation is wired to a resize remediation that changes the IOPS setting in place.
• Orphaned EBS Snapshot and EBS Snapshot Archive Tier Candidate cover the snapshot side.
• EBS Volume Not Encrypted covers posture.

Deletion is handled carefully. ZopNight’s safety gate allows an automatic delete only with authoritative evidence that a resource is unused. AWS exposes no detach timestamp for a volume, so the orphaned-volume delete is advisory and a person confirms it. Snapshot deletion is guided with a type-to-confirm step, because a snapshot can still back an AMI.

Stopped instances and their volumes

The one place EBS and scheduling meet is the stopped instance: its compute stops charging while its volumes do not. The Idle EC2 Instance rule prices exactly that residue for instances stopped for 30 days or more. See the EC2 page.

Resource details: EBS volume fact sheet and EBS snapshot fact sheet. Cleanup practice across services is on orphan cleanup.