This section describes how to create an Elasticsearch cluster in security mode.
Public IP address access and Kibana public access can be used only after security mode is enabled.
Node Type |
Number |
---|---|
ess |
ess: 1-32 |
ess, ess-master |
ess: 1-200 ess-master: an odd number ranging from 3 to 9 |
ess, ess-client |
ess: 1-32 ess-client: 1-32 |
ess, ess-cold |
ess: 1-32 ess-cold: 1-32 |
ess, ess-master, ess-client |
ess: 1-200 ess-master: an odd number ranging from 3 to 9 ess-client: 1-32 |
ess, ess-master, ess-cold |
ess: 1-200 ess-master: an odd number ranging from 3 to 9 ess-cold: 1-32 |
ess, ess-client, ess-cold |
ess: 1-32 ess-client: 1-32 ess-cold: 1-32 |
ess, ess-master, ess-client, ess-cold |
ess: 1-200 ess-master: an odd number ranging from 3 to 9 ess-client: 1-32 ess-cold: 1-32 |
Details about the four node types:
|
Alternatively, choose Clusters > Elasticsearch in the navigation tree on the left. Click Create Cluster in the upper right corner. The Create page is displayed.
Parameter |
Description |
---|---|
Region |
Select a region for the cluster from the drop-down list on the right. Currently, only eu-de and eu-nl are supported. |
AZ |
Select AZs associated with the cluster region. You can select a maximum of three AZs. For details, see Deploying a Cross-AZ Cluster. |
Parameter |
Description |
---|---|
Version |
Select a cluster version from the drop-down list box. |
Name |
Cluster name, which contains 4 to 32 characters. Only letters, numbers, hyphens (-), and underscores (_) are allowed and the value must start with a letter. NOTE:
After a cluster is created, you can modify the cluster name as required. Click the name of a cluster to be modified. On the displayed Basic Information page, click |
Parameter |
Description |
---|---|
Nodes |
Number of nodes in a cluster. Select a number from 1 to 32. You are advised to configure three or more nodes to ensure high availability of the cluster.
|
CPU Architecture |
Currently, support x86. The supported type is determined by the actual regional environment. |
Node Specifications |
Specifications of nodes in a cluster. You can select a specified specification based on your needs. Each cluster supports only one specification. After you select a flavor, the CPU and memory corresponding to the current specification are displayed below the parameter. For example, if you select css.medium.8, then 1 vCPUs | 8 GB will be displayed, indicating that the node flavor you select contains one vCPU and 8 GB memory. |
Node Storage Type |
In the current version, the following options are available: Common I/O, High I/O, and Ultra-high I/O. |
Node Storage Capacity |
Storage space. Its value varies with node specifications. The node storage capacity must be a multiple of 20. |
Disk Encryption |
If you select this option, the nodes in the cluster you create will use encrypted EVS disks to protect data. By default, this option is not selected. Note that you cannot modify this setting after the cluster is created. Therefore, exercise caution when performing the setting. After you select this option, you need to select an available key from the Key Name drop-down list. If no key is available, click Create/View Key to go to the KMS management console and create or modify a key. For details, see Creating a CMK. Enabling disk encryption has no impact on your operations on a cluster (such as accessing the cluster and importing data to the cluster). However, after you enable disk encryption, operation performance deteriorates by about 10%. NOTE:
|
Master node |
The master node manages all nodes in the cluster. If more than 20 nodes are required to store and analyze a large amount of data, you are advised to enable the master node to ensure cluster stability. Otherwise, you are advised to set only the Nodes parameter and use the nodes as both master and client nodes. After enabling the master node, specify Node Specifications, Nodes, and Node Storage Type. The value of Nodes must be an odd number equal to or greater than 3. Up to nine nodes are supported. The value of Node Storage Capacity is fixed. You can select a storage type based on your needs. |
Client node |
The client node allows clients to access clusters and analyze data. If more than 20 nodes are required to store and analyze a large amount of data, you are advised to enable the client node to ensure cluster stability. Otherwise, you are advised to set only the Nodes parameter and use the nodes as both master and client nodes. After enabling the client node, specify Node Specifications, Nodes and Node Storage Type. The value of Nodes ranges from 1 to 32. The value of Node Storage Capacity is fixed. You can select a storage type based on your needs. |
Cold data node |
The cold data node is used to store historical data, for which query responses can be returned in minutes. If you do not quire a quick query response, store historical data on cold data nodes to reduce costs. After enabling cold data node, configure Node Specifications, Nodes, Node Storage Type, and Node Storage Capacity. The value of Nodes ranges from 1 to 32. Select Node Storage Type and Node Storage Capacity as requirement. After the cold data node is enabled, CSS automatically adds cold and hot tags to related nodes. |
When creating a CSS cluster, you can bind an enterprise project to the cluster if you have enabled the enterprise project function. You can select an enterprise project created by the current user from the drop-down list on the right or click View Project Management to go to the Enterprise Project Management console and create a new project or view existing projects.
Parameter |
Description |
---|---|
VPC |
A VPC is a secure, isolated, and logical network environment. Select the target VPC. Click View VPC to enter the VPC management console and view the created VPC names and IDs. If no VPCs are available, create one. NOTE:
The VPC must contain CIDRs. Otherwise, cluster creation will fail. By default, a VPC will contain CIDRs. |
Subnet |
A subnet provides dedicated network resources that are isolated from other networks, improving network security. Select the target subnet. You can access the VPC management console to view the names and IDs of the existing subnets in the VPC. |
Security Group |
A security group implements access control for ECSs that have the same security protection requirements in a VPC. To view more details about the security group, click View Security Group. NOTE:
|
Security Mode |
After the security mode is enabled, communication will be encrypted and authentication required for the cluster.
|
HTTPS Access |
HTTPS access can be enabled only after the security mode of the cluster is enabled. After HTTPS access is enabled, communication is encrypted when you access the cluster. NOTE:
Security clusters use HTTPS for communication, which is much slower than non-security clusters that use HTTP for communication. If you want fast read performance and the permission provided by the security mode to isolate resources (such as indexes, documents, and fields), you can disable the HTTPS Access function. After HTTPS Access is disabled, HTTP protocol is used for cluster communication. In this case, data security cannot be ensured and public IP address cannot be used. |
Public IP Address |
If HTTPS Access is enabled, you can configure Public Network Access and obtain an IP address for public network access. This IP address can be used to access this security cluster through the public network. For details, see Accessing a Cluster from a Public Network. |
The cluster snapshot function is enabled by default. You can also disable this function as required. To store automatic snapshots in OBS, an agency will be created to access OBS. Additional cost will be incurred if snapshots are stored in standard storage.
Parameter |
Description |
---|---|
OBS bucket |
Select an OBS bucket for storing snapshots from the drop-down list box. You can also click Create Bucket on the right to create an OBS bucket. For details, see Creating a Bucket. The created or existing OBS bucket must meet the following requirements:
|
Backup Path |
Storage path of the snapshot in the OBS bucket. The backup path configuration rules are as follows:
|
IAM Agency |
IAM agency authorized by the current account to CSS access or maintain data stored in the OBS bucket. You can also click Create IAM Agency on the right to create an IAM agency. For details, see Creating an Agency. The created or existing IAM agency must meet the following requirements:
|
Snapshot Encryption |
Indicates whether to enable the snapshot encryption function. Enabling the snapshot encryption function ensures the security of your snapshot data. After the snapshot encryption function is enabled, select a key from the Key Name drop-down list. If no key is available, click Create/View Key to switch to the KMS management console to create or modify a key. For details, see Creating a CMK.
|
Parameter |
Description |
---|---|
Snapshot Name Prefix |
The snapshot name prefix contains 1 to 32 characters and must start with a lowercase letter. Only lowercase letters, digits, hyphens (-), and underscores (_) are allowed. A snapshot name consists of a snapshot name prefix and a timestamp, for example, snapshot-1566921603720. |
Time Zone |
Time zone for the backup time, which cannot be changed. Specify backup started time based on the time zone. |
Backup Start Time |
The time when the backup starts automatically every day. You can specify this parameter only in full hours, for example, 00:00 or 01:00. The value ranges from 00:00 to 23:00. Select a time from the drop-down list. |
Retention Period (days) |
The number of days that snapshots are retained in the OBS bucket. The value ranges from 1 to 90. You can specify this parameter as required. The system automatically deletes expired snapshots every hour at half past the hour. |
Parameter |
Description |
---|---|
VPC Endpoint Service |
After enabling this function, you can obtain a private domain name for accessing the cluster in the same VPC. For details, see Accessing a Cluster Using a VPC Endpoint. |
Kibana Public Access |
You can configure this parameter only when security mode is enabled for a cluster. After enabling this function, you can obtain a public IP address for accessing Kibana. For details, see Accessing a Cluster from a Kibana Public Network. |
Tag |
Adding tags to clusters can help you identify and manage your cluster resources. You can customize tags or use tags predefined by Tag Management Service (TMS). For details, see Managing Tags. |
If the cluster creation fails, create the cluster again.