# Launch Elasticsearch - really an error?

**URL:** <https://discuss.elastic.co/t/launch-elasticsearch-really-an-error/215336>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [January 16, 2020, 3:03pm UTC](https://discuss.elastic.co/t/launch-elasticsearch-really-an-error/215336 "2020-01-16T15:03:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![newKibanaUser](https://avatars.discourse-cdn.com/v4/letter/n/ea5d25/32.png) [@newKibanaUser](https://discuss.elastic.co/u/newKibanaUser)\
**Post date:** [January 16, 2020, 3:03pm UTC](https://discuss.elastic.co/t/launch-elasticsearch-really-an-error/215336/1 "2020-01-16T15:03:15Z")

</div>

Hello -

I am getting 401 error while launching elasticsearch as below from my ECE deployment. I am able to add/view indices onto this elasticsearch from my local instance using curl. Is this really an error or what should really happen after clicking on this **Launch** button?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/8/086e17db21ff6f46665e3f858ac703e9a8c3d1c2.png)

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [January 16, 2020, 4:02pm UTC](https://discuss.elastic.co/t/launch-elasticsearch-really-an-error/215336/2 "2020-01-16T16:02:56Z")

</div>

Honestly I've no idea why we have that launch button! Launching a tab with an unauthenticated `/` request directly to the ES server indeed doesn't make much sense, though given it does exist the behavior you observed is intended 🙂

To get the URL to use in clients etc, just click the `Copy Endpoint URL` button to its right

To access the Elasticearch UI (ie Kibana) there is a "Launch" link at the top level or under the Kibana sub-heading

Alex

---

<div class="post-metadata">

**Author:** ![newKibanaUser](https://avatars.discourse-cdn.com/v4/letter/n/ea5d25/32.png) [@newKibanaUser](https://discuss.elastic.co/u/newKibanaUser)\
**Post date:** [January 16, 2020, 4:15pm UTC](https://discuss.elastic.co/t/launch-elasticsearch-really-an-error/215336/3 "2020-01-16T16:15:22Z")

</div>

Thank you. Hope Elastic removes that option in future release. Yes, I am able to launch and use Kibana and access ElasticSearch using the URL.

I was having another issue in configuring Filebeat using cloud.id and cloud.auth, and was curious whether this 'Launch' issue might be related to that one.

I have posted my original Filebeat issue under Beats section with no luck yet. If possible, can you take a look at that one also.

Thank you.

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [January 16, 2020, 4:37pm UTC](https://discuss.elastic.co/t/launch-elasticsearch-really-an-error/215336/4 "2020-01-16T16:37:51Z")

</div>

Yep I created an issue to remove it, thanks for pointing out! I'll go have a look at the `cloud.id` issue

---

<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:** [January 30, 2020, 4:38pm UTC](https://discuss.elastic.co/t/launch-elasticsearch-really-an-error/215336/5 "2020-01-30T16:38:05Z")

</div>

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