.png)
How It Works
EBS volumes are network-attached storage devices that behave like physical hard drives. When you launch an EC2 instance, you attach one or more EBS volumes to it. The volume persists even after the instance stops or terminates, which makes EBS the standard choice for databases, file systems, and applications that need durable storage.
AWS offers several EBS volume types, each optimized for a different workload. General Purpose SSD (gp2 and gp3) volumes handle most workloads at a balance of price and performance. Provisioned IOPS SSD (io1 and io2) volumes deliver consistent, high-throughput performance for I/O-intensive databases. Throughput Optimized HDD (st1) and Cold HDD (sc1) volumes serve large, sequential workloads at lower cost.
You pay for the storage capacity you provision, not just what you use. A 500 GB gp3 volume bills at the full 500 GB even if your application only occupies 50 GB of it.
Why It Matters for Cloud Cost
EBS is a significant and frequently overlooked cost driver in AWS environments. Costs accumulate across three dimensions: provisioned volume capacity, provisioned IOPS (for io1 and io2 volumes), and snapshot storage in Amazon S3.
Teams that over-provision volume sizes, leave volumes attached to stopped instances, or retain outdated snapshots accumulate waste that compounds quietly month over month. A volume detached from any instance still bills at full price. Snapshots taken daily across hundreds of volumes add up to substantial S3 storage costs, especially when retention policies are absent.
Choosing the right volume type also matters. Many workloads running on gp2 can migrate to gp3 and receive higher baseline performance at a lower price per GB, but the migration requires deliberate action. Without visibility into volume utilization and snapshot age across accounts, teams have no practical way to identify and eliminate this waste.
ClearCost provides cost visibility and showback reporting across your AWS environment.