Your OpenSearch Bill Is Bigger Than You Think: A Technical Cost Breakdown

OpenSearch can look cheap at first glance, then surprise you in the monthly bill. Most teams look at one line item and assume that is “the OpenSearch cost.” In reality, OpenSearch spend is a composite of compute, storage, backups, and data movement, and each part scales differently under real workloads. If you are trying to reduce spend without breaking search performance, you need to model the full stack, not just one rate card. 1) Start with the right mental model There are two major OpenSearch consumption models: OpenSearch Service domains (provisioned clusters) OpenSearch Serverless collections This post focuses on domain-based OpenSearch, where cost generally includes: Data node instance-hours (often the biggest component) Dedicated master node instance-hours (if enabled) Warm/cold tier node-hours (if used) EBS storage attached to nodes EBS performance dimensions (for gp3: provisioned IOPS/throughput beyond baseline) Snapshot storage Data transfer and network-related charges If yo