The "Open Distro"-fork of Elasticsearch uses Tenants instead of Kibana Spaces where each tenant corresponds to a separate Kibana Index / Alias.
When provisioning Kibana Objects on an "Open Distro"-cluster using the Phil Bakers Terraform Elasticsearch community provider it will by default create resources in .kibana-index which corresponds to the global tenant.
For example after spinning up a single node cluster the different Kibana indexes may look like
GET _alias/.kibana_*
{
// The private admin tenant
".kibana_92668751_admin_1" : {
"aliases" : {
".kibana_92668751_admin" : { }
}
},
// The global tenant'
".kibana_1" : {
"aliases" : {
".kibana" : { }
}
}
// Some custom private tenant 'monitoring'
".kibana_1852089416_monitoring_1" : {
"aliases" : {
".kibana_1852089416_monitoring" : { }
}
}
}Say you have a terraform module for provisioning Index Patterns, Dashboards & Visualizations for an Open Distro Cluster
After successfully applying it the resources will be only visible in the global tenant and not in the private tenants admin or monitoring.
Until this is possible you may use kibana_alias.py as a workaround.
See example usage in elastic.tf
- GitHub Issue: Failed to create index patterns via elasticsearch_kibana_object resource
- Terraform: External Data Source