Add and manage smart routing listeners - Global Accelerator

Prerequisites

You have created a standard GA instance.
For HTTPS listeners, you must have purchased an SSL certificate and submitted a certificate signing request.
If your GA instance uses the subscription billing method, you must have purchased and associated a basic bandwidth plan.

Add a smart routing listener

TCP or UDP listener

Configure the listener and protocol.

Log on to the Global Accelerator console.
On the Instances page, find the target GA instance, and click Configure Listener in the Actions column.
On the Listeners tab, click Add Listener.

Note
If you are adding a listener for the first time, or if the current Global Accelerator instance has no listeners, skip this step.

On the Configure Listener & Protocol page of the configuration wizard, set the following parameters and click Next.

Parameter	Description
Listener Name	Enter a name for the listener.
Routing Type	Select a routing type. In this topic, Smart Routing is selected. Smart Routing: Routes traffic to the nearest or healthiest endpoint group based on latency. Custom Routing: Generates a port mapping table based on the listener port range, destination endpoint group port range, and IP addresses of endpoints (vSwitches). This deterministically routes traffic to a specific IP address and port in a specified vSwitch. For more information about how to configure a custom routing listener, see Add and manage custom routing listeners. Note The custom routing listener feature is available for invitational preview. To use this feature, contact your account manager. After your request is approved, you can select the routing type for your listeners.
Protocol	Select a network transport protocol for the listener. The following protocols are supported: TCP A connection-oriented protocol that ensures high reliability by establishing a connection before transmitting data. Supports session persistence based on source IP addresses. The source address is visible at the network layer. Slower data transmission. UDP A connectionless protocol with low reliability. It sends data packets without a three-way handshake and does not provide error recovery or data retransmission. Faster data transmission. Warning The maximum transmission unit (MTU) for UDP listeners of GA is 1,452 bytes. When you use a UDP listener, ensure that the MTU of the network interface card (NIC) used for communication between the backend server and GA is greater than 1,452 bytes. Otherwise, packets that exceed this size may be dropped.
Port	Specify the listener port that is used to receive and forward requests to endpoints. The port number must be in the range of 1 to 65499. You can specify up to 30 ports for each listener. Separate multiple ports with commas (,), for example, `80,90,8080`. If you have multiple consecutive ports, you can use a hyphen (-) to specify a port range, for example, `80-85`. Note The ports of TCP, HTTP, and HTTPS listeners cannot be the same. The port of a UDP listener cannot be the same as the port of an HTTPS listener for which HTTP/3 is enabled. For more information about the limits, see Listener ports for smart routing.
Advanced Settings	Optionally, configure Client Affinity and Idle Connection Timeout Period.
Client Affinity	Specify whether to enable client affinity: Source IP: Enables client affinity. When a client accesses a stateful application, all requests from the client are routed to the same endpoint. Disable: Disables client affinity. Requests from the same client are not guaranteed to be routed to the same endpoint.
Idle Connection Timeout Period	Specify the idle timeout period. If no data is transferred over a connection during the timeout period, GA closes the connection. A new connection is established when the next request is received. The value range of this parameter varies based on the listener protocol: TCP listener: 10 to 900 seconds. The default value is 900 seconds. UDP listener: 10 to 20 seconds. The default value is 20 seconds. Note If your standard GA instance does not support configuring the Idle Connection Timeout Period for a smart routing listener, your instance version may not support this feature. To use this feature, contact your business manager to upgrade the instance.

Configure endpoints.

Each listener is associated with an endpoint group in a specific region. Traffic is distributed to the optimal endpoint within the endpoint group that is associated with the listener.

On the Configure Endpoint Group page of the configuration wizard, configure the endpoint group and endpoints, and then click Next.

This topic describes only the basic configurations of an endpoint group and its endpoints. For more information about other configurations such as health checks, see Add a default endpoint group. For more information about endpoint groups and endpoints, see Endpoint groups and endpoints.

