It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.
The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Default profileedit
A profile to get you started and for backwards compatibility with existing deployments.
The default profile is suitable for search and general all-purpose workloads that don’t require more specialized resources. If this profile doesn’t solve your use cases, you can create new deployment templates.
Existing deployments that were created in an ECE version before 2.0 are switched to this profile automatically, if you edit their deployment configuration. The profile is fully backwards compatible and enables you to add Elastic Stack features such as machine learning and dedicated master nodes to existing deployments.
Included in this profile:
-
Elasticsearch:
-
Data nodes:
-
Hot data and content tier:
+ Starts at 1 GB memory x 1 availability zone. Uses the
data.defaultinstance configuration. - The warm data tier and cold data tier are optional but can be enabled when you have a scenario that would benefit from them. See Data tiers for more information.
-
Hot data and content tier:
+ Starts at 1 GB memory x 1 availability zone. Uses the
-
Master nodes: With three or fewer data nodes, master nodes are co-located with the data nodes. With more than three data nodes, one dedicated master node per availability zone is used. Uses the
masterinstance configuration.
-
-
Kibana: Starts at 1 GB memory x 1 availability zone. Uses the
kibanainstance configuration. -
Machine learning (ML): Disabled by default. The functionality is pre-wired into the profile, but you must explicitly enable it in the UI. Uses the
mlinstance configuration. -
Application Performance Monitoring (APM): Enabled by default. The functionality is pre-wired into the profile, but you must explicitly enable it in the UI. Uses the
apminstance configuration.
To use this profile effectively, you must tag your allocators and edit the default instance configurations, so that ECE knows where to host the Elastic Stack products that are part of your deployment.