# Same ES cluster for non prod environments (for both dev and qa)

**URL:** <https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937>\
**Category:** Elasticsearch\
**Created:** [November 1, 2020, 12:58pm UTC](https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937 "2020-11-01T12:58:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kcs08](https://avatars.discourse-cdn.com/v4/letter/k/a88e4f/32.png) [@kcs08](https://discuss.elastic.co/u/kcs08)\
**Post date:** [November 1, 2020, 12:58pm UTC](https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937/1 "2020-11-01T12:58:56Z")

</div>

Hello,

I have setup Elasticsearch (ES) cluster and using it for dev environment with set of indexes. And wanted to use the same ES cluster for qa environment as well. I mean two different environments with same index names. Please suggest how do we design this way.

Thank you,  
Chandra

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 2, 2020, 11:29pm UTC](https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937/2 "2020-11-02T23:29:22Z")

</div>

Welcome to our community! 😃

The easiest way would be to just add the name of the environment to each index.

---

<div class="post-metadata">

**Author:** ![kcs08](https://avatars.discourse-cdn.com/v4/letter/k/a88e4f/32.png) [@kcs08](https://discuss.elastic.co/u/kcs08)\
**Post date:** [November 3, 2020, 4:44am UTC](https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937/3 "2020-11-03T04:44:21Z")

</div>

Thank you for invite and suggestion, Mark.

So the suggested approach is create two separate indexes one for dev env and another one for qa env. For example dev\_index1 and qa\_index1. Please correct if me if my understanding is wrong.

With this approach we need the code changes (or provide some configs) in the application as well to use corresponding index based on the deployment environment (i.e dev or qa).

Thank you,  
Chandra

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 4, 2020, 5:27am UTC](https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937/4 "2020-11-04T05:27:07Z")

</div>

Yes, that's the approach.

Otherwise how will you differentiate the two?

---

<div class="post-metadata">

**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:** [November 4, 2020, 5:33am UTC](https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937/5 "2020-11-04T05:33:19Z")

</div>

If you want the same index name in two separate environments you must have separate clusters.

---

<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 2, 2020, 5:33am UTC](https://discuss.elastic.co/t/same-es-cluster-for-non-prod-environments-for-both-dev-and-qa/253937/6 "2020-12-02T05:33:21Z")

</div>

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