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
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/create-deployment.md
+85-12Lines changed: 85 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,22 +7,95 @@ mapped_urls:
7
7
8
8
# Create a deployment
9
9
10
-
% What needs to be done: Refine
10
+
An ECE deployment is a fully managed Elastic Stack environment running on {{ece}}. It includes {{es}}, {{kib}}, and optional features like Machine Learning, or an Integrations (Fleet & APM) Server.
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
13
14
-
% Scope notes: create then access. and then link to add data
14
+
In this section, you'll learn how to:
15
15
16
-
% Use migrated content from existing pages that map to this page:
On the **Create deployment** page, you can edit the basic settings or adjust advanced configurations. **Advanced settings** allow you to modify deployment parameters defined by the selected template, such as autoscaling, storage, memory, data tiers, and additional {{stack}} components.
30
+
31
+
2. Set a name for your deployment.
32
+
33
+
3. Select a deployment template.
34
+
35
+
::::{tip}
36
+
* Refer to [](./deployment-templates.md) for more information about deployment templates, including descriptions of the default system templates.
37
+
* If the system templates do not meet your requirements, you can [modify them](./ece-configuring-ece-configure-system-templates.md) or [create your own custom templates](../../../deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md).
38
+
::::
39
+
40
+
4. Choose your {{stack}} version. To manage available versions, refer to [](./manage-elastic-stack-versions.md).
41
+
42
+
5. Optionally, [use snapshots](../../tools/snapshot-and-restore/cloud-enterprise.md) to back up your data or [restore data from another deployment](../../tools/snapshot-and-restore/ece-restore-across-clusters.md).
43
+
44
+
::::{tip}
45
+
Restoring a snapshot can help with major version upgrades by creating a separate, non-production deployment where you can test, for example. Or, make life easier for your developers by providing them with a development environment that is populated with real data.
46
+
::::
47
+
48
+
6. Select **Advanced settings**, to configure your deployment for [autoscaling](../../autoscaling/ece-autoscaling.md), storage, memory, and data tiers. Check [Customize your deployment](../../../deploy-manage/deploy/cloud-enterprise/customize-deployment.md) for more details.
49
+
50
+
7. Select **Create deployment**. It takes a few minutes before your deployment gets created.
51
+
52
+
While waiting, you are prompted to save the admin credentials for your deployment which provides you with superuser access to Elasticsearch. Write down the password for the `elastic` user and keep it somewhere safe. These credentials also help you [add data using Kibana](../../../manage-data/ingest.md). If you need to refresh these credentials, you can [reset the password](../../../deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md).
53
+
54
+
8. Once the deployment is ready, select **Continue** to open the deployment’s main page.
55
+
56
+
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
+
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
+
## Next steps
92
+
93
+
Once you have created your deployment, consider the following activities:
94
+
95
+
* Connect your applications to your {{es}} cluster to start sending data.
96
+
*[Add data](../../../manage-data/ingest.md)
97
+
* Configure [users and roles](../../users-roles.md)
98
+
* TBD
99
+
From "here", you can start ingesting data or simply [try a sample data](../../../explore-analyze/index.md#gs-get-data-into-kibana) set to get started.
100
+
101
+
Check all other actions from [](./working-with-deployments.md).
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/working-with-deployments.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,3 +34,21 @@ The documentation team is working to combine content pulled from the following p
34
34
35
35
% from the post-install instructions
36
36
% * [Set up traffic filters](../../security/traffic-filtering.md) to restrict traffic to your deployment to only trusted IP addresses or VPCs.
37
+
38
+
39
+
TBD: where to put this:
40
+
41
+
## Other actions
42
+
43
+
From the deployment page you can also:
44
+
45
+
* Access to different feature sections like
46
+
*
47
+
48
+
**Kibana** page you can also:
49
+
50
+
* Terminate your Kibana instance, which stops it. The information is stored in your Elasticsearch cluster, so stopping and restarting should not risk your Kibana information.
51
+
* Restart it after stopping.
52
+
* Upgrade your Kibana instance version if it is out of sync with your Elasticsearch cluster.
53
+
* Delete to fully remove the instance, wipe it from the disk, and stop charges.
0 commit comments