# Implementing security on a live production stack

**URL:** <https://discuss.elastic.co/t/implementing-security-on-a-live-production-stack/249818>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [September 24, 2020, 1:02pm UTC](https://discuss.elastic.co/t/implementing-security-on-a-live-production-stack/249818 "2020-09-24T13:02:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfs1](https://avatars.discourse-cdn.com/v4/letter/j/439d5e/32.png) [@jfs1](https://discuss.elastic.co/u/jfs1)\
**Post date:** [September 24, 2020, 1:02pm UTC](https://discuss.elastic.co/t/implementing-security-on-a-live-production-stack/249818/1 "2020-09-24T13:02:32Z")

</div>

I'm in the process of upgrading a (very) old stack. Now at version 6.8.12, I want to implement security.

The issue is : it's a live, production system. It's ingesting 2.6K e/s and altough I have a little bit of spooling (through redis), it is not unlimited. It is also not-minimal, with 6 data nodes and 2 ingest/display nodes.

How can I enable inter-node encryption and TLS security with minimal downtime and without losing any event data ?

(note : I have read the documentation at [https://www.elastic.co/blog/getting-started-with-elasticsearch-security](https://www.elastic.co/blog/getting-started-with-elasticsearch-security) and others and I think I have a pretty good understanding of the process - but most examples are for either small or idle clusters where mine is neither small nor idle)

---

<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:** [October 22, 2020, 1:02pm UTC](https://discuss.elastic.co/t/implementing-security-on-a-live-production-stack/249818/2 "2020-10-22T13:02:38Z")

</div>

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