Each listener is associated with an endpoint group. You can associate a listener with an endpoint group by specifying the region to which you want to distribute network traffic. After you associate a listener with an endpoint group, the system distributes network traffic to the endpoint in the endpoint group based on the routing type of the listener. This topic describes how to create and manage endpoint groups of intelligent routing listeners.
Background information
After you create an intelligent routing listener for a Global Accelerator (GA) instance, the GA instance automatically selects a nearby and healthy endpoint group and forwards client requests to the optimal endpoint in the endpoint group.
Intelligent routing listeners support the following types of endpoint groups:
Default endpoint group: the endpoint group that you configured when you create a listener.
By default, you can create two default endpoint groups for a TCP or UDP listener. If you want to create additional endpoint groups, go to the Quota Management page and increase the quota named gaplus_quota_epgs_per_listener. For more information, see Manage GA quotas.
You must deploy default endpoint groups in different regions. You can specify a traffic distribution ratio for each endpoint group. The traffic distribution ratio specifies the proportion of traffic that is distributed to an endpoint group. For more information about how to specify traffic distribution ratios, see Distribute traffic across endpoint groups in different scenarios.
You can create one default endpoint group for each HTTP or HTTPS listener.
Virtual endpoint group: After you create a listener, you can create a virtual endpoint group on the Endpoint Groups page.
By default, you can create up to 10 virtual endpoint groups for each listener regardless of the listener protocol. If you want to create additional virtual endpoint groups, go to the Quota Management page and increase the quota named gaplus_quota_vepg_per_listener. For more information, see Manage GA quotas.
After you create a virtual endpoint group for a listener, you can create a custom forwarding rule and associate the rule with the virtual endpoint group. After you associate a forwarding rule with an endpoint group, the listener forwards the requests that meet the forwarding conditions to the default endpoint group or the virtual endpoint group that is specified in the forwarding rule. This way, Global Accelerator (GA) can access multiple endpoints at the same time. For more information about how to create a forwarding rule, see Add and manage forwarding rules.
NoteIf the TCP or UDP listener of your standard GA instance does not support virtual endpoint groups or forwarding rules, the instance may be using an earlier version. Contact your account manager to upgrade your GA instance.
Prerequisites
A standard Global Accelerator instance is created. For more information, see Create and manage standard GA instances.
A basic bandwidth plan is created and associated with the GA instance if the GA instance uses the pay-by-bandwidth bandwidth metering method.
An application that serves as the endpoint of a standard Global Accelerator (GA) instance is deployed. The application is used to receive requests that are forwarded from the GA instance. For more information about the endpoint types that are supported by GA, see the "Endpoint groups" section of the Overview topic.
Create a default endpoint group
Log on to the GA console.
On the Instances page, find the GA instance that you want to manage and click Configure Listeners in the Actions column.
On the Listeners tab, click Add Listener.
NoteIf this is the first time that you add a listener or if no listener is created for the specified Global Accelerator instance, skip this step.
On the Configure Listener & Protocol wizard page, select Intelligent Routing as the routing type, configure the listener protocol and port, and then click Next.
If you want to create an endpoint group for an HTTPS listener, you must configure SSL certificates. For more information, see Add and manage intelligent routing listeners.
On the Configure Endpoint Group wizard page, configure the parameters. The following table describes the parameters.
Parameter
Description
Endpoint Group Name
Specify a name for the endpoint group.
Region
Select the region where you want to deploy the endpoint group.
Configuration
Endpoints are the destinations of client requests. To add an endpoint, configure the following parameters:
Backend Service Type: If your backend server is deployed on Alibaba Cloud, you can select Alibaba Cloud Public IP Address, ECS, ENI, CLB, ALB, NLB, or OSS. If your backend server is not deployed on Alibaba Cloud, you can select Custom IP Address or Custom Domain Name.
NoteIf your standard GA instance does not support using ALB instances, ECS instances in VPCs, CLB instances in VPCs, NLB instances, or ENIs as endpoints, your instance may be using an earlier version. Contact your account manager to upgrade your GA instance.
The endpoint group IP addresses of a GA instance are unique and are not shared with other GA instances.
If no service-linked roles exist when you specify Elastic Compute Service (ECS) instances, elastic network interfaces (ENIs), Classic Load Balancer (CLB) instances, Application Load Balancer (ALB) instances, Network Load Balancer (NLB) instances, or Object Storage Service (OSS) buckets as endpoints, the system automatically creates the corresponding service-linked role. For more information, see AliyunServiceRoleForGaVpcEndpoint, AliyunServiceRoleForGaAlb, AliyunServiceRoleForGaOss, and AliyunServiceRoleForGaNlb.
Backend Service: enter the IP address, domain name, or instance ID of the backend server.
Weight: specify a weight for the endpoint. Valid values: 0 to 255. GA routes network traffic to endpoints based on the weights of the endpoints.
WarningIf you set the weight of an endpoint to 0, Global Accelerator stops distributing network traffic to the endpoint. Proceed with caution.
You can click + Add Endpoint to add more endpoints. You can create up to four endpoints in each endpoint group. If you want to add more endpoints, go to the Quota Management page and increase the quota. For more information, see Manage GA quotas.
Preserve Client IP
Specify whether to preserve client IP addresses.
If you enable this feature, the backend server can obtain client IP addresses. For more information, see Preserve client IP addresses.
Backend Service Protocol
Select the protocol that is used by the backend server. Valid values:
HTTP (default)
HTTPS
NoteIf the listener protocol is HTTP, this parameter is automatically set to HTTP and cannot be modified.
You can configure the Backend Service Protocol parameter only when you configure an endpoint group for an HTTP or HTTPS listener.
Port Mapping
If the listener port and the port that is used by the endpoint to provide services are different, you must configure this parameter.
Listener Port enter the listener port.
Endpoint Port enter the port over which the endpoint provides services.
If the listener port is the same as the port over which the endpoint provides services, ignore this parameter. GA automatically forwards requests to the listener port of the endpoint.
NoteYou can configure the Port Mapping parameter only when you configure an endpoint group for an HTTP or HTTPS listener.
Traffic Distribution Ratio
Specify a traffic distribution ratio for the endpoint group.
Valid values: 0 to 100.
NoteYou can set the Traffic Distribution Ratio parameter only when you create an endpoint group for a TCP or UDP listener. For more information about how to specify traffic distribution ratios, see Distribute traffic across endpoint groups in different scenarios.
A value of 0 specifies that no traffic is forwarded to the endpoint group. A value of 100 specifies that all traffic is forwarded to the endpoint group.
Health Check
Specify whether to enable the health check feature.
After you enable this feature, you can perform health checks to check the status of endpoints. For more information about the health check feature, see Enable and manage health checks.
NoteIf your GA instance uses UDP listeners, you can enable the health check feature for an endpoint only if the endpoint is associated with a TCP, HTTP, or HTTPS service. Otherwise, the endpoint is marked as unhealthy.
Health Check Protocol
Select the protocol that you want to use for health checks. Valid values: TCP, HTTP, and HTTPS.
- A TCP health check probes whether a server port is healthy at the network layer by sending SYN packets to the port.
- An HTTP health check probes whether an endpoint is healthy by simulating HTTP GET requests sent from a browser.
Port
Specify the port of the endpoint to which probe packets are sent for health checks.
Valid values: 1 to 65535.
Health Check Interval
Specify the interval between two consecutive health checks. Unit: seconds.
Valid values: 1 to 50. Default value: 2.
URI
Specify the path that is used for health checks.
By default, GA sends a GET request to the default homepage of the backend service. If you do not want to use the default homepage for health checks, you can manually specify a URI.
Note This parameter is supported only for HTTP and HTTPS health checks.Healthy Threshold
The number of consecutive health check failures that must occur before a healthy endpoint is considered unhealthy, or the number of consecutive health check successes that must occur before an unhealthy endpoint is considered healthy.
Valid values: 2 to 10. Default value: 3.
Tag
Specify a tag for the endpoint group.
You must configure the Tag Key and Tag Value parameters. For more information, see Manage tags.
Optional. Click + Add Endpoint Group to add multiple endpoint groups and repeat the operation in Step 5 to configure the endpoint groups.
NoteYou can add multiple endpoint groups only for TCP and UDP listeners.
In the Cross-border Acceleration Settings section, read Compliance Commitments Regarding Cross-border Data Transfers and select Agree to the Preceding Compliance Agreement.
This parameter takes effect only when cross-border acceleration is disabled for your GA instance and the selected endpoint group and existing acceleration regions are deployed across borders. For example, the endpoint group resides in a region in the Chinese mainland and the acceleration regions are located outside the Chinese mainland, such as the China (Hong Kong), China (Macao), and China (Taiwan) regions.
After the configuration is complete, the Transmission Network Type parameter of the GA instance is automatically set to BGP (Multi-ISP) Pro. For more information, see Pay-by-data-transfer.
Click Next.
On the Confirm wizard page, check the configurations and click Submit.
If you want to modify a specific setting, click Modify that corresponds to the setting. Then, you are redirected to the configuration page.
Create a virtual endpoint group
Before you can create a virtual endpoint group, you must add the default endpoint group.
Log on to the GA console.
On the Instances page, find the GA instance that you want to manage and click Configure Listeners in the Actions column.
On the Listeners tab, find the listener that you want to manage and click the number in the Virtual Endpoint Group column.
On the Endpoint Group tab, click Add Virtual Endpoint Group in the Virtual Endpoint Group section.
In the Create Virtual Endpoint Group dialog box, set the parameters and click Create.
For more information, see Create a default endpoint group.
More operations
Operation | Description |
Modify an endpoint group |
|
Specify the traffic distribution ratio for an endpoint group | Specify a traffic distribution ratio for the endpoint group. Note You can configure the Traffic Distribution Ratio parameter only when you create an endpoint group for a TCP or UDP listener. For information about how to specify traffic distribution ratios, see Distribute traffic across endpoint groups in different scenarios.
|
Specify the weight of an endpoint | You can specify 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 routed to endpoints based on the proportions of the weights of the endpoints. 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.
|
View the public IP address of an endpoint |
Note The system assigns at least four public IP addresses to each endpoint. The number of public IP addresses assigned to an endpoint varies based on the following factors when different billing methods are used:
|
Delete an endpoint group | You can delete an endpoint group that you no longer require. After you delete an endpoint group, GA stops forwarding requests to the endpoint group. Warning If a listener is associated with only one endpoint group and you delete the endpoint group, the listener becomes unavailable. Proceed with caution.
|
Delete an endpoint | You can delete an endpoint that you no longer require. 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.
|
References
Distribute traffic across endpoint groups in different scenarios
CreateEndpointGroup: creates an endpoint group for a standard GA instance.
CreateEndpointGroups: creates multiple endpoint groups for a standard GA instance.
UpdateEndpointGroup: modifies an endpoint group of a standard GA instance.
DeleteEndpointGroup: deletes an endpoint group of a standard GA instance.