Create and manage Standard GA instances | Global Accelerator - Global Accelerator

A Standard Global Accelerator (GA) instance provides a fully meshed acceleration network with Layer 4 (TCP/UDP) and Layer 7 (HTTP/HTTPS) support across multiple regions.

Create a Standard GA instance

Standard GA instances support two billing methods: Pay-As-You-Go and Subscription.

Pay-as-you-go charges based on actual usage. Configure the instance, acceleration region, listener, and endpoint group at once without selecting an instance type. Best for fluctuating or unpredictable workloads.
Subscription requires purchasing a specific instance type upfront before completing the remaining configuration. Best for stable, predictable workloads.

Pay-as-you-go standard instance

Before you create a pay-as-you-go Standard GA instance, review the following:

The first time you use a pay-as-you-go GA instance, you must Activate the Service.
Pay-as-you-go GA instances use Pay-By-Data-Transfer for bandwidth billing. You do not need to associate a bandwidth package. Cloud Data Transfer (CDT) handles traffic billing.

Log on to the GA console.
On the Instances page, click Create Standard Pay-as-you-go Instance.

On the Basic Instance Configuration page, configure the following parameters and click Next.

Parameter	Description
GA Instance Name	Enter a name for the GA instance.
Billing Method	The default is Pay-As-You-Go. A pay-as-you-go standard GA instance incurs these fees: instance fee, CU fee, and traffic fee.
Accelerated IP Address Type	Select an acceleration IP type for the Standard GA instance. EIP (default): Uses custom nearest access mode. Select acceleration areas and regions as needed. GA assigns an independent EIP per acceleration region. Anycast EIP: Uses automatic nearest access — no need to select acceleration areas or regions. GA provides 2 Anycast EIPs across multiple regions worldwide. For a Standard GA instance, the number of acceleration IPs per region depends on the acceleration IP type: If the accelerated IP address type is Elastic IP Address, two EIPs are allocated to each acceleration region. The two EIPs can be used to simultaneously accelerate client traffic and ensure high availability for the acceleration region. If the accelerated IP address type is Anycast EIP, GA provides two Anycast EIPs in multiple regions across the globe.
Resource Group	Select the resource group for the standard Global Accelerator instance. The resource group must already exist in Resource Management.

In the Configure Acceleration Area wizard, configure the acceleration area, and then click Next.

The following parameters configure the acceleration area.

EIP

Parameter	Description
Acceleration Area	Select one or more acceleration regions, then click Add to List. Note If the acceleration area includes Chinese mainland regions, complete an ICP filing for your domain. Alternatively, select the BGP Pro line in China (Hong Kong) to serve Chinese mainland users.
Assign Bandwidth	Maximum Bandwidth: Set the bandwidth for the acceleration region. Default: 200 Mbps. Supported range per region: 2 to 10,000 Mbps. This peak bandwidth is only used for rate limiting. You are billed for the resulting traffic through CDT. Important Setting the peak bandwidth too low causes rate limiting and packet loss. Plan accordingly. IP Protocol: Select the IP protocol for the Global Accelerator service. IPv4: Allocates an IPv4 accelerated IP address. This allows IPv4 clients to connect to the GA network. IPv6: Allocates an IPv6 accelerated IP address. This allows IPv6 clients to connect to the GA network and enables the IPv6 Translation Service. Dual-stack: Allocates both an IPv4 and an IPv6 accelerated IP address. This allows both IPv4 and IPv6 clients to connect to the GA network. ISP Line Type: Select the public network quality type for the Global Accelerator service. BGP (Multi-ISP): BGP (Multi-ISP) provides high-quality BGP lines that cover multiple regions across the globe. It connects to the networks of multiple carriers and automatically selects the optimal route to ensure fast and stable access. All acceleration regions support and use the BGP (Multi-ISP) type by default. BGP Pro: BGP Pro is a premium network line that optimizes traffic from regions outside the Chinese mainland to the Chinese mainland. It improves the quality of international connections. Compared with standard BGP (Multi-ISP) lines, BGP Pro lines provide lower latency when they serve clients in the Chinese mainland (excluding data centers in the Chinese mainland) because they are directly connected to the Chinese mainland through premium carrier networks. Currently, GA supports the BGP Pro type only in the China (Hong Kong) and Japan (Tokyo) regions.

