All Products
Search
Document Center

Server Load Balancer:CreateVServerGroup

Last Updated:Mar 14, 2024

Creates a server group and adds backend servers to the server group.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
slb:CreateVServerGroupWRITE
  • instance
    acs:ecs:{#regionId}:{#accountId}:instance/{#instanceId}
  • loadbalancer
    acs:slb:{#regionId}:{#accountId}:loadbalancer/{#loadbalancerId}
  • slb:tag
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

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

cn-hangzhou
LoadBalancerIdstringYes

The ID of the Server Load Balancer (SLB) instance.

lb-bp1qjwo61pqz3ahl******
VServerGroupNamestringNo

The name of the vServer group.

The name must be 1 to 80 characters in length, and can contain letters, digits, hyphens (-), forward slashes (/), periods (.),and underscores (_).

Group1
BackendServersstringNo

The list of backend servers to be added.

The value of this parameter must be a STRING list in the JSON format. You can specify up to 20 elements in each request.

  • ServerId: Required. Specify the ID of an Elastic Compute Service (ECS) instance or an Elastic Network Interface (ENI). This parameter must be of the STRING type.

  • Port: Required. Specify the port that is used by the backend server. This parameter must be of the INTEGER type. Valid values: 1 to 65535.

  • Weight: Required. Specify the weight of the backend server. This parameter must be of the INTEGER type. Valid values: 0 to 100.

  • Description: Optional. Specify the description of the backend server. This parameter must be of the STRING type. The description must be 1 to 80 characters in length, and can contain letters, digits, hyphens (-), forward slashes (/), periods (.),and underscores (_).

  • Type: Specify the type of the backend server. This parameter must be of the STRING type. Valid values:

    • ecs: an ECS instance. This is the default value.
    • eni: an ENI.
  • ServerIp: The IP address of the ECS instance or ENI.

Examples:

  • ECS instance: [{ "ServerId": "i-xxxxxxxxx", "Weight": "100", "Type": "ecs", "Port": "80", "Description": "test-112" }].
  • ENI: [{ "ServerId": "eni-xxxxxxxxx", "Weight": "100", "Type": "eni", "ServerIp": "192.168.**.**", "Port":"80","Description":"test-112" }]
  • ENI with multiple IP addresses: [{ "ServerId": "eni-xxxxxxxxx", "Weight": "100", "Type": "eni", "ServerIp": "192.168.**.**", "Port":"80","Description":"test-112" },{ "ServerId": "eni-xxxxxxxxx", "Weight": "100", "Type": "eni", "ServerIp": "172.166.**.**", "Port":"80","Description":"test-113" }]
[{ "ServerId": "eni-xxxxxxxxx", "Weight": "100", "Type": "eni", "ServerIp": "192.168.**.**", "Port":"80","Description":"test-112" }, { "ServerId": "eni-xxxxxxxxx", "Weight": "100", "Type": "eni", "ServerIp": "192.168.**.**", "Port":"80","Description":"test-112" }]

Response parameters

ParameterTypeDescriptionExample
object
VServerGroupIdstring

The ID of the vServer group.

rsp-cige6******
RequestIdstring

The ID of the request.

9DEC9C28-AB05-4DDF-9A78-6B08EC9CE18C
BackendServersobject []

The list of backend servers.

Typestring

The type of the backend server. Valid values:

  • ecs: an ECS instance. This is the default value.
  • eni: an ENI.
Type
Weightinteger

The weight of the backend server.

100
Descriptionstring

The description of the vServer group.

backend server
Portinteger

The port that is used by the backend server.

70
ServerIdstring

The ID of the ECS instance or ENI.

vm-2****

Examples

Sample success responses

JSONformat

{
  "VServerGroupId": "rsp-cige6******",
  "RequestId": "9DEC9C28-AB05-4DDF-9A78-6B08EC9CE18C",
  "BackendServers": {
    "BackendServer": [
      {
        "Type": "Type",
        "Weight": 100,
        "Description": "backend server",
        "Port": 70,
        "ServerId": "vm-2****"
      }
    ]
  }
}

Error codes

HTTP status codeError codeError message
400LBNotSupportIpv6BackendThe specified loadbalancer does not support ipv6 backend.
400Mismatched.ZoneIdThe zone of the server is not matched with the cloud box loadbalancer.
400InvalidBackendServers.ServerIpConflict%s.
400OperationUnsupported.CreateVServerGroupThis type of backend server is not allowed to attached to singleTunnel or anyTunnel lb.
400IncorrectStatus.RSByPassToas%s.
400BackendServer.InvalidTypeThe specified Type is invalid.
400BackendServer.ServerRegionIdNotEqualThe specified ServerRegionId must be equal.
400OperationFailed.InvalidCenThe cen related with this loadbalancer is invalid.
400IncorrectStatus.CenNotAssociatedThe action is invalid because the loadbalancer is not associated with cen.
400InvalidBackendServers.MissingCenBandWidthThe bandwidth is missing between loadbalancer and backendServers in cen.
400InvalidBackendServers.VpcNotInCenThe BackendServers is not in the cen associated with the loadbalancer.
400InvalidServerId.NotExistThe specified ServerId is not exist.
400MissingParameter.ServerRegionIdThe parameter ServerRegionId is required.
400MissingParameter.VbrIdThe parameter VbrId is required.
400InvalidParameter.ServerRegionIdThe parameter ServerRegionId is invalid for crossborder.
400InvalidVbrId.NotInCenThe VbrId is not in the cen associated with the loadbalancer.
400InvalidParameter.ServerRegionIdThe specified ServerRegionId is invalid.
400InvalidParameter.ZoneNotSupportThe zone does not support the parameter %s.
400NetworkConflict%s.
400InvalidParam.TagValue %s.
400InvalidParam.TagKey%s.
400SizeLimitExceeded.Tag%s.
400MissingParam.TagKeyThe param MissingParam.TagKey is missing.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2023-09-08The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 400 change
2023-06-02The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400