Create ElasticSearch datasource on gateway

[Georgedebt]

Hello,
I'm trying to add Elasticsearch (open source on AWS instance) as datasource on gateway, credentials and link are provided correctly, the gateway itself was whitelisted, so I expected no error on Power BI service side

The error I get is: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel"
Status code: 400

However I'm able to connect from the Power BI desktop to Elasticsearch using the same link

I don't use ODBC driver

What might be the issue here?

[collinq]

Hey @Georgedebt ,

I believe that this is not a Power BI issue but a networking or setting type of situation.  You can refer to these two articles:

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure ...

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure ...

[Georgedebt]

I see

But it's the error which Power BI service interface tells me about,  is there a way to fix it via Power BI service?

I'm able to connect to Elasticsearch from the same server where's the gateway, so I wonder while I get this erro

[collinq]

Hey @Georgedebt ,

Well, sure, you can have all sorts of security settings that prevent data movement - including in the browser and in your network and in the gateway server (the physical server, not the gateway settings).  And, you may have security on your data source that is not accepting certain ports.

You might want to do a network trace (like with Fiddler) and see if that gives you a fail point.

[Georgedebt]

Got it

But it's the error which Power BI service interface tells me about,  is there a way to fix it via Power BI service?

I'm able to connect to Elasticsearch from the same server where's the gateway is located , so I wonder why I get this error and it's hard to believe it's because of browser (but I'll check it anyway, thank you)

[collinq]

Hey @Georgedebt ,

You have installed the ODBC driver onto the Gateway Server and have a DSN installed on it?   This article Microsoft Power BI Desktop | Elasticsearch Guide [master] | Elastic

states those are prerequisites.

And, this article states you need to use web and not Odata, so maybe try that method as well?  Querying Elasticsearch with PowerBI (sixeyed.com)

If one of those methods don't work, let us know

[Georgedebt]

Hi @collinq 
The thing is as I said previously I'm not using ODBC driver
And I'm not trying to use Power BI desktop , I'm trying to create the data source in Power BI service with type "Elasticsearch"" on my gateway

I was expecting that odbc driver is not necessary when the gateway is whitelisted and the only thing is needed from me is just the link to elasticsearch in correct format and credentials of user.
The way  I do it in Power BI Service: Manage gateways - Data Sources - New- data source with type "Elasticsearch" (which is there in the list)

Do you think that ODBC driver is still necessary here?
Because I was able to get data from ES without it in power bi desktop (via ES API)
It's just Power BI Service that won't let do it

[collinq]

Hey @Georgedebt ,

I do think that you need the ODBC because that is what the report is using.  I don't believe that you can have a gateway with one type of link and the Desktop file with a different one.  A test might be to create a report in the Service and then see if you can use the link from the gateway.