# How to run ElasticSearch containers in FIPS 140-2 compliant mode

**URL:** <https://discuss.elastic.co/t/how-to-run-elasticsearch-containers-in-fips-140-2-compliant-mode/323380>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [January 18, 2023, 6:08am UTC](https://discuss.elastic.co/t/how-to-run-elasticsearch-containers-in-fips-140-2-compliant-mode/323380 "2023-01-18T06:08:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinay\_Chaudhari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinay_chaudhari/32/116060_2.png) [@Vinay\_Chaudhari](https://discuss.elastic.co/u/Vinay_Chaudhari)\
**Post date:** [January 18, 2023, 6:08am UTC](https://discuss.elastic.co/t/how-to-run-elasticsearch-containers-in-fips-140-2-compliant-mode/323380/1 "2023-01-18T06:08:55Z")

</div>

We self host ES 8.x on AKS using ECK operator. For one of government project, we need to comply with FIPS 140-2. There is some documentation available on the same [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/fips-140-compliance.html) but there is no mention what to do while using ECK operator. We can run AKS nodes in FIPS 140-2 enabled modes but how to ensure JVM within container is running in FIPS2 compliant mode? Any help is appreciated including whether such configuration is even possible or not.

---

<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:** [February 15, 2023, 6:09am UTC](https://discuss.elastic.co/t/how-to-run-elasticsearch-containers-in-fips-140-2-compliant-mode/323380/2 "2023-02-15T06:09:04Z")

</div>

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