Add funds to Alibaba Cloud balance Alibaba Cloud Global Accelerator Pricing, Purchase Guide, KYC, and Setup for Cross-Region Application Access
What users usually need to decide before they click Buy
Users searching for Alibaba Cloud Global Accelerator usually already know they have a practical issue: overseas users open the site slowly, users in another region see unstable API latency, remote office access is inconsistent, or a cross-border application needs a more stable public entry point. The real decision is not whether acceleration sounds useful, but whether the account can pass review, what the service will actually cost after bandwidth and data transfer are counted, how long activation takes, and what settings must be prepared before traffic is switched.
In most cases, the first problems appear before configuration begins. Typical blockers include incomplete identity verification, unsupported payment method, insufficient account balance for postpaid resources, compliance review delay for cross-border traffic, backend service not ready for health checks, or DNS cutover planned too early. This tutorial focuses on those operational questions so you can avoid paying for a resource that remains unusable due to account or configuration issues.
| Decision area | What users care about most | Where problems usually happen |
| Account readiness | Can my account buy Global Accelerator immediately? | Real-name verification not completed, enterprise document review pending |
| Billing | Prepaid or postpaid, and what are the hidden charges? | Bandwidth and data transfer expectations are inaccurate |
| Compliance | Will cross-border traffic trigger extra review? | Business scenario, region, and content type require manual checks |
| Deployment | How do I bind backend servers and switch traffic safely? | Listener port mismatch, health check failure, DNS TTL too high |
| Operations | What happens at renewal or expiration? | Prepaid instance expires, traffic is interrupted, backend remains healthy but entry point becomes unavailable |
Preparation checklist before purchase
1. Account requirements
Before ordering Alibaba Cloud Global Accelerator, confirm the account is ready at the billing and compliance level, not just technically logged in.
- Alibaba Cloud account must be registered and able to access the international console or the account environment where Global Accelerator is sold.
- Real-name verification or enterprise verification should be completed in advance.
- If the account belongs to a company, use the company account instead of a personal account when the application serves commercial traffic. This reduces later ownership and invoicing issues.
- If multiple teams operate the account, grant RAM permissions for billing, networking, and backend resource management.
2. Identity verification and KYC checks
KYC is frequently ignored until the purchase page shows a restriction. If you expect to deploy a production service, finish verification before funding the account.
| Account type | Typical documents | Operational advice |
| Individual | ID or passport, personal details, phone/email verification | Suitable for testing, demos, and small personal projects |
| Enterprise | Business registration, company name, legal representative details, corporate contact info | Recommended for websites, APIs, SaaS platforms, and any service needing stable billing records |
Common KYC review issues include mismatch between account name and payment instrument, unclear uploaded documents, incomplete business registration information, or a billing contact from a different entity. If your order is urgent, submit verification at least one business day before purchase.
3. Funding, payment, and renewal planning
Users often ask whether they need to preload the account. In practice, the answer depends on the billing model and your payment setup.
- For prepaid purchases, make sure the available balance or attached payment method can cover the full subscription term.
- For postpaid charges, verify that the account has a valid payment method or enough balance to avoid overdue suspension.
- For enterprises, confirm internal procurement rules: some teams can purchase only prepaid resources with approved budget codes.
Typical payment methods vary by account region and billing entity, but usually include credit card and account balance. Some enterprise accounts may use contract billing arrangements, but this must be enabled in advance and cannot be assumed at checkout.
4. Permission requirements
If the person creating Global Accelerator is not the primary account owner, grant permissions for:
- Global Accelerator resource creation and management
- Elastic IP, SLB, ECS, and backend service viewing or binding
- Billing center access for renewal and invoice checking
- DNS management if domain cutover will happen immediately after testing
5. Required backend resources
Add funds to Alibaba Cloud balance Do not start with the accelerator. Start with a ready backend.
| Resource | Required status | Why it matters |
| ECS or origin server | Reachable on target port | Listener forwarding will fail if the origin is not already serving traffic |
| SLB/ALB/NLB | Healthy listener already configured | Best option when you want to separate acceleration from backend scaling |
| Domain name | DNS access available | Needed for production traffic cutover |
| SSL certificate | Ready if HTTPS is used | Avoids deployment delays after listener creation |
Step-by-step: purchase and deploy Alibaba Cloud Global Accelerator
Step 1: Review account eligibility before entering the product page
Log in to the Alibaba Cloud console, then check three places before opening the Global Accelerator purchase screen.
- Add funds to Alibaba Cloud balance Billing Center: confirm there are no overdue invoices or suspended services.
- Account Center: verify identity status shows approved rather than pending review.
- Quota or service availability pages: confirm Global Accelerator can be purchased in your current account environment.
If the account is new and has no payment history, some orders may trigger additional review. This is more likely when you immediately order cross-border networking products, higher-spec bandwidth plans, or multiple resources in a short time.
Add funds to Alibaba Cloud balance Step 2: Open the Global Accelerator console and create an instance
In the console, go to the networking or global networking category and open Global Accelerator. Click Create Instance or Buy Now, depending on the console version.
At this stage, pay attention to the following fields:
| Field | How to choose | Notes |
| Billing method | Prepaid for predictable stable workloads, postpaid for short-term validation or variable traffic | Postpaid can look cheaper initially but may exceed budget under high transfer volume |
| Service duration | 1 month for testing, longer subscription for steady production use | Longer terms reduce renewal operations but increase commitment |
| Acceleration area | Select according to user locations, not server location only | Wrong area selection can reduce the expected improvement |
| Bandwidth plan | Size according to peak concurrent traffic and protocol type | Many users underestimate HTTPS and file-download traffic |
Where to click: on the buy page, first set the billing method, then choose acceleration coverage and bandwidth plan, review price details, and proceed to payment. Save a screenshot of the selected parameters before submitting. This helps later if finance asks why cost changed after the first month.
Step 3: Complete payment and wait for compliance or risk review if triggered
After clicking Pay, the order may be activated immediately or placed under review. Users often assume payment success means the instance is ready, but this is not always true.
Possible order states:
- Paid and active: you can continue to configuration immediately.
- Paid but under review: risk control, KYC verification, or compliance checks are still pending.
- Payment failed: balance insufficient, card declined, or billing method not permitted.
If the order remains pending, collect these details before opening a support ticket:
- Order number
- Account UID
- Business scenario description
- Planned source user regions and backend deployment region
- Whether content includes regulated sectors or restricted traffic types
Step 4: Configure the accelerator instance
After activation, open the instance details page and create the forwarding configuration.
Typical operation sequence:
- Create or select the acceleration instance.
- Add a listener.
- Add funds to Alibaba Cloud balance Choose protocol such as TCP, UDP, or HTTP/HTTPS depending on your application.
- Enter the frontend listening port.
- Add backend endpoint groups.
- Bind backend endpoints such as ECS, SLB, or custom IP.
- Set health checks.
- Review and save.
Important considerations:
- The listener port must match the service your backend is actually exposing.
- If you are accelerating HTTPS and terminating TLS at the backend, confirm certificates are already installed there.
- For custom origin IPs, make sure the backend firewall allows traffic from the relevant Alibaba Cloud access path.
Step 5: Add endpoint groups and backend servers
This is the step where users most frequently encounter health check errors. In the endpoint group section, specify the region of the backend service and add one or more endpoints.
| Backend type | Recommended use | Typical mistake |
| ECS instance | Single application server or small cluster | Security group blocks listener port |
| SLB/ALB/NLB | Production applications with multiple servers | Selecting the wrong existing listener |
| Custom IP | On-premises or third-party server | Origin IP reachable from internet but application only allows internal source IPs |
When entering parameters, use the backend port that is already tested locally. Do not change the application port just to match a desired external port. Keep frontend and backend mapping explicit.
Step 6: Configure health checks carefully
Health checks determine whether traffic is sent to the backend. A working server can still fail health checks if the path, protocol, or timeout is wrong.
| Parameter | Practical recommendation | Troubleshooting tip |
| Check protocol | Use TCP for simple port reachability, HTTP/HTTPS for application-level confirmation | If HTTP health checks fail but TCP succeeds, inspect URL path and HTTP status code |
| Check path | Use a lightweight endpoint such as /healthz or /status | A login redirect or 403 page may cause false unhealthy status |
| Interval | 5-10 seconds for critical services, longer for low-priority workloads | Very aggressive intervals may increase noise during maintenance |
| Timeout | At least above normal backend response time | If cross-region origin is slow under load, a short timeout causes intermittent unhealthy marking |
Step 7: Test before DNS cutover
After the listener is active, obtain the accelerated access address and test from the target user region.
- Use curl for HTTP/HTTPS verification.
- Add funds to Alibaba Cloud balance Use telnet or nc to confirm the listener port is open for TCP services.
- Measure latency from different regions using external probes or your own distributed clients.
- Check origin logs to confirm requests are reaching the expected backend.
Only after validating latency, HTTP status, and session behavior should you update DNS. Lower the DNS TTL several hours in advance if you are replacing an existing production endpoint.
Step 8: Set renewal reminders and billing monitoring immediately
This step is often skipped and later causes avoidable outages. After deployment, go to Billing Center and configure:
- Auto-renew if the workload is production and prepaid
- Add funds to Alibaba Cloud balance Balance alerts or spending alerts if the resource uses postpaid components
- Monthly budget review for traffic-heavy applications
For team environments, send renewal notices to both technical owners and finance contacts. A prepaid networking service expiring during a holiday weekend can interrupt healthy backend systems even when servers themselves are fully operational.
How to estimate actual cost before you place the order
The most common purchasing mistake is comparing only the displayed base price. For cross-region application access, total cost usually depends on more than the accelerator instance alone.
| Cost component | What to check | Why users miss it |
| Instance fee | Subscription or usage fee for the accelerator | Visible on the order page, so users focus on it too much |
| Bandwidth plan | Peak bandwidth needed during busy periods | Users estimate average traffic, not burst traffic |
| Data transfer | Cross-region or international usage volume | Often changes sharply after launch |
| Backend charges | ECS, SLB, EIP, disk, and outbound traffic | Acceleration improves traffic intake, which can increase backend bills |
| Certificate or DNS related cost | If HTTPS and managed DNS services are involved | Added later during production go-live |
Cost comparison by billing approach
| Scenario | Recommended billing | Reason |
| Short proof-of-concept under 2 weeks | Postpaid if available | Avoids overcommitting before measurement |
| Stable SaaS or website traffic | Prepaid plus scheduled review | Better budget predictability |
| Seasonal traffic spikes | Mixed approach with conservative base capacity | Reduces idle spend in low seasons |
| Cross-border expansion with unknown growth | Start small, monitor transfer cost weekly | Traffic behavior is hard to estimate during market entry |
A practical estimate method is to calculate three traffic bands: normal weekday average, expected marketing peak, and failure scenario where users retry heavily because origin performance degrades. If your pricing model includes transfer-related cost, the third band often surprises teams more than the first two.
Configuration recommendations by real usage scenario
For individual developers
If you are testing an overseas demo site, game launcher, or personal API, keep the initial architecture simple. Use one accelerator entry, one backend group, and one tested ECS or ALB listener. Prefer short subscription periods or postpaid where available. Do not purchase large bandwidth immediately. Validate performance from the target user region first, then expand.
For enterprise users
Use an enterprise-verified account, separate billing ownership from daily operations through RAM roles, and attach backend load balancing instead of binding a single ECS instance directly. Plan renewals centrally. Keep screenshots or exported configuration records for procurement and audit review. If traffic serves multiple business units, tag resources and align them to cost centers from day one.
For cross-border businesses
This is where compliance and account review matter most. Prepare a brief written description of your business model, user geography, deployed regions, and content type. If your service includes logins, payments, or data-sensitive workloads, involve legal or compliance stakeholders before final cutover. Technically, test from real target countries rather than relying only on ping tests from cloud VMs in nearby regions.
For website applications
Use HTTP or HTTPS listeners with a dedicated health check path such as /healthz. Lower DNS TTL before migration. If the website already uses a CDN, define the order of optimization clearly: CDN for static caching, Global Accelerator for better entry routing and stable access to dynamic requests. Do not point the accelerator to an origin that is already overloaded; acceleration cannot compensate for exhausted backend CPU or disk I/O.
For database-related workloads
Do not expose databases directly to the public accelerator entry unless there is a very specific and controlled requirement. For MySQL, Redis, or other database traffic, use private connectivity, bastion access, or application-layer proxying where possible. If acceleration is required for database-adjacent APIs, accelerate the application service rather than the raw database endpoint. This reduces attack surface and simplifies permission control.
Account restrictions, compliance review, and risk control checks
Users planning a fast deployment often underestimate service restrictions. Common controls include account age checks, unusual purchase behavior, mismatch between declared business type and intended traffic pattern, and region-specific compliance review.
| Restriction type | Typical symptom | Action |
| KYC incomplete | Buy button disabled or order blocked | Complete identity verification first |
| Payment risk control | Card charged unsuccessfully or order held | Use a verified payment method, check bank approval, contact billing support |
| Compliance review | Order remains pending after payment | Provide business scenario and requested documents promptly |
| Quota limit | Cannot create additional instances or listeners | Request quota increase in advance |
| Restricted traffic usage | Service not approved for intended scenario | Confirm acceptable use and regional policy before deployment |
If your service handles regulated content, financial data, gaming, media distribution, or international user traffic across multiple legal jurisdictions, expect stricter reviews than a simple static corporate website.
Troubleshooting common purchase and deployment failures
Order paid but instance not usable
Check whether the order is in review status instead of active status. Then verify account messages, email notices, and support center requests for additional documents. Do not create duplicate orders unless support confirms the first one failed permanently.
Cannot bind backend server
Common causes include missing permission to view backend resources, wrong region selected for the endpoint group, unsupported backend type in the current configuration, or the backend listener not created yet. Test the backend independently first.
Health check fails immediately
Verify the backend firewall, ECS security group, and operating system firewall all allow the target port. For Linux, check commands such as ss -lntp, ufw status, or firewall-cmd --list-ports. For Windows, verify the inbound rule in Windows Defender Firewall and confirm the service listens on the expected interface.
Users still reach the old endpoint after DNS change
This is usually not an accelerator problem. Check DNS TTL, local resolver cache, enterprise proxy cache, or CDN origin configuration. Use multiple public DNS resolvers to confirm propagation.
Latency did not improve enough
Measure end-to-end application time, not just ICMP latency. If TTFB is still high, the bottleneck may be backend processing, slow database queries, or TLS handshake delay at origin. Also review whether the selected acceleration area matches your actual user distribution.
FAQ
Q1: Do I need enterprise verification to buy Alibaba Cloud Global Accelerator?
A: Not always, but enterprise verification is usually the safer choice for production workloads. Personal accounts may be sufficient for testing, but enterprise accounts reduce later issues with billing ownership, invoice management, and compliance review for commercial traffic.
Q2: Why did my order go into review after payment?
A: Common reasons include incomplete KYC, first-time purchase of networking products, unusual payment pattern, cross-border use case requiring compliance confirmation, or account risk control checks. Gather the order number, account UID, and a short business description before contacting support.
Q3: Which is better for cost control, prepaid or postpaid?
A: Prepaid is better when your traffic is stable and you want predictable monthly or annual budgeting. Postpaid is better for testing or uncertain demand, but it requires closer monitoring because transfer-related charges can rise quickly during peaks.
Q4: What payment methods are usually available?
Add funds to Alibaba Cloud balance A: In most account environments, users rely on account balance and credit card. Some enterprise arrangements may support invoicing or contractual billing, but that depends on prior account setup and cannot be assumed during a new purchase.
Q5: Why can the accelerator listener be created but the service is still unreachable?
Add funds to Alibaba Cloud balance A: Usually because the backend port is blocked, the health check marks the backend unhealthy, the origin service is bound to the wrong interface, or DNS still points to the old endpoint. Check listener port mapping, security groups, operating system firewall, and backend service status.
Q6: What should I prepare before renewal time?
A: Confirm auto-renew settings, valid payment method, sufficient balance, and alert recipients. Also review whether the existing bandwidth plan still matches demand; renewal is a good time to right-size the instance instead of blindly extending the current configuration.
Q7: Is Global Accelerator enough to solve slow overseas website access?
A: Not by itself. It improves access path quality, but you still need a healthy backend, efficient application code, reasonable database latency, and possibly CDN for static resources. Treat it as one layer in the delivery path, not the entire optimization plan.
Optimization recommendations after deployment
Security optimization
- Use enterprise accounts and RAM roles instead of sharing the root account.
- Add funds to Alibaba Cloud balance Restrict backend origin exposure where possible; allow only required traffic paths.
- Do not accelerate raw database ports to the public internet unless there is a controlled and audited reason.
- Review TLS configuration and certificate validity before large-scale cutover.
Performance optimization
- Test from actual user regions using application-level metrics such as TTFB and transaction response time.
- Use load balancers as backend targets for scalable production applications.
- Tune health checks so they detect real failures without causing false negatives during temporary load spikes.
- Separate static and dynamic optimization strategy; use CDN where caching is appropriate.
Cost optimization
- Start with measured bandwidth rather than assumed marketing estimates.
- Review weekly transfer trend in the first month after launch.
- Use prepaid only when traffic is reasonably stable and approved by budget owners.
- Tag resources and associate them with applications or departments for internal chargeback.
Stability optimization
- Bind redundant backend endpoints or use an existing load balancer.
- Lower DNS TTL before planned migration so rollback remains possible.
- Enable renewal reminders for both technical and finance teams.
- Keep a written rollback plan: old DNS record, backend direct endpoint, and support contact path.
If your goal is to improve cross-region application access with Alibaba Cloud Global Accelerator, the main success factor is not just buying the service. It is buying it with the correct account type, passing verification early, selecting a billing model that fits your traffic pattern, preparing a compliant business description if needed, and validating backend readiness before DNS cutover. That sequence prevents most delays users face in real deployments.