Parameter	Description
Endpoint Group Name	Enter a name for the endpoint group.
Region	Select the region where the endpoint group is deployed.
Backend IP protocol	Select the IP protocol that the GA instance uses to communicate with the backend service. IPv4: Uses only IPv4 addresses to communicate with the endpoint service. IPv6: Uses only IPv6 addresses to communicate with the endpoint service. IPv4/IPv6 (protocol affinity): The IP protocol that GA uses matches the protocol of the client request. If the client request uses IPv6, GA uses IPv6 to communicate with the endpoint service. If the client request uses IPv4, GA uses IPv4 to communicate with the endpoint service. Note Only standard GA instances that use the pay-as-you-go billing method and have listeners with a smart routing type support the configuration of backend IP protocols. Other types of GA instances do not support this configuration and use IPv4 by default. The backend IP address protocol feature is in invitational preview. To use this feature, contact your business manager. You cannot configure backend IP protocols if the endpoint group region is an Alibaba Cloud point of presence (POP). Call the ListAvailableBusiRegions operation to check whether a region is an Alibaba Cloud POP. You cannot configure OSS as a backend service if the backend IP protocol is set to IPv6 or IPv4/IPv6 (Protocol Affinity).
Endpoint Configuration	Endpoints are the destination hosts that process client requests. You can configure endpoints based on the following information: Backend Service Type: You can select ECS, ALB, NLB, CLB, OSS, ENI, Custom private IP address, Alibaba Cloud Public IP Address, Custom Public IP Address, or Custom Domain Name. Note If your standard GA instance does not support backend service types such as ECS (VPC type), ALB, NLB, CLB (VPC type), ENI, or Custom Private IP Address, the instance version may be outdated. To use these features, contact your business manager to request an instance upgrade. If you want to use GA to accelerate an Alibaba Cloud backend service type that is not currently supported or an on-premises IDC service, and you want GA to connect to the backend service over a private network, you can add an endpoint of the custom private IP address type. Custom private IP addresses include but are not limited to the following standard private CIDR blocks: 10.0.0.0/8 100.64.0.0/10 172.16.0.0/12 192.168.0.0/16 To ensure high availability, we recommend that you select two or more vSwitches for the Backend Service. If you want to use public IP addresses as private IP addresses, these addresses are treated as private IP addresses when you use the custom private IP feature. If necessary, configure the required routes in the VPC. UDP listeners do not support ALB backend services. To ensure uninterrupted connectivity between the GA instance and backend services, you must configure access policies based on the network connectivity type of the backend service: Public connection: The access policy of the backend service, such as a security group or firewall, must allow traffic from the GA egress public IP address. Private connection: The access policy of the backend service, such as a security group or access control rule, must allow traffic from the vSwitch CIDR block where the backend service resides. You must also ensure that at least eight private IP addresses are available in the vSwitch CIDR block. The egress public IP address of the endpoints for each GA instance is unique and not shared with users of other GA instances. If you select ECS, ALB, NLB, CLB, OSS, ENI, or Custom Private IP Address as the backend service type and a service-linked role does not exist, the system automatically creates one. 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 (Valid values: 0 to 255): The routing weight for the endpoint, from 0 to 255. GA routes traffic to endpoints in proportion to their weights. Warning If the weight of an endpoint is set to 0, Global Accelerator stops distributing traffic to that endpoint. Proceed with caution. You can click Add Endpoint to add multiple endpoints. You can add up to four endpoints. To add more endpoints, request a quota increase in the Quota Center. For more information, see Manage Global Accelerator quotas.
Preserve Client IP	Specify whether to preserve client IP addresses. If you enable this feature, backend servers can retrieve client source IP addresses. For more information, see Preserve client IP.
Port Mapping	Configure port mapping if the listener port differs from the service port on the endpoint. Listener Port: The port must be within the port range of the current listener. Endpoint Port: The port that the endpoint uses to provide services. Valid values: 1 to 65535. If the listener port is the same as the port that the endpoint uses to provide services, you do not need to configure port mapping. GA automatically sends access requests to the endpoint on the port that matches the listener port. For TCP and UDP listeners, you can click Add Port Mapping to add multiple port mappings. The Listener Port in each port mapping must be unique. You can add up to 30 port mappings. Note If your standard GA instance does not support configuring Port Mapping for TCP or UDP listeners, it may be because the instance version does not support this feature. To use this feature, contact your business manager to apply for an instance upgrade. For TCP listeners: You cannot configure port mapping for virtual endpoint groups. If a virtual endpoint group already exists for the listener, you cannot configure port mapping for the default endpoint group. If port mapping is already configured for the default endpoint group, you cannot add a virtual endpoint group. After you configure port mapping, the following limits apply to subsequent listener changes: Listener protocol: You can switch only between HTTP and HTTPS. Switching between other protocols is not supported. Listener port: The modified listener port range must include all listener ports that have existing port mappings. For example, if the listener port range is 80–82 and is mapped to endpoint ports 100–102, the modified listener port range must include ports 80–82. You can change the range to 80–90, but you cannot narrow it to 80–81. For more information about how to use port mapping, see Use GA port mapping to improve application flexibility and security.
Traffic Distribution Ratio	Configure the percentage of traffic that is distributed to different endpoint groups. Valid values: 0 to 100. Note For the subscription billing method, only TCP and UDP listeners support traffic distribution. For the pay-as-you-go billing method, all listener types support traffic distribution. A value of 0 indicates that traffic is not forwarded to this endpoint group. A value of 100 indicates that all traffic is forwarded to this endpoint group. For more information about how to use traffic dialing, see How traffic dialing works and its use cases.
Cross-border service configuration	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.

