All Products
Search
Document Center

Global Accelerator:Manage endpoint groups for custom routing listeners

Last Updated:Sep 16, 2026

Each listener uses endpoint groups to distribute traffic. For a custom routing listener, traffic is routed to specific endpoints within these groups.

Prerequisites

  • A standard GA instance is created.

  • For subscription-based GA instances, you must have purchased and associated a basic bandwidth plan.

  • You have deployed your applications as backend services for Global Accelerator. For custom routing listeners, the backend service type must be a vSwitch. For more information, see Endpoints.

  • You must have permission to use custom routing listeners. This feature is in invitational preview. To use it, contact your account manager. After your request is approved, you can select custom routing as the routing type for your listeners.

  • To ensure proper connectivity between the GA instance and your backend services, the access control policies of the backend services, such as security group rules, must allow traffic from the CIDR block of the vSwitch. You must also ensure that the vSwitch has at least eight idle private IP addresses.

Background information

After you configure a custom routing listener, the Global Accelerator instance creates a mapping table. This table is based on the listener's port range, the port mapping of the destination endpoint group, and the endpoint's subnet information. GA uses this table to deterministically route traffic to either all IP addresses within the specified vSwitch or to specific IP addresses and destination ports.

Custom routing listeners support only the TCP and UDP protocols. Each listener supports a maximum of 10 endpoint groups, and this quota cannot be increased.

Add an endpoint group

  1. Log on to the GA console.

  2. On the Instances page, find the GA instance that you want to manage and click Configure Listener in the Actions column.

  3. On the Listeners tab, click Add Listener.

    Skip this step if you are adding the first listener or if the Global Accelerator instance has no listeners.
  4. On the Configure Listener & Protocol page, select Custom Routing as the routing type, configure the listener, and then click Next.

    For more information, see Add and manage custom routing listeners.

  5. On the Configure Endpoint Group page, configure the endpoint group and its endpoints.

    An endpoint group defines the mapping between the listener port range and the backend service port range and protocol. An endpoint specifies the backend destination subnet and its traffic handling policy.

    1. Configure the endpoint group.

      On the Configure Endpoint Group page, configure the endpoint group based on the following information.

      Parameter

      Description

      Endpoint Group Name

      Enter a name for the endpoint group.

      Region

      Select the Alibaba Cloud region where the endpoint group is deployed.

      Port Mapping Range and Protocol

      Select an entry mode to define the port and protocol mappings from the listener to the backend services in the endpoint group.

      • List Mode: Enter the Port Range and Protocol. For Protocol, you can select TCP, UDP, or both.

        Click Add to enter multiple mappings.

        Use this mode to add up to 20 mappings at a time.

      • Batch Mode: Enter the port ranges and protocols according to the formatting instructions, or download the template, fill it out, and upload the file.

        Use this mode to add up to 100 mappings at a time.

      The total number of ports in the endpoint group multiplied by the total number of IP addresses in all vSwitch endpoints must be less than or equal to the total number of ports specified for the listener. The formula is: (Total number of ports in the endpoint group) × (Total number of IP addresses in all vSwitch endpoints) ≤ (Number of listener ports).
    2. Configure endpoints.

      In the Endpoint section, click Add Endpoint. In the Add Endpoint dialog box, configure the endpoint based on the following information, and then click OK.

      Parameter

      Description

      Backend Service Type

      Only vSwitch is supported.

      Backend Service

      Select the vSwitch to which you want to forward traffic.

      Subnet Traffic

      Select a subnet traffic access policy.

      • Allow All Traffic: All inbound traffic is forwarded to the specified backend service through Global Accelerator.

      • Deny All Traffic (Default): No inbound traffic is forwarded to the specified backend service through Global Accelerator.

      • Allow traffic for specific vSwitch IP addresses and ports: Specify the Access Policy that can receive traffic. Traffic destinations are the IP addresses and ports of ECS instances.

        Select an entry mode for the Access Policy:

        • List Mode: Enter an IP Address and Port. You can also select the All Ports option.

          Click +Add to enter multiple mappings.

          Use this mode to add up to 20 mappings at a time.

        • Batch Mode: Enter the IP address ranges and port mappings according to the formatting instructions, or download the template, fill it out, and upload the file.

          Use this mode to add up to 100 mappings at a time.

    3. Optional: Click + Add Endpoint Group to configure another endpoint group.

    4. In the Cross-border Acceleration Settings section, read the Compliance Commitments Regarding Cross-border Data Transfers and select Agree to the Preceding Compliance Agreement.

      This step is required only if cross-border acceleration is not enabled for your GA instance and your service configuration involves cross-border acceleration between the Chinese mainland and other regions.

    5. Click Next.

  6. Review the configuration.

    On the Configuration Review wizard page, verify the listener and endpoint configurations, and then click Submit.

    To modify configurations, click Edit in the corresponding section to return to the previous page.

    A new listener takes about 3 minutes to become active. Configuration changes take about 1 minute to apply.

