# Is it viable to create a ElasticSearch user for each customer? And indexes?

**URL:** <https://discuss.elastic.co/t/is-it-viable-to-create-a-elasticsearch-user-for-each-customer-and-indexes/239539>\
**Category:** Elasticsearch\
**Created:** [July 1, 2020, 7:39pm UTC](https://discuss.elastic.co/t/is-it-viable-to-create-a-elasticsearch-user-for-each-customer-and-indexes/239539 "2020-07-01T19:39:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jodinathan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jodinathan/32/45821_2.png) [@jodinathan](https://discuss.elastic.co/u/jodinathan)\
**Post date:** [July 1, 2020, 7:39pm UTC](https://discuss.elastic.co/t/is-it-viable-to-create-a-elasticsearch-user-for-each-customer-and-indexes/239539/1 "2020-07-01T19:39:20Z")

</div>

We are pondering in creating one user in elasticsearch & kibana for each of our customers through the api and also creating a unique index for them, ie: `somedata12345`, `somedata54321`, where the 12345 would be the user ID in our system.  
With that, we can also create visualizations to embed in our website.

Questions:

1. Does this make sense? Or are we trying to do something that ELK is not supposed to do?
2. Is it possible to protect one customer from seeing other customer(user) visualization? (I've seen some articles here and there that it should be able to authenticate users to kibana's visualization through nginx reverse proxy)

---

<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:** [July 1, 2020, 8:07pm UTC](https://discuss.elastic.co/t/is-it-viable-to-create-a-elasticsearch-user-for-each-customer-and-indexes/239539/2 "2020-07-01T20:07:06Z")

</div>

It typically works for small number of users but tend to scale badly.

---

<div class="post-metadata">

**Author:** ![jodinathan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jodinathan/32/45821_2.png) [@jodinathan](https://discuss.elastic.co/u/jodinathan)\
**Post date:** [July 1, 2020, 8:42pm UTC](https://discuss.elastic.co/t/is-it-viable-to-create-a-elasticsearch-user-for-each-customer-and-indexes/239539/3 "2020-07-01T20:42:58Z")

</div>

do you have a suggestion?  
Maybe create the user when it log into my system and then erase it when the session expires?

---

<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:** [July 2, 2020, 5:03am UTC](https://discuss.elastic.co/t/is-it-viable-to-create-a-elasticsearch-user-for-each-customer-and-indexes/239539/4 "2020-07-02T05:03:49Z")

</div>

What is the use case? How many users do you need to support?

---

<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:** [July 30, 2020, 5:03am UTC](https://discuss.elastic.co/t/is-it-viable-to-create-a-elasticsearch-user-for-each-customer-and-indexes/239539/5 "2020-07-30T05:03:53Z")

</div>

Closed on July 30, 2020, 5:03am UTC

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