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
* Maximize the hardware utilization for the various clusters.
21
22
* Centralize the management of multiple Elastic deployments across teams or geographies.
22
23
23
-
Refer to [](./cloud-enterprise/ece-architecture.md)and [Containerized design](./cloud-enterprise/ece-containerization.md)for details about the ECE platform architecture and technologies used.
24
+
Refer to [](./cloud-enterprise/ece-architecture.md) for details about the ECE platform architecture and the technologies used.
-**High availability & resilience**: Ensures uptime through multiple Availability Zones, data replication, and automated restore and snapshot.
30
+
-**Centralized monitoring & logging**: Provides insights into cluster performance, resource usage, and logs.
31
+
-**Single Sign-On (SSO) & role-based access aontrol (RBAC)**: Allows organizations to manage access and security policies.
32
+
-**API & UI management**: Offers a web interface and API to create and manage clusters easily.
32
33
-**Air-gapped installations**: Support for off-line installations.
33
-
-**Microservices**: All services are containerized through Docker. Refer to [](./ece-containerization.md) for more details.
34
-
35
-
## ECE features
36
-
37
-
* All services are containerized through Docker.
38
-
* High Availability through multiple Availability Zones.
39
-
* Deployment state coordination using ZooKeeper.
40
-
* Easy access for admins through the Cloud UI and API.
41
-
* Support for off-line installations.
42
-
* Automated restore and snapshot.
34
+
-**Microservices architecture**: All services are containerized through Docker.
43
35
44
36
Check the [glossary](https://www.elastic.co/guide/en/elastic-stack-glossary/current/terms.html) to get familiar with the terminology for ECE as well as other Elastic products and solutions.
45
37
46
-
% delete or keep. this wasn't part of the original content
47
-
%### Use cases
48
-
%
49
-
%- Organizations that need full control over their Elastic Stack while benefiting from cloud-like automation.
50
-
%- Enterprises managing multiple Elasticsearch clusters across different teams or environments.
51
-
%- Businesses looking for a self-hosted alternative to Elastic Cloud with centralized administration.
52
-
53
38
## Section overview
54
39
55
40
This section focuses on deploying ECE and orchestrating and configuring {{es}} clusters, also referred to as `deployments`.
56
41
57
-
In ECE, a deployment is a managed {{stack}} environment that provides users with an {{es}} cluster along with supporting components such as {{kib}} and other optional services like APM and Fleet.
42
+
In ECE, a deployment is a managed {{stack}} environment that provides users with an {{es}} cluster along with supporting components such as {{kib}} and other optional services like APM and {{fleet}}.
Now that you have Elastic Cloud Enterprise up and running, take a look at some of the additional features that you can configure:
12
15
13
16
*[System deployment configuration](system-deployments-configuration.md) - Best practices for ECE system deployments to ensure a highly available and resilient setup.
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/deploy-an-orchestrator.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
-
applies:
3
-
ece: all
2
+
applies_to:
3
+
deployment:
4
+
ece: all
4
5
---
5
6
# Deploy an orchestrator
6
7
@@ -32,10 +33,20 @@ This section provides step-by-step guidance on:
32
33
33
34
## Additional topics
34
35
35
-
Once ECE is deployed, you may need to configure security, manage snapshots, or perform maintenance tasks. Refer to the following sections for more details:
36
+
After deploying ECE platform, you may need to configure your own proxy certificates, security, snapshot repositories, or perform maintenance tasks. Refer to the following sections for more details:
36
37
37
38
*[Secure your ECE installation](../../security/secure-your-elastic-cloud-enterprise-installation.md)
38
39
*[Users and roles](../../users-roles/cloud-enterprise-orchestrator.md)
@@ -17,7 +19,6 @@ Elastic Cloud Enterprise has a service-oriented architecture that lets you:
17
19
:alt: Elastic Cloud Enterprise high level architecture
18
20
:::
19
21
20
-
21
22
## Control plane [ece_control_plane]
22
23
23
24
The *control plane* of ECE include the following management services:
@@ -67,3 +68,19 @@ Provide web and API access for administrators to manage and monitor the ECE inst
67
68
68
69
* Advertise the memory capacity of the underlying host machine to ZooKeeper so that the Constructor can make an informed decision on where to deploy.
69
70
71
+
## Services as Docker containers [ece-containerization]
72
+
73
+
Services are deployed as Docker containers, which simplifies the operational effort and makes it easy to provision similar environments for development and staging. Using Docker containers has the following advantages:
74
+
75
+
***Shares of resources**
76
+
77
+
Each cluster node is run within a Docker container to make sure that all of the nodes have access to a guaranteed share of host resources. This mitigates the *noisy neighbor effect* where one busy deployment can overwhelm the entire host. The CPU resources are relative to the size of the Elasticsearch cluster they get assigned to. For example, a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM.
78
+
79
+
***Better security**
80
+
81
+
On the assumption that any cluster can be compromised, containers are given no access to the platform. The same is true for the services: each service can read or write only those parts of the system state that are relevant to it. Even if some services are compromised, the attacker won’t get hold of the keys to the rest of them and will not compromise the whole platform.
82
+
83
+
***Secure communication through Stunnel**
84
+
85
+
Docker containers communicate securely with one another through Transport Layer Security, provided by [Stunnel](https://www.stunnel.org/) (as not all of the services or components support TLS natively). Tunneling all traffic between containers makes sure that it is not possible to eavesdrop, even when someone else has access to the underlying cloud or network infrastructure.
0 commit comments