OpenSearch versions and configurations
Versions
OpenSearch version 2.18 is supported. OpenSearch is distributed under the Apache 2.0 license.
Node group configurations
An OpenSearch cloud database cluster consists of groups of nodes. All nodes in a group have the same configuration — number of vCPUs, RAM and disk size. The configurations are divided into lineages. The available lanes and lane configurations depend on the role of the node group.
When selecting a configuration, consider that about 5 GB of disk space in all configurations is reserved for the operating system, service components, and log storage. The rest of the disk space is available for databases.
The configuration can be selected when creating an OpenSearch cloud database cluster. After the cluster is created, you can change the configuration of the node group — scale the node group.
Configuration lines
The available node configurations are divided into ranges. The selected line of configurations determines the disks used.
The ratio of resources in line configurations can be:
To see the availability of configuration lineups in the regions, see the Cloud Databases availability matrix.
Standard
The ruler is only available for node groups with Manager and Data roles — see the Node Groups instructions for more information on roles.
A line of fixed configurations with local disk and balanced vCPU:RAM ratio, suitable for most DBMSs. We recommend using this lineup if you do not know the load profile.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. See the Processors table to view the processor frequencies of the different configuration lines.
See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
CPU
The ruler is only available for node groups with Manager and Data roles — see the Node Groups instructions for more information on roles.
A line of fixed configurations with local disk and balanced vCPU:RAM ratio. Suitable for workload profiles that are computationally demanding. For example, if the database is running analytic queries, multiple nested queries, or data encryption. One way to determine such a load profile is to monitor the Load Average metric, which shows the average system load over one, five, or 15 minutes.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. See the Processors table to view the processor frequencies of the different configuration lines.
See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
Memory
The ruler is only available for node groups with Manager and Data roles — see the Node Groups instructions for more information on roles.
A line of fixed configurations with local disk and balanced vCPU:RAM ratio. Suitable for workload profiles that are cache-intensive. For example, if the database runs multiple, infrequent queries on different parts of tables. One way to determine such a load profile is to monitor the Cash_hit_ratio metric, which shows the percentage of data in a query that is read from the cache.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. See the Processors table to view the processor frequencies of the different configuration lines.
See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
HighFreq
A line of fixed configurations with a balanced vCPU:RAM ratio.
High-performance Enterprise-level equipment is used:
- Intel® Xeon® Gold 6354 processors (in pools ru-9, ru-2, ru-8, ke-1) or AMD EPYC 9474F (in pools ru-3, ru-7, uz-1). To see the frequency of processors in different configuration lines see the Processors table;
- RAM ECC Reg 3.2 GHz (in pools ru-9, ru-2, ru-8, ke-1) or RAM DDR5 ECC Reg 4.8 GHz (in pools ru-3, ru-7, uz-1);
- SSD NVMe disks with higher performance. See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
Flex
A line of arbitrary configurations with local or network disk, in which you can choose the resource ratio.
To see information about the disks, see the Disks manual.
See the Performance and Throughput table to see the performance and throughput of the drives in the different product lines.
Intel® Xeon® Scalable or AMD EPYC™ processors are used. See the Processors table to view the processor frequencies of the different configuration lines.
To see the availability of configurations in the regions, see the Cloud Databases availability matrix.
Local disk
Network disk
* If there are more than 8 vCPUs in the configuration, the vCPU:RAM ratio must be at least 1:4. For example, 10 vCPUs require at least 40 GB of RAM.
** If the configuration has more than 8 vCPUs, the vCPU:Local Disk ratio must be at least 1:32. For example, 10 vCPUs require a disk size of at least 320 GB.
If the configurations are not suitable, you can order your own configuration. Create a ticket and specify the resource ratio:
- vCPU:RAM — at least 1:4;
- vCPU:RAM:Local disk — at least 1:4:32.
Processors
Configuration lines differ in the available processors. Processor frequency affects the speed of processing user requests, performing complex algorithms and data operations. When the cloud server load is 100%, the processor is running Turbo Boost technology. Since the processor is emulated, a lower frequency will be displayed during testing.
To see the availability of configuration lineups in the regions, see the Cloud Databases availability matrix.