This topic describes the endpoints for Simple Log Service (SLS) by network type.
View endpoints
When using the private endpoint of SLS on Alibaba Cloud public cloud, you must use Alibaba Cloud's private DNS addresses (100.100.2.136 and 100.100.2.138). Otherwise, you may not obtain the correct VIP address for the private endpoint and fail to access SLS.
An endpoint is the domain name used to access Simple Log Service. SLS provides private endpoints and public endpoints.
In the Projects list, click the target project.
On the Overview page of the project, view the endpoint for the region where the project resides. In the Endpoints section of the Overview tab, you can find the private endpoint (
cn-shanghai-intranet.log.aliyuncs.com), public endpoint (cn-shanghai.log.aliyuncs.com), and internal cross-region endpoint (cn-shanghai-share.log.aliyuncs.com).
Choose an endpoint
Private and public endpoints provide the same service features but differ slightly in network latency and billing rules.
Comparison item | Private endpoint | public domain name |
Request protocol | HTTP, HTTPS | HTTP, HTTPS |
Use case | Internal communication between Alibaba Cloud services. For example, ECS instances in the same region accessing SLS. We recommend using private endpoints first. | Accessing SLS over the Internet. For example, using APIs or SDKs from your local machine over the public network. |
Billing | Billed according to standard SLS billing items. For more information, see SLS billing items. | Includes additional outbound traffic charges compared to private endpoint usage. For more information, see SLS billing items. |
Public endpoints
An endpoint is the URL used to access a project and its log data. Endpoints depend on the region where the project resides. SLS is available in multiple regions. The following table lists public endpoints by region.
Region | Endpoint |
China (Hangzhou) | cn-hangzhou.log.aliyuncs.com |
China (Shanghai) | cn-shanghai.log.aliyuncs.com |
China (Qingdao) | cn-qingdao.log.aliyuncs.com |
China (Beijing) | cn-beijing.log.aliyuncs.com |
China (Zhangjiakou) | cn-zhangjiakou.log.aliyuncs.com |
China (Hohhot) | cn-huhehaote.log.aliyuncs.com |
China (Ulanqab) | cn-wulanchabu.log.aliyuncs.com |
China (Shenzhen) | cn-shenzhen.log.aliyuncs.com |
China (Heyuan) | cn-heyuan.log.aliyuncs.com |
China (Guangzhou) | cn-guangzhou.log.aliyuncs.com |
China (Chengdu) | cn-chengdu.log.aliyuncs.com |
China (Hong Kong) | cn-hongkong.log.aliyuncs.com |
Japan (Tokyo) | ap-northeast-1.log.aliyuncs.com |
South Korea (Seoul) | ap-northeast-2.log.aliyuncs.com |
Singapore | ap-southeast-1.log.aliyuncs.com |
Malaysia (Kuala Lumpur) | ap-southeast-3.log.aliyuncs.com |
Indonesia (Jakarta) | ap-southeast-5.log.aliyuncs.com |
Philippines (Manila) | ap-southeast-6.log.aliyuncs.com |
Thailand (Bangkok) | ap-southeast-7.log.aliyuncs.com |
Malaysia (Johor) | ap-southeast-8.log.aliyuncs.com |
UAE (Dubai) | me-east-1.log.aliyuncs.com |
US (Silicon Valley) | us-west-1.log.aliyuncs.com |
Germany (Frankfurt) | eu-central-1.log.aliyuncs.com |
US (Virginia) | us-east-1.log.aliyuncs.com |
UK (London) | eu-west-1.log.aliyuncs.com |
Brazil (Sau Paulo) | sa-east-1.log.aliyuncs.com |
SAU (Riyadh - Partner Region) | me-central-1.log.aliyuncs.com |
Private network
If you use SLS APIs from an Alibaba Cloud ECS instance, you can also use private endpoints. The following table lists private endpoints by region.
SLS APIs at these endpoints support only HTTP and HTTPS protocols.
Using private endpoints to access SLS does not consume ECS public bandwidth, helping you save on public bandwidth costs.
Region | Endpoint |
China (Hangzhou) | cn-hangzhou-intranet.log.aliyuncs.com |
China (Shanghai) | cn-shanghai-intranet.log.aliyuncs.com |
China (Qingdao) | cn-qingdao-intranet.log.aliyuncs.com |
China (Beijing) | cn-beijing-intranet.log.aliyuncs.com |
China (Shenzhen) | cn-shenzhen-intranet.log.aliyuncs.com |
China (Heyuan) | cn-heyuan-intranet.log.aliyuncs.com |
China (Guangzhou) | cn-guangzhou-intranet.log.aliyuncs.com |
China (Zhangjiakou) | cn-zhangjiakou-intranet.log.aliyuncs.com |
China (Hohhot) | cn-huhehaote-intranet.log.aliyuncs.com |
China (Ulanqab) | cn-wulanchabu-intranet.log.aliyuncs.com |
China (Chengdu) | cn-chengdu-intranet.log.aliyuncs.com |
China (Hong Kong) | cn-hongkong-intranet.log.aliyuncs.com |
US (Silicon Valley) | us-west-1-intranet.log.aliyuncs.com |
Japan (Tokyo) | ap-northeast-1-intranet.log.aliyuncs.com |
South Korea (Seoul) | ap-northeast-2-intranet.log.aliyuncs.com |
Singapore | ap-southeast-1-intranet.log.aliyuncs.com |
Malaysia (Kuala Lumpur) | ap-southeast-3-intranet.log.aliyuncs.com |
Indonesia (Jakarta) | ap-southeast-5-intranet.log.aliyuncs.com |
Philippines (Manila) | ap-southeast-6-intranet.log.aliyuncs.com |
Thailand (Bangkok) | ap-southeast-7-intranet.log.aliyuncs.com |
Malaysia (Johor) | ap-southeast-8-intranet.log.aliyuncs.com |
UAE (Dubai) | me-east-1-intranet.log.aliyuncs.com |
Germany (Frankfurt) | eu-central-1-intranet.log.aliyuncs.com |
US (Virginia) | us-east-1-intranet.log.aliyuncs.com |
UK (London) | eu-west-1-intranet.log.aliyuncs.com |
Brazil (Sau Paulo) | sa-east-1-intranet.log.aliyuncs.com |
SAU (Riyadh - Partner Region) | me-central-1-intranet.log.aliyuncs.com |
Transfer acceleration
Simple Log Service adds a transfer acceleration network type on top of private and public networks. Compared with standard public access, transfer acceleration offers significantly lower latency and higher stability, making it suitable for scenarios with high requirements for data ingestion latency and reliability. For more information, see Manage transfer acceleration.
The transfer acceleration endpoint is the same across all regions:
log-global.aliyuncs.comTransfer acceleration is disabled by default. You must enable it manually before use. For details, see Ingestion acceleration.
The transfer acceleration endpoint log-global.aliyuncs.com supports only IPv4 and does not support IPv6. If you need IPv6 access, use a regional dual-stack endpoint (for example, cn-beijing.dualstack.log.aliyuncs.com), which supports both IPv4 and IPv6 access. Simple Log Service does not currently provide a unified endpoint that combines global acceleration with IPv4/IPv6 dual-stack support.