Thanks, Kyle.
I understand the importance of governing this project as an independent open source entity and the need to distance it from vendor-specific implementation details. But since cloud-provider-hosted ElasticSearch (licensing) is the raison d’etre for OpenSearch, I think it makes all the sense in the world that the OpenSearch client docs would at least include examples of how to connect to various providers. Even if those examples are buried away in some isolated “vendor” section.
I would also suggest that we look at the Kubernetes project as a good example of how to navigate this territory. Kubernetes is kept pretty vendor neutral, but it also has all the necessary hooks and plugins to support real-world vendor integration. I’d love to see OpenSearch follow a similar path.