Explanation
Why the waste happens and who it affects.
These charges are persistent and apply even if the domain is inactive or lightly used. Many teams overlook this cost when delaying upgrades or maintaining non-critical environments like dev, test, or staging. In large organizations, outdated versions can silently drive meaningful spend over time, especially across many small or idle domains.
Billing model
The pricing dimensions that drive this cost.
OpenSearch domains are billed per hour based on:
- Instance size and count
- Storage (including UltraWarm if enabled)
- Extended Support Charges - billed per Normalized Instance Hour (a factor of instance size and instance hours) on top of instance pricing once a version exceeds its standard support window, so the fee grows with node count and size
- For OpenSearch 1.0-1.2 and 2.3-2.9 (and Elasticsearch 1.5 through 7.8), the pricing page states that Extended Support charges for the extension period ending November 7, 2027 are equal to your instance pricing; later versions such as OpenSearch 1.3 are charged the standard Extended Support rate of $0.0065 per NIH in US East (N. Virginia) once they leave standard support
How to detect
5 checks to find it in your estate.
- List all OpenSearch domains and record their engine version
- Compare against the AWS OpenSearch Support Calendar
- Identify any domains running versions outside standard support
- Use the AWS Console or API to retrieve version metadata
- Review billing data to detect Extended Support fees under OpenSearch spend
How to fix
4 ways to remove the waste.
- Upgrade OpenSearch domains to a supported version
- Test upgrade compatibility in lower environments before applying in production
- Decommission inactive domains to eliminate unnecessary support and compute charges
- Incorporate version tracking into platform reviews to proactively avoid future Extended Support exposure
Documentation
Vendor references for pricing and configuration.