# Elastic cloud with auth but without https

**URL:** <https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [September 6, 2019, 4:12am UTC](https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337 "2019-09-06T04:12:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![O\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/o_k/32/52424_2.png) [@O\_K](https://discuss.elastic.co/u/O_K)\
**Post date:** [September 6, 2019, 4:12am UTC](https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337/1 "2019-09-06T04:12:45Z")

</div>

hello,

I wonder the proper way to disable https but remain authentication for this example [https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-quickstart.html#k8s-deploy-eck](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-quickstart.html#k8s-deploy-eck)

---

<div class="post-metadata">

**Author:** ![Thibault\_Richard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thibault_richard/32/50513_2.png) [@Thibault\_Richard](https://discuss.elastic.co/u/Thibault_Richard)\
**Post date:** [September 6, 2019, 7:33am UTC](https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337/2 "2019-09-06T07:33:34Z")

</div>

Hello,

In 0.9, you can explicitly disable TLS for Kibana or APM Server as shown here: [https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-accessing-elastic-services.html#k8s-disable-tls](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-accessing-elastic-services.html#k8s-disable-tls).

The same behaviour has recently been added for Elasticsearch ([https://github.com/elastic/cloud-on-k8s/pull/1623](https://github.com/elastic/cloud-on-k8s/pull/1623)) and will be possible in the next release.

---

<div class="post-metadata">

**Author:** ![O\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/o_k/32/52424_2.png) [@O\_K](https://discuss.elastic.co/u/O_K)\
**Post date:** [September 6, 2019, 7:36am UTC](https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337/3 "2019-09-06T07:36:41Z")

</div>

Thank you, @Thibault_Richard

BTW, is ECK described here [https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-quickstart.html#k8s-deploy-eck](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-quickstart.html#k8s-deploy-eck) free?

---

<div class="post-metadata">

**Author:** ![Thibault\_Richard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thibault_richard/32/50513_2.png) [@Thibault\_Richard](https://discuss.elastic.co/u/Thibault_Richard)\
**Post date:** [September 6, 2019, 7:56am UTC](https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337/4 "2019-09-06T07:56:10Z")

</div>

TL;DR Yes, the default distribution of ECK is free.

Since the early days of Elasticsearch, Elastic's goal has always been to provide new users with a rich getting started experience by packing a lot of powerful features into the free, default distribution. ECK is no different.

The default distribution of ECK is forever free under the Basic license ([https://www.elastic.co/subscriptions](https://www.elastic.co/subscriptions)). In the spirit of openness and transparency, Elastic has also made all the source code for ECK publicly viewable, licensed under the Elastic License, in the Elastic [cloud-on-k8s GitHub repository](https://github.com/elastic/cloud-on-k8s).

An Enterprise (paid) subscription enables additional features, including the ability to deploy clusters with advanced features such as field- and document-level access control, machine learning, graph analytics, and more. In the future, the Enterprise subscription will also unlock additional advanced orchestration features.

---

<div class="post-metadata">

**Author:** ![O\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/o_k/32/52424_2.png) [@O\_K](https://discuss.elastic.co/u/O_K)\
**Post date:** [September 7, 2019, 8:43pm UTC](https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337/5 "2019-09-07T20:43:24Z")

</div>

Hi @Thibault_Richard

Do you know what might be the reason of getting timeout error while loggining into kibana with **elastic** username (both http/https) with port-forward to localhost? This issue doesn't occur while using helm charts

```
{"statusCode":503,"error":"Service Unavailable","message":"Request Timeout after 30000ms"} 

```

`{"type":"response","@timestamp":"2019-09-07T20:38:01Z","tags":[],"pid":1,"method":"post","statusCode":503,"req":{"url":"/api/security/v1/login","method":"post","headers":{"host":"localhost:5601","user-agent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0","accept":"application/json, text/plain, */*","accept-language":"en-US,en;q=0.5","accept-encoding":"gzip, deflate","content-type":"application/json;charset=utf-8","kbn-version":"7.2.0","content-length":"60","connection":"keep-alive","referer":"http://localhost:5601/login?next=%2F"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1","referer":"http://localhost:5601/login?next=%2F"},"res":{"statusCode":503,"responseTime":38458,"contentLength":9},"message":"POST /api/security/v1/login 503 38458ms - 9.0B"}`

---

<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:** [November 4, 2022, 7:24am UTC](https://discuss.elastic.co/t/elastic-cloud-with-auth-but-without-https/198337/6 "2022-11-04T07:24:17Z")

</div>


