Server Load Balancer:CreateServerGroup

The backend port that is used for health checks.

Valid values: 0 to 65535.

The default value is 0, which specifies that the port of a backend server is used for health checks.

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

• true
• false

The domain name that is used for health checks. The domain name must meet the following requirements:

• The domain name must be 1 to 80 characters in length.
• The domain name can contain lowercase letters, digits, hyphens (-), and periods (.).
• The domain name must contain at least one period (.) but cannot start or end with a period (.).
• The rightmost domain label of the domain name can contain only letters, and cannot contain digits or hyphens (-).
• The domain name cannot start or end with a hyphen (-).

The HTTP status codes that are used to indicate whether the backend server passes the health check.

The version of the HTTP protocol. Valid values: HTTP1.0 and HTTP1.1. Default value: HTTP1.1.

The interval at which health checks are performed. Unit: seconds.

Valid values: 1 to 50.

Default value: 2.

The HTTP method that is used for health checks. Valid values:

• GET: If the length of a response exceeds 8 KB, the response is truncated. However, the health check result is not affected.
• POST: By default, gRPC health checks use the POST method.
• HEAD (default): By default, HTTP and HTTPS use the HEAD method.

The URL that is used for health checks.

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

The protocol that is used for health checks. Valid values:

• HTTP: HTTP health checks simulate browser behaviors by sending HEAD or GET requests to probe the availability of backend servers.
• HTTPS: HTTPS health checks simulate browser behaviors by sending HEAD or GET requests to probe the availability of backend servers. HTTPS provides higher security than HTTP because HTTPS supports data encryption.
• TCP: TCP health checks send TCP SYN packets to a backend server to check whether the port of the backend server is reachable.
• gRPC: gRPC health checks send POST or GET requests to a backend server to check whether the backend server is healthy.

The timeout period of a health check response. If a backend server does not respond within the specified timeout period, the backend server is declared unhealthy. Unit: seconds.

Valid values: 1 to 300.

Default value: 5.

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 changes from fail to success.

Valid values: 2 to 10.

Default value: 3.

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 changes from success to fail.

Valid values: 2 to 10.

Default value: 3.

The cookie that you want to configure for the server.

The cookie must be 1 to 200 characters in length, and can contain only ASCII letters and digits. It cannot contain commas (,), semicolons (;), or space characters. It cannot start with a dollar sign ($).

The maximum amount of time to wait before the session cookie expires. Unit: seconds.

Valid values: 1 to 86400.

Default value: 1000.

Specifies whether to enable session persistence. Valid values:

• true
• false

The method that is used to handle cookies. Valid values:

• Insert (default value): inserts a cookie. The first time a client accesses SLB, SLB inserts the SERVERID cookie into the HTTP or HTTPS response packet. Subsequent requests from the client that carry this cookie are forwarded to the same backend server as the first request.
• Server: rewrites a cookie. SLB rewrites the custom cookies in requests from a client. Subsequent requests from the client that carry the new cookie are forwarded to the same backend server as the first request.

The type of the parameter.

The parameter value for consistent hashing.

Specifies whether to enable connection draining. Valid values:

• true
• false (default)

The timeout period of connection draining.

Valid values: 0 to 900.

Default value: 300.

Specifies whether to enable slow starts. Valid values:

• true

• false(default)

The duration of a slow start. Valid values: 30 to 900. Default value: 30.