Imply Hybrid overview
Imply Hybrid (formerly Imply Cloud) gives you the easiest way to get started and grow with Imply.
With Imply Hybrid, Imply is deployed completely within your own AWS account, using a dedicated virtual private network (VPC). This gives you full control over your machines and your data. Imply hosts the control plane (for example, Imply Manager) for your cluster in a separate VPC within Imply's account. The VPC created in your AWS account is linked through a peering connection with the Manager VPC in Imply's account.
More information
The Imply Manager is the central administration point for your Imply Hybrid deployment. You can use it to create and configure Imply clusters. For more information on Imply Manager, see Using Imply Manager.
For more information about security, see Imply Hybrid security.
Imply Hybrid instance types
This section lists the instance types available for Imply cluster server instances, by node type. For more information about machine sizing, see planning.
Keep in mind that not every instance type is available in every region.
For more information about the instance types, see the AWS documentation on instance types.
Master nodes
Node type | vCPU | RAM | Disk space | Note |
---|---|---|---|---|
t2.small | 1 vCpu | 2 GB RAM | 8 GB disk | not recommended for production |
m4.large | 2 vCpu | 8 GB RAM | 16 GB disk | |
m5.large | 2 vCpu | 8 GB RAM | 16 GB disk | |
m5.xlarge | 4 vCpu | 16 GB RAM | 24 GB disk | |
m4.2xlarge | 8 vCpu | 32 GB RAM | 40 GB disk | |
m5.2xlarge | 8 vCpu | 32 GB RAM | 40 GB disk | |
m4.4xlarge | 16 vCpu | 64 GB RAM | 70 GB disk | |
m5.4xlarge | 16 vCpu | 64 GB RAM | 70 GB disk | |
r5.large | 2 vCpu | 16 GB RAM | 24 GB disk | |
r5.xlarge | 4 vCpu | 32 GB RAM | 40 GB disk | |
r5.2xlarge | 8 vCpu | 64 GB RAM | 70 GB disk |
Query nodes
Node type | vCPU | RAM | Disk space | Note |
---|---|---|---|---|
t2.small | 1 vCpu | 2 GB RAM | 8 GB disk | not recommended for production |
m4.large | 2 vCpu | 8 GB RAM | 12 GB disk | |
m4.4xlarge | 16 vCpu | 64 GB RAM | 25 GB disk | |
m5.large | 2 vCpu | 8 GB RAM | 12 GB disk | |
m5d.large | 2 vCpu | 8 GB RAM | 75 GB disk | |
m5.xlarge | 4 vCpu | 16 GB RAM | 20 GB disk | |
m5d.xlarge | 4 vCpu | 16 GB RAM | 150 GB disk | |
c5.large | 2 vCpu | 4 GB RAM | 12 GB disk | |
c5.xlarge | 4 vCpu | 8 GB RAM | 12 GB disk | |
c5.2xlarge | 8 vCpu | 16 GB RAM | 16 GB disk | |
c5.4xlarge | 16 vCpu | 32 GB RAM | 20 GB disk | |
c5.9xlarge | 36 vCpu | 72 GB RAM | 36 GB disk |
Data nodes
Node type | vCPU | RAM | Disk space | Note |
---|---|---|---|---|
t2.small | 1 vCpu | 2 GB RAM | 20 GB disk | not recommended for production |
m4.large | 2 vCpu | 8 GB RAM | 60 GB disk | |
m5.large | 2 vCpu | 8 GB RAM | 60 GB disk | |
m5d.large | 2 vCpu | 8 GB RAM | 75 GB disk | |
m5d.xlarge | 4 vCpu | 16 GB RAM | 150 GB disk | |
m5d.2xlarge | 8 vCpu | 32 GB RAM | 300 GB disk | |
m5d.4xlarge | 16 vCpu | 64 GB RAM | 600 GB disk | |
m5d.8xlarge | 32 vCpu | 128 GB RAM | 1200 GB disk | |
m5d.16xlarge | 64 vCpu | 256 GB RAM | 2400 GB disk | |
m5ad.8xlarge | 32 vCpu | 128 GB RAM | 1200 GB disk | |
r4.2xlarge | 8 vCpu | 61 GB RAM | 140 GB disk | high memory |
r5d.2xlarge | 8 vCpu | 64 GB RAM | 300 GB disk | high memory |
r5d.4xlarge | 16 vCpu | 128 GB RAM | 600 GB disk | high memory |
r5d.24xlarge | 96 vCpu | 768 GB RAM | 3600 GB disk | high memory |
r5d.metal | 96 vCpu | 768 GB RAM | 3600 GB disk | high memory |
i3.xlarge | 4 vCpu | 31 GB RAM | 950 GB disk | large disk |
i3.2xlarge | 8 vCpu | 61 GB RAM | 1900 GB disk | large disk |
i3.4xlarge | 16 vCpu | 122 GB RAM | 3800 GB disk | very large disk |
i3.8xlarge | 32 vCpu | 244 GB RAM | 7600 GB disk | very large disk |
i3.metal | 72 vCpu | 512 GB RAM | 15200 GB disk | very large disk |
i3en.2xlarge | 8 vCpu | 64 GB RAM | 5000 GB disk | very large disk |
i3en.3xlarge | 12 vCpu | 96 GB RAM | 7500 GB disk | very large disk |
i3en.6xlarge | 24 vCpu | 192 GB RAM | 15000 GB disk | very large disk |
i3en.12xlarge | 48 vCpu | 384 GB RAM | 30000 GB disk | very large disk |
c5.4xlarge | 16 vCpu | 32 GB RAM | 130 GB disk | high CPU |
c5d.4xlarge | 16 vCpu | 32 GB RAM | 400 GB disk | high CPU |
c5.9xlarge | 36 vCpu | 72 GB RAM | 300 GB disk | very high CPU |
c5d.9xlarge | 36 vCpu | 72 GB RAM | 900 GB disk | very high CPU |
c5ad.2xlarge | 8 vCpu | 16 GB RAM | 300 GB disk | high CPU |
c5ad.4xlarge | 16 vCpu | 32 GB RAM | 600 GB disk | high CPU |
c5ad.8xlarge | 32 vCpu | 64 GB RAM | 1200 GB disk | very high CPU |
m6id.large | 2 vCpu | 8 GB RAM | 118 GB disk | |
m6id.xlarge | 4 vCpu | 16 GB RAM | 237 GB disk | |
m6id.2xlarge | 8 vCpu | 32 GB RAM | 474 GB disk | |
m6id.4xlarge | 16 vCpu | 64 GB RAM | 950 GB disk | |
m6id.8xlarge | 32 vCpu | 128 GB RAM | 1900 GB disk | |
m6id.16xlarge | 64 vCpu | 256 GB RAM | 3800 GB disk |
Imply Hybrid AWS regions
An Imply account is associated with a single AWS region, and all Imply and related components must reside in that region.
Imply Hybrid supports the following AWS regions:
- ap-south-1 (Mumbai)
- ap-southeast-1 (Singapore)
- ap-southeast-2 (Sydney)
- ap-northeast-1 (Tokyo)
- ap-northeast-2 (Seoul)
- ca-central-1 (Central Canada)
- eu-central-1 (Frankfurt)
- eu-west-1 (Ireland)
- eu-west-2 (London)
- us-east-1 (N Virginia)
- us-east-2 (Ohio)
- us-west-1 (N California)
- us-west-2 (Oregon)