Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New supported distribution checker fails for AWS Managed Elasticsearch #1666

Closed
nkazarian-spokeo opened this issue Aug 4, 2021 · 2 comments

Comments

@nkazarian-spokeo
Copy link

We use this library and mainly talk to AWS' managed elasticsearch service, which seems to not play nice with the most recent version of this library

Elasticsearch version (bin/elasticsearch --version): 7.4

elasticsearch-py version (elasticsearch.__versionstr__): 7.14.0

Description of the problem including expected versus actual behavior:

We expect connecting to ES to work just fine via this library, instead we get:

Unable to connect to Elasticsearch cluster. Error: The client noticed that the server is not a supported distribution of Elasticsearch

We also have issues with curator since it sources this same library. I imagine this has a huge blast radius if Amazon ES is going to be problematic with the new changes/checks for "supported distributions"?

@nkazarian-spokeo nkazarian-spokeo changed the title New supported version checker fails for AWS Managed Elasticsearch New supported distribution checker fails for AWS Managed Elasticsearch Aug 4, 2021
@sethmlarson
Copy link
Contributor

The Elasticsearch clients go through rigorous testing and validation against the official Elasticsearch distribution coming from Elastic. Since the AWS Elasticsearch Service has incompatible APIs with Elasticsearch itself, either by missing APIs or has incompatible format, we do not support it. Please consider using Elastic Cloud for an official and formally supported hosted Elasticsearch distribution.

@nkazarian-spokeo
Copy link
Author

So it was (unofficially) supported until 2 days ago? Seems like more of an oversight to me, a missed edge case perhaps. I would have liked something in the changelog that would've highlighted this change (a warning to those using managed Elasticsearch service on AWS or other cloud providers too perhaps), as it occurred quite abruptly and disrupted workflows for us.

@elastic elastic deleted a comment from SamStephens Aug 5, 2021
@elastic elastic locked as resolved and limited conversation to collaborators Aug 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants