Last updated：2020-12-28 14:51:02
A cluster is the basic unit in which KES provides the managed Elasticsearch service. A cluster is also the main object for you to use and manage the Elasticsearch service. This topic describes how to create a KES cluster in the KES console.
Log in to the Kingsoft Cloud console and choose Data Analysis > Elasticsearch to access the KES console.
On the Cluster Management page, click Create Cluster.
Configure the cluster.
Billing Mode: You can select the Subscription, Pay-As-You-Go, Pay-By-Daily-Config (Trial), or Pay-By-Daily-Config billing mode.
Cluster Name: When you create a KES cluster, the system generates a default name based on the system timestamp. You can also enter a custom name for the KES cluster. The cluster name must be 1 to 25 characters in length and can contain digits, uppercase and lowercase letters, hyphens (-), and underscores (_).
Data Center: You can select the cn-beijing-6, cn-shanghai-2, or cn-guangzhou-1 region.
Availability Zone: You can select availability zone A, B, or C in the cn-beijing-6 region, availability zone A or B in the cn-shanghai-2 region, and availability zone A in the cn-guangzhou-1 region.
Product Version: You can select only Open-source Edition.
Version Number: You can select the Elasticsearch 5.6.16, 6.8.4, or 7.4.2 version.
Data Node: You can select the EBS, Local SSD, or EPC model. The minimum number of nodes is 3. If you do not configure master nodes for the cluster, the system automatically selects three data nodes as master nodes. The EPC model supports multiple nodes on a single instance. The default number of nodes on a single instance is equal to the memory capacity divided by 64. RAID1 and SRAID0 are supported.
Master Node: The default model is EBS. The number of nodes is 3, which cannot be changed. In a large-scale cluster, you can configure master nodes to enhance the cluster stability.
Coordinator Node: The default model is EBS. The minimum number of nodes is 2. In a large-scale cluster, you can configure coordinator nodes to relieve the load on data nodes, avoiding service unavailability due to contention of CPU, I/O, and memory resources.
Warm Node: You can select the EBS or Local SSD model. The minimum number of nodes is 2. If the cluster contains a large number of rarely accessed historical indexes, you can configure warm nodes to separate hot data from cold data.
Enable Internet Access: To use Kibana or the Elasticsearch-SQL plug-in, you need to associate an elastic IP address (EIP) with the cluster to enable Internet access. If you select the Pay-As-You-Go (Trial) billing mode, you cannot enable Internet access when you create the cluster. After the cluster is created, you can go to the cluster details page to associate an EIP.
Associate EIP: You can select an existing EIP, or go to the EIP console to create an EIP and then select it. Alternatively, you can select Create EIP. The system creates an EIP with a bandwidth of 1 Mbit/s for you when the system creates the cluster. The selected EIP must be in the same region as the cluster.
VPC: You can use any virtual private cloud (VPC) in the same region to create the cluster. If you have not created a VPC in the region, go to the VPC console to create a VPC, an endpoint subnet in the VPC, and a VPC subnet in the same availability zone as the cluster.
KEC Subnet/EPC Subnet: A VPC subnet is a network unit for managing Kingsoft Cloud Elastic Compute (KEC) instances in a VPC. You can use any VPC subnet in the same availability zone as the cluster to create the cluster.
Endpoint Subnet: An endpoint subnet can be used to create private connections between your VPC and other Kingsoft Cloud services. You must specify an endpoint subnet when you use KES. You can use any endpoint subnet in the VPC to create the cluster.
Project: Select the project to which the cluster belongs. After the cluster is created, you can go to the cluster list page, click Assign to Project, and select the project to which the cluster belongs.
Confirm the configurations, click Buy Now to go to the order page, and preview the cluster configurations. If the configurations do not meet your expectations, you can click Back to modify the configurations.
Automatic renewal is optional. Subscription clusters have a service period. After the service period expires, the clusters become unavailable. We recommend that you select Automatically Renew Resources on a Monthly Basis When Account Balance Is Sufficient for Subscription clusters.
Did you find the above information helpful?
Please give us your feedback.
Thank you for your feedback.