The Hidden Cost Layers of EC2 (And Why Stopped Instances Still Drain Your Budget)

EC2 looks simple on the bill — until you pull it apart. What most teams see is a single line item for instance hours. In reality, every running (and even stopped) EC2 instance generates charges across multiple dimensions, and the overlooked ones tend to accumulate quietly. Let's break down where EC2 costs actually come from, what keeps billing you after you click "Stop", and what you can do about it. The Obvious: Instance Hours On-Demand pricing ranges from roughly $0.0042/hr for a t4g.nano to over $30/hr for GPU-accelerated instances like the p4d.24xlarge . The exact rate depends on the instance family (general purpose, compute-optimized, memory-optimized, GPU, etc.), the instance size, and the region. Most teams have a reasonable handle on this cost. The real surprises come from everything else attached to those instances. The Persistent One: EBS Storage Every EC2 instance boots from at least one EBS volume, and most production instances have additional data volumes attached. EBS is