When you import data from data nodes such as MySQL, SQL Server, or Kafka data nodes, you must enable the whitelist feature for the data import jobs. This way, the jobs can access the data nodes. This topic describes the IP address whitelists for different data import jobs. This topic also provides an example on how to configure a whitelist.
IP addresses
If your data node and the project to which your data import job belongs reside in virtual private clouds (VPCs) in the same region, you must add a VPC IP address whitelist to your data node. In other cases, your data import job can access your data node only over the Internet. In this case, you must add an Internet IP address whitelist to your data node.
For example, you create a data import job in a project that resides in the China (Beijing) region to import data from an ApsaraDB RDS for MySQL database that is deployed on the Internet. In this example, you must add a whitelist that contains the following IP addresses to the database: 59.110.6.146, 39.105.19.110, 47.93.61.189, and 182.92.187.76.
Region | VPC IP address whitelist | Internet IP address whitelist |
China (Hangzhou) | 100.104.0.0/16 |
|
China (Shanghai) | 100.104.0.0/16 |
|
China (Qingdao) | 100.104.0.0/16 |
|
China (Beijing) | 100.104.0.0/16 |
|
China (Zhangjiakou) | 100.104.0.0/16 |
|
China (Hohhot) | 100.104.0.0/16 |
|
China (Ulanqab) | 100.104.0.0/16 |
|
China (Shenzhen) | 100.104.0.0/16 |
|
China (Heyuan) | 100.104.0.0/16 |
|
China (Guangzhou) | 100.104.0.0/16 |
|
China (Chengdu) | 100.104.0.0/16 |
|
China (Hong Kong) | 100.104.0.0/16 |
|
Singapore | 100.104.0.0/16 |
|
South Korea (Seoul) | 100.104.0.0/16 |
|
Japan (Tokyo) | 100.104.0.0/16 |
|
Malaysia (Kuala Lumpur) | 100.104.0.0/16 |
|
Indonesia (Jakarta) | 100.104.0.0/16 |
|
Philippines (Manila) | 100.104.0.0/16 |
|
Thailand (Bangkok) | 100.104.0.0/16 |
|
Germany (Frankfurt) | 100.104.0.0/16 |
|
UK (London) | 100.104.0.0/16 |
|
US (Virginia) | 100.104.0.0/16 |
|
US (Silicon Valley) | 100.104.0.0/16 |
|