Each Tablestore instance has an endpoint. You must specify an endpoint before you can perform operations on data and tables in Tablestore. Different instance endpoints are used in different scenarios.

Note For information about the endpoint of each region, see Region.

Endpoint types

Endpoints are classified into public endpoints, dual-stack public endpoints, VPC endpoints, and classic network endpoints. When you access a Tablestore instance from a specific type of network, you must use the endpoint that is specific to the network type.

Note For information about virtual private clouds (VPCs) and the classic network, see Network types.
Scenario Endpoint
Access over the Internet Select a public endpoint or a dual-stack public endpoint based on the IP protocol that is supported by the client.
Access over a VPC Use a VPC endpoint.
Access over a classic network Use a classic network endpoint.

Public endpoints

Public endpoints are used to access Tablestore instances over the Internet.

Important When 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.com
  • Example

    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.com
  • Example

    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 Elastic Compute Service (ECS) instances that reside in the classic network in the same region.

Note When applications access Tablestore instances from ECS instances that reside in the classic network in the same region over the internal network, the response latency is reduced and no Internet traffic is generated.
  • Endpoint format
    https://instanceName.RegionID.ots-internal.aliyuncs.com
  • Example

    The endpoint that is used to access the instance named myInstance from ECS instances that reside in the classic network in the China (Hangzhou) region 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 the client uses the IPv6 protocol, you can use only dual-stack public endpoints.
  • If the client does not support the IPv6 protocol, you can use public endpoints or dual-stack public endpoints.
Important 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 format
    https://instanceName.RegionID.tablestore.aliyuncs.com
  • Example

    The endpoint that is used to access the instance named myInstance in the China (Hangzhou) region from a dual-stack public network is https://myInstance.cn-hangzhou.tablestore.aliyuncs.com.

Query endpoints

  1. Log on to the Tablestore console.
  2. 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 that you want to manage.

    Go to the Instance Details tab. You can view the endpoints of the instance in the Instance Access URL section.

    fig_intl_enpoint