The network architecture of Data Management was upgraded on April 26, 2023. During the upgrade, the outbound IP addresses of DMS were changed in some regions. As a result, the IP address whitelists must be updated for databases that are not deployed on Alibaba Cloud and databases that are deployed on the Alibaba Cloud classic network. To ensure that you can use DMS as expected after the network architecture upgrade, you must manually check and update the IP address whitelists of your databases that are managed by DMS.
Upgrade date
April 26, 2023
Impacts
This network architecture upgrade affects only the IP address whitelists of Alibaba Cloud databases, self-managed databases that are not deployed on Alibaba Cloud and connected over the Internet, and self-managed databases hosted on Elastic Compute Service (ECS) instances that are managed by DMS in the following regions: China (Hangzhou), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Shenzhen), China (Guangzhou), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo), US (Silicon Valley), US (Virginia), UK (London), Germany (Frankfurt), SAU (Riyadh), China North 2 Finance (Preview), China East 1 Finance, and China East 2 Finance. This upgrade does not have impacts on the operating of database instances.
You can log on to the DMS console V5.0 and choose Data Assets > Instances to filter instances based on the instance source and region.
Add new outbound IP addresses to IP address whitelists of databases
Alibaba Cloud databases or self-managed databases hosted on ECS instances
Alibaba Cloud database: You need to log on to the console of the corresponding database instance to add the outbound IP addresses to the IP address whitelist of the database instance. After you add the outbound IP addresses to the IP address whitelist, you can try the connection in DMS to check whether the modification is successful.
For example, you can add the outbound IP addresses to the IP address whitelist of an ApsaraDB RDS for MySQL instance. For more information, see Configure an IP address whitelist.
Self-managed database on an ECS instance: You need to modify the security group rules to allow access from the outbound IP addresses for the ECS instance. After access from the outbound IP addresses is allowed, you can try the connection in DMS to check whether the modification is successful. For more information about how to modify security group rules, see Add a security group rule.
Databases connected over the Internet
You need to modify the firewall rules or IP address whitelist for your instance or network to allow access from the outbound IP addresses. After access from the outbound IP addresses is allowed, you can try the connection in DMS to check whether the modification is successful.
DMS outbound IP addresses
Region | Classic network for Alibaba Cloud databases or self-managed databases on ECS instances | Public network |
China (Shanghai) | 11.154.24.173 | 101.133.205.192/26, 47.102.181.128/26, 47.102.181.192/26, 47.102.234.0/26, and 47.102.234.64/26 |
China (Qingdao) | 10.245.213.244 | 118.190.207.194, 118.190.207.25, 120.27.72.0/26, 120.27.72.64/26, 120.27.72.128/26, and 120.27.72.192/26 |
China (Beijing) | 11.115.125.224 | 8.131.132.0/26, 39.107.7.0/26, 39.107.7.64/26, 182.92.32.128/26, and 182.92.32.192/26 |
China (Zhangjiakou) | 11.193.233.87 | 39.101.252.128/26, 47.92.185.0/26, 47.92.185.64/26, 47.92.185.128/26, and 47.92.185.192/26 |
China (Hohhot) | 11.197.113.225 | 39.104.78.173, 39.104.79.122, 39.104.86.0, 39.104.62.152, 39.104.72.87, 39.99.77.0/26, 39.99.77.64/26, 39.99.77.128/26, and 39.104.220.192/26 |
China (Chengdu) | 11.119.156.53 | 47.109.5.0/26, 47.108.45.128/26, 47.108.45.192/26, 47.108.47.0/26, and 47.108.47.64/26 |
China (Shenzhen) | 10.245.164.219 | 47.113.76.192/26, 47.112.83.192/26, 47.112.84.0/26, 47.112.84.64/26, and 47.112.84.128/26 |
China (Guangzhou) | 10.58.93.2 | 8.134.23.174, 8.134.23.38, 8.134.23.84, 8.134.69.233, 8.134.24.129, 8.134.0.64/26, 8.134.0.128/26, 8.134.0.192/26, and 8.134.5.0/26 |
China (Hong Kong) | 10.254.102.13 | 47.243.0.32/28, 47.56.45.128/26, 47.56.45.192/26, 47.90.24.0/26, and 47.90.24.64/26 |
Singapore | 10.88.51.209 | 161.117.172.0/28, 161.117.146.128/26, 161.117.146.192/26, 161.117.164.0/26, and 161.117.164.64/26 |
Malaysia (Kuala Lumpur) | 11.196.42.179 | 47.250.34.128/28, 47.250.30.0/26, 47.250.30.64/26, 47.250.30.128/26, and 47.250.30.192/26 |
Indonesia (Jakarta) | 11.59.138.151 | 147.139.165.206, 147.139.133.46, 147.139.179.168, 147.139.132.101, 147.139.156.0/26, 147.139.156.64/26, 147.139.156.128/26, and 149.129.230.192/26 |
Japan (Tokyo) | N/A | 8.209.192.160/28, 47.91.0.128/26, 47.91.0.192/26, 47.245.51.128/26, and 47.245.51.192/26 |
US (Silicon Valley) | 10.60.82.16 | 47.88.1.17, 47.88.6.196, 47.88.10.217, 47.88.15.174, 47.88.98.0/26, 47.88.98.64/26, 47.88.98.128/26, and 47.88.98.192/26 |
US (Virginia) | 11.194.67.243 | 47.253.64.0/28, 47.252.71.128/26, 47.252.71.192/26, 47.252.90.0/26, and 47.252.90.64/26 |
UK (London) | 11.199.225.130 | 8.208.75.64/28, 8.208.73.0/26, 8.208.73.64/26, 8.208.73.128/26, and 8.208.73.192/26 |
Germany (Frankfurt) | 11.194.56.218 | 47.245.155.0/28, 8.209.86.0/26, 47.254.165.64/26, 47.254.165.128/26, and 47.254.165.192/26 |
SAU (Riyadh) | 10.187.115.137 | 8.213.16.59, 8.213.16.91, 8.213.16.111, 8.213.16.17, 8.213.16.123, 8.213.6.0/26, 8.213.6.64/26, 8.213.6.128/26, and 8.213.6.192/26 |
China North 2 Finance (Preview) | 10.254.22.182 | 39.107.7.0/26, 39.107.7.64/26, 182.92.32.128/26, and 182.92.32.192/26 |
China East 1 Finance | N/A | 116.62.251.150, 47.96.59.4, 47.96.58.245, 116.62.250.113, and 116.62.249.73 |
China East 2 Finance | 10.254.213.170 | 139.224.122.227, 139.224.123.13, 139.224.124.107, 139.224.123.165, 47.102.181.128/26, 47.102.181.192/26, 47.102.234.0/26, and 47.102.234.64/26 |