Copy the fingerprint value that’s output to your terminal when Elasticsearch starts, and configure your client to use this fingerprint to establish trust when it connects to Elasticsearch.
If the auto-configuration process already completed, you can still obtain the fingerprint of the security certificate by running the following command. The path is to the auto-generated CA certificate for the HTTP layer.
System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
System.Security.Authentication.AuthenticationException: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
Why are you not using the suggested Cloud Method... Though this should work too.
Also can you show more of the logs... more you show... more we can help
And since it is a Publicly Signed Cert and perhaps you just want to test, I don't think you even need the fingerprint check (maybe you do but this is not a self-signed cert which is what that example is)
note the .es in the Uri
var settings = new ElasticsearchClientSettings(new Uri("https://my-deployment.es.us-west1.gcp.cloud.es.io:9243"))
.Authentication(new BasicAuthentication("elastic", "<PASSWORD>"));
You could also probably just use the ClientCertificate setting
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.