To associate a listener with an endpoint group, you can specify the region to which you want to distribute network traffic. Then, the system distributes network traffic to the optimal endpoint in the endpoint group.
Prerequisites
- A Global Accelerator (GA) instance is created. For more information, see Create and manage GA instances.
- A basic bandwidth plan is purchased and associated with the GA instance. For more information, see Purchase and manage basic bandwidth plans.
- You have deployed an application that serves as the endpoint of the GA instance. The application is used to receive requests that are forwarded from GA. For more information about the backend service types that are supported by GA, see Endpoints.
Background information
Each endpoint group is associated with a specific region. You can associate an endpoint group with a listener by specifying the region to which you want to distribute network traffic. After you associate an endpoint group with a listener, the system distributes network traffic to the optimal endpoints in the endpoint group.
- TCP or UDP listeners
By default, you can create two default endpoint groups for each TCP or UDP listener. If you want to create more default endpoint groups, go to the Quota Management page and increase the quota of gaplus_quota_epgs_per_listener. For more information, see Manage quotas.
You must deploy default endpoint groups in different regions. You can set a traffic distribution ratio for each default endpoint group. The traffic distribution ratio specifies the proportion of traffic that is distributed to a default endpoint group.
- HTTP or HTTPS listeners
By default, you can create one default endpoint group and one virtual endpoint group for each HTTP or HTTPS listener. If you want to create multiple virtual endpoint groups, go to the Quota Management page and increase the quota of gaplus_quota_vepg_per_listener. For more information, see Manage quotas.
- A default endpoint group refers to the endpoint group that you configure when you create an HTTP or HTTPS listener.
- A virtual endpoint group refers to the endpoint group that you can create on the Endpoint Group page after you create a listener.
After you create a virtual endpoint group for an HTTP or HTTPS listener, you can create a forwarding rule and associate the forwarding rule with the virtual endpoint group. Then, the HTTP or HTTPS listener forwards requests with different destination domain names or paths to the default or virtual endpoint group based on the forwarding rule. This way, you can use one Global Accelerator (GA) instance to accelerate multiple domain names or paths. For more information about how to create a forwarding rule, see Create and manage forwarding rules.
Manage the endpoint groups of a standard GA instance
Create a default endpoint group
Create a virtual endpoint group
- You can create a virtual endpoint group only for an HTTP or HTTPS listener.
- Before you can create a virtual endpoint group, you must create a default endpoint group.
Related operations
Operation | Description |
---|---|
Modify an endpoint group |
|
Set the traffic distribution ratio for an endpoint group | You can set the proportion of traffic that is distributed to different endpoint groups.
Note You can set traffic distribution ratios only for TCP and UDP listeners. For more information about how to set traffic distribution ratios, see Distribute traffic across endpoint groups in different scenarios.
|
Set the weight of an endpoint | You can set the weight of an endpoint. The weight specifies the proportion of traffic
that GA distributes to an endpoint in the endpoint group.
GA calculates the sum of all endpoint weights in an endpoint group. Then, traffic is forwarded to endpoints based on the proportions of their weights. For example, if you want to distribute 1/3 of the network traffic to Endpoint 1 and 2/3 of the network traffic to Endpoint 2, you can set the weight of Endpoint 1 to 1 and the weight of Endpoint 2 to 2. To disable GA from distributing network traffic to an endpoint, set the weight of the endpoint to 0.
|
Delete an endpoint group | You can delete an endpoint group that you no longer need. After you delete an endpoint
group, GA stops forwarding requests to the endpoint group.
Note If a listener is associated with only one endpoint group and you delete the endpoint
group, the listener becomes unavailable.
|
Delete an endpoint | You can delete an endpoint that you no longer need. After you delete an endpoint,
GA stops forwarding requests to the endpoint. If an endpoint group contains only one
endpoint, you cannot delete the endpoint.
|
Manage the endpoint groups of a basic GA instance
Create an endpoint group
Related operations
Operation | Description |
---|---|
Modify an endpoint group |
|
Delete an endpoint group |
|
References
Documentation and API operations related to endpoint groups for standard GA instances
- Distribute traffic across endpoint groups in different scenarios
- CreateEndpointGroup: You can call this API operation to create an endpoint group for a standard GA instance.
- CreateEndpointGroups: You can call this API operation to create multiple endpoint groups for a standard GA instance.
- UpdateEndpointGroup: You can call this API operation to modify an endpoint group of a standard GA instance.
- DeleteEndpointGroup: You can call this API operation to delete an endpoint group of a standard GA instance.
API operations related to endpoint groups for basic GA instances
- CreateBasicEndpointGroup: You can call this API operation to create an endpoint group for a basic GA instance.
- UpdateBasicEndpointGroup: You can call this API operation to modify the endpoint group of a basic GA instance.
- DeleteBasicEndpointGroup: You can call this API operation to delete the endpoint group of a basic GA instance.