Compute optimized template

A template to run CPU-intensive workloads faster. Alternatively, you can use this template to run smaller workloads cost-effectively when you need less memory and storage, as CPU resources are assigned proportional to cluster size. A smaller, compute-optimized cluster can run a workload just as quickly as a larger cluster optimized for, say, storage.

Included with this template:

Amazon Web Services (AWS)
  • Elasticsearch:

    • Data nodes: Start at 8 GB memory x 2 availability zones. Hosted on AWS m5 instances.
    • Master nodes:

      Additional master-eligible node added when choosing 2 availability zones (to create a quorum of 3).

      When 1 AZ or 3 AZ are selected, the data nodes act as master-eligible node and there is no requirement for an additional master-eligible node.

      Configurations beyond 5 nodes per AZ can also spin up a dedicated master-eligible set of nodes (in 3 AZs always) to offload the data nodes. Hosted on AWS r4 instances.

  • Kibana: Starts at 1 GB memory x 1 availability zone. Hosted on AWS r4 instances.
  • Machine learning (ML): Disabled by default. The functionality is pre-wired into the template, but you must explicitly enable it in the UI. Hosted on AWS m5 instances.
  • APM (application performance monitoring): Enabled by default. The functionality is pre-wired into the template, but you must explicitly enable it in the UI. Hosted on AWS r4 instances.
Google Cloud Platform (GCP)
  • Elasticsearch:

    • Data nodes: Start at 8 GB memory x 2 availability zones. Hosted on custom CPU-optimized GCP instances.
    • Master nodes:

      Additional master-eligible node added when choosing 2 availability zones (to create a quorum of 3).

      When 1 AZ or 3 AZ are selected, the data nodes act as master-eligible node and there is no requirement for an additional master-eligible node.

      Configurations beyond 5 nodes per AZ can also spin up a dedicated master-eligible set of nodes (in 3 AZs always) to offload the data nodes. Hosted on custom memory-optimized GCP instances.

  • Kibana: Starts at 1 GB memory x 1 availability zone. Hosted on custom memory-optimized GCP instances.
  • Machine learning (ML): Disabled by default. The functionality is pre-wired into the template, but you must explicitly enable it in the UI. Hosted on custom CPU-optimized GCP instances.
  • APM (application performance monitoring): Enabled by default. The functionality is pre-wired into the template, but you must explicitly enable it in the UI. Hosted on custom memory-optimized GCP instances.
Microsoft Azure
  • Elasticsearch:

    • Data nodes: Start at 8 GB memory x 2 availability zones. Hosted on Azure D64sv3 instances.
    • Master nodes:

      Additional master-eligible node added when choosing 2 availability zones (to create a quorum of 3).

      When 1 AZ or 3 AZ are selected, the data nodes act as master-eligible node and there is no requirement for an additional master-eligible node.

      Configurations beyond 5 nodes per AZ can also spin up a dedicated master-eligible set of nodes (in 3 AZs always) to offload the data nodes. Hosted on Azure E32sv3 instances.

  • Kibana: Starts at 1 GB memory x 1 availability zone. Hosted on Azure E32sv3 instances.
  • Machine learning (ML): Disabled by default. The functionality is available in the template, but you must explicitly enable it in the UI. Hosted on Azure D64sv3 instances.
  • APM (application performance monitoring): The functionality is available in the template and is enabled by default (free tier 0.5GB). Hosted on Azure E32sv3 instances.