：CreateServerGroup

The operation that you want to perform. Set the value to CreateServerGroup.

The type of the server group. Valid values:

• Instance: allows you to add servers of the Ecs, Ens, or Eci type. This is the default value.
• Ip: allows you to add servers by specifying IP addresses.

The name of the server group.

The name must be 2 to 128 characters in length and can contain letters, digits, periods (.), underscores (_), and hyphens (-). The name must start with a letter.

The protocol version. Valid values:

• ipv4: IPv4. This is the default value.
• DualStack: dual stack.

The protocol used to forward requests to the backend servers. Valid values:

• TCP: This is the default value.
• UDP
• TCPSSL

The ID of the VPC to which the server group belongs.

Specifies whether to enable all-port forwarding. Valid values:

• true: yes.
• false: no. This is the default value.

Specifies whether to enable connection draining. Valid values:

• true: yes.
• false: no. This is the default value.

The timeout period of connection draining. Unit: seconds.

Valid values: 10 to 900.

The scheduling algorithm. Valid values:

• Wrr: The weighted round-robin algorithm is used. Backend servers with higher weights receive more requests than backend servers with lower weights. This is the default value.
• rr: The round-robin algorithm is used. Requests are forwarded to backend servers in sequence.
• sch: Source IP hashing is used. Requests from the same source IP address are forwarded to the same backend server.
• tch: Four-element hashing is used. It specifies consistent hashing that is based on four factors: source IP address, destination IP address, source port, and destination port. Requests that contain the same information based on the four factors are forwarded to the same backend server.
• qch: QUIC ID hashing is used. Requests that contain the same QUIC ID are forwarded to the same backend server.

Specifies whether to enable client IP preservation. Valid values:

• true: yes.
• false: no. This is the default value.

Specifies whether to enable the health check feature. Valid values:

• true: yes. This is the default value.
• false: no.

The protocol that is used for health checks. Valid values: TCP (default) and HTTP.

The backend port that is used for health checks.

Valid values: 0 to 65535.

Default value: 0. If you set the value to 0, the port of a backend server is used for health checks.

The number of times that an unhealthy backend server must consecutively pass health checks before it is declared healthy. In this case, the health status is changed from fail to success.

Valid values: 2 to 10.

Default value: 2.

The number of times that a healthy backend server must consecutively fail health checks before it is declared unhealthy. In this case, the health status is changed from success to fail.

Valid values: 2 to 10.

Default value: 2.

The maximum timeout period of a health check response. Unit: seconds.

Valid values: 1 to 300.

Default value: 5.

The interval between two consecutive health checks. Unit: seconds.

Valid values: 5 to 50.

Default value: 10.

The domain name that is used for health checks. Valid values:

• $SERVER_IP: the private IP address of a backend server.
• domain: the domain name you want to use for health checks. The domain name must be 1 to 80 characters in length and can contain lowercase letters, digits, hyphens (-), and periods (.).

The path to which health check requests are sent.

The path must be 1 to 80 characters in length, and can contain only letters, digits, and the following special characters: - / . % ? # & =. It can also contain the following extended characters: _ ; ~ ! ( ) * [ ] @ $ ^ : ' , +. The path must start with a forward slash (/).

The HTTP status codes to return for health checks. Separate multiple HTTP status codes with commas (,).

Valid values: http_2xx (default), http_3xx, http_4xx, and http_5xx.

The HTTP method that is used for health checks. Valid values: GET (default) and HEAD.

The ID of the resource group to which the server group belongs.

Specifies whether to perform a dry run. Valid values:

• true: performs a dry run. The system checks the required parameters, request syntax, and limits. If the request fails the dry run, an error message is returned. If the request passes the dry run, the DryRunOperation error code is returned.
• false: performs a dry run and sends the request. If the request passes the dry run, a 2xx HTTP status code is returned and the operation is performed.

The client token that is used to ensure the idempotence of the request.

You can use the client to generate the value, but you must make sure that the value is unique among different requests. The token can contain only ASCII characters.

The ID of the region where the NLB instance is deployed.

You can call the DescribeRegions operation to query the most recent region list.

The ID of the request.

The ID of the server group.

The ID of the asynchronous task.