Connect ApsaraDB RDS from a Desktop GUI (Public Endpoint + Whitelist + verify-full)
Connect Alibaba Cloud ApsaraDB RDS for PostgreSQL (or MySQL) from a laptop GUI: apply for a public endpoint, replace the default 127.0.0.1 whitelist, enable SSL, and use ApsaraDB-CA-Chain.pem with sslmode=verify-full—with HiDataLinker, a free local-first PostgreSQL and MySQL desktop client.
A laptop cannot reach an ApsaraDB RDS instance on the internal VPC endpoint alone. By default the IP whitelist is only 127.0.0.1, SSL is off until you enable it, and a cloud certificate protects one endpoint at a time—internal or public. This guide walks an Alibaba Cloud RDS desktop GUI path for PostgreSQL (and MySQL) with HiDataLinker, a free MIT PostgreSQL and MySQL desktop client: local-first credentials, URL paste, Dump / same-engine migrate, and no seat or tab freemium wall on the core workflow.
1. Apply for a public endpoint
In the ApsaraDB RDS console, open the instance → Database Connection. An internal endpoint (for example ….pg.rds.aliyuncs.com) is provided by default. For a laptop or any host outside that VPC, click Apply for Public Endpoint and copy the public host and port—do not assume 5432 or 3306 if you changed them. Prefer the internal endpoint for apps already in the same VPC. Enabling a public endpoint on PostgreSQL can add 0.0.0.0/0 automatically—replace it after a short test. On MySQL, decline that option unless you are testing.
2. Fix the default 127.0.0.1 whitelist
Open Data Security and edit the IP whitelist. The default group starts with only 127.0.0.1, which blocks every real client. Add your laptop’s current public IP (a /32) for an ApsaraDB RDS desktop GUI session; re-add it if your public IP changes. Do not delete the default group, and do not leave 0.0.0.0/0 on production.
3. Enable SSL and download ApsaraDB-CA-Chain.pem
SSL is not on by default. On Data Security → SSL, enable a cloud certificate and protect the public hostname (a cloud certificate covers only one endpoint). Enabling or changing SSL can restart the instance—do this off-peak. Click Download CA Certificate and unzip ApsaraDB-CA-Chain.pem for the desktop client.
4. sslmode=require vs verify-full (PostgreSQL)
| Mode | Encrypted | Verifies server cert | Verifies hostname |
|---|---|---|---|
require |
Yes | No* | No |
verify-ca |
Yes | Yes | No |
verify-full (use when the client can attach the CA) |
Yes | Yes | Yes |
*With libpq, a CA in the default path can make require act like verify-ca—set sslmode=verify-full explicitly for hostname checks.
Build a URI from the public endpoint the certificate protects (not an IP):
postgresql://USER:PASSWORD@PUBLIC_HOST:PORT/APP_DB?sslmode=verify-full&sslrootcert=/path/to/ApsaraDB-CA-Chain.pem
Use your application database, not the default postgres system database as a daily workspace. For connect ApsaraDB RDS verify-full, the Host must match the certificate CN/DNS name.
5. MySQL twin (same public endpoint + CA idea)
For ApsaraDB RDS for MySQL, apply for the public endpoint (….mysql.rds.aliyuncs.com), whitelist the laptop IP, enable SSL on the public endpoint, and download the same ApsaraDB-CA-Chain.pem. Use REQUIRED for encryption, or attach the PEM and choose VERIFY_CA / VERIFY_IDENTITY against the public hostname.
6. Connect with HiDataLinker
- Install from hidatalinker.onesolo.app (check the download page for macOS / Windows / Linux builds).
- Open New Connection → paste the ApsaraDB URI (keep TLS on; do not strip
sslmode). - Test, then connect. Profiles stay on your machine—local-first, no hosted workspace for secrets.
- Browse schemas, run SQL, and use Dump (
.sql) or same-engine migrate when you need a free clone between saved connections.
Source: github.com/henrybit/HiDataLinker · Overview: /db-client
Why a light dual-engine client helps here
ApsaraDB RDS ships PostgreSQL and MySQL under one console family. HiDataLinker is a thin Tauri desktop app for both engines—paste DATABASE_URL, keep creds local, and avoid seat / connection / tab freemium walls on daily browse and query. Honest v1 focus: MySQL + PostgreSQL as marketed; not an ApsaraDB console, VPC/CEN manager, or in-app Alibaba bastion.
Common failures (and the fix)
- Timeout, no clear auth error — No public endpoint, the whitelist is still
127.0.0.1or missing your current public IP, or you pasted the internal host from outside the VPC. certificate verify failed/ missing root cert — SSL not enabled, wrong or missingApsaraDB-CA-Chain.pem, or the cloud certificate protects the internal endpoint while you connect to the public host.- verify-full fails after “it worked with require” — Connecting by IP or a hostname that is not the protected endpoint; use the exact public host from Database Connection.
- Auth / wrong database — Re-copy credentials from Accounts; connect to your app database, not only
postgres/mysql. Keep password percent-encoding in the URI.
Soft next step
Need an ApsaraDB RDS desktop GUI that pastes the string, respects verify-full with ApsaraDB-CA-Chain.pem, and stays local-first for PostgreSQL and MySQL?
- Download: https://hidatalinker.onesolo.app/
- Source: https://github.com/henrybit/HiDataLinker
Apply for the public endpoint, replace the default 127.0.0.1 whitelist, protect the public host with a cloud certificate, then query from a free MIT dual-engine desktop client.