More operations

Actions

Description

Modify an endpoint group

  1. On the Listeners tab, find the target listener and click the listener ID.

  2. On the listener details page, click the Endpoint Group tab.

  3. On the Endpoint Group tab, find the target endpoint group and perform the following operations as needed to modify its name or port mapping information.

    • Modify the endpoint group name: In the Endpoint Group ID/Name column, hover over the name and click the 编辑 icon.

    • Modify the port mapping range and protocol: Click the number in the Port Mapping Range and Protocol column. In the Port Mapping Range and Protocol panel, perform the following operations:

      • To modify an existing mapping, click Edit in the Actions column. In the Modify Port Mapping Range and Protocol dialog box, modify the mapping.

      • To add a new mapping, click Add. In the Add dialog box, add a mapping.

      • To delete mappings, find the mapping that you want to delete and click Delete in the Actions column, or select multiple mappings and click Batch Delete. In the Delete dialog box, click OK.

      For more information about the limits on port mapping ranges, see Listener ports for custom routing listeners.

Add an endpoint

  1. On the Listeners tab, find the target listener and click the listener ID.

  2. On the listener details page, click the Endpoint Group tab.

  3. On the Endpoint Group tab, find the target endpoint group, and click Add Endpoint in the Actions column.

  4. In the Add Endpoint dialog box, select the Backend Service and a policy for Subnet Traffic, and then click OK.

    For more information, see Configure endpoints.

Modify an endpoint

  1. On the Listeners tab, find the target listener and click the listener ID.

  2. On the listener details page, click the Endpoint Group tab.

  3. On the Endpoint Group tab, find the target endpoint group, and click the number in the Endpoint column.

  4. On the details page of the Endpoint, find the target endpoint in the Endpoint section, and then modify the subnet's traffic handling policy or add a traffic destination to the endpoint.

    • Modify the traffic handling method for the subnet: Click Edit in the Actions column. In the Edit Endpoint dialog box, select a new policy for Subnet Traffic.

    • Add a traffic destination: Click Add Access Policy in the Actions column. In the Add Access Policy dialog box, select an entry mode for the Access Policy and enter the required information.

    • Edit a traffic destination: Click the number in the Access Policy column. In the Access Policy panel, perform the following operations:

      • To modify an existing traffic destination, click Edit in the Actions column. In the Modify Access Policy dialog box, modify the traffic destination.

      • To add a new traffic destination, click Add. In the Add Access Policy dialog box, add a new traffic destination.

      • To delete traffic destinations, find the traffic destination that you want to delete and click Delete in the Actions column, or select multiple traffic destinations and click Batch Delete. In the Delete dialog box, click OK.

    For more information, see Configure endpoints.

Delete an endpoint

  1. On the Listeners tab, find the target listener and click the listener ID.

  2. On the listener details page, click the Endpoint Group tab.

  3. On the Endpoint Group tab, find the target endpoint group and click the number in the Endpoint column.

  4. On the endpoint group details page, find the target endpoint in the Endpoint section, and then click Delete in the Actions column.

  5. In the Delete dialog box, click OK.

Delete an endpoint group

  1. On the Listeners tab, find the target listener and click the listener ID.

  2. On the listener details page, click the Endpoint Group tab.

  3. On the Endpoint Group tab, find the target endpoint group, and click Delete in the Actions column.

  4. In the Delete Endpoint Group dialog box, click OK.

API reference