View instance details and configure network - Hologres - Alibaba Cloud Documentation Center

This topic describes how to view instance details and configure its network in the Hologres console.

Important notes

If your instance's network type is set to dedicated VPC, only traffic from the VPC can access your instance. To enable access from other VPCs, connect them to the dedicated VPC. See Connect VPCs.
Services (Flink, ECS, etc.) in the dedicated VPC can access your instance from any zone within that VPC.

View instance details

On the Instance Details page, view basic information about your instance, such as the name, ID, region, version, billing method, instance type, and creation time.

Network types

The Network Information section displays four network types available for the Hologres instance: public network, classic, VPC (being phased out), and dedicated VPC. Select a network type to connect to your tools.

Note

The instance ID can be found in the Basic Information section of the Instance Details page. The region is the region where the instance is located.

Network type	Endpoint	Description	Scenarios	Actions
Public Network (Internet)	`<instanceID>-cn-<region>.hologres.aliyuncs.com:80`	Access over the public network (Internet) incurs traffic overhead. Hologres currently does not charge for this traffic. It supports a bandwidth of 200 Mbps.	The public network is suitable for scenarios without network access restrictions, including: Accessing your instance from other systems or services. Connecting to Hologres across different regions or network types. Note Before disabling the public network, ensure no applications are currently accessing Hologres via this method.	Defaults to disabled. You can switch it on to enable public network. Note Due to security and compliance requirements, the public network is not available for instances in Alibaba JST Titans .
Classic	`<instanceID>-cn-<region>-internal.hologres.aliyuncs.com:80`	This refers to Alibaba Cloud's intranet. Alibaba Cloud manages IP address allocation and network infrastructure. It supports a bandwidth of 20 Gbps.	Use this network type for applications operating within the classic network to access Hologres. For example, an application deployed on an Elastic Compute Service (ECS) instance within the classic network can connect to Hologres via its classic network endpoint.	Defaults to enabled and cannot be disabled.
Dedicated VPC	`<instanceID>-cn-<region>-vpc-st.hologres.aliyuncs.com:80`	A logically isolated private network that connects your Hologres instance exclusively to your dedicated VPC. It supports a bandwidth of 20 Gbps.	Dedicated VPC is the recommended network type for VPC connections. Unlike standard VPC networking, it strictly allows traffic only from within the associated VPC to your instance, blocking requests from other VPCs. This network type is ideal for: Connecting to Hologres directly through a dedicated VPC. Accessing Hologres from an on-premises data center by establishing a connection via VPN Gateway, Express Connect, Cloud Enterprise Network (CEN), or Smart Access Gateway. Note After associating a dedicated VPC, allow approximately 30 seconds for Domain Name System (DNS) updates before the IP address becomes resolvable.	You can associate or release a dedicated VPC by selecting the corresponding option in the Actions column.
VPC	`<instanceID>-cn-<region>-vpc.hologres.aliyuncs.com:80`	Logically isolated network environments. It supports leased line connections and provides a bandwidth of 20 Gbps.	Compared to the classic network, VPC offers enhanced security and flexibility. It's suitable for applications deployed on Elastic Compute Service (ECS) instances within a VPC, allowing direct connection to Hologres via the VPC endpoint. Cross-region connections are not supported. Note Deprecation notice: As of December 26, 2022, new instances (including those restored from backups) no longer provide VPC endpoints. Instead, they are provisioned with dedicated VPC endpoints. Existing instances are unaffected. For better security, it is recommended to disable the VPC endpoint and utilize a dedicated VPC endpoint.	You can enable or disable this network type. Note Important considerations after disabling VPC network: Once disabled, the VPC network type cannot be re-enabled. To use HoloWeb, you must associate a dedicated VPC with your instance. Scheduling tasks that rely on the VPC network type to connect to the instance will fail. For DataWorks to connect to the instance, you must use an exclusive resource group for scheduling. For more information, see Exclusive resource groups for scheduling.

Associate a dedicated VPC

A dedicated VPC endpoint offers enhanced security and isolation by connecting exclusively to the VPC you select. We recommend disabling the VPC endpoint and switching to a dedicated VPC endpoint.

Follow these steps:

Log on to the Hologres console.
In the top navigation bar, select a region.
In the left navigation menu, click Instances.
On the Instances page, click the target instance's name.
On the Instance Details page, in the Network Information section, click Associate VPC in the Actions column for the Dedicated VPC row.
In the Associate VPC dialog box, select a VPC and a vSwitch.
Note
- You will only see VPCs located in the same region and vSwitches within the same region and zone as your instance
- Hologres V1.3 consumes three IP addresses, while V2.0 consumes two. Please ensure your chosen vSwitch has sufficient available IP addresses to meet these needs.
Click OK.
The VPC association begins. After it is complete, a VPC endpoint is generated.

Release a dedicated VPC

Follow these steps:

Log on to the Hologres console.
In the top navigation bar, select a region.
In the left navigation pane, click Instances.
On the Instances page, click the name of the target instance.
On the Instance Details page, in the Network Information section, click Release VPC in the Actions column for the Dedicated VPC row.
Click Release in the dialog box.
The VPC is released.
Note
After release, you can no longer connect to the instance through the dedicated VPC endpoint.