All Products
Search
Document Center

Simple Log Service:VPC-specific internal domain names

Last Updated:Aug 25, 2026

Simple Log Service (SLS) provides a VPC-specific internal domain name in each region. Use this domain name as the endpoint in your SDK or API client to reach SLS over the internal network from within a Virtual Private Cloud (VPC). Clients in another region or in an on-premises data center can also reach SLS through these domain names after the networks are connected.

VPC-specific internal domain name format

A VPC-specific internal domain name has the format {regionId}-internal.log.aliyuncs.com, where {regionId} is the ID of the region where SLS resides. Take the value of {regionId} from the Region ID column of the tables in Region and CIDR block reference. This domain name is the value that you set as the endpoint in an SDK or API client.

Differences from existing internal domain names

VPC-specific internal domain names use dedicated CIDR blocks. In each region, SLS assigns a fixed CIDR block to the virtual IP address (VIP) of the VPC-specific internal domain name in that region. Because this CIDR block is fixed, you can use it as the destination of the route that you configure for access from outside the region.

Access through a VPC-specific internal domain name is limited to the internal network. The request must come from a network that is connected to the internal network of the region where SLS resides, such as a VPC in that region or a network that you connect to it. An environment outside such a network, including a client that connects over the Internet, cannot reach the domain name.

Access scenarios and network requirements

The network configuration that a VPC-specific internal domain name requires depends on where the client runs:

  • A client in a VPC in the same region as SLS — Set the VPC-specific internal domain name of that region as the endpoint. No additional network connection or route is required.

  • An Elastic Compute Service (ECS) instance in another region, or a device in an on-premises data center — Connect the client network to the internal network of the region where SLS resides, and then configure a route that points to the CIDR block of that region.

Connect the network and configure a route

To access SLS over the internal network from an ECS instance in another region or from a device in an on-premises data center, complete the following steps:

  1. Connect the client network to the internal network of the region where SLS resides. Use a connection service such as Cloud Enterprise Network (CEN), Express Connect, a leased line, or a Virtual Private Network (VPN).

  2. Configure a route that points to the fixed CIDR block of the region where SLS resides. Look up the CIDR block in Region and CIDR block reference.

  3. Set the VPC-specific internal domain name of that region as the endpoint in your client. For an example, see Set the domain name as the endpoint.

Set the domain name as the endpoint

Set the VPC-specific internal domain name of the region where SLS resides as the endpoint in your client. The following example uses Java:

import com.aliyun.openservices.log.Client;
import com.aliyun.openservices.log.http.client.ClientConfiguration;
import com.aliyun.openservices.log.http.signer.SignVersion;

public class Sample {

    public static void main(String[] args) throws Exception {
        // This example uses the China (Beijing) region. For other regions, specify the corresponding value.
        String endpoint = "cn-beijing-internal.log.aliyuncs.com";
        // This example obtains the AccessKey ID and AccessKey secret from environment variables.
        String accessKeyId = System.getenv("ALIBABA_CLOUD_ACCESS_KEY_ID");
        String accessKeySecret = System.getenv("ALIBABA_CLOUD_ACCESS_KEY_SECRET");
        ClientConfiguration clientConfiguration = new ClientConfiguration();
        clientConfiguration.setRegion("cn-beijing");
        clientConfiguration.setSignatureVersion(SignVersion.V4);
        Client client = new Client(endpoint,
                accessKeyId,
                accessKeySecret,
                clientConfiguration);
    }
}

The example builds a client for the China (Beijing) region. For another region, specify the endpoint and the region ID of that region. The client configuration in the example also specifies signature version V4. Before you run the example, set the ALIBABA_CLOUD_ACCESS_KEY_ID and ALIBABA_CLOUD_ACCESS_KEY_SECRET environment variables.

Region and CIDR block reference

The following tables list the VPC-specific internal domain name and the fixed IPv4 CIDR block of each region. Locate the region where SLS resides, and then use the domain name and the CIDR block in that row.

Important

CIDR block prefixes and mask lengths differ between regions. Copy the exact value from the row for your region instead of deriving it from other rows.

China

RegionRegion IDDomain nameFixed IPv4 CIDR block
China (Hangzhou)cn-hangzhoucn-hangzhou-internal.log.aliyuncs.com100.115.4.0/24
China (Shanghai)cn-shanghaicn-shanghai-internal.log.aliyuncs.com100.115.12.0/24
China (Qingdao)cn-qingdaocn-qingdao-internal.log.aliyuncs.com100.115.76.0/24
China (Beijing)cn-beijingcn-beijing-internal.log.aliyuncs.com100.115.44.0/24
China (Shenzhen)cn-shenzhencn-shenzhen-internal.log.aliyuncs.com100.115.10.0/24
China (Heyuan)cn-heyuancn-heyuan-internal.log.aliyuncs.com100.115.51.0/24
Heyuan Dedicated Cloud for Automotive Compliancecn-heyuan-acdr-1cn-heyuan-acdr-1-internal.log.aliyuncs.com100.115.92.0/24
China (Guangzhou)cn-guangzhoucn-guangzhou-internal.log.aliyuncs.com100.115.49.0/24
China (Zhangjiakou)cn-zhangjiakoucn-zhangjiakou-internal.log.aliyuncs.com100.115.28.0/24
China (Hohhot)cn-huhehaotecn-huhehaote-internal.log.aliyuncs.com100.115.69.0/24
China (Ulanqab)cn-wulanchabucn-wulanchabu-internal.log.aliyuncs.com100.118.12.0/24
China (Chengdu)cn-chengducn-chengdu-internal.log.aliyuncs.com100.115.52.0/24
China (Hong Kong)cn-hongkongcn-hongkong-internal.log.aliyuncs.com100.115.24.0/24

Outside China

RegionRegion IDDomain nameFixed IPv4 CIDR block
Japan (Tokyo)ap-northeast-1ap-northeast-1-internal.log.aliyuncs.com100.115.17.0/24
South Korea (Seoul)ap-northeast-2ap-northeast-2-internal.log.aliyuncs.com100.115.18.0/24
Singaporeap-southeast-1ap-southeast-1-internal.log.aliyuncs.com100.115.40.0/24
Malaysia (Kuala Lumpur)ap-southeast-3ap-southeast-3-internal.log.aliyuncs.com100.115.32.0/24
Indonesia (Jakarta)ap-southeast-5ap-southeast-5-internal.log.aliyuncs.com100.115.36.0/24
Philippines (Manila)ap-southeast-6ap-southeast-6-internal.log.aliyuncs.com100.115.34.0/24
Thailand (Bangkok)ap-southeast-7ap-southeast-7-internal.log.aliyuncs.com100.115.35.0/24
UAE (Dubai)me-east-1me-east-1-internal.log.aliyuncs.com100.115.57.0/24
Germany (Frankfurt)eu-central-1eu-central-1-internal.log.aliyuncs.com100.115.80.0/24
US (Virginia)us-east-1us-east-1-internal.log.aliyuncs.com100.115.86.0/24
UK (London)eu-west-1eu-west-1-internal.log.aliyuncs.com100.115.84.0/24
SAU (Riyadh - Partner Region)me-central-1me-central-1-internal.log.aliyuncs.com100.115.56.0/24
US (Silicon Valley)us-west-1us-west-1-internal.log.aliyuncs.com100.115.87.0/24
Atlantaus-southeast-1us-southeast-1-internal.log.aliyuncs.com100.115.125.128/25