# Elasticsearch Interpreter Zeppelin - Elastic Cloud - Found to be : ZEPPELIN-2031

**URL:** <https://discuss.elastic.co/t/elasticsearch-interpreter-zeppelin-elastic-cloud-found-to-be-zeppelin-2031/119048>\
**Category:** Elasticsearch\
**Created:** [February 8, 2018, 1:25pm UTC](https://discuss.elastic.co/t/elasticsearch-interpreter-zeppelin-elastic-cloud-found-to-be-zeppelin-2031/119048 "2018-02-08T13:25:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wayne\_Taylor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wayne_taylor/32/45984_2.png) [@Wayne\_Taylor](https://discuss.elastic.co/u/Wayne_Taylor)\
**Post date:** [February 8, 2018, 1:25pm UTC](https://discuss.elastic.co/t/elasticsearch-interpreter-zeppelin-elastic-cloud-found-to-be-zeppelin-2031/119048/1 "2018-02-08T13:25:41Z")

</div>

Hi All,

I am trying to setup Elastcisearch interpreter in zeppelin with our [elastic.co/cloud](http://elastic.co/cloud) server and unable to access.

I can CURL to the server fine:  
**curl -X GET [https://myuser:mypassword@myhostname.us-east-1.aws.found.io:9243/\_cat/health](https://myuser:mypassword@myhostname.us-east-1.aws.found.io:9243/_cat/health)**  
\*\* 1518095418 13:10:18 clustername green 3 2 978 489 0 0 0 0 - 100.0%\*\*

When I configure Zeppelin I have following following configuration per screenshot.  
 ![19%20AM](https://us1.discourse-cdn.com/elastic/original/3X/7/3/7348f74ddbc8ccb7b3773260782bf48d4cce5ed9.png)

\*\*When I restart it I get the following error: \*\*  
**Problem with the Elasticsearch client, please check your configuration (host, port,...)**

Has anyone been able to get this working with Elastic Cloud?

Update: This is on Elasticsearch version 5.6.4. If i use localhost elasticsearch with no username & password configured it works fine

Thanks  
Wayne

---

<div class="post-metadata">

**Author:** ![Wayne\_Taylor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wayne_taylor/32/45984_2.png) [@Wayne\_Taylor](https://discuss.elastic.co/u/Wayne_Taylor)\
**Post date:** [February 9, 2018, 1:27pm UTC](https://discuss.elastic.co/t/elasticsearch-interpreter-zeppelin-elastic-cloud-found-to-be-zeppelin-2031/119048/2 "2018-02-09T13:27:25Z")

</div>

Short answer is: [https://issues.apache.org/jira/browse/ZEPPELIN-2031](https://issues.apache.org/jira/browse/ZEPPELIN-2031). Currently doesn't support SSL

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 9, 2018, 1:27pm UTC](https://discuss.elastic.co/t/elasticsearch-interpreter-zeppelin-elastic-cloud-found-to-be-zeppelin-2031/119048/3 "2018-03-09T13:27:25Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
