Creating a Logstash Cluster

Prerequisites

You have planned the Logstash clusters that need to be created by following the instructions in Logstash Cluster Planning Suggestions.

Creating a Cluster

1. Log in to the CSS management console.
2. On the Dashboard page, click Create Cluster in the upper right corner. The Create Cluster page is displayed.

   Alternatively, choose Clusters > Logstash in the navigation tree on the left. Click Create Cluster in the upper right corner.

3. On the Basic Configuration page, configure basic information and resources for the Logstash cluster.

   Table 1 Basic configuration of the Logstash cluster

   Parameter	Description
   Region	Select the region where the cluster is located. ECSs in different regions cannot communicate with each other over an intranet. For lower network latency and quicker resource access, select the nearest region.
   AZ	Select AZs associated with the cluster region. A maximum of two AZs can be configured. For details about the use of multiple AZs, see Suggestions on Multi-AZ Deployment.
   Type	Select Logstash.
   Version	Select a cluster version from the drop-down list.
   Name	User-defined cluster name. The cluster name must start with a letter and can contain 4 to 32 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
   Cluster Description	Add a description for the cluster for easy recognition. The value can contain 0 to 128 characters.
   Nodes	Number of nodes in the cluster, in the range 1 to 100.
   CPU Architecture	x86. The supported types depend on the actual regional environment.
   Node Specifications	Specifications of nodes in the cluster. You can select a node flavor based on your needs. Each cluster supports only one specification. For details, see ECS Types.
   Node Storage Type	Options include Common I/O, High I/O, Ultra-high I/O. NOTE: If the type of storage in use is not supported, the storage type is not displayed.
   Node Storage Capacity	It can only be set to 40 GB for a Logstash cluster.
   Enterprise Project	When creating a CSS cluster, you can bind an enterprise project to the cluster if you have enabled the enterprise project function. Select an enterprise project from the Enterprise Project drop-down list, or click View Enterprise Project to go to the Enterprise Project Management Service page and check existing enterprise projects.

4. Click Next: Network.
5. On the Network page, configure the network and security group settings for the Logstash cluster.

   Table 2 Parameter description

   Parameter	Description
   VPC	Specify a VPC to isolate the cluster's network. Click View VPC to go to the VPC management console and check the created VPCs. If no VPC is available, contact the CSS administrator to create a new VPC. For details, see Creating a VPC with a Subnet. NOTE: The VPC must contain CIDRs. Otherwise, cluster creation will fail. By default, a created VPC contains CIDRs.
   Subnet	A subnet provides dedicated network resources that are isolated from other networks, improving network security. Select a subnet needed by the cluster in the current VPC. If no existing subnets meet your requirements, click Create Subnet to create a new subnet. For details, see Creating a VPC with a Subnet.
   Security Group	A security group serves as a virtual firewall that provides access control policies for clusters. Select a security group for the cluster. Click View Security Group to go to the security group list, where you can view details about security groups. NOTE: To enable cluster access, ensure that port 9600 is allowed by the security group.

6. Click Next: Confirm Configuration. Confirm the settings, and click Create Now to create the cluster.
7. Return to the cluster list and check the newly created cluster. If the cluster is created successfully, Cluster Status changes to Available. Cluster creation time depends on the number of nodes. Typically, this process takes less than 60 minutes, though clusters with a large number of nodes may require additional time.

   If cluster creation fails, try creating the cluster again by rectifying the errors returned.