Logging In to an Elasticsearch Cluster Using Kibana

Constraints on Kibana Usage

• You can customize the username, role name, and tenant name in Kibana.
• With an Elasticsearch 7.10.2 cluster (the image version is 7.10.2_24.3.3_* or later), you can switch between Chinese and English on Kibana.

  In the upper right corner of the Kibana console, click , select a language, and confirm the language change.

Logging In to an Elasticsearch Cluster by Accessing Kibana Through the Console

1. Log in to the CSS management console.
2. On the Clusters page, locate the target cluster and click Access Kibana in the Operation column to go to the Kibana login page.
   • Non-security cluster: The Kibana console is displayed without asking for a username and password.
   • Security cluster: Enter the username and password on the login page and click Log In to log in to the Kibana console. The default username is admin and the password is the one specified during cluster creation.
3. After the login is successful, you can access clusters through Kibana.

Logging In to an Elasticsearch Cluster by Accessing Kibana Using a Public IP Address

• Only clusters in security mode support Kibana access through a public IP address.
• If you disable Kibana public network access and then re-enable it, the public IP address for accessing Kibana may change. Exercise caution.

1. Log in to the CSS management console.
2. Enable Kibana public network access for the Elasticsearch cluster. You can do that either when creating an Elasticsearch cluster or afterwards.
   • For how to enable Kibana public network access when creating an Elasticsearch cluster, see Creating an Elasticsearch Cluster.
   • To enable public network access for Kibana for an existing cluster, perform the following steps:
     1. Choose Clusters in the navigation pane. On the Clusters page, click the name of the target cluster.
     2. Click the Kibana Public Access tab, and enable Kibana Public Access.
     3. On the displayed page, set parameters. If Kibana public network access is already enabled, you can modify relevant settings.

        Table 2 Configuring public network access for Kibana

        Parameter	Description
        Bandwidth	Bandwidth for accessing Kibana through a public IP address Value range: 1 to 100. Unit: Mbit/s
        Access Control	If you disable this function, all IP addresses can access Kibana through the public IP address. If you enable this function, only IP addresses or IP address ranges in the whitelist can access Kibana through the public IP address.
        Whitelist	IP addresses or IP address ranges allowed to access the cluster. Use commas (,) to separate multiple IP addresses or ranges. This parameter can be configured only when Access Control is enabled. You are advised to enable the whitelist. NOTE: The whitelist that controls Kibana public network access depends on whitelist support by the ELB service. After you update the whitelist, the new settings take effect immediately for new connections. For existing persistent connections using the IP addresses that have been removed from the whitelist, the new settings take effect in approximately 1 minute after these connections are disconnected.

     4. Click OK.
3. After Kibana public network access is enabled, obtain the Kibana public IP address on the Kibana Public Access page.
   Figure 1 Obtaining the Kibana public IP address
   
4. Enter the public IP address for Kibana in the browser address box to go to the Kibana login page.

   Enter the username and password on the login page and click Log In to log in to the Kibana console. The default username is admin and the password is the administrator password you specified during cluster creation.

5. After the login is successful, you can access the Elasticsearch cluster through Kibana.

Logging In to an Elasticsearch Cluster by Accessing Kibana Using a Private Network Address

Only servers in the same VPC can access Kibana using a private network address of the Elasticsearch cluster.

1. Log in to the CSS management console.
2. On the Clusters page, click the name of a cluster. The Cluster Information page is displayed.
3. On the Cluster Information page, obtain the cluster's private network address.
   Figure 2 Obtaining the private IP address
   
4. Change the port number in the cluster's private network address from 9200 to 5601, which becomes the private network address of Kibana. For example, if the cluster's private network IPv4 address is 192.168.0.***:9200, the private network address of Kibana is 192.168.0.***:5601.
5. On the server, enter the private network address of Kibana to go to the Kibana login page.
   • Non-security cluster: The Kibana console is displayed without asking for a username and password.
   • Security cluster: Enter the username and password on the login page and click Log In to log in to the Kibana console. The default username is admin and the password is the one specified during cluster creation.
6. After the login is successful, you can access the Elasticsearch cluster through Kibana.

More: Configuring a Custom Kibana Base Path for Public Network Access

With Elasticsearch 7.10.2, you can configure a custom Base Path for Kibana access after Kibana public network access is enabled. Or you can use the default Kibana Base Path instead.

• This feature is available for Elasticsearch 7.10.2 clusters (the image version is 7.10.2_24.3.3_* or later) where Kibana public network access is enabled.
• Only the cluster administrator admin under Global Tenant has the permission to configure a custom Kibana Base Path, which applies globally.

1. Log in to the CSS management console.
2. Choose Clusters > Elasticsearch in the navigation pane. On the Clusters page, locate the target cluster and click Access Kibana in the Operation column.
3. Log in to Kibana using an administrator account.
   • Username: admin (default administrator account)
   • Password: Enter the administrator password you set when creating the cluster in security mode.
4. After a successful login, choose Stack Management in the left navigation pane of the Kibana console.
5. Choose Advanced Settings on the left of the Stack Management page.
6. On the Settings page, set Base Path Alias. The value must start with a slash (/) and must not end with one. A multi-layer path is allowed, but its length cannot exceed 255 characters.
   Figure 3 Custom Base Path
   
7. Click Save changes. The saved changes take effect in approximately 10 seconds.
8. Access Kibana using the Kibana public network address plus Base Path Alias.

   For example, if the Kibana public network address of the Elasticsearch cluster is https://xx.xx.xx.xx:5601 and the configured Base Path Alias is /test, you can access Kibana via https://xx.xx.xx.xx:5601/test from the public network.