# Hardening elasticsearch using certificate from sectigo

**URL:** <https://discuss.elastic.co/t/hardening-elasticsearch-using-certificate-from-sectigo/311296>\
**Category:** Elasticsearch\
**Created:** [August 3, 2022, 11:10am UTC](https://discuss.elastic.co/t/hardening-elasticsearch-using-certificate-from-sectigo/311296 "2022-08-03T11:10:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![xalastoi](https://avatars.discourse-cdn.com/v4/letter/x/53a042/32.png) [@xalastoi](https://discuss.elastic.co/u/xalastoi)\
**Post date:** [August 3, 2022, 11:10am UTC](https://discuss.elastic.co/t/hardening-elasticsearch-using-certificate-from-sectigo/311296/1 "2022-08-03T11:10:54Z")

</div>

0

Due to auditing requirements, it is necessary to encrypt all connections between the application and the elasticsearch cluster after a little googling, I realized that the elasticsearch cluster protection looks like this

1. Enable x-pack: true in elasticsearch.yml
2. generate CA
3. copy the CA to each node in the cluster
4. generate a certificate for each node (by signing it using the generated CA in paragraph 2) in this case, we will have a secure connection ONLY between the nodes in the cluster (on port 9300) inter-node tls

I have purchased an SSL certificate and the certificate files look like this STAR\_rem-masters\_com.ca-bundle star\_rem\_masters\_com\_certificate.crt

(I bought these certificates from sectigo) Now the question is how can these certificates be used for inter-node ssl and client-server ( application \> elasticsearch ) because in all examples they use self-signed certificates that are generated using elasticsearch-certutil

---

<div class="post-metadata">

**Author:** ![79g](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/79g/32/109191_2.png) [@79g](https://discuss.elastic.co/u/79g)\
**Post date:** [August 3, 2022, 11:18am UTC](https://discuss.elastic.co/t/hardening-elasticsearch-using-certificate-from-sectigo/311296/2 "2022-08-03T11:18:47Z")

</div>

Hello,

have you checked the documentation?

[Set up basic security for the Elastic Stack plus secured HTTPS traffic](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-basic-setup-https.html)

It refers to the scenario you mean.

See:

```auto
server.ssl.certificate: $KBN_PATH_CONF/kibana-server.crt
server.ssl.key: $KBN_PATH_CONF/kibana-server.key

```

Hope it helps.

---

<div class="post-metadata">

**Author:** ![xalastoi](https://avatars.discourse-cdn.com/v4/letter/x/53a042/32.png) [@xalastoi](https://discuss.elastic.co/u/xalastoi)\
**Post date:** [August 3, 2022, 11:43am UTC](https://discuss.elastic.co/t/hardening-elasticsearch-using-certificate-from-sectigo/311296/3 "2022-08-03T11:43:42Z")

</div>

is this configured in elasticsearch.yml?

---

<div class="post-metadata">

**Author:** ![79g](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/79g/32/109191_2.png) [@79g](https://discuss.elastic.co/u/79g)\
**Post date:** [August 3, 2022, 11:47am UTC](https://discuss.elastic.co/t/hardening-elasticsearch-using-certificate-from-sectigo/311296/4 "2022-08-03T11:47:04Z")

</div>

> **[Security settings in Elasticsearch | Elasticsearch Guide \[8.3\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settings.html)**

---

<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:** [August 31, 2022, 11:47am UTC](https://discuss.elastic.co/t/hardening-elasticsearch-using-certificate-from-sectigo/311296/5 "2022-08-31T11:47:33Z")

</div>

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