Review the configurations.

On the Configuration Review page of the configuration wizard, confirm the listener and endpoint configurations, and then click Submit.

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

Note
After you create a listener for the first time, it takes about 3 minutes for the configurations to take effect. If you modify the configurations of a listener, the modifications take effect in about 1 minute.

HTTP or HTTPS listener

Configure the listener and protocol.

Log on to the Global Accelerator console.
On the Instances page, find the target GA instance, and click Configure Listener in the Actions column.
On the Listeners tab, click Add Listener.

Note
If you are adding a listener for the first time, or if the current Global Accelerator instance has no listeners, skip this step.

On the Configure Listener & Protocol page of the configuration wizard, set the following parameters and click Next.

Parameter	Description
Listener Name	Enter a name for the listener.
Routing Type	Select a routing type. In this topic, Smart Routing is selected. Standard: Forwards traffic to the nearest or healthiest endpoint group based on latency, delivering requests to the optimal endpoint. Custom: Generates a port mapping table based on the listener port range, destination endpoint group port range, and IP addresses of endpoints (vSwitches). This allows you to deterministically route traffic to specific IP addresses and ports on a vSwitch. For more information about how to configure a listener that uses the Custom routing type, see Add and manage listeners of the Custom routing type. Note The custom routing listener feature is available for invitational preview. To use this feature, contact your account manager. After your request is approved, you can select the routing type for your listeners.
Protocol	Select a network transport protocol for the listener: HTTPS: The HTTPS protocol has the following characteristics: A connection-oriented protocol that ensures high reliability by establishing a connection before transmitting data. Ensures high data reliability by binding a server SSL certificate. Data is encrypted during transmission. HTTP: The HTTP protocol has the following characteristics: A connection-oriented protocol that ensures high reliability by establishing a connection before transmitting data. Faster data transmission. Data is transmitted in plaintext.
Maximum HTTP Version	Select the maximum HTTP version supported by GA. The Maximum HTTP Version is required only when Protocol is set to HTTPS. HTTP/1.1: Based on HTTP/1.0, HTTP/1.1 introduces technologies such as persistent connections and pipelining, but is subject to head-of-line blocking. HTTP/2 (Default): Based on the TCP protocol, HTTP/2 supports multiplexing and header compression to improve the concurrency capability of a single connection. HTTP/3: Uses the QUIC protocol that is based on UDP to resolve the head-of-line blocking issue. HTTP/3 introduces mechanisms such as error recovery, and flow control to improve transmission stability and efficiency. The latest version of the HTTP/3 protocol is h3. This version is supported by Chrome 87 and later. If you use other browsers, make sure that your browser supports HTTP/3. HTTP versions are forward compatible. For example, if you select HTTP/3 as the maximum version but the client does not support HTTP/3, GA also accepts requests over HTTP/2 or HTTP/1.1. Note If your pay-as-you-go GA instance does not support configuring Maximum HTTP Version, it may be because the instance version is not supported. Contact your account manager to upgrade your GA instance. Subscription Global Accelerator instances do not currently support HTTP/3. The TLS Security Policies configuration only applies to non-HTTP/3 connections. HTTP/3 connections use a built-in default security policy.
Port	Specify the listener port that is used to receive and forward requests to endpoints. The port number must be in the range of 1 to 65499. An HTTP or HTTPS listener supports only one port. Note The ports of TCP, HTTP, and HTTPS listeners cannot be the same. The port of a UDP listener cannot be the same as the port of an HTTPS listener for which HTTP/3 is enabled.
Server Certificate	Select the server certificate that you have applied for. This parameter is required only when you set Protocol to HTTPS. The server certificate provides encryption for data transmitted by Global Accelerator. For more information about how to purchase a certificate, see Select and purchase an SSL certificate and Submit a certificate signing request. When you configure a server certificate for a Global Accelerator instance, the system automatically creates the required service-linked role if the role does not exist.
TLS Security Policies	Select a TLS security policy that meets your business requirements. This parameter is required only when you set Protocol to HTTPS. You can select a system default policy or a custom policy. The TLS Security Policies configuration is not applicable to HTTP/3 connections. HTTP/3 connections use a built-in default security policy. A TLS security policy includes a TLS protocol version and supported cipher suites. Only standard pay-as-you-go GA instances support custom TLS security policies. If you set Maximum HTTP Version to HTTP/3, you cannot select a custom TLS security policy.
Advanced Settings	Optionally, configure Client Affinity, Idle Connection Timeout Period, Connection Request Timeout, and Custom HTTP Headers.
Client Affinity	Specify whether to enable client affinity: Source IP: Enables client affinity. When a client accesses a stateful application, all requests from the client are routed to the same endpoint. Disable: Disables client affinity. Requests from the same client are not guaranteed to be routed to the same endpoint.
Idle Connection Timeout Period	Specify the idle timeout period. If no access request is received during the timeout period, GA closes the connection. A new connection is established when the next request is received. The value can be from 1 to 60 seconds. The default value is 15 seconds. For pay-as-you-go GA instances, you can request a quota increase in Quota Center. Note If your standard GA instance does not support configuring the Idle Connection Timeout Period for a smart routing listener, your instance version may not support this feature. To use this feature, contact your business manager to upgrade the instance.
Connection Request Timeout	Specify the request timeout period. If a backend server does not respond within the timeout period, GA stops waiting and returns an HTTP 504 error code to the client. The value can be from 1 to 180 seconds. The default value is 60 seconds. For pay-as-you-go GA instances, you can request a quota increase in Quota Center. Note If your standard GA instance does not support configuring the Connection Request Timeout for a smart routing listener, your instance version may not support this feature. To use this feature, contact your business manager to upgrade the instance.
Custom HTTP Headers	Select the custom HTTP header fields that you want to add. Use the `GA-ID` header field to retrieve the ID of the GA instance. Use the `GA-AP` header field to retrieve information about the acceleration region of GA. Use the `GA-X-Forwarded-Proto` header field to retrieve the listener protocol of the GA instance. Use the `GA-X-Forwarded-Port` header field to retrieve the listener port of the GA instance. Use the `X-Real-IP` header field to retrieve the real client IP address.

