# \[KIBANA\]\[Rules and Connectors\] You must enable Transport Layer Security

**URL:** <https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350>\
**Category:** Kibana\
**Tags:** elastic-stack-security, elastic-stack-alerting\
**Created:** [August 13, 2021, 12:14pm UTC](https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350 "2021-08-13T12:14:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrick57](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Patrick57](https://discuss.elastic.co/u/Patrick57)\
**Post date:** [August 13, 2021, 12:14pm UTC](https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350/1 "2021-08-13T12:14:21Z")

</div>

Dear Elastic Community,

I am writing to request for your help.  
I am currently running an ELK stack on latest version (7.14) on a standalone CentOS 7 server.

I would like to use the Rules and Connectors functionality but I am struggling to get it working.

I understood that I need to activate TLS communication between Kibana and Elasticsearch and also generate an API Key on kibana side to make it works.

Here are the configuration files:  
**elasticsearch.yml:**

```auto
#SSL config:
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.keystore.path: /etc/elasticsearch/http.p12

xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.client_authentication: required

xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.keystore.path: /etc/elasticsearch/http.p12
xpack.security.transport.ssl.truststore.path: /etc/elasticsearch/http.p12

# Disable API key:
xpack.security.authc.api_key.enabled: false

```

**kibana.yml:**

```auto
 elasticsearch.hosts: ["https://{SERVER_PRIVATE_IP}:9200"]
 elasticsearch.ssl.certificateAuthorities: /etc/kibana/elasticsearch-ca.pem
 elasticsearch.ssl.verificationMode: certificate
 
 xpack.encryptedSavedObjects.encryptionKey: "a0d93b89eb18100a23b3bf7b9f69951f"

```

The SSL configuration works fine. I also had to update logstash output config to connect to Elasticsearch via https.

The interface still shows the

> You must enable Transport Layer Security  
> Alerting relies on API keys, which require TLS between Elasticsearch and Kibana.

I have raised kibana's log level but I see nothing wrong:

```auto
logging.verbose: true

```

I do not know what I am missing.

Do you have any idea what could be my problem?

Many thanks in advance for your help.

Kind regards,

Patrick

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 17, 2021, 1:16am UTC](https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350/2 "2021-08-17T01:16:17Z")

</div>

Welcome to our community! 😃

Can you share your Elasticsearch and Kibana logs from when they startup?  
Feel free to use gist/pastebin/etc if they don't fit here.

---

<div class="post-metadata">

**Author:** ![Yang\_Wang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yang_wang/32/48857_2.png) [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)\
**Post date:** [August 17, 2021, 1:38am UTC](https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350/3 "2021-08-17T01:38:18Z")

</div>

> [@Patrick57](#):
>
> ```auto
> # Disable API key:
> xpack.security.authc.api_key.enabled: false
> 
> ```

You explicitly disabled API key but Kibana laerts requires API keys to work as it says in the error message:

```auto
Alerting relies on API keys

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [August 17, 2021, 2:47am UTC](https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350/4 "2021-08-17T02:47:30Z")

</div>

In case anyone is interested,  
We just had a fairly lengthy conversation on this and this thread

> [@Alert in single node](https://discuss.elastic.co/t/alert-in-single-node/281595):
>
> I'm using Machine learning 7.13 and planning to create alert rule for warning. But I saw this [image] After searching I found these steps to enable TLS. But I saw in [Set up minimal security for Elasticsearch | Elasticsearch Guide [7.13] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.13/security-minimal-setup.html) wrote If you’re running a [single-node cluster](https://www.elastic.co/guide/en/elasticsearch/reference/7.13/bootstrap-checks.html#single-node-discovery), then you can stop here. If your cluster has multiple nodes, then you must configure Transport Layer Security (TLS) between nodes. [Production mode](https://www.elastic.co/guide/en/elasticsearch/reference/7.13/bootstrap-checks.html#dev-vs-prod-mode) clusters will not start if you do not enable TLS. An…

---

<div class="post-metadata">

**Author:** ![Patrick57](https://avatars.discourse-cdn.com/v4/letter/p/aeb1de/32.png) [@Patrick57](https://discuss.elastic.co/u/Patrick57)\
**Post date:** [August 17, 2021, 6:14am UTC](https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350/5 "2021-08-17T06:14:18Z")

</div>

Hi Yang\_Wang,

Indeed that was it.  
I tested it because it was advised somewhere in the documentation but forgot to remove it.

Many thanks!

Best regards,

---

<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:** [September 14, 2021, 6:14am UTC](https://discuss.elastic.co/t/kibana-rules-and-connectors-you-must-enable-transport-layer-security/281350/6 "2021-09-14T06:14:24Z")

</div>

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