Why Elastic Is Blocking OpenSearch: The Client Library Controversy Explained

Elastic developer submitted a PR to elasticsearch-py to modify authentication logic, which will prevent the client from connecting to AWS‑maintained OpenSearch, older Elasticsearch open‑source releases, or the AWS Elasticsearch Service.

AWS responded that Elastic’s open‑source client libraries provide convenient high‑level interfaces, but the new logic restricts connections to Elastic’s commercial products only.

AWS argues that widely adopted open‑source projects should remain flexible and inclusive, so they will fork all Elasticsearch client libraries to ensure they can connect to any OpenSearch or Elasticsearch cluster. The clients to be forked include:

elasticsearch-py

elasticsearch-java

elasticsearch-net

go-elasticsearch

elasticsearch-js

elasticsearch-ruby

eland

elasticsearch-php

elasticsearch-rs

elasticsearch-perl

elasticsearch-specification

elasticsearch-hadoop

AWS says developers only need minor code changes to continue connecting to Elasticsearch and its derivatives, and advises not to upgrade Elastic‑maintained clients to the latest versions to avoid interruptions.

Since Elastic changed its open‑source license, AWS and Elastic have been diverging, with AWS creating a “truly open‑source” Elasticsearch fork, while Elastic’s new client restrictions have sparked debate over open‑source principles.