This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Overview

Service Overview

Search Engine provides automated creation and configuration of the distributed search and analytics engines Elasticsearch and OpenSearch through a web-based console. Users can select a server type that matches the system configuration to set up a cluster, and it supports the data analysis and visualization tools Kibana and the OpenSearch dashboard.

Notice
  • Search Engine provides the Elasticsearch Enterprise version and the OpenSearch version.
  • Elasticsearch Enterprise’s software license uses a user-owned license (BYOL, Bring Your Own License), and software licensing policies in cloud environments must follow the vendor’s policies.

The Search Engine Cluster consists of multiple master nodes and data nodes. Data nodes can be installed from a minimum of one up to a maximum of ten, and are typically deployed with three or more. If a master node is not installed separately, the data nodes also perform the master node role, and up to ten can be installed. When master nodes are installed separately, up to 50 data nodes are possible.

Provided features

Search Engine provides the following features.

  • Auto Provisioning (Auto Provisioning): You can configure and set up Elasticsearch and OpenSearch clusters via the UI.
  • Operation Control Management: Provides functionality to control the status of running servers. In addition to starting and stopping the cluster, it can be restarted to apply configuration values.
  • Backup and Recovery: You can back up using the built-in backup feature, and you can restore to the point in time of the backup file.
  • Add Data Node: If cluster expansion is required, you can add nodes with the same specifications as the existing data nodes. Up to 10 nodes can be added within the cluster.
  • Visualization Tool Support: Provides data analysis and visualization tools, and supports Elasticsearch Kibana or OpenSearch dashboards.
  • Monitoring: CPU, memory, and cluster performance monitoring information can be accessed through the Cloud Monitoring service.

Component

Search Engine provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use them based on the scale of the service they wish to configure.

Engine version

The engine versions supported by Search Engine are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.

The EOS and EoTS dates may change according to the supplier’s policy, so please refer to the supplier’s license management policy page for details.

Notice

The next version of Search Engine is scheduled to be offered after March 2026. The actual service schedule may change.

  • OpenSearch version 3.4.0
Provided versionEoS DateEoTS Date
8.15.02027-01 (planned)2027-07-15
8.19.72027-01 (planned)2027-07-15
Table. Search Engine Elasticsearch Engine Version
Provided versionEoS DateEoTS Date
2.19.32027-01 (planned)2027-07-15
3.4.0TBDTBD
Table. Search Engine OpenSearch Engine Version

Server Type

The server types supported by Search Engine are as follows.

For detailed information about the server types provided by Search Engine, see Search Engine Server Types.

Standard se1v2m4
CategoryexampleDetailed description
Server typeStandardProvided server types
  • Standard: Standard configuration (vCPU, Memory) commonly used
  • High Capacity: Large-capacity server specifications of 24 vCores or more
Server specificationsse1Provided server specifications
  • se1: Standard specifications (vCPU, Memory) commonly used
  • seh2: High-capacity server specifications
    • Providing servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. Search Engine Server Type Components

Preliminary Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

Service CategoryserviceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
Table. Search Engine Pre-requisite Services

1 - Server Type

Search Engine server type

Search Engine provides server types composed of various combinations such as CPU, Memory, and Network Bandwidth. When creating a Search Engine, Elastic Search is installed according to the server type selected for the intended use.

The server types supported by Search Engine are as follows.

Standard ses1v2m4
Category
exampleDetailed description
Server typeStandardProvided server type classifications
  • Standard: Configured with commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large-capacity server specifications exceeding Standard
Server specificationsdb1Provided server type classification and generation
  • ses1: s means standard specification, and 1 indicates the generation
  • seh2: h means high-capacity server specification, and 2 indicates the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. Search Engine Server Type Format

ses1 server type

