I/O optimized template

New to Elasticsearch or not sure yet what you need? This template is suitable for many search and general all-purpose workloads that don’t require more specialized resources. Your Elasticsearch data nodes are optimized for high I/O throughput, and the template is geared towards providing a balance of compute (CPU), memory, and storage resources.

Included with this template:

Amazon Web Services (AWS)
  • Elasticsearch:

    • Data nodes: Start at 1 GB memory x 1 availability zone. The default is 8 GB memory x 2 availability zones. Hosted on AWS i3 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 (free). Hosted on AWS r4 instances.
  • Machine learning (ML): Disabled by default. The functionality is available in the template, but you must explicitly enable it in the UI. 1GB of ML is free. 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. 0.5GB RAM is free. Hosted on AWS r4 instances.
Google Cloud Platform (GCP)
  • Elasticsearch:

    • Data nodes: Start at 1 GB memory x 1 availability zone. The default is 8 GB memory x 2 availability zones. Hosted on custom I/O-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 1 GB memory x 1 availability zone. Hosted on L32sv2 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-eliglble 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 pre-wired into the template, but you must explicitly enable it in the UI. Hosted on D64sv3 Azure 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 Azure E32sv3 instances.