DLC supports configuring the network (VPC) for the data engine, facilitating the management of data engine access to different data source networks.
Network Configuration Type
Based on different business scenarios, Data Lake Computing offers two types of network configurations.
Enhanced Network Configuration: Suitable for situations requiring high-speed, stable access to data within a single VPC.
Caution
Data engines of non-Spark job types can only be bound to one Enhanced Network Configuration.
Cross-origin Network Configuration: Suitable for cross-origin federated data queries requiring access to multiple VPCs. A data engine can be bound to multiple Cross-origin Network Configurations.
Network Configuration Status
Initial: The network configuration is being initialized, and the network is not yet effective.
Success: The network configuration is effective for the bound engine.
Failure: Network configuration failed, it can be deleted and reconfigured.
Network Configuration Security Policies
If you have configured a Security Group Policy for the VPC, inbound rules need to be added for different types of network configurations.
Enhanced Network: In the Security Group, add inbound rules for the IP range of the VPC where the data source is located.
Cross-origin Network: In the Security Group, add inbound rules for the IP range where the network configuration's bound engine is located.
Create Network Configuration
1. log in to DLC console, select the service region.
2. Access Engine Management> Engine Network Configuration through the left navigation menu.
3. Click the Create Network Configuration button to enter the creation page.
Configure parameters as follows:
Configuration
Required
Filling Instructions
Network Configuration Type
Yes
Select based on use case:
Enhanced Network Configuration: Suitable for scenarios requiring high-speed, stable access to data within a single VPC
Cross-origin Network Configuration: Suitable for scenarios involving cross-origin federated query analysis requiring access to data across multiple VPCs
Configuration Name
Yes
Supports Chinese, English, and _, with a maximum of 35 characters
Instance Source
Yes
Supports two sources:
DLC data directory: You can select the data directory that has been created under DLC's Data Management
New Network Configuration: Choose a new data source to create a network connection. Currently, supported data sources include MySQL, Kafka, EMR HDFS (COS, HDFS, Chdfs), PostgreSQL, SQLServer, and ClickHouse. If the data source required for the network configuration is not yet supported, select Other and manually specify the VPC
Data directory
Yes
Based on the selected instance source, choose the corresponding data directory. The range of available data directories will be related to your account permissions
Bind data engine
Yes
Select the data engine associated with this network configuration. If the data engine is in an isolated or initializing status, it cannot be selected
Configuration description
No
No more than 100 characters
4. Fill out and save to create a network configuration.
Caution
After creation, the network will be in an initialization state, and its status can be viewed in the list afterward.
Delete network configuration
You can manage and delete network configurations that are no longer needed or have failed to configure by deleting them. The steps are as follows:
2. Access Engine Management> Engine Network Configuration through the left navigation menu.
3. Find the network configuration you wish to delete. You can filter search results, but be sure to select the correct Network Configuration Type.
4. Click the Delete button. After a secondary confirmation, the deletion will be complete.
Caution
After deletion, the data engine will not be able to use this network configuration. If access is required, it must be reconfigured. Please proceed with caution.
Modifying description information
You can modify the description of an existing network configuration by following these steps:
Yes
No
Was this page helpful?