The ses1 server type of Search Engine is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardses1v1m21 vCore2 GBUp to 10 Gbps
Standardses1v2m82 vCore8 GBUp to 10 Gbps
Standardses1v2m162 vCore16 GBUp to 10 Gbps
Standardses1v2m242 vCore24 GBUp to 10 Gbps
Standardses1v2m322 vCore32 GBUp to 10 Gbps
Standardses1v4m84 vCore8 GBUp to 10 Gbps
Standardses1v4m164 vCore16 GBUp to 10 Gbps
Standardses1v4m324 vCore32 GBUp to 10 Gbps
Standardses1v4m484 vCore48 GBUp to 10 Gbps
Standardses1v4m644 vCore64 GBUp to 10 Gbps
Standardses1v6m126 vCore12 GBUp to 10 Gbps
Standardses1v6m246 vCore24 GBUp to 10 Gbps
Standardses1v6m486 vCore48 GBUp to 10 Gbps
Standardses1v6m726 vCore72 GBUp to 10 Gbps
Standardses1v6m966 vCore96 GBUp to 10 Gbps
Standardses1v8m168 vCore16 GBUp to 10 Gbps
Standardses1v8m328 vCore32 GBUp to 10 Gbps
Standardses1v8m648 vCore64 GBUp to 10 Gbps
Standardses1v8m968 vCore96 GBUp to 10 Gbps
Standardses1v8m1288 vCore128 GBUp to 10 Gbps
Standardses1v10m2010 vCore20 GBUp to 10 Gbps
Standardses1v10m4010 vCore40 GBUp to 10 Gbps
Standardses1v10m8010 vCore80 GBUp to 10 Gbps
Standardses1v10m12010 vCore120 GBUp to 10 Gbps
Standardses1v10m16010 vCore160 GBUp to 10 Gbps
Standardses1v12m2412 vCore24 GBUp to 12.5 Gbps
Standardses1v12m4812 vCore48 GBMaximum 12.5 Gbps
Standardses1v12m9612 vCore96 GBUp to 12.5 Gbps
Standardses1v12m14412 vCore144 GBUp to 12.5 Gbps
Standardses1v12m19212 vCore192 GBUp to 12.5 Gbps
Standardses1v14m2814 vCore28 GBUp to 12.5 Gbps
Standardses1v14m5614 vCore56 GBUp to 12.5 Gbps
Standardses1v14m11214 vCore112 GBUp to 12.5 Gbps
Standardses1v14m16814 vCore168 GBUp to 12.5 Gbps
Standardses1v14m22414 vCore224 GBUp to 12.5 Gbps
Standardses1v16m3216 vCore32 GBUp to 12.5 Gbps
Standardses1v16m6416 vCore64 GBMaximum 12.5 Gbps
Standardses1v16m12816 vCore128 GBUp to 12.5 Gbps
Standardses1v16m19216 vCore192 GBUp to 12.5 Gbps
Standardses1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. Search Engine Server Type Specifications - ses1 Server Type

ses2 server type

The ses1 server type of Search Engine is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typeCPU vCoreMemoryNetwork Bandwidth(Gbps)
Standardses2v2m42 vCore4 GBUp to 10 Gbps
Standardses2v2m82 vCore8 GBUp to 10 Gbps
Standardses2v2m162 vCore16 GBUp to 10 Gbps
Standardses2v2m242 vCore24 GBUp to 10 Gbps
Standardses2v2m322 vCore32 GBUp to 10 Gbps
Standardses2v4m84 vCore8 GBUp to 10 Gbps
Standardses2v4m164 vCore16 GBUp to 10 Gbps
Standardses2v4m324 vCore32 GBUp to 10 Gbps
Standardses2v4m484 vCore48 GBUp to 10 Gbps
Standardses2v4m644 vCore64 GBUp to 10 Gbps
Standardses2v6m126 vCore12 GBUp to 10 Gbps
Standardses2v6m246 vCore24 GBUp to 10 Gbps
Standardses2v6m486 vCore48 GBUp to 10 Gbps
Standardses2v6m726 vCore72 GBUp to 10 Gbps
Standardses2v6m966 vCore96 GBUp to 10 Gbps
Standardses2v8m168 vCore16 GBUp to 10 Gbps
Standardses2v8m328 vCore32 GBUp to 10 Gbps
Standardses2v8m648 vCore64 GBUp to 10 Gbps
Standardses2v8m968 vCore96 GBUp to 10 Gbps
Standardses2v8m1288 vCore128 GBUp to 10 Gbps
Standardses2v10m2010 vCore20 GBUp to 10 Gbps
Standardses2v10m4010 vCore40 GBUp to 10 Gbps
Standardses2v10m8010 vCore80 GBUp to 10 Gbps
Standardses2v10m12010 vCore120 GBUp to 10 Gbps
Standardses2v10m16010 vCore160 GBUp to 10 Gbps
Standardses2v12m2412 vCore24 GBUp to 12.5 Gbps
Standardses2v12m4812 vCore48 GBUp to 12.5 Gbps
Standardses2v12m9612 vCore96 GBUp to 12.5 Gbps
Standardses2v12m14412 vCore144 GBUp to 12.5 Gbps
Standardses2v12m19212 vCore192 GBUp to 12.5 Gbps
Standardses2v14m2814 vCore28 GBUp to 12.5 Gbps
Standardses2v14m5614 vCore56 GBUp to 12.5 Gbps
Standardses2v14m11214 vCore112 GBUp to 12.5 Gbps
Standardses2v14m16814 vCore168 GBUp to 12.5 Gbps
Standardses2v14m22414 vCore224 GBUp to 12.5 Gbps
Standardses2v16m3216 vCore32 GBUp to 12.5 Gbps
Standardses2v16m6416 vCore64 GBUp to 12.5 Gbps
Standardses2v16m12816 vCore128 GBUp to 12.5 Gbps
Standardses2v16m19216 vCore192 GBUp to 12.5 Gbps
Standardses2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. Search Engine Server Type Specifications - ses2 Server Type

