Explanation
Why the waste happens and who it affects.
Once these versions exceed their standard support window, AWS begins charging an Extended Support fee per Normalized Instance Hour for the instances in each domain. Elasticsearch 1.5 through 7.8 (including all 5.x) and OpenSearch 1.0-1.2 and 2.3-2.9 are already in Extended Support, while Elasticsearch 6.8, 7.9, and 7.10, OpenSearch 1.3, and OpenSearch 2.11-2.17 and 2.19 remain in standard support until November 7, 2027. These fees are often missed in cost reviews, especially in environments that are inactive but still provisioned. In aggregate, outdated Elasticsearch clusters contribute to significant silent spend unless proactively addressed.
Billing model
The pricing dimensions that drive this cost.
Elasticsearch domains are billed per hour based on:
- Instance size and count
- Storage (EBS or UltraWarm)
- Extended Support Charges - billed per Normalized Instance Hour (a factor of instance size and instance hours) on top of instance pricing for versions outside standard support, so the fee grows with node count and size
- For 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
How to detect
4 checks to find it in your estate.
- Inventory all Elasticsearch domains running on Amazon OpenSearch Service
- Identify engine versions using the AWS Console or API
- Review cost reports for Extended Support line items
- Flag domains that are inactive or non-critical but still incurring support costs
How to fix
4 ways to remove the waste.
- Upgrade to a supported version of OpenSearch
- Be aware that upgrading from Elasticsearch 7.x may require reindexing or application compatibility changes
- Where possible, consolidate or delete unused domains to eliminate unnecessary charges
- Establish a lifecycle policy review process to ensure domains stay within standard support timelines
Documentation
Vendor references for pricing and configuration.