Deploy Acceleration Services with Global Accelerator (GA)

Create a GA instance from scratch and complete end-to-end configuration (Instance -> Acceleration Region -> Listener -> Endpoint Group -> Forwarding Rules) to enable global network acceleration for your services.

1. Scenario Overview

1.1 Applicable Scenarios

• - Cross-border Web/API acceleration: Overseas users accessing domestic web services, or domestic users accessing overseas services
• Global gaming acceleration: Reduce cross-region latency and improve player experience
• Audio/video transmission acceleration: Optimize cross-region real-time audio/video communication
• Enterprise application acceleration: Accelerate cross-border enterprise internal system access

1.2 Architecture

CODEBLOCK0

CODEBLOCK1

Products involved: GA + Certificate Management Service (for HTTPS scenarios)

1.3 Customer Value

• - Leverage the Alibaba Cloud global transmission network to significantly reduce cross-region access latency
• Complete end-to-end configuration in a single session to quickly enable Global Accelerator

---

2. Installation

Pre-check: Aliyun CLI >= 3.3.1 required
Run aliyun version to verify >= 3.3.1. If not installed or version too low, see references/cli-installation-guide.md for installation instructions.
Then [MUST] run the following to enable automatic plugin installation:
CODEBLOCK2

---

3. Authentication

Pre-check: Alibaba Cloud Credentials Required
Security Rules:

• - NEVER read, echo, or print AK/SK values (e.g., echo $ALIBABA_CLOUD_ACCESS_KEY_ID is FORBIDDEN)
• NEVER ask the user to input AK/SK directly in the conversation or command line
• NEVER use aliyun configure set with literal credential values
• ONLY use aliyun configure list to check credential status

> aliyun configure list --user-agent AlibabaCloud-Agent-Skills
> 

Check the output for a valid profile (AK, STS, or OAuth identity).
If no valid profile exists, STOP here.

1. 1. Obtain credentials from Alibaba Cloud Console
2. Configure credentials outside of this session (via aliyun configure in terminal or environment variables in shell profile)
3. Return and re-run after aliyun configure list shows a valid profile

---

4. RAM Policy

This skill requires the following RAM permissions. See references/ram-policies.md for the complete list.

---

5. GA Service Activation Check

Pre-check: GA service must be activated
Before performing any GA operation, you must confirm that the Global Accelerator service has been activated.

> aliyun ga DescribeAcceleratorServiceStatus --region cn-hangzhou --user-agent AlibabaCloud-Agent-Skills
> 

Check the Status field in the response:

• - Normal: The service is activated. Proceed with subsequent steps.
• Other statuses: The service is not activated. Activate it first:

> aliyun ga OpenAcceleratorService --region cn-hangzhou --user-agent AlibabaCloud-Agent-Skills
> 

After activation, re-run DescribeAcceleratorServiceStatus to confirm the status is Normal, then proceed.
If the service is not activated and activation fails, STOP here.

---

6. Parameter Confirmation

Important: Parameter Confirmation -- Before executing any command or API call,
all user-configurable parameters must be confirmed with the user.
Do not assume or use default values without the user's explicit consent.

Parameter	Required	Description	Default
AcceleratorName	Optional	GA instance name	-
AccelerateRegionId

Required | Acceleration region ID (region where users access) | - | | IspType | Optional | ISP line type for the acceleration region | China (Hong Kong): BGP_PRO, Others: BGP | | Bandwidth | Required | Acceleration region bandwidth (Mbps) | - | | ListenerProtocol | Optional | Listener protocol: TCP/UDP/HTTP/HTTPS | HTTPS | | ListenerPort | Optional | Listener port | 443 | | CertificateId | Conditional | SSL certificate ID (HTTPS listeners only) | - | | EndpointGroupRegion | Required | Endpoint group region (region of the origin server) | - | | EndpointType | Required | Endpoint type | - | | Endpoint | Required | Endpoint address (IP/domain/instance ID) | - | | EndpointPort | Optional | Endpoint port | Same as listener port | | CrossBorder | Required | Whether cross-border acceleration is involved | - | | CrossBorderMode | Required | Cross-border mode: private or bgpPro | private (recommended for production) |

Supported endpoint types: Domain (Custom Domain) / Ip (Custom IP) / ECS / SLB (CLB) / ALB / NLB / OSS

---

7. Core Workflow

7.1 Prerequisites and General Rules

Blocking requirement: Before entering the workflow, you MUST use the Read tool to fully read the following files. No steps may be executed until reading is complete.

• - references/important-notes.md -- GA defaults, constraints, and common pitfalls
• references/related-apis.md -- API list and CLI parameter formats

Scope constraints (strictly enforced):