seh2 server type

The seh2 server type of Search Engine is offered with high-capacity server specifications and is suitable for database workloads for large-scale data processing.

  • Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
  • Supports up to 72 vCPUs and 288 GB of memory
  • Networking speed up to 25 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacityseh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacityseh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacityseh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacityseh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacityseh2v32m6432 vCore64 GBMaximum 25 Gbps
High Capacityseh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacityseh2v32m25632 vCore256 GBMaximum 25 Gbps
High Capacityseh2v48m9648 vCore96 GBMaximum 25 Gbps
High Capacityseh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacityseh2v64m12864 vCore128 GBMaximum 25 Gbps
High Capacityseh2v64m25664 vCore256 GBMaximum 25 Gbps
High Capacityseh2v72m14472 vCore144 GBMaximum 25 Gbps
High Capacityseh2v72m28872 vCore288 GBMaximum 25 Gbps
Table. Search Engine Server Type Specifications - seh2 Server Type

2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Notice on Applying Monitoring Service by Resource

    • New Resources: Resources created after the service improvement work in July 2026 are monitored by default using the ServiceWatch service.
    • Existing resources: After the service improvement work in September 2026 We provide monitoring concurrently through Cloud Monitoring and ServiceWatch services.
    • During the parallel operation period, we must prepare for the Servicewatch transition. *
      Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (e.g. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch is available in the ServiceWatch Overview.

Search Engine Monitoring Metrics

The table below shows the performance monitoring metrics for Event Streams that can be viewed through Cloud Monitoring. For detailed Cloud Monitoring usage, refer to the Cloud Monitoring guide.

Refer to the Virtual Server Monitoring Metrics guide for the Search Engine server monitoring metrics.

Performance itemsDetailed descriptionunit
Disk Usagedatadir usageMB
Documents [Deleted]Total number of deleted documentscnt
Documents [Existing]Total number of existing documentscnt
Filesystem Bytes [Available]Available file systemsbytes
Filesystem Bytes [Free]Available file systembytes
Filesystem Bytes [Total]Total file systembytes
Instance Status [PID]Elasticsearch process PIDPID
JVM Heap Used [Init]Heap init used by JVM (bytes)bytes
JVM Heap Used [MAX]Heap max used by JVM (bytes)bytes
JVM Non Heap Used [Init]init (bytes) outside the heap used by the JVMbytes
JVM Non Heap Used [MAX]max (bytes) other than the heap used by the JVMbytes
Kibana ConnectionsKibana connectioncnt
Kibana Memory Heap Allocated [Limit]Maximum heap size allocated to a Node.js process (bytes)bytes
Kibana Memory Heap Allocated [Total]Maximum heap size allocated to a Node.js process (bytes)bytes
Kibana Memory Heap UsedMaximum heap size allocated to a Node.js process (bytes)bytes
Kibana Process UptimeKibana processms
Kibana Requests [Disconnected]Request count metriccnt
Kibana Requests [Total]Request count metriccnt
Kibana Response Time [Avg]Response time metricms
Kibana Response Time [MAX]Response time metricms
Kibana Status [PID]Kibana process PIDPID
License Expiry Date [ms]License expiration date [milisecond]ms
License StatusLicense statusstatus
License TypeLicense typetype
Queue TimeQueue timems
SegmentsTotal number of segmentscnt
Segments BytesTotal segment size (bytes)bytes
ShardsCluster shard countcnt
Store BytesTotal storage size (bytes)bytes
Table. Search Engine Monitoring Metrics