Alibaba Cloud global account signup discount Alibaba Cloud VPN Gateway Pricing, Purchase, KYC, Billing, and Setup Guide for Site-to-Site VPN and Remote Access
What users usually want to know before they place an order
Most users searching for Alibaba Cloud VPN Gateway are not looking for a generic explanation of what a VPN is. They are usually trying to answer operational questions such as: Can my account buy this product today? Do I need identity verification first? Which payment method is accepted in my region? Why is my order blocked by compliance review? Which specification should I choose for a branch office tunnel versus remote employee access? After I pay, what exact configuration steps are needed to bring the tunnel up?
In real projects, the biggest delays rarely come from the tunnel configuration itself. They usually happen earlier during account setup, KYC review, payment settlement, region mismatch, or later when routes and security rules are incomplete. This guide is structured around those real decision points so you can move from account preparation to production connectivity with fewer failed orders and fewer tunnel-down incidents.
Typical usage scenarios behind this search
| Scenario | What the user is trying to do | Most likely problem point |
| Headquarters to Alibaba Cloud VPC | Build site-to-site IPsec connectivity between on-premises firewall and VPC | Wrong peer IP, mismatched IKE/IPsec parameters, missing routes |
| Remote employee access | Allow users to connect securely to private cloud resources | SSL-VPN client address pool conflict, certificate distribution, authorization rules |
| Multi-region branch access | Connect offices in different countries or regions | Region purchase availability, latency, compliance review |
| Short-term project environment | Deploy a temporary VPN for migration or testing | Buying a subscription period that does not match project duration |
| Production website and database access | Protect admin traffic to ECS, RDS, Redis, or internal apps | Security group, firewall, private route, and DNS resolution issues |
Preparation before purchase
Alibaba Cloud global account signup discount Account requirements
Alibaba Cloud global account signup discount Before you open the buy page, verify that the account can actually complete the order and manage networking resources.
- Alibaba Cloud account must be registered and able to sign in to the console.
- If you are using a RAM user, confirm the user has permissions for VPC, VPN Gateway, route tables, SSL certificates if used, and billing visibility.
- If the environment belongs to a company, use a dedicated owner account for purchase and delegate daily operations through RAM users instead of sharing the root account.
Identity verification and KYC
Identity verification is often the first operational blocker. Depending on account type and country, you may be asked for personal verification or enterprise verification before some networking products can be purchased or before account limits are increased.
| Verification item | What to prepare | Common delay reason |
| Individual verification | Government-issued ID, matching account name, contact information | Uploaded image unclear or account profile name mismatch |
| Business verification | Company registration documents, authorized contact, company address | Legal entity name mismatch or incomplete company documents |
| Payment verification | Valid card or funded balance | Payment method rejected by bank or card risk checks |
Practical advice: complete KYC before project cutover week. If you wait until the deployment window, any manual review can delay procurement and go-live.
Funding, billing, and payment preparation
Depending on your billing mode and region, you may pay by credit card, debit card in supported regions, bank transfer, account balance, or invoiced enterprise settlement where available. The accepted payment methods vary, so check the checkout page for your account and billing country rather than relying on third-party screenshots.
Before ordering, check these four items:
- Whether the product is billed as subscription, pay-as-you-go, or both in your target region.
- Whether your account balance is sufficient if prepaid balance is required.
- Whether auto-renewal is enabled, especially for production VPN connections.
- Whether the finance team needs tax invoice information before payment.
Technical prerequisites
Alibaba Cloud global account signup discount Collect the network values before opening the console. Most failed configurations come from missing or conflicting values.
| Required item | Example | Why it matters |
| Alibaba Cloud region | Singapore, Frankfurt, US East | Determines latency, availability, and product availability |
| VPC CIDR block | 172.16.0.0/16 | Used in route exchange and must not overlap with on-premises network |
| vSwitch CIDR | 172.16.1.0/24 | Affects subnet routing and workload placement |
| On-premises gateway public IP | 203.0.113.10 | Required to create the customer gateway |
| On-premises CIDR | 10.20.0.0/16 | Used in VPN route configuration |
| IKE version and crypto policy | IKEv1 or IKEv2, AES256, SHA256, DH14 | Must match both ends or tunnel negotiation fails |
| Pre-shared key | Strong random string | Authentication between peers |
| NAT-T requirement | Yes or No | Important if on-premises gateway is behind NAT |
Step-by-step: buying Alibaba Cloud VPN Gateway correctly
Step 1: Select the region and confirm product availability
In the Alibaba Cloud console, go to the networking section and open VPN Gateway. Select the region first. Do not assume you can buy in one region and attach it to a VPC in another region. VPN Gateway is region-specific and should be deployed in the same region as the VPC you want to access.
Important checks before clicking buy:
- Confirm that your ECS, RDS, Redis, or internal applications are in the same region.
- For cross-border access, test latency from your office or branch network to the region by ping, TCP connect, or an existing public IP in the same geography.
- Make sure the region meets your data residency or internal compliance requirements.
Step 2: Choose billing mode and service duration
On the purchase page, choose the billing model available to your account. For steady production environments, subscription often gives more predictable budgeting. For short migration projects or proof-of-concept work, a flexible billing mode may be more suitable if supported.
When selecting duration:
- Choose 1 month only for short-lived projects or testing.
- Choose longer subscription periods if the tunnel is business-critical and budget approval is already in place.
- Enable auto-renewal for production so the VPN does not expire unexpectedly during a weekend or holiday.
A common mistake is buying a short term manually and forgetting the expiration date. If the VPN Gateway expires, site-to-site traffic and remote admin access can drop immediately.
Step 3: Select specification and feature set
On the configuration page, choose the VPN Gateway specification that matches expected throughput and connection count. If your use case includes only one branch firewall and a few internal services, you may not need a high specification. If the gateway will terminate multiple branch tunnels or carry backup replication traffic, choose a higher tier.
| Workload type | Recommended purchase logic | Risk if undersized |
| Single office to VPC | Start with an entry or mid-level spec based on expected peak traffic | Tunnel works but bandwidth becomes a bottleneck during backup or file sync |
| Remote admin access for a small team | Prioritize SSL-VPN user capacity and concurrent sessions | User login failures or unstable remote desktop sessions |
| Multiple branches | Choose a spec with enough concurrent tunnels and future growth margin | Frequent redesign when a second or third site is added |
| Database replication or migration | Prioritize stable throughput and avoid the smallest tier | Long migration windows and application lag |
Step 4: Review payment and submit the order
At checkout, confirm account balance, tax settings, coupon or discount applicability if any, and whether the payment method triggers bank verification. If the order fails after submission, the most common causes are insufficient balance, unsupported payment method for the account location, or fraud/risk screening by the payment processor.
If your order enters manual review:
- Check the registered email and console notifications for document requests.
- Make sure account name, payment name, and company verification data are consistent.
- Do not repeatedly create multiple failed orders in a short period. That can trigger additional automated risk checks.
Step-by-step: configure site-to-site VPN after purchase
Step 1: Prepare VPC, vSwitch, and route information
In the VPC console, identify the target VPC and note its CIDR block. If the cloud and on-premises networks overlap, the tunnel may establish but traffic routing will fail or become ambiguous. Resolve overlapping CIDR blocks before deployment whenever possible.
Then check route tables:
- Confirm the workloads you want to access are inside the VPC and subnets you expect.
- Document the route table associated with each vSwitch.
- Alibaba Cloud global account signup discount If using custom route tables, verify you will add the on-premises destination route after the VPN connection is created.
Step 2: Create the customer gateway
In the VPN Gateway console, click the option to create a customer gateway. Enter the public IP address of your on-premises firewall or VPN device. Name it clearly, such as hq-fw-sg-01 or branch-london-edge.
Considerations:
- The IP must be the actual public peer seen by Alibaba Cloud.
- If your firewall is behind NAT, verify whether NAT traversal is supported and enabled.
- If the public IP changes often, use a static IP before production rollout. Dynamic peer IP changes create recurring outages.
Step 3: Create the IPsec-VPN connection
Click to create an IPsec-VPN connection and select the VPN Gateway you purchased and the customer gateway you just created. Enter the local and remote CIDR blocks exactly as planned. Then configure IKE and IPsec parameters.
| Parameter | Example value | Notes |
| Remote network | 10.20.0.0/16 | On-premises CIDR |
| Local network | 172.16.0.0/16 | VPC CIDR |
| Pre-shared key | 24 to 32+ random characters | Avoid dictionary words |
| IKE version | IKEv2 | Often preferred for interoperability |
| Encryption | AES-256 | Must match on both sides |
| Authentication | SHA-256 | Must match on both sides |
| DH group | Group 14 | Check firewall support |
| PFS | Enabled, Group 14 | Optional but recommended if supported |
| NAT-T | Enabled if needed | Required when peer is behind NAT |
Typical tunnel-up failure causes at this step:
- One side uses IKEv1 and the other uses IKEv2.
- Encryption or authentication algorithms do not match.
- On-premises firewall local/remote subnet definitions are reversed.
- The public IP entered in the customer gateway is outdated.
- UDP 500 and UDP 4500 are blocked by an upstream firewall.
Step 4: Add or verify routes
After creating the IPsec connection, check whether routes are propagated automatically in your design. If not, manually add a route in the VPC route table so the destination on-premises CIDR points to the VPN Gateway. On the on-premises side, add a static route or equivalent policy so the VPC CIDR is sent through the tunnel.
If routes are wrong, the tunnel may show as connected but traffic still fails. This is one of the most common operational misunderstandings.
Step 5: Configure security groups and host firewalls
Even with a healthy tunnel, ECS instances and databases may remain inaccessible if security groups or operating system firewalls block the traffic.
| Target service | Common port | What to check |
| Linux SSH | 22 | ECS security group inbound rule from on-premises CIDR, firewalld or iptables |
| Windows RDP | 3389 | Security group rule, Windows Defender Firewall, NLA settings |
| MySQL | 3306 | RDS whitelist or ECS security group, database bind address |
| Redis | 6379 | Private access settings, auth config, security group |
| HTTPS app | 443 | Web server listener, certificate deployment, security group |
For Linux ECS, useful checks include commands such as ss -lntp, firewall-cmd --list-all, and ip route. For Windows, use Test-NetConnection in PowerShell to verify reachability from a client host.
Step-by-step: configure remote access with SSL-VPN
Step 1: Enable SSL-VPN on the purchased gateway
In the VPN Gateway console, open the gateway instance and choose the SSL-VPN related configuration. Create a server configuration and define the client address pool. This address pool must not overlap with your VPC CIDR, office LAN, home user subnet, or any peered network.
Example:
- VPC CIDR: 172.16.0.0/16
- Office LAN: 10.20.0.0/16
- Home LAN often used by users: 192.168.1.0/24
- Suggested SSL-VPN client pool: 10.250.0.0/24
Step 2: Define access permissions
Specify which VPC subnets or internal resources remote users can reach. Do not grant broad access to all ports and all internal networks unless there is a strong reason. If users need only bastion host access or private Git access, restrict to those subnets and ports.
Step 3: Download client configuration and distribute securely
Generate or download the client profile and any required certificates from the console. Distribute them through a controlled internal method, not through public file sharing or personal chat tools. Track who received client profiles and revoke them when employees leave or contractors finish work.
Step 4: Test end-user connectivity
After the client connects, test in this order:
- Can the client reach the private IP of an ECS instance by ping or TCP connect if ICMP is blocked?
- Can the user resolve internal DNS names if required?
- Can the user reach SSH, RDP, HTTPS, MySQL, or Redis only according to the allowed policy?
If the client connects but cannot access internal services, check route push settings, client local firewall, VPC route tables, and ECS security groups.
Purchasing, billing, and compliance questions that often delay projects
Identity verification not completed
If the console allows sign-in but blocks purchase or activation, complete the account verification workflow first. Some users create a new account on deployment day and assume payment alone is enough. In practice, networking services may still require validated identity details.
Payment method rejected
If a card fails, verify:
- The card supports international or online B2B transactions.
- Alibaba Cloud global account signup discount The billing address matches what the issuer expects.
- The bank is not blocking the transaction as suspicious.
- The account owner country and payment instrument country do not create a mismatch requiring manual review.
Order submitted but service unavailable
This can happen due to risk review, unpaid order timeout, or region-specific stock or policy restrictions. Check the order status in the billing center, not only the product page.
Renewal concerns
Production VPNs should not rely on manual renewal reminders. Use auto-renewal where possible and set internal alerts 30 days, 7 days, and 1 day before expiration. Also confirm the payment source for renewal is still valid. A replaced corporate card can silently break auto-renewal.
Cost comparison and configuration recommendations
How to evaluate cost realistically
Do not compare VPN Gateway cost using only the listed instance price. Include these components:
- VPN Gateway instance fee
- Internet bandwidth or related egress charges if applicable to your design
- Cross-region or cross-border traffic implications
- Operational cost of managing certificates, routes, and monitoring
- Potential cost of downtime if the gateway is undersized or manually renewed
Practical recommendations by scenario
| Scenario | Purchase and configuration advice | Cost control advice |
| Individual developer | Use the smallest specification that supports one tunnel or a light SSL-VPN workload, short subscription if testing | Avoid overbuying throughput; shut down temporary related resources after tests |
| Enterprise user | Choose a production-grade spec, enable renewal controls, use RAM for operation delegation | Standardize one approved region and review annual subscription options |
| Cross-border business | Test latency from each branch before selecting region, confirm compliance and data flow policies | Place workloads closer to users to reduce network inefficiency and repeated redesign |
| Website application | Use VPN mainly for admin access, database management, or origin protection rather than public web delivery | Do not use a large VPN spec if only occasional admin traffic passes through it |
| Database workload | Choose stable throughput, verify MTU and packet fragmentation behavior during sync or migration | Time data migration windows to reduce prolonged high-throughput use if billing is usage-sensitive |
Alibaba Cloud global account signup discount Common troubleshooting procedures after purchase
The VPN tunnel is down
Check these items in order:
- Customer gateway public IP matches the current on-premises firewall WAN IP.
- UDP 500 and 4500 are reachable.
- Pre-shared key matches exactly.
- IKE version, encryption, hash, and DH group are identical on both ends.
- NAT-T is enabled if the peer is behind NAT.
- The on-premises device has not exceeded its own tunnel or license limit.
The tunnel is up, but ECS cannot be reached by SSH or RDP
Check route tables first, then security groups, then OS firewall. For Linux, verify SSH is listening on the expected port. For Windows, verify RDP is enabled and inbound 3389 is allowed. If you recently reinstalled the operating system, previous host firewall settings may have changed.
Alibaba Cloud global account signup discount MySQL or Redis cannot be accessed over the VPN
For MySQL, check whether the database listens only on localhost, whether RDS whitelist or private connection rules allow the on-premises CIDR, and whether DNS resolution points to the private endpoint. For Redis, check authentication, protected mode or ACL-related settings, and whether private endpoint access is expected rather than public endpoint access.
Remote users connect to SSL-VPN but cannot resolve internal domains
This usually points to DNS configuration rather than the VPN tunnel itself. Push the correct internal DNS server settings to clients if supported, or configure split-DNS behavior on the client side. Also confirm that the internal DNS server allows queries from the SSL-VPN client address pool.
Alibaba Cloud global account signup discount Optimization recommendations
Security optimization
- Use a long random pre-shared key and rotate it during scheduled maintenance.
- Restrict security groups to on-premises CIDRs instead of allowing broad private ranges.
- For SSL-VPN, issue client profiles only to named users and revoke them promptly when access is no longer required.
- Use RAM users with least privilege for daily administration.
- Log configuration changes and store a copy of IKE/IPsec settings in your change management system.
Performance optimization
- Choose a region close to the office or branch firewall to reduce latency.
- Avoid overlapping CIDR blocks and excessive route complexity.
- For data migration, test throughput with real packet sizes and monitor fragmentation behavior.
- If users report intermittent slowness, compare tunnel utilization during backup windows or peak business hours.
Cost optimization
- Size for measured traffic, not estimated worst case unless the environment is business-critical.
- Use shorter subscription periods for temporary migration projects.
- Review renewal settings quarterly so expired cards or stale finance approvals do not interrupt service.
- Do not deploy separate gateways in multiple regions unless application placement requires it.
Stability optimization
- Document all routes, peer IPs, crypto parameters, and contact owners.
- Monitor tunnel state and set alerts on disconnection, latency increase, or packet loss.
- Keep a tested rollback plan for changing IKE/IPsec algorithms or readdressing networks.
- Take snapshots or backups of ECS systems before major network cutovers if administrative access depends on the VPN.
Alibaba Cloud global account signup discount Final decision checklist before production go-live
Before you depend on Alibaba Cloud VPN Gateway for a production office connection or remote admin access, verify all of the following:
- Account KYC is complete and billing is stable.
- Auto-renewal is enabled or renewal ownership is documented.
- Region selection matches workload location and latency expectations.
- VPC and on-premises CIDRs do not overlap.
- Customer gateway public IP is fixed and confirmed.
- IKE and IPsec parameters are documented and matched on both ends.
- Routes, security groups, and host firewalls are tested.
- SSH, RDP, database access, and internal DNS resolution are validated over the tunnel.
- Operations team has a runbook for tunnel-down troubleshooting.
Alibaba Cloud global account signup discount If you complete these checks in order, you avoid the majority of failed purchases and post-deployment support incidents associated with Alibaba Cloud VPN Gateway for site-to-site connectivity and remote access.

