IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Access Kibana

edit

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, we automatically create a Kibana instance for you.

To access Kibana:

  1. Log into the Cloud UI.
  2. 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.

  3. Under Applications, select the Kibana Launch link and wait for Kibana to open.

    The URL provided to access Kibana is based on the endpoint URL configured in the ECE Settings UI.

    This URL should resolve to your external load balancer, which forwards the traffic to ECE proxies on port 9243. If your load balancer is configured to accept traffic on both ports 9243 and 443, you can use either port when connecting to Kibana. However, built-in SSO will only work with the URL configured in ECE Settings UI.

  4. Log into Kibana. Single sign-on (SSO) is enabled between your Cloud account and the Kibana instance. If you’re logged in already, then Kibana opens without requiring you to log in again. However, if your token has expired, choose from one of these methods to log in:

    • Select 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 elastic superuser. The password was provided when you created your cluster or can be reset.
    • 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 .kibana index.

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.