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
Whether you're planning to use Elastic's pre-built solutions or Serverless projects, build your own applications with {{es}}, or analyze your data using {{kib}} tools, you'll need to deploy Elastic first.
21
21
22
22
This page will help you understand your deployment options and choose the approach that best fits your needs.
23
23
24
24
## Core components
25
25
26
-
Every Elastic deployment requires Elasticsearch as its core data store and search/analytics engine.
27
-
Additionally, Kibana provides the user interface for all Elastic solutions and Serverless projects. It is required for most use cases, from data exploration to monitoring and security analysis.
26
+
Every Elastic deployment requires {{es}} as its core data store and search/analytics engine.
27
+
Additionally, {{kib}} provides the user interface for all Elastic solutions and Serverless projects. It is required for most use cases, from data exploration to monitoring and security analysis.
28
28
29
29
Your choice of deployment type determines how you'll set up and manage these core components, plus any additional components you need.
30
30
31
-
Elastic offers deployment options ranging from fully automated to fully self-managed.
32
-
33
31
:::{tip}
34
32
Learn more about the [{{stack}}](/get-started/the-stack.md) to understand the core and optional components of an Elastic deployment.
In {{serverless-full}}, you automatically get access to the latest versions of Elastic features and you don't need to manage version compatibility.
45
-
46
-
All other deployment types use stack versioning, where components are tested and versioned together to ensure compatibility. ECE and ECK have their own deployment versions, in addition to stack versioning.
40
+
### Who manages the infrastructure?
47
41
48
-
Consider this when choosing your deployment type:
42
+
#### Managed by Elastic
49
43
50
-
- Choose Serverless if you want automatic access to the latest features and don't want to manage version compatibility
51
-
- Choose other deployment types if you need more control over version management
44
+
If you want to focus on using Elastic products rather than managing infrastructure, choose:
52
45
53
-
:::{tip}
54
-
Learn more about [versioning and availability](/get-started/versioning-availability.md).
55
-
:::
46
+
-**Serverless**: Zero operational overhead, automatic scaling and updates, latest features
47
+
-**Cloud hosted**: Balance of control and managed operations, choice of resources and regions
56
48
57
-
##Choose your deployment path
49
+
#### Self-managed options
58
50
59
-
Your deployment choice determines how you'll set up and manage these components.
51
+
If you need to run Elastic on your infrastructure, choose between a fully self-managed deployment or using an orchestrator:
60
52
61
-
### Step 1: Who manages the infrastructure?
53
+
-**Fully self-managed**: Complete control and responsibility for your Elastic deployment
54
+
-**With orchestration**:
55
+
-**Elastic Cloud on Kubernetes (ECK)**: If you need Kubernetes-native orchestration
56
+
-**Elastic Cloud Enterprise (ECE)**: If you need a multi-tenant orchestration platform
62
57
63
-
#### Managed by Elastic
58
+
:::::{note}
59
+
:::{dropdown} About orchestration
64
60
65
-
If you want to focus on using Elastic products rather than managing infrastructure, choose:
61
+
An orchestrator automates the deployment and management of multiple Elastic clusters, handling tasks like scaling, upgrades, and monitoring.
66
62
67
-
-**Serverless**: Zero operational overhead, automatic scaling and updates, latest features
68
-
-**Cloud hosted**: Balance of control and managed operations, choice of resources and regions
63
+
Consider orchestration if you:
64
+
- Need to manage multiple Elastic clusters
65
+
- Want automated operations at scale
66
+
- Have a Kubernetes environment (ECK)
67
+
- Need to build a multi-tenant platform (ECE)
69
68
70
-
#### Self-managed with your infrastructure
69
+
Orchestrators manage the lifecycle of your Elastic deployments but don't change how the core products work. When using ECK or ECE:
70
+
- You'll still use the same Elasticsearch and Kibana features and configurations
71
+
- Most product documentation remains applicable
72
+
- You can add other Elastic products as needed
73
+
- The orchestrator handles operational tasks while you focus on using and configuring the products
71
74
72
-
If you need to run Elastic on your infrastructure, you have three options:
75
+
::::{tip}
76
+
Documentation will specify when certain features or configurations are not applicable to specific deployment types.
77
+
::::
78
+
:::
79
+
:::::
73
80
74
-
-**Basic self-managed**: Direct control over all aspects of deployment
75
-
-**Elastic Cloud on Kubernetes (ECK)**: Kubernetes-native orchestration
### Step 2: For self-managed - do you need orchestration?
83
+
In {{serverless-full}}, you automatically get access to the latest versions of Elastic features and you don't need to manage version compatibility.
79
84
80
-
If you chose self-managed, consider whether you need orchestration:
85
+
With other deployment types ({{ecloud}} Hosted, ECE, and ECK), you control which {{stack}} versions you deploy and when you upgrade. The ECE and ECK orchestrators themselves also receive regular version updates, independent of the {{stack}} versions they manage.
81
86
82
-
-**No orchestration needed**:
83
-
Choose basic self-managed deployment for full control and direct management
87
+
Consider this when choosing your deployment type:
84
88
85
-
-**Kubernetes environment**:
86
-
Use ECK for native Kubernetes orchestration and automated operations
89
+
-Choose Serverless if you want automatic access to the latest features and don't want to manage version compatibility
90
+
- Choose other deployment types if you need more control over version management
87
91
88
-
-**Multi-tenant platform**:
89
-
Use ECE to deploy {{ecloud}} on your own infrastructure
92
+
:::{tip}
93
+
Learn more about [versioning and availability](/get-started/versioning-availability.md).
94
+
:::
90
95
91
-
## Cost considerations
96
+
###Cost considerations
92
97
93
98
-**Serverless**: Pay for what you use
94
99
-**Cloud hosted**: Subscription-based with resource allocation
95
100
-**Self-managed options**: Infrastructure costs plus operational overhead mean a higher total cost of ownership (TCO)
101
+
102
+
:::::{tip}
103
+
For a detailed comparison of features and capabilities across deployment types, see the [Deployment comparison reference](./deploy/deployment-comparison.md).
This reference provides detailed comparisons of features and capabilities across Elastic's deployment options: self-managed deployments, Elastic Cloud Hosted, and Serverless. For a high-level overview of deployment types and guidance on choosing between them, see the [overview](../deploy.md).
0 commit comments