You need to enable JavaScript to run this app.
Intelligent Data Insight

Intelligent Data Insight

  • Documentation
    • Intelligent Data InsightDataWind User GuideManagement, Operation and MaintenanceSystem Operation and MaintenanceAccess Regions and BytePlus Intranet Connection
Copy page
Download PDF
System Operation and Maintenance
Access Regions and BytePlus Intranet Connection
Copy page
Download PDF
Access Regions and BytePlus Intranet Connection

This document introduces basic information about access regions (Region) and the fundamental features of BytePlus intranet connection.

Access regions

The available access regions (Region) for the SaaS version include: North China 2 (Beijing), East China 2 (Shanghai), and Asia Pacific Southeast (Johor).
The regions supported by Intelligent Data Insight are shown in the following table:

Region

City

RegionID

North China 2

Beijing

cn-beijing

East China 2

Shanghai

cn-shanghai

Southeast Asia Pacific

Johor

ap-southeast-1

  • If you have already purchased the product:
    • You can view the access region (Region) for the product you are currently using in the upper right corner of the product interface.
    • In general, for enterprise customers who have activated product services, the access region (Region) is North China 2 (Beijing).
  • If you have not purchased the product:
    • If you have not yet purchased Intelligent Data Insight, you will be able to select the access region (Region) yourself when making a future purchase.
    • The currently available access regions (Region) include North China 2 (Beijing), East China 2 (Shanghai), and Asia Pacific Southeast (Johor).

tip

  • Region refers to the geographic area where the physical data center is located. After a resource is created, the region cannot be changed. The internal networks of different regions are completely isolated.
  • From a geographical perspective, it is generally recommended to select the region closest to you or your target users to reduce network latency and improve access speed. For more information, see Regions and Availability Zones.
  • If the user switches the access region from North China 2 (Beijing) to East China 2 (Shanghai), a new purchase is required, and the product interface will present the purchase page to the user. In addition, please note that data in North China 2 (Beijing) and East China 2 (Shanghai) are isolated from each other. Data connections and datasets in Intelligent Data Insights do not support cross-region access or usage.
  • If the user switches the access region of other products under BytePlus to East China 2 (Shanghai), the access region of Intelligent Data Insights will also be displayed as East China 2 (Shanghai). Products under BytePlus do not support multiple access regions.

BytePlus intranet connection

warning

When users select the internal network connection of BytePlus, it is necessary to add the IP address "100.64.0.0/10" to the allowlist configuration of the corresponding database (using MySQL as an example); otherwise, the connection cannot be established.

Feature overview

  • Currently, among the data connection methods of Intelligent Data Insight, the data sources that support intranet connection include:
    MySQL, Oracle, Bytehouse CDW, SQL Server, ClickHouse, PostgreSQL, LAS_jdbc, StarRocks, Bytehouse_CE, Trino, TIDB, OpenGauss, OceanBase Oracle, Oceanbase MySQL, Inceptor, GoldenDB, DM, Presto, Impala, Hive_jdbc, Doris, DB2.

  • When a data source supports intranet connection, you also need to select the VPC Mode option in the connection parameters. After selecting it, you can enter the VPC ID where the database is located, and then connect to the database through the LAN IP address under that VPC.
    As shown in the following figure, you need to obtain Server IP.

    tip

    Only internal network access within the same region of BytePlus is supported. For example, if DataWind is purchased in the North China region, the VPC must also be in North China. To establish a cross-region connection, it is necessary to use products such as Cloud Enterprise Network to connect the VPCs in both regions and set up a proxy node in North China for the connection.

Obtain the database LAN IP

There are two methods to obtain the database LAN IP. The first method is to query by pinging the LAN domain name, and the second method is to query through NIC management under the VPC. The following section provides detailed instructions.

Query by pinging the LAN domain name

  1. Open the command line tool: In Windows, press Windows+R, enter cmd and press Enter to open the Command Prompt window; in macOS or Linux, open the Terminal application.
  2. Ping the LAN domain name: Enter ping [database LAN domain name], for example, ping mysql-server.local, and press Enter. After executing the command, the IP address corresponding to the domain name will be displayed. This IP address is the database server's IP address in the LAN.

Query through VPC NIC management

Using MySQL as an example, the same applies to databases deployed in environments for other products such as PostgreSQL, load balancing, ECS, and others.

  1. Go to the MySQL instance list page and click to view "Instance Information".
  2. Go to the network interface page. In the Private IP Address section, you can view the LAN IP.

Obtain the VPC ID

The user can only query the VPC ID through the VPC's network interface management.
Using MySQL as an example, the same applies to databases deployed in environments for other products such as PostgreSQL, load balancing, ECS, and others.

  1. Go to the MySQL instance list page and click to view "Instance Information".
  2. Copy the "ID" from the "Basic Information" section shown in the figure below to obtain the VPC ID.

Enter the server IP and VPC ID

  1. Go to the data connection configuration page and enter the copied "ID" in field A, "VPC ID".
  2. Copy the LAN IP and enter this IP in field B, "Server", on the data connection page.

Last updated: 2026.06.11 17:50:47