# Alerting UI in 7.7 and TLS **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-alerting\ **Created:** [May 15, 2020, 9:33am UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782 "2020-05-15T09:33:24Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![LLin](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@LLin](https://discuss.elastic.co/u/LLin)\ **Post date:** [May 15, 2020, 9:33am UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/1 "2020-05-15T09:33:24Z")
The new feature in the UI in Kibana is a welcome one, but currently, it's saying for me to enable TLS between Kibana and Elasticsearch. We are using a Load Balancer in front of Elasticsearch that terminates HTTPS, so the `elasticsearch.hosts` variable in the Kibana config is using a HTTPS url. According to the documentation [here](https://www.elastic.co/guide/en/kibana/7.7/configuring-tls.html#configuring-tls-kib-es) that should be sufficient as it offers 2 options, to set up http encryption on Elasticsearch itself, or use a proxy that provides an HTTPS endpoint for Elasticsearch, which the load balancer does. Or am I reading this incorrectly? ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [May 27, 2020, 12:13am UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/2 "2020-05-27T00:13:30Z")
cc @gidimorris @mikecote ---
**Author:** ![mikecote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikecote/32/58549_2.png) [@mikecote](https://discuss.elastic.co/u/mikecote)\ **Post date:** [May 27, 2020, 1:55pm UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/4 "2020-05-27T13:55:52Z")
Hi @LLin, In the alerting [setup and prerequisites documentation](https://www.elastic.co/guide/en/kibana/current/alerting-getting-started.html#alerting-setup-prerequisites), it mentions that [TLS on the HTTP interface](https://www.elastic.co/guide/en/elasticsearch/reference/7.7/configuring-tls.html#tls-http) is required for alerting to work. This would mean a proxy will not suffice. ---
**Author:** ![LLin](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@LLin](https://discuss.elastic.co/u/LLin)\ **Post date:** [May 28, 2020, 5:48am UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/5 "2020-05-28T05:48:54Z")
Hey @mikecote , so in the documentation here: > **[Encrypt communications in Kibana | Kibana Guide \[7.7\] | Elastic](https://www.elastic.co/guide/en/kibana/7.7/configuring-tls.html#configuring-tls-kib-es)** There's the following statement: > To perform this step, you must [enable the Elasticsearch security features](https://www.elastic.co/guide/en/elasticsearch/reference/7.7/configuring-security.html) or you must have a proxy that provides an HTTPS endpoint for Elasticsearch.\< Is the or part not valid then? Kibana is configured to connect to an HTTPS endpoint that is provided by an F5 proxy for Elasticsearch, so the wording would seem to indicate that it should work. ---
**Author:** ![mikecote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikecote/32/58549_2.png) [@mikecote](https://discuss.elastic.co/u/mikecote)\ **Post date:** [May 28, 2020, 12:36pm UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/6 "2020-05-28T12:36:04Z")
Hi @LLin, We're working on clarifying the alerting documentation in this PR: [https://github.com/elastic/kibana/pull/67486](https://github.com/elastic/kibana/pull/67486). The proxy portion is insufficient for alerting to work as it depends on [API keys](https://www.elastic.co/guide/en/kibana/current/api-keys.html#api-keys-service) in Elasticsearch which itself requires TLS on Elasticsearch's HTTP interface to work. Hope this helps, Mike ---
**Author:** ![Reeker](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Reeker](https://discuss.elastic.co/u/Reeker)\ **Post date:** [June 4, 2020, 2:36pm UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/7 "2020-06-04T14:36:55Z")
Hey Mike, I've installed Elasticsearch,Kibana and Logstash on one server and i am monitoring folders with Filebeat on another PC. How can i get the Alarms and Actions portion to be visible in Kibana since i am using all 3 components on one device? Also i am with the free version of all 4 so i presume i need to be at least a Premium user. Please let me know if there is any way to accomplish this. Regards Metodi ---
**Author:** ![mikecote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikecote/32/58549_2.png) [@mikecote](https://discuss.elastic.co/u/mikecote)\ **Post date:** [June 4, 2020, 3:04pm UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/8 "2020-06-04T15:04:49Z")
Hi @Reeker, To get started you can find the documentation here: [https://www.elastic.co/guide/en/kibana/7.7/alerting-getting-started.html](https://www.elastic.co/guide/en/kibana/7.7/alerting-getting-started.html). Since alerting is an xpack feature, all you need is a basic license. There are a few items to complete before using alerting: - [https://www.elastic.co/guide/en/kibana/7.7/alerting-getting-started.html#alerting-setup-prerequisites](https://www.elastic.co/guide/en/kibana/7.7/alerting-getting-started.html#alerting-setup-prerequisites) - [https://www.elastic.co/guide/en/kibana/7.7/alerting-getting-started.html#alerting-security](https://www.elastic.co/guide/en/kibana/7.7/alerting-getting-started.html#alerting-security) Hope this helps! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 2, 2020, 3:04pm UTC](https://discuss.elastic.co/t/alerting-ui-in-7-7-and-tls/232782/9 "2020-07-02T15:04:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.