Elasticsearch Service default provider instance configurationsedit
Elasticsearch data nodes are available in these configurations:
- highio - Optimized for balanced RAM/vCPU/disk ratios and performance.
- highstorage - Optimized for cost effective storage.
- datafrozen - Optimized for frozen data storage, acts as a cache for the frozen tier.
- highcpu - Optimized for higher CPU performance compared to highio types.
- highmem - Optimized for lower cost with lower storage ratio.
The following table contains the specific hardware for each cloud provider.
| Instance configuration | Provider | Preferred Instance Type or Machine Configuration1 | Storage Type1 | Disk:Memory Ratio2 | vCPU/RAM Ratio |
|---|---|---|---|---|---|
AWS |
i3 |
NVMe |
30:1 |
0.137 |
|
Azure |
l32sv2 |
NVMe |
30:1 |
0.131 |
|
GCP |
n1 |
NVMe |
30:1 |
0.167 |
|
AWS |
d3 |
HDD |
190:1 |
0.133 |
|
AWS |
3d2 |
HDD |
160:1 |
0.138 |
|
Azure |
e16sv3 |
Standard Managed Disks (HDD) |
160:1 |
0.133 |
|
GCP |
n1 |
Standard persistent disks (HDD) |
160:1 |
0.172 |
|
AWS |
i3en |
NVMe |
41600:1 |
0.133 |
|
Azure |
lsv2 |
NVMe |
41600:1 |
0.133 |
|
GCP |
n2d |
SSD |
41600:1 |
0.133 |
|
AWS |
m5d |
NVMe |
8:1 |
0.264 |
|
AWS |
3m5 |
EBS |
8:1 |
0.267 |
|
Azure |
d64sv3 |
Standard SSD |
8:1 |
0.258 |
|
GCP |
n1 |
Local SSD |
8:1 |
0.244 |
|
AWS |
r5d |
NVMe |
2:1 |
0.130 |
|
AWS |
3r4 |
EBS |
2:1 |
0.136 |
|
Azure |
e32sv3 |
Standard SSD |
2:1 |
0.131 |
|
GCP |
n1 |
Local SSD |
2:1 |
0.169 |
Additional instancesedit
| Instance configuration | Provider | Preferred Instance Type or Machine Configuration1 | Storage Type1 | Disk:Memory Ratio2 | vCPU/RAM Ratio |
|---|---|---|---|---|---|
AWS |
r5d |
NVMe |
2:1 |
0.130 |
|
AWS |
3r4 |
EBS |
2:1 |
0.136 |
|
Azure |
e32sv3 |
Standard SSD |
2:1 |
0.131 |
|
GCP |
gcp.apm.1 |
Local SSD |
2:1 |
0.169 |
|
AWS |
m5d |
NVMe |
2:1 |
0.264 |
|
AWS |
3m5 |
EBS |
2:1 |
0.267 |
|
Azure |
d64sv3 |
Standard SSD |
2:1 |
0.258 |
|
GCP |
n1 |
Local SSD |
8:1 |
0.244 |
|
AWS |
r5d |
NVMe |
2:1 |
0.130 |
|
AWS |
3r4 |
EBS |
2:1 |
0.136 |
|
Azure |
e32sv3 |
Standard SSD |
2:1 |
0.131 |
|
GCP |
gcp.ccs.1 |
Local SSD |
2:1 |
0.169 |
|
AWS |
m5d |
NVMe |
2:1 |
0.264 |
|
AWS |
3m5 |
EBS |
2:1 |
0.267 |
|
Azure |
d64sv3 |
Standard SSD |
8:1 |
0.258 |
|
GCP |
n1 |
Local SSD |
8:1 |
0.244 |
|
AWS |
r5d |
NVMe |
2:1 |
0.130 |
|
AWS |
3r4 |
EBS |
2:1 |
0.136 |
|
Azure |
e32sv3 |
Standard SSD |
2:1 |
0.131 |
|
GCP |
gcp.kibana.1 |
Local SSD |
2:1 |
0.169 |
|
AWS |
r5d |
NVMe |
2:1 |
0.130 |
|
AWS |
3r4 |
EBS |
2:1 |
0.136 |
|
Azure |
e32sv3 |
Standard SSD |
2:1 |
0.131 |
|
GCP |
gcp.master.1 |
Local SSD |
2:1 |
0.169 |
|
AWS |
m5d |
NVMe |
2:1 |
0.264 |
|
AWS |
3m5 |
EBS |
2:1 |
0.267 |
|
Azure |
d64sv3 |
Standard SSD |
2:1 |
0.258 |
|
GCP |
n1 |
Local SSD |
2:1 |
0.244 |
1 Preferred instance and storage types are subject to provider availability. To learn more about our provider instances, see AWS, Azure, and GCP reference pages.
2 Ratios are estimations.
3 This configuration is now deprecated and not available for new deployments.
4 This is the amount of searchable storage in the frozen tier snapshot. The cached storage volume is a lower value than the searchable storage volume, ranging from about 30:1 to 90:1 depending on the hardware type.
JVM Heapedit
Memory sizes ensure efficient hardware utilization and might not scale to the power of two (n2). For sizes above 58, 60 or 64 GB (depending on instance type), we create multiple instances or nodes to ensure efficient JVM heap sizes. For example: If you provision a deployment with a 128 GB Elasticsearch cluster, two 64 GB nodes get created. To learn more about why we offer these JVM heap sizes, see Heap: Sizing and Swapping.