Configure endpoints.

Each listener is associated with an endpoint group in a specific region. The system automatically distributes traffic to the optimal endpoint within the endpoint group that is associated with the listener.

On the Configure Endpoint Group page of the configuration wizard, configure the endpoint group and endpoints, and then click Next.

This topic describes only the basic configurations of an endpoint group and its endpoints. For more information about other configurations such as health checks, see Add a default endpoint group. For more information about endpoint groups and endpoints, see Endpoint groups and endpoints.

Parameter	Description
Endpoint Group Name	Enter a name for the endpoint group.
Region	Select the region where the endpoint group is deployed.
Backend IP Version	Select the IP protocol that the GA instance uses to communicate with the backend service. IPv4: Uses only IPv4 addresses to communicate with the endpoint service. IPv6: Uses only IPv6 addresses to communicate with the endpoint service. IPv4/IPv6 (protocol affinity): The IP protocol that GA uses matches the protocol of the client request. If the client request uses IPv6, GA uses IPv6 to communicate with the endpoint service. If the client request uses IPv4, GA uses IPv4 to communicate with the endpoint service. Note Only standard GA instances that use the pay-as-you-go billing method and have listeners with a smart routing type support the configuration of backend IP protocols. Other types of GA instances do not support this configuration and use IPv4 by default. The backend IP address protocol feature is in invitational preview. To use this feature, contact your business manager. You cannot configure backend IP protocols if the endpoint group region is an Alibaba Cloud point of presence (POP). Call the ListAvailableBusiRegions operation to check whether a region is an Alibaba Cloud POP. You cannot configure OSS as a backend service if the backend IP protocol is set to IPv6 or IPv4/IPv6 (Protocol Affinity).
Endpoint Configuration	Endpoints are the destination hosts that process client requests. You can configure endpoints based on the following information: Backend Service Type: You can select ECS, ALB, NLB, CLB, OSS, ENI, Custom private IP address, Alibaba Cloud Public IP Address, Custom Public IP Address, or Custom Domain Name. Note If your standard GA instance does not support backend service types such as ECS (VPC type), ALB, NLB, CLB (VPC type), ENI, or Custom Private IP Address, the instance version may be outdated. To use these features, contact your business manager to request an instance upgrade. To use GA to accelerate an unsupported Alibaba Cloud backend service type or an on-premises IDC service over a private connection, you can add an endpoint of the Custom Private IP Address type. Custom private IP addresses include, but are not limited to, the following standard private CIDR blocks: 10.0.0.0/8 100.64.0.0/10 172.16.0.0/12 192.168.0.0/16 To ensure high availability, select two or more vSwitches for the Backend Service. If you want to use public IP addresses as private IP addresses, these addresses are treated as private IP addresses when you use the custom private IP feature. If necessary, configure the required routes in the VPC. To ensure uninterrupted connectivity between the GA instance and backend services, you must configure access policies based on the network connectivity type of the backend service: Public connection: The access policy of the backend service, such as a security group or firewall, must allow traffic from the GA egress public IP address. Private connection: The access policy of the backend service, such as a security group or access control rule, must allow traffic from the vSwitch CIDR block where the backend service resides. You must also ensure that at least eight private IP addresses are available in the vSwitch CIDR block. The egress public IP address of the endpoints for each GA instance is unique and not shared with users of other GA instances. If you select ECS, ALB, NLB, CLB, OSS, ENI, or Custom Private IP Address as the backend service type and a service-linked role does not exist, the system automatically creates one. 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 (Valid values: 0 to 255): Enter an integer from 0 to 255. Global Accelerator routes traffic to endpoints based on their configured weights. Warning If the weight of an endpoint is set to 0, Global Accelerator stops distributing traffic to that endpoint. Proceed with caution. You can click Add Endpoint to add multiple endpoints. You can add up to four endpoints. To add more endpoints, request a quota increase in the Quota Center. For more information, see Manage Global Accelerator quotas.
Preserve Client IP	Specify whether to preserve client IP addresses. HTTP and HTTPS listeners preserve client IP addresses by default and store them in the `X-Forwarded-For` header field of HTTP requests. For more information, see Preserve client IP.
Backend Service Protocol	Select the protocol used by the backend service. You need to configure Backend Service Protocol only when you configure an endpoint group for an HTTP or HTTPS listener. HTTP (Default) HTTPS Note If the listener protocol is HTTP, the backend service uses the HTTP protocol by default and this cannot be changed. When Backend Service Protocol is set to HTTPS, GA supports the following TLS security policy versions for connections to backend services: `TLSv1.0`, `TLSv1.1`, `TLSv1.2`, and `TLSv1.3`. GA automatically negotiates an available TLS version with the backend service. If your GA instance does not support selecting a IP Version for connections to the backend service, `TLSv1.3` negotiation is not supported by default. To use this feature, contact your account manager to request an instance upgrade.
IP Version	Select the protocol version that GA uses to connect to the backend service. You need to configure IP Version only when Backend Service Protocol is set to HTTPS. HTTP/1.1 (Default) HTTP/2 By setting the protocol version to HTTP/2, backend HTTPS services can take full advantage of this protocol to significantly improve performance, reduce latency and network overhead, and enhance the overall access experience. This applies to backend services that already support HTTP/2. If your backend service supports only HTTP/2, you must select HTTP/2. Note If you cannot select a IP Version for a backend service in your GA instance, your instance version may not support this feature. To use this feature, contact your business manager to request an instance upgrade. If you set the protocol version to HTTP/2, the following limits apply: The WebSocket protocol is not supported. The Server Push feature in HTTP/2 is not supported. GA cannot accelerate gRPC requests that are based on HTTP/2.
Port Mapping	Configure port mapping if the listener port differs from the service port on the endpoint. Listener Port: The port must be within the port range of the current listener. Endpoint Port: The port that the endpoint uses to provide services. Valid values: 1 to 65535. If the listener port is the same as the port that the endpoint uses to provide services, you do not need to configure port mapping. GA automatically sends access requests to the endpoint on the port that matches the listener port. For HTTP and HTTPS listeners, you can add only one port mapping. Note After you configure port mapping, the following limits apply to subsequent listener changes: Listener protocol: You can switch only between HTTP and HTTPS. Switching between other protocols is not supported. Listener port: The modified listener port range must include all listener ports that have existing port mappings. For example, if the listener port range is 80–82 and is mapped to endpoint ports 100–102, the modified listener port range must include ports 80–82. You can change the range to 80–90, but you cannot narrow it to 80–81. For more information about how to use port mapping, see Use GA port mapping to improve application flexibility and security.
Traffic Distribution Ratio	Configure the percentage of traffic that is distributed to different endpoint groups. Valid values: 0 to 100. Note For the subscription billing method, only TCP and UDP listeners support traffic distribution. For the pay-as-you-go billing method, all listener types support traffic distribution. A value of 0 indicates that traffic is not forwarded to this endpoint group. A value of 100 indicates that all traffic is forwarded to this endpoint group. For more information about how to use traffic dialing, see How traffic dialing works and its use cases.
Cross-border service configuration	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.

