# Production Infrastructure Guidelines - Elastic search

**URL:** <https://discuss.elastic.co/t/production-infrastructure-guidelines-elastic-search/210360>\
**Category:** Elasticsearch\
**Created:** [December 3, 2019, 1:45pm UTC](https://discuss.elastic.co/t/production-infrastructure-guidelines-elastic-search/210360 "2019-12-03T13:45:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nages](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nages/32/46943_2.png) [@nages](https://discuss.elastic.co/u/nages)\
**Post date:** [December 3, 2019, 1:45pm UTC](https://discuss.elastic.co/t/production-infrastructure-guidelines-elastic-search/210360/1 "2019-12-03T13:45:57Z")

</div>

I am going through the following documentation

```auto
https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html

```

What are the best practises for production infracture in terms of making it exposed for search requests, index requests - should it expose ip address of (only) coordinating node ?

As i understood, it is not good idea to expose any other node details other nodes apart from coordinating node. As other nodes are implicitly coordinating nodes, they might have extra burden if these nodes are exposed.

---

<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:** [December 31, 2019, 1:55pm UTC](https://discuss.elastic.co/t/production-infrastructure-guidelines-elastic-search/210360/2 "2019-12-31T13:55:05Z")

</div>

Closed on December 31, 2019, 1:55pm UTC

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