Anycast EIP

Parameter

Description

Acceleration Area

No acceleration area or region selection required. Follow the on-screen prompts to view supported access points.

The supported acceleration areas depend on the access points covered by Anycast EIP. This service primarily accelerates access for users in regions outside the Chinese mainland. Clients in the Chinese mainland connect through the access point in China (Hong Kong).

Bandwidth

Set a single bandwidth for all acceleration regions. Default: 200 Mbps. Supported range: 200 to 5,000 Mbps.

On the Configure Listeners page, configure the listener and click Next.

Configure the listener based on the routing type. Listener routing types.

Intelligent routing (formerly standard listener)

Parameter	Description
Listener Name	Enter a name for the listener.
Routing Type	Select a routing type. In this example, Intelligent Routing (formerly standard listener) is selected. An intelligent routing listener forwards traffic to the nearest or healthiest endpoint group based on latency.
Protocol	Select a listener protocol: TCP UDP HTTP HTTPS For details, see Listener protocols.

TCP and UDP listener

Parameter	Description
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`. 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. Port limits:Intelligent routing listener ports.
Advanced Settings	Optionally, configure Client Affinity and Idle Connection Timeout Period.
Client Affinity	Select whether to enable client affinity: Source IP: All requests from the same client are routed to the same endpoint. Use for stateful applications. Disable: No client affinity. Requests from the same client may reach different endpoints.
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 valid range 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.

HTTP and HTTPS listener

Parameter	Description
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. 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.
Select a server certificate	Select an existing server certificate. This setting is required only when Protocol is set to HTTPS. A server certificate secures data transmission. Purchase a certificate:Purchase a commercial certificate and Submit a certificate application.
TLS Security Policy	Select the appropriate TLS security policy. This parameter is required only when you set Protocol to HTTPS. System-default and custom policies are available.The TLS Security Policies setting applies only to non-HTTP/3 connections. HTTP/3 connections use a built-in default security policy. A TLS security policy specifies the TLS protocol versions and cipher suites for HTTPS. TLS security policies.
Advanced Settings	Optionally, configure Client Affinity, Idle Connection Timeout Period, Connection Request Timeout, and Custom HTTP Headers.
Client Affinity	Select whether to enable client affinity: Source IP: All requests from the same client are routed to the same endpoint. Use for stateful applications. Disable: No client affinity. Requests from the same client may reach different endpoints.
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 additional HTTP header fields you want to use. `GA-ID`: Retrieves the GA instance ID. `GA-AP`: Retrieves acceleration region information. `GA-X-Forwarded-Proto`: Retrieves the GA listener protocol. `GA-X-Forwarded-Port`: Retrieves the GA listener port. `X-Real-IP`: Retrieves the client's real IP address.

Custom routing

Note

The custom routing listener feature is in invitation-only preview. To use this feature, contact your account manager. Once approved, you can select this routing type when you create a listener.
Custom routing listeners are not supported when the accelerated IP protocol is IPv6.

Parameter	Description
Listener Name	Enter a name for the listener.
Routing Type	Select a routing type. In this example, Custom routing is selected. A custom routing listener generates a port mapping table from the listener port range, endpoint group port range, and endpoint IP addresses (vSwitches), then deterministically routes traffic to a specific IP and port in a designated vSwitch. Add and manage custom routing listeners.
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. Use a comma (,) to separate multiple ports, for example, 80,90,8080. For multiple consecutive ports, use a hyphen (-) to specify a port range, for example, `80-85`. Note The listener ports of different custom routing listeners on the same Global Accelerator instance cannot overlap. Ports 25, 250, 4789, and 4790 are reserved by the system. GA automatically ignores these ports when it generates a mapping table. Port 6081 cannot be configured for pay-as-you-go Global Accelerator instances. The listener port range determines the number of possible combinations of ports in the associated endpoint group and IP addresses in all vSwitch endpoints. The formula is: `Number of listener ports ≥ Total number of ports in the endpoint group × Total number of IP addresses in all vSwitch endpoints`. We recommend that you configure a large port range for the listener.

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

Endpoint group and endpoint parameters. Endpoint groups and endpoints.

Endpoint group for intelligent routing

Parameter	Description
Region	Select the region for the endpoint group.
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	Configure your endpoints. You can select an existing instance in the region to which the endpoint group belongs, or create a new instance in that region and then select it. When the accelerated IP type is set to EIP, GA allocates a separate EIP as the accelerated IP for each acceleration region. These accelerated IPs are independent of the public IPs bound to your existing instances, and the original public IPs can still be used to access your services directly. Backend Service Type: You can select ECS, ALB, NLB, CLB, OSS, ENI, Custom private IP address, Alibaba Cloud Public IP, Custom public IP address, or Custom Domain Name. Note If your standard GA instance does not support backend service types such as ECS, 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. 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): 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	Preserve client source IP addresses. When enabled, the backend server can retrieve the client's source IP address. Preserve client source IP addresses.
Backend Service Protocol	Select the protocol used by the backend service. Configure this parameter only when you set up an endpoint group for an HTTP or HTTPS listener. HTTP (default) HTTPS Note If the listener protocol is HTTP, the backend service uses HTTP by default and you cannot change the protocol. When the Backend Service Protocol is set to HTTPS, Global Accelerator (GA) supports TLSv1.0, TLSv1.1, TLSv1.2, and TLSv1.3 for connections to backend services, and automatically negotiates an available TLS version with the backend service. If your GA instance does not allow you to select the IP Version for backend service connections, the instance also does not support TLSv1.3 negotiation by default. To use this feature, contact your account manager to request an instance upgrade.
IP Version	Select the protocol version that Global Accelerator uses to connect to the backend service. This parameter applies only when Backend Service Protocol is set to HTTPS. HTTP/1.1 (default) HTTP/2 HTTP/2 significantly improves performance, reduces latency and network overhead, and enhances the overall access experience for backend HTTPS services. 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 your GA instance does not support selecting the IP Version for a backend service, this may be because the instance version is not supported. To use this feature, please contact your business manager to request an instance upgrade. If you select HTTP/2, the following limits apply: The WebSocket protocol is not supported. The Server Push feature of HTTP/2 is not supported. gRPC requests that are based on HTTP/2 cannot be accelerated.
Port Mapping	If the listener port differs from the endpoint port, you must configure port mapping. Listener Port: The port must be within the port range configured for 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. Global Accelerator automatically sends access requests to the endpoint on 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. For HTTP and HTTPS listeners, you can add only one port mapping. 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.
Health Check	Enable or disable health checks. When enabled, GA checks endpoint health status. Enable and manage health checks. Note UDP listener endpoints require a TCP, HTTP, or HTTPS service for health checks. Otherwise, they are marked unhealthy.
Health Check Protocol	The protocol used for health checks. Valid values: TCP, HTTP, and HTTPS. TCP: sends SYN handshake packets to probe whether the server port is active. HTTP and HTTPS: send GET requests to simulate browser access and check the health of the backend service application.
Port	The endpoint port that Global Accelerator probes for health checks. Valid values: 1 to 65535.
Health Check Interval	The interval between health checks, in seconds. Valid values: 1 to 50. Unit: seconds. Default value: 2.
URI	The path for health checks. This parameter is available only when Health Check Protocol is set to HTTP or HTTPS. By default, GA sends a GET request to the default home page of the backend service application. If the page used for health checks is not the default home page, you must specify a path.
Healthy Threshold	The number of consecutive health checks that must succeed or fail to change an endpoint's status from unhealthy to healthy or vice versa. Valid values: 2 to 10. Default value: 3.
Tag	Add tags to the endpoint group. Use a Key and Value to label and categorize the endpoint group. Tag management.
Cross-border Acceleration Settings	Read the Compliance Commitments Regarding Cross-border Data Transfers and select Agree to the Preceding Compliance Agreement. This parameter is required only if your Global Accelerator instance is used for cross-border data transfer.

Endpoint group for custom routing

Parameter	Description
Region	Select the Alibaba Cloud region for the endpoint group.
Port Mapping Range and Protocol	Enter the Port Range and Protocol. For Protocol, you can select TCP or UDP. You can also select both TCP and UDP. The endpoint group's port range and protocol map to the listener's port range. Click +Add for multiple entries (up to 20). 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)`.
Endpoint	Click Add Endpoint. In the Add Endpoint dialog box, configure the endpoint based on the following parameters, and then click OK. Backend Service Type: Only vSwitch is supported. Backend Service: Select the destination vSwitch to which traffic is forwarded. Subnet Traffic: Select a policy to control traffic flow to the vSwitch. 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.
Cross-border Acceleration Settings	Read the Compliance Commitments Regarding Cross-border Data Transfers and select Agree to the Preceding Compliance Agreement. This parameter is required only if your Global Accelerator instance is used for cross-border data transfer.