Review the configurations.

On the Configuration Review page of the configuration wizard, confirm the listener and endpoint configurations, and then click Submit.

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

Note
After you create a listener for the first time, it takes about 3 minutes for the configurations to take effect. If you modify the configurations of a listener, the modifications take effect in about 1 minute.

More operations

Actions	Description
Edit a listener	When your business requirements change, you can modify the listener and protocol, SSL certificate, and endpoint group information to meet your business needs. The routing type of a listener cannot be modified. If port mapping is configured, take note of the following limits: Listener protocol: You can switch only between HTTP and HTTPS. Switching between other protocols is not supported. Listener port: The modified listener port range must include all listener ports that have existing port mappings. For example, if the listener port range is 80–82 and is mapped to endpoint ports 100–102, the modified listener port range must include ports 80–82. You can change the range to 80–90, but you cannot narrow it to 80–81. For a TCP listener with Preserve Client IP enabled and a public backend connection, you cannot change the listener protocol to UDP. Warning Modifying listener ports or the protocol after configuration may cause traffic interruptions. Perform these modifications during off-peak hours or after you switch traffic to another GA instance. On the Listeners tab, find the target listener, and in the Actions column, click Edit. On the Edit Listener page, modify the listener, protocol, SSL certificate, or endpoint group information, and then click Next. For more information about the listener, protocol, SSL certificate, and endpoint group, see Add a TCP or UDP listener or Add an HTTP or HTTPS listener.
Delete a listener	You can delete a listener. After a listener is deleted, its associated endpoint groups are also deleted. On the Listeners tab, find the target listener, and in the Actions column, click Delete. In the Delete Listener dialog box, click OK.
Configure a virtual endpoint group and forwarding rules for a listener	After configuring a smart routing listener, you can add virtual endpoint groups and forwarding rules. The listener uses these rules to forward requests to the appropriate default or virtual endpoint group. This enables a single GA instance to accelerate access to multiple destination endpoints. For more information, see the following topics: Add and manage endpoint groups for a smart routing listener Add and manage forwarding rules Use a single GA instance to accelerate access to multiple HTTPS domain names

References

CreateListener: Creates a listener for a GA instance.
UpdateListener: Modifies the configurations of a specified listener for a GA instance.
DeleteListener: Deletes a specified listener from a GA instance.