# Low Commitment Coverage for Steady-State OpenSearch Service Domains Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/low-commitment-coverage-for-steady-state-opensearch-service-domains Production OpenSearch Service domains for search, logging and observability usually run around the clock with a stable node configuration for months or... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Production OpenSearch Service domains for search, logging and observability usually run around the clock with a stable node configuration for months or years. PointFive Research Cloud cost research at PointFive AWS service [AWS OpenSearch](https://www.pointfive.co/efficiency-hub/cloud-services/aws-opensearch) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0369 Type Suboptimal Pricing Model ## Explanation Why the waste happens and who it affects. When none of that usage is covered by a commitment, every instance-hour is billed at the On-Demand rate even though the baseline is predictable. OpenSearch Service offers two ways to discount it: Reserved Instances for a specific instance type in a Region, and Database Savings Plans, a dollar-per-hour commitment that also covers OpenSearch Serverless. Coverage gaps are common because OpenSearch spend is often owned by a platform or observability team rather than the group that manages EC2 commitments, because OpenSearch Reserved Instances are not size flexible and teams hesitate to lock in an instance type, and because reservations expire silently and usage returns to On-Demand. Database Savings Plans added OpenSearch Service only in March 2026, so commitment strategies written earlier may not consider it. ## Billing model The pricing dimensions that drive this cost. Managed domains are billed per instance-hour at On-Demand rates unless a commitment applies. On-Demand instance-hours Billed for each hour a node runs in an available state, at the full published rate for its instance type Reserved Instances 1- or 3-year terms with No, Partial or All Upfront payment, applied only to the exact instance type reserved, and charged for the full term even if no matching instance runs Database Savings Plans A 1-year, no upfront commitment in dollars per hour that applies to eligible OpenSearch managed cluster and Serverless usage regardless of instance family, size or Region, covering Generation 7 and newer instances No stacking Database Savings Plans cannot be combined with Reserved Instances on the same workload ## How to detect 5 checks to find it in your estate. - Review the Trusted Advisor check Amazon OpenSearch Service Reserved Instance purchase recommendations , sourced from Cost Optimization Hub, which flags accounts with an identified OpenSearch savings action - Open Cost Explorer reservation recommendations with OpenSearch Service selected, using a 30- or 60-day lookback, and compare the recommended instance counts with the domains that have run unchanged over that period - Group OpenSearch Service spend by Purchase Option in Cost Explorer to see what share of instance-hours is billed On-Demand - Review Database Savings Plans purchase recommendations and coverage, noting that only Generation 7 and newer instance types are eligible, so domains on older families will not be covered until they are upgraded - List existing OpenSearch Reserved Instances and their end dates to catch reservations that are about to expire ## How to fix 5 ways to remove the waste. - Cover domains whose instance type and count are unlikely to change for the term with Reserved Instances; because they apply only to the exact instance type, align them with any planned instance migration first - Use Database Savings Plans for OpenSearch baselines that may change instance family, size or Region, move to Serverless, or shift between database services, accepting a lower maximum discount in exchange for that flexibility - Do not plan to cover the same workload with both; assign each baseline to one commitment type - Right-size and move domains to current-generation instances before committing, so the commitment is sized to the capacity the domain actually needs and, for Savings Plans, the instances are eligible - Size commitments to the minimum steady usage and review coverage and upcoming expirations on a regular schedule so usage does not silently return to On-Demand ## Documentation Vendor references for pricing and configuration. - [Amazon OpenSearch Service Pricing aws.amazon.com](https://aws.amazon.com/opensearch-service/pricing/) - [Reserved Instances in Amazon OpenSearch Service docs.aws.amazon.com](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ri.html) - [Cost optimization techniques for Amazon OpenSearch Service docs.aws.amazon.com](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/cost-optimization.html) - [Database Savings Plans aws.amazon.com](https://aws.amazon.com/savingsplans/database-pricing/) - [Accessing reservation recommendations docs.aws.amazon.com](https://docs.aws.amazon.com/cost-management/latest/userguide/ri-recommendations.html) - [Cost optimization - AWS Support docs.aws.amazon.com](https://docs.aws.amazon.com/awssupport/latest/user/cost-optimization-checks.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS OpenSearch CER-0130 ### [Suboptimal Use of Intel-Based Instances in OpenSearch](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-intel-based-instances-in-opensearch) AWS Graviton processors are designed to deliver better price-performance than comparable Intel-based instances, often reducing cost by 20-30% at equivalent workload performance. OpenSearch domains running on older Intel-based families... Databases - AWS OpenSearch CER-0147 ### [Outdated Elasticsearch Version Triggering Extended Support Charges](https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-elasticsearch-version-triggering-extended-support-charges) Many legacy workloads still run on older Elasticsearch versions - such as 5.x, 6.0-6.7, or 7.1-7.8 - due to inertia, compatibility constraints, or lack of ownership. Once these versions exceed their standard support window, AWS begins... Databases - AWS OpenSearch CER-0101 ### [Outdated OpenSearch Version Triggering Extended Support Charges](https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-opensearch-version-triggering-extended-support-charges) Domains running outdated OpenSearch versions - particularly Elasticsearch 1.5 through 7.8, OpenSearch 1.0-1.2, and OpenSearch 2.3-2.9, whose standard support ended on November 7, 2025 - begin to incur AWS Extended Support charges once they... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.