On the Configuration Review page, review the settings and click Submit. Creating a GA instance takes about 3 to 5 minutes.

What to do next

If you accelerate access to your service through a domain name, you need to configure DNS to point the accelerated domain name to the CNAME address allocated by the GA instance.

To implement traffic splitting, you can configure line-based routing policies in DNS resolution. For example, you can resolve cross-border lines to GA's CNAME address and non-cross-border lines to your service's original public IP address. This way, cross-border traffic is accelerated through GA while non-cross-border traffic connects directly, achieving traffic isolation with the two links operating independently of each other.

Create a Standard instance (subscription)

Log on to the GA console.
On the Instances page, click Create Standard Subscription Instance.

On the Create Standard Instance (Subscription) page, configure the following parameters, click Buy Now, and complete the payment.

Parameter	Description
Instance Specification	Select the specifications for the standard GA instance.
Accelerated IP Address Type	By default, subscription Standard GA instances support only the EIP type, which uses custom nearby access mode — select acceleration regions as needed. GA assigns one EIP per acceleration region.
Bandwidth Billing Method	Select the billing method for network bandwidth. Pay-By-Bandwidth is selected by default. After purchasing a GA instance with the Pay-By-Bandwidth billing method, you must associate a basic bandwidth plan.
Subscription Duration	Select the subscription duration. Select Auto-renewal. (Make sure that your account balance is sufficient.) to enable auto-renewal for the instance.
GA Instance Name	Enter a name for the GA instance.
Resource Group	Select a resource group for the standard GA instance. The group must already exist in Resource Management.
Coupon	Select whether to use a coupon. Do Not Use Coupons is selected by default. You can also select a coupon from the drop-down list.

