# Does implementing security require a rolling restart or full cluster restart **URL:** \ **Category:** Elasticsearch\ **Tags:** docker\ **Created:** [March 27, 2023, 10:27am UTC](https://discuss.elastic.co/t/does-implementing-security-require-a-rolling-restart-or-full-cluster-restart/328603 "2023-03-27T10:27:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Umang\_Pachaury](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/umang_pachaury/32/113523_2.png) [@Umang\_Pachaury](https://discuss.elastic.co/u/Umang_Pachaury)\ **Post date:** [March 27, 2023, 10:27am UTC](https://discuss.elastic.co/t/does-implementing-security-require-a-rolling-restart-or-full-cluster-restart/328603/1 "2023-03-27T10:27:18Z")
I have a cluster(non-https) running in the production environment with docker and now I want to implement security on that cluster. While adding https related configurations, certs etc.. to all the nodes in cluster, will the rolling restart work or I need to do full cluster restart only. What should be the best approach to enable security on production clusters ? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 27, 2023, 10:33am UTC](https://discuss.elastic.co/t/does-implementing-security-require-a-rolling-restart-or-full-cluster-restart/328603/2 "2023-03-27T10:33:03Z")
Enabling security in a cluster do require a full cluster restart. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 24, 2023, 10:33am UTC](https://discuss.elastic.co/t/does-implementing-security-require-a-rolling-restart-or-full-cluster-restart/328603/3 "2023-04-24T10:33:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.