When you can't connect to an ApsaraDB RDS for SQL Server instance, the problem is most likely network-related. The self-service diagnostics feature runs a connectivity test between your client and the RDS instance, checks whether your IP address is in the IP address whitelist, and tells you what to fix.
How it works
The feature tests the network path between the connection initiator and your RDS instance:
-
If the IP address of the connection initiator is not in the IP address whitelist, the test fails.
-
If the IP address falls within a CIDR block that is added to the whitelist, the test succeeds.
Common causes of connection failures
Before running the diagnostic, check whether your situation matches one of the common causes below:
| Cause | Details |
|---|---|
| IP address not whitelisted | The IP address of your client or ECS instance is not in the RDS IP address whitelist. Use the diagnostic to identify and add the correct IP. |
| VPC mismatch | If your RDS instance is in a virtual private cloud (VPC), only ECS instances in the same VPC can connect over the internal network. An ECS instance in a different VPC cannot connect, even if its IP address is whitelisted. |
| No public endpoint | To connect over the Internet, your RDS instance must have a public endpoint. If you haven't applied for one, apply for a public endpoint first. |
Run the diagnostic
-
Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region where your RDS instance resides. Find and click the ID of the instance.
-
In the left-side navigation pane, click Database Connection.
-
In the Connection Troubleshooting section, add the IP address you want to test:
-
Internal network: Click the Intranet Troubleshooting tab, then click Add intranet ECS IP. In the dialog box, select the ECS instance, add it to the Selected ECS instances section, and click OK.
-
Internet: Click the Extranet Troubleshooting tab, then click Add Extranet IP. Enter the IP address of your on-premises device, or click Load Local Public IP Address (If there is a network proxy on your PC, please turn it off first) to auto-detect the current machine's public IP. Then click OK.
Auto-detection only works when your network proxy is disabled. If you're behind a proxy, turn it off before clicking Load Local Public IP Address (If there is a network proxy on your PC, please turn it off first).
-
-
Click Start Check.
-
Based on the test result, take the appropriate action:
Status What it means Action Normal Connectivity is fine No action required IP is not in the instance whitelist Your IP is not whitelisted Click Configure Whitelist in the Action column to add the IP to the whitelist Abnormal An issue was detected Click Submit Ticket in the Action column
What's next
-
Connect to an RDS instance using SQL Server Management Studio (SSMS) or Data Management (DMS).
-
If the issue persists after whitelisting, see What do I do if I fail to connect to an ApsaraDB RDS instance?