Optional: In the GA console, choose Standard Instance > Instances. On the Instances page, view the purchased standard GA instance.

Next steps

After creating a subscription Standard GA instance, complete these steps:

Associate a basic bandwidth plan
Add an acceleration region
Add and manage an intelligent routing listener or Add and manage a custom routing listener
Add and manage an endpoint group for an intelligent routing listener or Add and manage an endpoint group for a custom routing listener
Configure a CNAME record (required when accelerating access to your service through a domain name)

Note

After purchasing a subscription Standard GA instance, follow Get started with Global Accelerator to deploy the Global Accelerator service.

Change standard instance specifications

You can upgrade or downgrade a subscription standard Global Accelerator instance.

Before you begin, review the following information:

Limitations	Effective time	Billing impact	Use cases
By default, you can only upgrade an instance. The downgrade feature is not enabled by default. To use this feature, you must apply for the Console Downgrade quota in Quota Center. For more information, see Apply for an entitlement quota. An upgrade may add new endpoint group IP addresses. The number of new IP addresses depends on the instance specification and is displayed in the console. You must manually confirm these IP addresses to make them available. You can confirm the IP addresses in the console or by calling the UpdateAcceleratorConfirm API operation. A downgrade may reduce the number of endpoint group IP addresses.	Specification changes take effect immediately but may be delayed by a few minutes due to network latency.	After you submit an upgrade order, you must pay the price difference for the remainder of the current billing cycle. A real-time downgrade may result in a refund. The refund amount is the difference between the cost of the new configuration for the remaining billing cycle and the remaining value of the previous configuration. The remaining value is affected by factors such as discounts and coupons applied at the time of purchase. The actual amount is displayed on the order page. For more information, see Refunds for resource downgrades.	Upgrade or downgrade a standard Global Accelerator instance when its current specification no longer meets your business needs.

