Call the Cloud Control API over PrivateLink to access the service privately, without exposing traffic to the public internet.
Overview
What is PrivateLink?
PrivateLink establishes private connections between your VPC and Alibaba Cloud services, enhancing security and stability by keeping traffic off the public internet.
Use cases
PrivateLink is recommended for calling the Cloud Control API from production environments. Typical use cases include:
-
High security and compliance requirements: Your corporate security policy prohibits or restricts public internet access.
-
Cost optimization: You want to reduce public data transfer fees and lower your total cost of ownership (TCO).
-
Cross-region deployment: You need to deploy applications across multiple regions with a unified network architecture.
Benefits
|
Benefit |
Description |
|
Low latency |
Direct private connections reduce network latency by 30% to 50% compared to public internet access. |
|
High stability |
Avoids the volatility of the public internet. |
|
Secure isolation |
Traffic does not traverse the public internet. |
Prerequisites
Permission requirements
Configuring a PrivateLink endpoint requires the following permissions:
-
AliyunVPCFullAccess: Full access to VPC. -
AliyunPrivateLinkFullAccess: Full access to PrivateLink.
Resource requirements
Ensure the following resources are available in the region of the Cloud Control API service you want to call:
|
API service region |
Domain name |
VPC region |
|
Domestic service |
cloudcontrol.aliyuncs.com |
cn-zhangjiakou (China (Zhangjiakou)) |
|
International service |
cloudcontrol.ap-southeast-1.aliyuncs.com |
ap-southeast-1 (Singapore) |
Resource checklist:
-
A VPC instance in the target region.
-
At least one available vSwitch in the VPC.
-
Ensure the vSwitch has sufficient available IP addresses.
Service regions
The Cloud Control API is available in the following regions. Select a region based on your business needs.
Domestic service (cn-zhangjiakou)
-
Endpoint service:
com.aliyuncs.privatelink.cn-zhangjiakou.cloudcontrol-api -
Public domain name:
cloudcontrol.aliyuncs.com -
Private domain name:
cloudcontrol.vpc-proxy.aliyuncs.com
International service (ap-southeast-1)
-
Endpoint service:
com.aliyuncs.privatelink.ap-southeast-1.cloudcontrol -
Public domain name:
cloudcontrol.ap-southeast-1.aliyuncs.com -
Private domain name:
cloudcontrol-vpc.ap-southeast-1.aliyuncs.com
After configuring PrivateLink, update your application code to use the corresponding private domain name.
Procedure
Same-region configuration
If your application is deployed in the same region as the Cloud Control API service (cn-zhangjiakou or ap-southeast-1), you can create an endpoint directly in that region.
Step 1: Log on to the console
-
Log on to the VPC console.
-
In the left-side navigation pane, click Endpoints.
-
On the Interface Endpoint tab, click Enable PrivateLink .
Step 2: Select a region
From the Region drop-down list, select a region:
-
To access the domestic service, select China (Zhangjiakou).
-
To access the international service, select Singapore.
Step 3: Configure basic information
|
Parameter |
Description |
Example |
|
Endpoint Name |
Enter a descriptive name for the endpoint. |
|
|
Endpoint Type |
Select Interface Endpoint. |
Interface Endpoint |
|
Resource Type |
Select Alibaba Cloud Service. |
Alibaba Cloud Service |
Step 4: Select an endpoint service
-
In the Endpoint Service search box, enter the service name based on your target service:
-
Domestic service:
com.aliyuncs.privatelink.cn-zhangjiakou.cloudcontrol-api -
International service:
com.aliyuncs.privatelink.ap-southeast-1.cloudcontrol
-
-
Select the endpoint service from the search results.
Step 5: Enable a custom domain name
Select Enable Custom Domain Name. The system automatically assigns a private domain name.
-
Domestic service domain name:
cloudcontrol.vpc-proxy.aliyuncs.com -
International service domain name:
cloudcontrol-vpc.ap-southeast-1.aliyuncs.com
Step 6: Configure network settings
|
Parameter |
Description |
Best practice |
|
VPC |
Select the VPC where your application is deployed. |
Verify the VPC matches your application deployment. |
|
Zone and vSwitch |
Select at least one vSwitch. We recommend selecting multiple vSwitches for high availability. |
For production environments, select vSwitches in two to three different zones. |
|
Security group |
Select a security group to restrict access sources. |
Configure rules that allow access only from your application's security group. |
Multi-zone configuration example:
Zone A: vsw-xxxxx
Zone B: vsw-yyyyy
Step 7: Configure an endpoint policy
An endpoint policy defines which Alibaba Cloud accounts or RAM users can access the service through the endpoint.
Grant access only to necessary accounts based on the principle of least privilege.
Default policy (allows all):
{
"Version": "1",
"Statement": [
{
"Effect": "Allow",
"Principal": "*",
"Action": "*",
"Resource": "*"
}
]
}
Recommended policy (allows only the current account):
{
"Version": "1",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Aliyun": [
"acs:ram::YOUR_ACCOUNT_ID:root"
]
},
"Action": "*",
"Resource": "*"
}
]
}
Step 8: Create and verify
-
Click OK to create the endpoint.
-
Wait 2 to 5 minutes for the endpoint status to become Active.
-
The connection status changes to Connected.
Status descriptions:
-
Creating: The endpoint is being created.
-
Active: The endpoint is ready for use.
-
Abnormal : The creation failed or the connection is not working. Check your configuration.
After the endpoint is created, verify the following on its details page: in the Basic Information section, the Status is Active and the Connection Status is Connected. In the Endpoint Service Domain Name section, confirm that the Custom Domain Name is enabled and shows the expected domain.
Cross-region configuration
To connect from a region other than cn-zhangjiakou or ap-southeast-1, you must use CEN to establish a cross-region connection.
Step 1: Create endpoint in target region
-
Create an endpoint in
cn-zhangjiakouorap-southeast-1. For instructions, see Same-region configuration. -
Record the ID of the VPC where the endpoint is located.
Step 2: Connect regions with CEN
For information about how to configure CEN, see Connect VPCs across regions.
Verification and testing
Verify connectivity
Log on to the ECS or container instance that runs your application and run the following command:
Domestic service verification:
curl -v cloudcontrol.vpc-proxy.aliyuncs.com
International service verification:
curl -v cloudcontrol-vpc.ap-southeast-1.aliyuncs.com
Success indicator:
A successful connection includes an x-acs-request-id header in the HTTP response. Example output:
< HTTP/1.1 401 Unauthorized
< date: Thu, 09 Oct 2025 10:30:00 GMT
< content-type: application/json
< x-acs-request-id: 23C12345-1234-1234-1234-123456789ABC
< x-acs-trace-id: 0b12345678901234567890123456789a
...
The API is expected to return a 401 status code because the request does not include credentials.
The presence of the x-acs-request-id header confirms that the request reached the Alibaba Cloud service endpoint through the private connection.
Application integration example
Java example
import com.aliyun.cloudcontrol20220830.Client;
import com.aliyun.teaopenapi.models.Config;
public class PrivateLinkExample {
public static void main(String[] args) throws Exception {
// Configure the client.
Config config = new Config()
.setAccessKeyId("<YOUR-ACCESS-KEY-ID>")
.setAccessKeySecret("<YOUR-ACCESS-KEY-SECRET>")
// Use the private endpoint.
// For the domestic service
.setEndpoint("cloudcontrol.vpc-proxy.aliyuncs.com")
.setHost("cloudcontrol.aliyuncs.com")
// For the international service
// .setEndpoint("cloudcontrol-vpc.ap-southeast-1.aliyuncs.com")
.setProtocol("https");
Client client = new Client(config);
// Use the client object for subsequent API calls.
try {
var response = client.listResources(...);
System.out.println("Request successful: " + response.getBody().getRequestId());
} catch (Exception e) {
System.err.println("Request failed: " + e.getMessage());
}
}
}