# Elasticsearch and SSL certificates

**URL:** <https://discuss.elastic.co/t/elasticsearch-and-ssl-certificates/50721>\
**Category:** Elasticsearch\
**Created:** [May 23, 2016, 1:03pm UTC](https://discuss.elastic.co/t/elasticsearch-and-ssl-certificates/50721 "2016-05-23T13:03:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simon\_Hanmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simon_hanmer/32/9780_2.png) [@Simon\_Hanmer](https://discuss.elastic.co/u/Simon_Hanmer)\
**Post date:** [May 23, 2016, 1:03pm UTC](https://discuss.elastic.co/t/elasticsearch-and-ssl-certificates/50721/1 "2016-05-23T13:03:57Z")

</div>

Hi, we're just trying out the latest versions of elasticsearch in an ELK stack. Is there any method to configure authentication using SSL certificates to ensure that only authorised clients submit data into elasticsearch? We're using beats rather than logstash.

Thanks

---

<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:** [May 25, 2016, 8:45am UTC](https://discuss.elastic.co/t/elasticsearch-and-ssl-certificates/50721/2 "2016-05-25T08:45:20Z")

</div>

Yep - [https://www.elastic.co/guide/en/shield/current/index.html](https://www.elastic.co/guide/en/shield/current/index.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:** [July 5, 2017, 10:49pm UTC](https://discuss.elastic.co/t/elasticsearch-and-ssl-certificates/50721/3 "2017-07-05T22:49:09Z")

</div>