Log on to the GA console.
On the Instances page, change the specification of a standard Global Accelerator instance.

For more information about the specifications of standard Global Accelerator instances, see Standard Global Accelerator instances.
- Upgrade the instance specification
  1. Find the instance that you want to manage and choose > Instance Management > Change Specification in the Actions column.
  2. In the Upgrade Notes dialog box, confirm the information for the Change Specification operation and click OK.
    
    Note
    The Change Specification operation supports only upgrades. To downgrade an instance, see Downgrade the instance specification.
  3. On the Change Specifications page, select the new specification, select the Terms of Service check box, and then click Buy Now and complete the payment.
  4. Check the status of the Global Accelerator instance in the Status column. If the status is Unconfirmed Endpoint Group IPs, click Confirm. In the Confirm Endpoint Group IPs dialog box, click OK.
- Downgrade the instance specification
  1. Find the instance that you want to manage and choose > Instance Management > Downgrade in the Actions column.
  2. In the Downgrade Notes dialog box, confirm the prompt for the Downgrade operation and click OK.
  3. On the Downgrade page, select the new specification, select the Terms of Service check box, and then click Buy Now and complete the payment.

More operations

More operations (pay-as-you-go)

Actions

Procedure

Update a GA instance's basic information

In the navigation pane on the left, choose Standard Instance > Instances.
On the Instances page, find the target GA instance, hover over its name, and click the icon.
In the dialog box, change the instance name and click OK.

Delete a GA instance

You can delete pay-as-you-go Standard GA instances. Complete data migration before deleting.

In the navigation pane on the left, choose Standard Instance > Instances.
In the Actions column, click > Instance Management > Delete Instance.
In the dialog box, click OK.

More operations (subscription)

Actions	Procedure
Update a GA instance's basic information	In the navigation pane on the left, choose Standard Instance > Instances. On the Instances page, find the target GA instance, hover over its name, and click the icon. In the dialog box, change the instance name and click OK.
Renew a subscription GA instance	In the navigation pane on the left, choose Standard Instance > Instances. On the Instances page, find the target GA instance. In the Actions column, click > Instance Management > Renew. On the Renew page, select a Subscription Duration, agree to the terms of service, and click Buy Now.
Replace a basic bandwidth plan	You can replace the basic bandwidth plan bound to a Global Accelerator instance without interrupting traffic. After the replacement, the original plan is unbound and the new plan is bound to the Global Accelerator instance. Before replacing a plan, ensure you have purchased a new one with bandwidth greater than or equal to the total allocated bandwidth across all acceleration areas. For more information, see Purchase a basic bandwidth plan. In the navigation pane on the left, choose Standard Instance > Instances. On the Instances page, find the target GA instance. In the Actions column, click > Basic Bandwidth Plan > Replace Basic Bandwidth Plan. In the Replace Basic Bandwidth Plan dialog box, set the following parameters, and then click OK. Resource Group: The Resource Group to which the replacement basic bandwidth plan belongs. Bandwidth Plan to Use: Select the replacement basic bandwidth plan from the drop-down list. You can select only basic bandwidth plans that are in the No Instance Associated state.
Cancel the subscription for a GA instance	You can cancel the subscription for a Standard GA instance. Before canceling, verify that the instance meets cancellation requirements and data migration is complete. Refund policy.

References

Tutorials

GA quick start:
- Accelerate access to backend services by IP address
- Accelerate access to backend services by domain name
More GA tutorials:

API reference

CreateAccelerator: Creates a Standard GA instance.
ListAccelerators: Lists Standard GA instances.
DescribeAccelerator: Describes a specified Standard GA instance.
UpdateAccelerator: Modifies a Standard GA instance.
UpdateAcceleratorConfirm: Confirms a specification change for a Standard GA instance.
DescribeAcceleratorAutoRenewAttribute: Describes the auto-renewal status of a Standard GA instance.
UpdateAcceleratorAutoRenewAttribute: Modifies the auto-renewal attribute of a Standard GA instance.