This topic describes how to configure a database whitelist in DataV. Before you add a data source in DataV, you must add the IP addresses in the whitelist of the target region to that of your data source so that DataV can access your database.
If you are using a ApsaraDB for RDS database, add the following IP addresses to the configuration of the RDS database. For more information, see Connect to an ApsaraDB RDS for MySQL instance by using a client or a CLI.
If you are using a user-created database hosted on an Alibaba Cloud ECS instance as the data source, you must add the IP addresses listed in the following table to the security group rules of the ECS instance, system firewall, and your database whitelist.
If you are using a database hosted on a local physical machine as the data source, you must add the IP addresses listed in the following table to the system firewall of the physical machine, network firewalls, and your database whitelist.
The following table lists the IP addresses in whitelists in different regions. You can configure your database whitelist based on the database type.
Whitelist for the Internet
Acceleration area | Whitelist |
Singapore | 47.88.235.235/0,47.74.136.56/0,47.88.250.141/0,47.88.235.217/0,47.74.136.64/0,47.74.136.22/0,47.74.136.12/0,47.88.235.207/0,8.222.246.161/0 |
Malaysia (Kuala Lumpur) | 47.254.212.25/0,47.250.57.176/0 |
Japan (Tokyo) | 47.91.9.73/0,47.91.13.92/0,47.91.9.1/0,47.91.9.42/0,47.74.7.181/0 |
Germany (Frankfurt) | 47.91.83.106/0,47.91.82.104/0,47.91.84.120/0,47.91.84.16/0,47.91.84.36/0 |
China (Hong Kong) | 47.90.68.215/0,47.75.228.154/0,47.91.171.160/0,47.90.68.160/0,47.75.228.234/0,47.91.172.161/0,47.91.172.151/0,8.217.17.213/0 |
US (Silicon Valley) | 47.88.99.201/0,47.254.58.179/0,47.88.99.83/0,47.88.108.155/0,47.88.99.128/0 |
US (Virginia) | 47.89.170.94/0,47.89.170.79/0,47.89.170.80/0,47.89.170.71/0,47.89.170.97/0 |
Whitelist for an internal network (classic network)
Acceleration area | Whitelist |
Singapore | 11.193.8.8/0,11.192.152.94/0,11.193.8.55/0,11.193.8.59/0,10.152.165.219/0,11.192.152.89/0,11.192.152.117/0,11.193.8.60/0 |
Malaysia (Kuala Lumpur) | 11.193.189.75/0,11.193.189.69/0,11.193.189.73/0,11.193.189.72/0 |
Japan (Tokyo) | 11.192.149.155/0,11.192.149.118/0,11.192.147.75/0,11.192.149.66/0 |
Germany (Frankfurt) | 11.192.169.2/0,11.192.168.143/0,11.193.107.16/0,11.192.170.80/0,11.192.170.221/0 |
China (Hong Kong) | 11.193.118.80/0,11.193.118.65/0,11.193.12.4/0,11.193.118.48/0,11.193.118.86/0,11.193.11.239/0,11.193.11.200/0 |
US (Silicon Valley) | 11.193.216.239/0,11.193.216.224/0,11.193.216.227/0,11.193.216.234/0,11.193.216.184/0 |
US (Virginia) | 10.152.235.192/0,10.152.235.29/0,10.152.235.171/0,10.152.235.194/0,10.152.235.191/0 |
When you configure an intranet (classic network) whitelist, you may encounter 11 CIDR blocks. For more information, see 11 CIDR blocks.
Whitelist for an internal network (VPC)
Acceleration area | Whitelist |
Singapore | 100.104.13.0/24 |
Malaysia (Kuala Lumpur) | 100.104.133.64/26 |
Japan (Tokyo) | 100.104.175.0/24 |
Germany (Frankfurt) | 100.104.244.192/26 |
China (Hong Kong) | 100.104.188.0/24 |
US (Silicon Valley) | 100.104.144.0/26 |
US (Virginia) | 100.104.89.64/26 |
Troubleshoot inaccessible IP addresses on the 11.x.x.x network segments
If IP addresses on the 11.x.x.x network segments are inaccessible, run the following command to add a route to the /etc/rc.local file.
sudo route add -net 11.0.0.0/8 gw 10.152.28.247gw the IP address behind the gateway for your server native.
If the problem persists, submit a ticket to ECS technical personnel.