# Microsoft recommendations to improve security and resilience in the elasticsearch service **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [September 18, 2024, 10:09pm UTC](https://discuss.elastic.co/t/microsoft-recommendations-to-improve-security-and-resilience-in-the-elasticsearch-service/366759 "2024-09-18T22:09:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![sairinraychoudhury](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sairinraychoudhury/32/137696_2.png) [@sairinraychoudhury](https://discuss.elastic.co/u/sairinraychoudhury)\ **Post date:** [September 18, 2024, 10:09pm UTC](https://discuss.elastic.co/t/microsoft-recommendations-to-improve-security-and-resilience-in-the-elasticsearch-service/366759/1 "2024-09-18T22:09:54Z")
Hi Everyone, Needed advice from community members. We have deployed elasticsearch 8.5.1 using helm in Microsoft Azure Kubernetes Service (AKS). Also during an assessment of our platform towards improved security & resilience angle received below recommendations from Microsoft experts to be implemented. 1. Privileged containers should be avoided. 2. The root access inside the service container should be avoided. We are not sure if above actions when implemented will have an impact on elasticsearch since we used default elasticsearch configs which are in helm chart for elasticsearch. Could anyone from the community please help or guide us on below queries? 1. Have you tried implementing custom configs apart from default configs provided? 2. Do you have a view of the impact by any means if we go ahead and implement this? 3. Are there any other general recommendation towards achieving this? ---
**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\ **Post date:** [September 19, 2024, 8:13am UTC](https://discuss.elastic.co/t/microsoft-recommendations-to-improve-security-and-resilience-in-the-elasticsearch-service/366759/2 "2024-09-19T08:13:34Z")
From #Elasticsearch to #Elastic Cloud on Kubernetes (ECK) ---
**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\ **Post date:** [September 19, 2024, 8:13am UTC](https://discuss.elastic.co/t/microsoft-recommendations-to-improve-security-and-resilience-in-the-elasticsearch-service/366759/3 "2024-09-19T08:13:35Z")
Hi @sairinraychoudhury ! Have you considered using [Elastic Cloud on Kubernetes](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-overview.html)? ---
**Author:** ![sairinraychoudhury](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sairinraychoudhury/32/137696_2.png) [@sairinraychoudhury](https://discuss.elastic.co/u/sairinraychoudhury)\ **Post date:** [December 4, 2024, 7:17pm UTC](https://discuss.elastic.co/t/microsoft-recommendations-to-improve-security-and-resilience-in-the-elasticsearch-service/366759/4 "2024-12-04T19:17:06Z")
Hi @Carlos_D , Thank you for suggestion, Could you please let me know how I can migrate from elasticsearch cluster to ECK and how I can get current indices at the new ECK. For info we have master, client and data nodes. I'm very new to this so have no idea how to proceed further. ---
**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\ **Post date:** [December 10, 2024, 8:28am UTC](https://discuss.elastic.co/t/microsoft-recommendations-to-improve-security-and-resilience-in-the-elasticsearch-service/366759/5 "2024-12-10T08:28:02Z")
Hey @sairinraychoudhury : You could [reindex from a remote cluster](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#reindex-from-remote), or also [restore from a snapshot](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshot-restore.html).