Each Tablestore instance has an endpoint. An endpoint must be specified before any operations can be performed on tables or data within Tablestore. You must use different instance endpoints for different scenarios.

Note For more information about region names, see Region.

Query endpoints

  1. Log on to the Tablestore console.
  2. On the instance details page of an instance, you can view its endpoint in the Instance Access URL section.

Public endpoint

The public endpoint is used for accessing Tablestore instances over the Internet.

Format:

https://instanceName.region.ots.aliyuncs.com

For example, the public endpoint used to access an instance named myInstance that is located in the China (Hangzhou) region is as follows:

https://myInstance.cn-hangzhou.ots.aliyuncs.com

VPC endpoint

The VPC endpoint is used for accessing Tablestore instances from ECS instances in VPCs.

Format:

https://instanceName.region.vpc.tablestore.aliyuncs.com

For example, the VPC endpoint used to access an instance named myInstance that is located in the China (Hangzhou) region from VPCs is as follows:

https://myInstance.cn-hangzhou.vpc.tablestore.aliyuncs.com

Private endpoint

The private endpoint is used for accessing Tablestore instances from ECS instances in the classic network in the same region. When applications access Tablestore instances from ECS instances in the classic network in the same region over the internal network, the response latency is reduced and no Internet traffic is generated.

Format:

https://instanceName.region.ots-internal.aliyuncs.com

For example, the private endpoint used to access an instance named myInstance that is located in the China (Hangzhou) region is as follows:

https://myInstance.cn-hangzhou.ots-internal.aliyuncs.com