Multi-tenancy Elastic Stack
Last updated
Last updated
This document will guide you through setting up your Elasticsearch and Kibana stack with ReadonlyREST such that:
There will be two tenancies: one for Sales and one for Ops department.
In each tenancy, 3 users will be able to login into Kibana using their own set of credentials
Each tenancy will contain its own, independant Kibana dashboards, visualizations and index patterns.
Each user within a tenancy may be restricted to visualizing distinct subsets of the whole data contained in Elasticsearch (i.e. only certain indices).
For this tutorials, we want to have three users per tenancy, each of them has a distinct access level to a shared Kibana tenancy (set of dashboards and settings).
| "sales_admin" | "sales_rw_usr" | "sales_ro_usr" | |
|---|---|---|---|
| "ops_admin" | "ops_rw_usr" | "ops_ro_usr" | |
|---|---|---|---|
NB: ReadonlyREST for Elastisearch and ReadonlyREST Enterprise for Kibana have an great amount of features like groups, connector for external systems like LDAP, etc. Don't forget to visit the full documentation and the forum to know more about it.
NB: The capabilities gained by admin users when they access the "readonlyrest" Kibana App are global, that is, they can add/remove tenancies, users, groups, etc.
For the scope of this guide, we will assume:
You will have a functioning installation of Elasticsearch and Kibana
If you don't have the ROR Enterprise for Kibana plugin, get yourself a two weeks free trial build!
Because ReadonlyREST is not compatible with XPack Security module please make sure you disable xpack.security module from both Kibana and Elasticsearch by adding the following line to both elasticsearch.yml and kibana.yml:
Right beside your elasticsearch.yml, create a file called readonlyrest.yml and write the following settings into it.
With ROR, we try as much as possible to keep all the settings withing the Elasticsearch domain. Therefore, you'll notice how few settings are needed on the Kibana side, apart from actually installing the plugin.
Open up config/kibana.yml and add/edit the following settings:
Fire up Elasticsearch
And then Kibana
Now you are ready to point your browser to the Kibana server IP (defaulting on port 5601) and you should see a login prompt. You can login as any user i.e. "sales_rw_usr", or "ops_admin" and the password is always "dev".
MJust remember to login with a RW user first, so Kibana can create its own default settings.
Can create,edit,delete Sales' dashboards
✅
✅
Can change Kibana settings for Sales
✅
✅
Only sees "sales_logstash*" data from 2018
✅
Can see "add","delete","edit" buttons
✅
✅
"dev-tools" Kibana App is hidden
✅
✅
"readonlyrest" Kibana App is hidden
✅
Can create,edit,delete Ops dashboards
✅
✅
Can change Kibana settings for Ops
✅
✅
Only sees ops_logstash data from 2018
✅
Can see "add","delete","edit" buttons
✅
✅
"dev-tools" Kibana App is hidden
✅
✅
"readonlyrest" Kibana App is hidden
✅