Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Jun 18, 2025

SIP Compatibility with AWS OpenSearch

The SIP is currently compatible with Elasticsearch 7.17.9 and future fix packs. It leverages the Elasticsearch Java client version 7.17.28, which includes a built-in validation for the response header "X-Elastic-Product: Elasticsearch".

This header check poses a challenge when interfacing with AWS OpenSearch. Although OpenSearch was originally forked from Elasticsearch 7.10, it has since diverged significantly in terms of architecture and functionality. Consequently, OpenSearch does not consistently include the "X-Elastic-Product" header in its responses, leading to compatibility issues with the SIP client.

Reference

This behavior is documented in an AWS blog post that outlines the differences between OpenSearch and Elasticsearch, and the rationale behind the development of dedicated OpenSearch clients to address these gaps.

Request

Given the above, we believe this may warrant an enhancement to the SIP to support AWS OpenSearch more gracefully, possibly by:

  • Allowing configurable header validation.
  • Supporting OpenSearch-specific client libraries.
  • Providing clearer integration guidelines for OpenSearch environments.
  • Admin
    Sampson Wong
    Jul 28, 2025

    Requirement out of scope for 2025, Will consider support in future roadmap. dates to be determined.

    To inform if the customer already has ES running, there will be a migration effort.