Global Accelerator 2.0 (GA2.0) allows a single instance to access multiple acceleration regions at the same time. It supports acceleration forwarding based on TCP/UDP/HTTP/HTTPS. This document describes how to quickly create a GA2.0 acceleration instance.
Note:
When you create a GA2.0 instance, you need to follow the guide to create a listener and an endpoint group, enabling end-to-end service connectivity. After the creation is completed, you can continue to add listeners and endpoint groups on the instance details page.
The cross-border segment of GA2.0 is operated by China Unicom. If cross-border traffic exists between the acceleration region and the endpoint group, your account must first pass the cross-border qualification review. Prerequisites
Operation Steps
Step 1: Creating a Standard Instance
2. In the GA2.0 left sidebar, choose Instance Management and click Create Standard Instance.
3. Enter a GA2.0 instance name, select a billing mode, and add a description as needed.
4. Click Next to go to the page for configuring an acceleration region.
Step 2: Configuring an Acceleration Region
1. On the page for configuring an acceleration region, select an acceleration region as needed and configure the bandwidth peak, IP address protocol, and public network quality type based on the guide.
2. After the configuration is completed, click Next to go to the page for configuring a listener.
Note:
If you need to use dedicated BGP to optimize the access quality, you can select Hong Kong (China) as the acceleration region.
When neither Chinese mainland nodes nor Hong Kong (China) nodes are configured as acceleration regions, if your business uses a global unified domain name and is connected to GA2.0 via a global CNAME, access requests from users in the Chinese mainland are resolved to 127.0.0.1 by default.
Step 3: Configuring a Listener
1. On the page for configuring a listener, enter the listener name.
2. Select a routing type. Currently, only intelligent routing is supported, which forwards traffic to the nearest endpoint group based on the latency.
3. Select the listening protocol, which supports TCP/UDP/HTTP/HTTPS.
4. Configure the listening port.
5. Configure the client source IP address obtaining method, session persistence, idle connection timeout period, and connection request timeout period as needed based on the selected listener type.
6. Click Next and go to the endpoint group configuration page.
Step 4: Configuring an Endpoint Group
1. On the endpoint group configuration page, enter the endpoint group name.
2. Select the region of the endpoint group. It is recommended that you select the nearest one.
3. Add endpoints to the endpoint group. You can add up to 4 endpoints to an endpoint group. Supported endpoint types include custom public IP addresses or custom domain names.
4. Select the cross-border service type as needed. Supported types include Premium Bandwidth Cross-border and China Unicom Private Line Cross-border.
5. Configure the port mapping by specifying the listening port and the endpoint group port.
6. Enable health check for the endpoint group as needed. Click Advanced Configuration to configure the check protocol, response timeout period, health check interval, health threshold, and other parameters.
7. Click Next to go to the configuration review page.
8. Click Confirm Activation to complete the instance configuration.
Step 5: Configuring a Forwarding Policy
Note:
This step applies only to listeners whose listening protocol is HTTP/HTTPS.
1. On the listener list page of the created instance, click the listener ID to go to the listener details.
2. On the forwarding policy tab of the listener, click Add Forwarding Policy and enter a domain name.
3. Click Add Forwarding Rule on the right side of the domain name to add a forwarding URL for the domain name and configure a forwarding action, which supports Forward to or Discard.
4. Fill in the origin-pull HOST as needed. If you left it empty, the default HOST is null.
5. Click OK to complete the forwarding rule configuration.
1. On the listener list page of the created instance, click listener ID to go to the listener details.
2. On the forwarding policy tab of the listener, click Add Forwarding Policy and enter a domain name.
3. Click Add Forwarding Rule on the right side of the domain name to add a forwarding URL for the domain name and configure a forwarding action, which supports Forward to or Discard.
4. Click Advanced Settings to configure the origin-pull SNI, origin-pull HOST, and origin-pull request headers for the rule.
5. Click the feature switch on the right side of the origin-pull SNI to enable the origin-pull SNI configuration feature.
6. Enter the origin-pull SNI value.
Attention:
If a forwarding rule configured with the origin-pull SNI is bound to an endpoint group whose origin-pull protocol is HTTP, GA2.0 still uses HTTP for origin-pull. In this case, the SNI configuration does not take effect.
7. Fill in the origin-pull HOST as needed in the origin-pull HOST input box. If you do not fill it in, the default HOST is null.
8. Click OK to complete the forwarding rule configuration.