Kibana is an open source analytics and visualization platform designed to search, view, and interact with data stored in Elasticsearch indices. The use of Kibana is included with your subscription.
For new Elasticsearch clusters at version 5.0 and later, we automatically create a Kibana instance for you.
To access Kibana:
- Log into the Cloud UI.
On the Deployments page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
Under Applications, click the Kibana Launch link and wait for Kibana to open.
The default port 9243 of the resulting URL can be also changed to 443.
Log into Kibana:
For versions 7.7 and later: Single sign-on (SSO) is enabled between your Cloud account and the Kibana instance, most likely you are logged in already and Kibana just opens. However, if your token has expired, choose from one of these methods to log in:
- Click Login with Cloud. You’ll need to log in with your Cloud account credentials and then you’ll be redirected to Kibana.
Log in with the
elasticsuperuser. The password was provided when you created your cluster or can be reset.
- You can also log in with any users you created in Kibana already.
For version 5.0 to 7.6: Log in with the
elasticsuperuser. The password was provided when you created your cluster or can be reset. Or you can also log in with any users you created in Kibana already.
For versions before 5.0: If Shield is enabled, you can log into Kibana with the
adminuser to try it out. The password was provided when you enabled Shield or can be reset. Or you can also log in with any users you created in Kibana already.
In production systems, you might need to control what Elasticsearch data users can access through Kibana, so you need create credentials that can be used to access the necessary Elasticsearch resources. This means granting read access to the necessary indexes, as well as access to update the
If you use a version before 5.0 or if your cluster didn’t include a Kibana instance initially, there might not be a Kibana endpoint URL shown, yet. To gain access, all you need to do is enable Kibana first.