Each Tablestore instance has an endpoint. You must specify an endpoint before you can perform operations on data and tables in Tablestore. The endpoint format varies based on the access scenarios.
For information about the endpoint of each region, see Regions.
Usage notes
Dual-stack public endpoints are available in the following regions: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Shenzhen), China (Chengdu), and China (Hong Kong).
Endpoint types
Endpoints are classified into public endpoints, dual-stack public endpoints, virtual private cloud (VPC) endpoints, and classic network endpoints. The required endpoint varies based on the network that you use to access a Tablestore instance.
Scenario | Required endpoint |
Access over the Internet | Use a public endpoint or a dual-stack public endpoint based on the IP protocol that is supported by the client. Access over the Internet causes high latency. We recommend that you access Tablestore over the classic network or a VPC. Important
|
Access over a VPC | Use a VPC endpoint. |
Access over the classic network | Use the classic network endpoint. |
For information about VPCs and the classic network, see Network types.
Public endpoints
Public endpoints are used to access Tablestore instances over the Internet.
If you access Tablestore over the Internet, you are charged for outbound traffic over the Internet. For more information, see Billing overview.
Endpoint format
https://instanceName.RegionID.ots.aliyuncs.comExample
The endpoint that is used to access the instance named myInstance in the China (Hangzhou) region over the Internet is
https://myInstance.cn-hangzhou.ots.aliyuncs.com.
VPC endpoints
VPC endpoints are used to access Tablestore instances over VPCs.
Endpoint format
https://instanceName.RegionID.vpc.tablestore.aliyuncs.comExample
The endpoint that is used to access the instance named myInstance in the China (Hangzhou) region over a VPC is
https://myInstance.cn-hangzhou.vpc.tablestore.aliyuncs.com.
Classic network endpoints
Classic network endpoints are used to access Tablestore instances from ECS instances in the same region over the classic network.
When applications on ECS instances access a Tablestore instance in the same region over the classic network, the response latency is lower and no outbound traffic over the Internet is generated.
Endpoint format
https://instanceName.RegionID.ots-internal.aliyuncs.comExample
The endpoint that is used to access the instance named myInstance from ECS instances that reside in the China (Hangzhou) region over the classic network is
https://myInstance.cn-hangzhou.ots-internal.aliyuncs.com.
Dual-stack public endpoints
Dual-stack public endpoints are used to access Tablestore instances over the Internet.
If you access Tablestore over the Internet, you are charged for outbound traffic over the Internet. For more information, see Billing overview.
Endpoint format
https://instanceName.RegionID.tablestore.aliyuncs.comExample
The dual-stack public endpoint that is used to access the instance named myInstance in the China (Hangzhou) region is
https://myInstance.cn-hangzhou.tablestore.aliyuncs.com.
Query endpoints
Log on to the Tablestore console.
In the top navigation bar, select a resource group and a region.
On the Overview page, click the name of the instance that you want to manage or click Manage Instance in the Actions column of the instance.
Go to the Instance Details tab. You can view the endpoints of the instance in the Instance Access URL section.
