View instance details, network settings, and connection information for your Hologres instance in the Hologres console.
Usage notes
-
A dedicated VPC endpoint allows access only from the associated VPC. To allow access from other VPCs, you must establish a VPC connection between them.
-
If your services, such as Flink or ECS, are in the same VPC as your Hologres instance, they can access the instance from any zone within that VPC by using the dedicated VPC endpoint.
Basic information
The Basic Information section displays the instance name, ID, region, version, billing method, instance type, and creation time.
It also shows the Zone, Tags, and the status of Data Lake Acceleration and Serverless Computing.
Network configuration
Hologres supports four network types: public network, classic network, VPC, and dedicated VPC. Choose a network type based on your business requirements.
You can find the instanceID in the Instance ID field under the section on the Instance Details page. The region is the region where your instance is located.
|
Network type |
Endpoint |
Description |
Use cases |
Actions |
|
Public Network |
|
Public network usage generates traffic costs, but Hologres currently waives these charges. This connection supports a bandwidth of 200 Mbps. |
Suitable for scenarios without network access restrictions, such as:
Note
Disabling public network access terminates all existing connections that use the public network endpoint. Before you disable this feature, ensure that no applications are connected to Hologres through the public network. |
This network type is disabled by default. You can enable or disable it as needed. Note
Due to security and compliance requirements, public network endpoints are not available for instances in Alibaba JST Titans and Logistics Cloud. |
|
Classic |
|
Alibaba Cloud's public infrastructure network. Alibaba Cloud manages the IP addressing, planning, and administration for this network. It supports a bandwidth of 20 Gbps. |
Use this network type when your application runs within the classic network. For example, an ECS instance in a classic network can connect to Hologres through the classic network endpoint. |
This network type is enabled by default and cannot be disabled. |
|
Dedicated VPC |
|
A logically isolated private network that connects exclusively to a specific VPC. It supports a bandwidth of 20 Gbps. |
Recommended for VPC connections. Unlike a standard VPC endpoint, a dedicated VPC endpoint is accessible only from the associated VPC. Suitable for:
Note
After you associate a VPC, you may need to wait about 30 seconds for the DNS record to update before the IP address can be resolved. |
By default, the VPC that you selected when creating the instance is associated. To associate a VPC, click Associate VPC in the Actions column. In the dialog box that appears, select a VPC and a vSwitch. |
|
VPC |
|
A logically isolated private network that supports dedicated line connections and provides a bandwidth of 20 Gbps. |
A VPC provides greater security and flexibility than a classic network. This network type is being phased out. For example, an ECS instance within a VPC can connect directly to the Hologres VPC endpoint. Cross-region connections are not supported. Note
Deprecation notice: As of December 26, 2022, new instances, including instances restored from backups, are no longer provided with VPC endpoints. Instead, use the more secure dedicated VPC endpoint. A dedicated VPC endpoint connects exclusively to the VPC that you selected when you purchased the instance, providing better security and isolation. Existing instances are not affected. We recommend that you disable the legacy VPC endpoint and switch to the dedicated VPC endpoint. |
You can enable or disable this network type. Note
Important: After you disable the VPC network, you cannot re-enable it.
|
Bind a dedicated VPC network
A dedicated VPC endpoint connects exclusively to your selected VPC for enhanced security and isolation. We recommend that you disable the legacy VPC endpoint and switch to a dedicated VPC endpoint.
Procedure
-
Log on to the Hologres console.
-
In the top navigation bar, select the region where your instance is located.
-
In the left-side navigation pane, click Instances.
-
On the Instances page, click the name of your target instance.
-
On the Instance Details page, go to the Network Information section. In the row for Dedicated VPC, click Associate VPC in the Actions column.
-
In the Bind to Dedicated VPC Network dialog box, select a VPC and a vSwitch.
Note-
You must select a VPC in the same region as your instance and a vSwitch in the same region and zone as your instance.
-
Binding a dedicated VPC network consumes two or three IP addresses from the VPC (three for Hologres V1.3, two for Hologres V2.0). Ensure that your vSwitch has enough available IP addresses.
-
-
Click OK.
The system starts to bind the dedicated VPC. After the process completes, the system generates a dedicated VPC endpoint.
Unbind a dedicated VPC network
Procedure
-
Log on to the Hologres console.
-
In the top navigation bar, select the region where your instance is located.
-
In the left-side navigation pane, click Instances.
-
On the Instances page, click the name of your target instance.
-
On the Instance Details page, go to the Network Information section. In the row for Dedicated VPC, click Release VPC in the Actions column.
-
In the confirmation dialog box, click Release.
The system releases the dedicated VPC endpoint.
NoteAfter the dedicated VPC endpoint is released, you can no longer use it to connect to the instance.