• - Instance type and billing restriction: This skill can ONLY create pay-as-you-go (postpay) + CDT Standard GA instances. Creating prepaid (subscription) Standard instances or Basic GA instances of any billing mode is FORBIDDEN. Calling CreateBasicAccelerator is FORBIDDEN. If the user requests a prepaid instance or a Basic instance, inform them that this skill does not support it and suggest creating it manually via the Alibaba Cloud Console.
• New instances by default: This skill defaults to creating and configuring new GA instances. Modifying, updating, or deleting existing GA instances or their sub-resources (acceleration regions, listeners, endpoint groups, forwarding rules, etc.) is only permitted when the user explicitly specifies the target GA instance ID to operate on. Without an explicit user instruction identifying a specific existing instance, all operations MUST target newly created instances only.
• GA product boundary: Write operations (create/update/delete) are limited to the GA product only. For all other Alibaba Cloud products and services (e.g., CAS, CMS, ECS, SLB, ALB, NLB, OSS), only read-only (Describe/List/Get/Query) operations are permitted. Any non-read-only operation on other products is FORBIDDEN.

General rules (apply throughout the entire workflow):

• - User-Agent requirement [MANDATORY]: ALL aliyun CLI commands (including ga, sts, cas, cms, and any other Alibaba Cloud service calls) MUST include --user-agent AlibabaCloud-Agent-Skills. This flag must be appended to every CLI invocation without exception. Commands missing this flag are non-compliant.
• Parameter confirmation: All user-configurable parameters must be confirmed with the user before execution. Do not assume or use default values.
• Status check: After each creation step, query the instance status and wait until it becomes active before proceeding to the next step.
• API metadata validation: Before generating CLI commands, use WebFetch to retrieve API metadata and verify parameter accuracy.

URL: INLINECODE38

7.2 Interaction Flow

CODEBLOCK6

7.3 API Execution Order

Call the following APIs in order to create resources. After each step, wait for the instance status to become active:

CODEBLOCK7

7.4 Cross-border Configuration Key Points

Cross-border mode MUST be set before creating IpSets/Listeners. Do not skip or defer this step.

Mode selection:

Mode	Description	Applicable Scenario
INLINECODE40 (Private cross-border)	Higher quality, lower cost	Recommended for production
INLINECODE41 (BGP Premium cross-border)

Temporary alternative | Use only when private fails due to compliance review |

Execution steps:

1. 1. Enable cross-border acceleration: INLINECODE43
2. Immediately set the cross-border mode: INLINECODE44
3. Confirm approval status: INLINECODE45

Fallback handling:

If switching to private fails (e.g., cross-border compliance review has not been approved), inform the user:
*"Switching cross-border mode to private is pending compliance approval. Currently using bgpPro (BGP Premium).
Please complete the cross-border compliance review, then re-run UpdateAcceleratorCrossBorderMode --CrossBorderMode private."*

Post-deployment check:

After all resources are created, call DescribeAccelerator to check the current cross-border mode. If the mode is not private, attempt to switch:

CODEBLOCK8

If it still fails, inform the user:
"The current cross-border mode is bgpPro (BGP Premium). It is recommended to switch to private (Private cross-border) mode after the cross-border compliance review is approved for better performance and stability."

---

8. Verification

Quick Verification

CODEBLOCK9

Acceleration Performance Testing

Must read: When performing acceleration performance testing or latency comparison, use the Read tool to read references/acceleration-test-guide.md and select the appropriate test method based on the listener protocol:

• - HTTP: curl output time_connect / time_starttransfer / INLINECODE56
• HTTPS: curl output time_connect / time_appconnect / time_starttransfer / INLINECODE60
• TCP (non-HTTP): curl with telnet:// protocol
• UDP: scripts/udping.py -c 10 <ip> <port> -- requires a UDP Echo Server running on the origin server

You must compare non-accelerated (direct to origin server) and accelerated (through GA) results.

---

9. Cleanup

CODEBLOCK10

---

10. API and Command Reference

See references/related-apis.md for the complete API list and CLI parameter formats.

Note: GA APIs use RPC-style PascalCase naming. Nested array parameters require dot notation + --method POST --force.

---

11. Important Notes

All important operational notes, constraints, defaults, and common pitfalls are maintained in references/important-notes.md.
You must fully read important-notes.md before starting the deployment workflow. It contains critical information on billing, cross-border configuration, status management, and parameter formats that directly affect deployment success.

---

12. Best Practices

1. 1. Gather before configuring -- Fully understand the business requirements before planning configuration
2. Confirm all parameters -- All user-configurable parameters must be confirmed before execution
3. Check status after each step -- After each creation operation, wait for the instance status to become INLINECODE64
4. Prefer private cross-border mode -- Use private mode whenever possible for cross-border scenarios
5. Isolate endpoint groups -- Use separate endpoint groups + forwarding rules for different domains/services
6. Verify after deployment -- Perform end-to-end configuration verification and connectivity testing after deployment

---

13. Reference Documents

Document	Description
references/important-notes.md	Must read -- GA defaults and common pitfalls
references/related-apis.md

API and CLI command reference | | references/ram-policies.md | RAM permission policies | | references/acceleration-test-guide.md | Acceleration performance testing guide | | GA Official Documentation | Global Accelerator official documentation | | GA OpenAPI Explorer | Online API debugging |