You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kibana is an open source analytics and visualization platform designed to search, view, and interact with data stored in Elasticsearch indices.
10
+
11
+
::::{tip}
12
+
Most deployment templates include a Kibana instance, but if it wasn’t part of the initial deployment you can [](./customize-deployment.md) and add {{kib}}.
13
+
::::
14
+
15
+
To access Kibana:
16
+
17
+
1.[Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
18
+
2. On the **Deployments** page, select your deployment.
19
+
20
+
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
21
+
22
+
3. Under **Applications**, select the Kibana **Launch** link and wait for Kibana to open.
23
+
24
+
::::{note}
25
+
Both ports 443 and 9243 can be used to access Kibana. SSO only works with 9243 on older deployments, where you will see an option in the Cloud UI to migrate the default to port 443. In addition, any version upgrade will automatically migrate the default port to 443.
26
+
::::
27
+
28
+
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:
29
+
30
+
* Select **Login with Cloud**. You’ll need to log in with your Cloud account credentials and then you’ll be redirected to Kibana.
31
+
* Log in with the `elastic` superuser. The password was provided when you created your cluster or [can be reset](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-users.md).
32
+
* Log in with any users you created in Kibana already.
33
+
34
+
::::{tip}
35
+
On AWS and not able to access Kibana? [Check if you need to update your endpoint URL first](../../../troubleshoot/deployments/cloud-enterprise/common-issues.md#ece-aws-private-ip).
36
+
::::
37
+
38
+
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.
@@ -11,13 +9,6 @@ An ECE deployment is a fully managed Elastic Stack environment running on {{ece}
11
9
12
10
Each deployment is based on a [deployment template](./deployment-templates.md), which defines its resources, default topology, scaling policies, and available features. Deployments can be customized based on workload requirements, including autoscaling, snapshot settings, and security configurations.
13
11
14
-
In this section, you'll learn how to:
15
-
16
-
*[Create a deployment](#ece-create-deployment)
17
-
*[Access Kibana](#ece-access-kibana)
18
-
19
-
## Create a deployment [ece-create-deployment]
20
-
21
12
To create a deployment in ECE:
22
13
23
14
1. From the Cloud UI, select **Create deployment**.
@@ -55,42 +46,12 @@ To create a deployment in ECE:
55
46
56
47
After a deployment is spun up, you can scale the size and add other features; however, the instance configuration and computing ratios cannot be changed. If you need to change an existing deployment to another template, we recommend [migrating your data](../../../manage-data/migrate.md).
57
48
58
-
## Access Kibana [ece-access-kibana]
59
-
60
-
Kibana is an open source analytics and visualization platform designed to search, view, and interact with data stored in Elasticsearch indices.
61
-
62
-
::::{tip}
63
-
Most deployment templates include a Kibana instance, but if it wasn’t part of the initial deployment you can [](./customize-deployment.md) and add {{kib}}.
64
-
::::
65
-
66
-
To access Kibana:
67
-
68
-
1.[Log into the Cloud UI](../../../deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
69
-
2. On the **Deployments** page, select your deployment.
70
-
71
-
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
72
-
73
-
3. Under **Applications**, select the Kibana **Launch** link and wait for Kibana to open.
74
-
75
-
::::{note}
76
-
Both ports 443 and 9243 can be used to access Kibana. SSO only works with 9243 on older deployments, where you will see an option in the Cloud UI to migrate the default to port 443. In addition, any version upgrade will automatically migrate the default port to 443.
77
-
::::
78
-
79
-
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:
80
-
81
-
* Select **Login with Cloud**. You’ll need to log in with your Cloud account credentials and then you’ll be redirected to Kibana.
82
-
* Log in with the `elastic` superuser. The password was provided when you created your cluster or [can be reset](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-users.md).
83
-
* Log in with any users you created in Kibana already.
84
-
85
-
::::{tip}
86
-
On AWS and not able to access Kibana? [Check if you need to update your endpoint URL first](../../../troubleshoot/deployments/cloud-enterprise/common-issues.md#ece-aws-private-ip).
87
-
::::
88
-
89
-
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.
90
-
91
49
## Next steps
92
50
93
-
Once you have created your deployment, consider the following activities:
51
+
Once you have created your deployment, consider the following activities:
52
+
(TBD)
53
+
54
+
*[Access {{kib}}](./access-kibana.md)
94
55
95
56
* Connect your applications to your {{es}} cluster to start sending data.
0 commit comments