Service endpoints by region and network type - Hologres - Alibaba Cloud - Hologres

Usage notes

A specified VPC network endpoint connects only to the VPC bound to the Hologres instance. To connect to other VPCs, see Network connections.

If you encounter VPC connectivity issues, prioritize binding a VPC to the resource group instead of creating a new instance. Resources within the same VPC communicate automatically. Create a new instance only when the original VPC belongs to a different resource group and you cannot establish a peering connection.

Available endpoints

The following tables describe the endpoints that you can use to connect to Hologres instances in different Alibaba Cloud regions and network environments.

Mappings between regions and public endpoints

Region	City	Public endpoint
China (Hong Kong)	Hong Kong (China)	`<instanceID>-cn-hongkong.hologres.aliyuncs.com:80`
Singapore	Singapore	`<instanceID>-ap-southeast-1.hologres.aliyuncs.com:80`
Malaysia (Kuala Lumpur)	Kuala Lumpur	`<instanceID>-ap-southeast-3.hologres.aliyuncs.com:80`
US (Silicon Valley)	Silicon Valley	`<instanceID>-us-west-1.hologres.aliyuncs.com:80`
Indonesia (Jakarta)	Jakarta	`<instanceID>-ap-southeast-5.hologres.aliyuncs.com:80`
Japan (Tokyo)	Tokyo	`<instanceID>-ap-northeast-1.hologres.aliyuncs.com:80`

Mappings between regions and classic network endpoints

Region	City	Classic network endpoint
China (Hong Kong)	Hong Kong (China)	`<instanceID>-cn-hongkong-internal.hologres.aliyuncs.com:80`
Singapore	Singapore	`<instanceID>-ap-southeast-1-internal.hologres.aliyuncs.com:80`
Malaysia (Kuala Lumpur)	Kuala Lumpur	`<instanceID>-ap-southeast-3-internal.hologres.aliyuncs.com:80`
US (Silicon Valley)	Silicon Valley	`<instanceID>-us-west-1-internal.hologres.aliyuncs.com:80`
Indonesia (Jakarta)	Jakarta	`<instanceID>-ap-southeast-5-internal.hologres.aliyuncs.com:80`
Japan (Tokyo)	Tokyo	`<instanceID>-ap-northeast-1-internal.hologres.aliyuncs.com:80`

Mappings between regions and specified VPC endpoints

Region	City	Specified VPC endpoint
China (Hong Kong)	Hong Kong (China)	`<instanceID>-cn-hongkong-vpc-st.hologres.aliyuncs.com`
Singapore	Singapore	`<instanceID>-ap-southeast-1-vpc-st.hologres.aliyuncs.com`
Malaysia (Kuala Lumpur)	Kuala Lumpur	`<instanceID>-ap-southeast-3-vpc-st.hologres.aliyuncs.com`
US (Silicon Valley)	Silicon Valley	`<instanceID>-us-west-1-vpc-st.hologres.aliyuncs.com`
Indonesia (Jakarta)	Jakarta	`<instanceID>-ap-southeast-5-vpc-st.hologres.aliyuncs.com`
Japan (Tokyo)	Tokyo	`<instanceID>-ap-northeast-1-vpc-st.hologres.aliyuncs.com`

Sample endpoints

The <instanceID> placeholder represents the ID of your instance. To find the ID, log on to the Hologres console. On the instance list page, click your instance's name. On the Instance Details page, find the instance ID field in the Basic Information section (for example, hgpostcn-xxx) and click the copy icon next to it.

For example, if you have a Hologres instance named testdemo in the Singapore region with an instance ID of hgprecn-cn-xxxk3ovx003, its endpoints are as follows:

Public network endpoint: hgprecn-cn-xxxk3ovx003-ap-southeast-1.hologres.aliyuncs.com
Classic network endpoint: hgprecn-cn-xxxk3ovx003-ap-southeast-1-internal.hologres.aliyuncs.com
Specified VPC network endpoint: hgprecn-cn-xxxk3ovx003-ap-southeast-1-vpc-st.hologres.aliyuncs.com