Connect Amazon RDS from a Desktop GUI (Security Group + global-bundle.pem + verify-full)
Connect Amazon RDS for PostgreSQL (or MySQL) from a laptop GUI: turn on public access, open the security group to your IP, and use global-bundle.pem with sslmode=verify-full—with HiDataLinker, a free local-first PostgreSQL and MySQL desktop client.
A laptop cannot reach a private-only Amazon RDS instance, or one whose security group still blocks inbound traffic. sslmode=verify-full also fails unless you attach the current RDS CA bundle and connect by hostname. This guide walks an Amazon RDS PostgreSQL desktop GUI path (and the MySQL twin) 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.
1. Confirm a public endpoint you can reach
In the RDS console, open the instance → Connectivity & security. Copy the endpoint (….region.rds.amazonaws.com) and port—do not assume 5432 or 3306. For a laptop, Public access must be Yes, and the DB subnet group needs an internet gateway. If it is No, use a VPC path, bastion, or VPN you already run—this guide does not add an in-app AWS tunnel. Use the instance endpoint (the name on the certificate), not a resolved IP or a custom DNS alias.
2. Open the security group to your laptop IP
VPC security groups for RDS start by blocking all inbound traffic. Add an inbound rule: TCP on the database port (5432 for PostgreSQL, 3306 for MySQL) from your current public IP as a /32. Re-add it when a home IP changes, and do not leave 0.0.0.0/0 on prod. A hang with no auth error is usually the security group or a private-only path—not the client.
3. Download global-bundle.pem
Amazon RDS signs the server certificate with an RDS CA (default rds-ca-rsa2048-g1). The older rds-ca-2019 CA expired in August 2024—do not keep an expired bundle for RDS global-bundle.pem GUI checks. For any commercial Region:
curl -O https://truststore.pki.rds.amazonaws.com/global/global-bundle.pem
A regional PEM also works in one Region. The certificate’s Common Name is the instance endpoint, so connect RDS sslmode=verify-full CA checks must use that hostname.
4. sslmode=require vs verify-full (PostgreSQL)
| Mode | Encrypted | Verifies cert | Verifies hostname |
|---|---|---|---|
require |
Yes | No* | No |
verify-ca |
Yes | Yes | No |
verify-full (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 for hostname checks.
postgresql://USER:PASSWORD@INSTANCE.XXXX.REGION.rds.amazonaws.com:5432/APP_DB?sslmode=verify-full&sslrootcert=/path/to/global-bundle.pem
rds.force_ssl defaults to on for RDS for PostgreSQL 15 and later, and off for 14 and older. When it is on, disabling TLS fails with FATAL: no pg_hba.conf entry … SSL off. Change it only in a custom parameter group (reboot if you attach that group later). Use your application database, not only postgres, and percent-encode passwords in the URI.
5. MySQL twin (same public access + CA idea)
For Amazon RDS for MySQL, copy the endpoint and port, set Public access to Yes, and allow your laptop IP on 3306. require_secure_transport defaults to OFF; if you set it ON, unencrypted clients get Error 3159. Attach global-bundle.pem and use REQUIRED for encryption, or VERIFY_CA / VERIFY_IDENTITY against the instance hostname (VERIFY_IDENTITY is the MySQL counterpart of verify-full).
6. Connect with HiDataLinker
- Install from hidatalinker.onesolo.app (see the download page for OS builds).
- Open New Connection → paste the RDS URI (keep TLS on; do not strip
sslmodeorsslrootcert). - Test, then connect. Profiles stay on your machine—local-first, no hosted workspace.
- Browse schemas, run SQL, and use Dump (
.sql) or same-engine migrate for a free clone between connections.
Source: github.com/henrybit/HiDataLinker · Overview: /db-client
RDS ships PostgreSQL and MySQL under one console family. HiDataLinker is a thin Tauri desktop app for both—paste DATABASE_URL, keep creds local, and avoid seat / connection / tab freemium walls. Honest v1: MySQL + PostgreSQL as marketed; not an RDS console, IAM DB auth / RDS Proxy manager, or in-app bastion.
Common failures (and the fix)
- Timeout, no clear auth error — Public access is No, the security group is missing your current public IP, or you used a private-only path.
certificate verify failed/ missing root cert — An expiredrds-ca-2019file, a missingglobal-bundle.pem, orverify-fullwithoutsslrootcert.- verify-full fails after “it worked with require” — You connected by IP or a custom alias; use the exact instance endpoint.
no pg_hba.conf entry … SSL off—rds.force_sslis on; do not stripsslmode.- Auth / wrong database — Re-copy the master user from Configuration; connect to your app database, not only
postgresormysql.
Soft next step
Need an Amazon RDS PostgreSQL desktop GUI that pastes the URI, respects sslmode=verify-full with global-bundle.pem, and stays local-first?
- Download: https://hidatalinker.onesolo.app/
- Source: https://github.com/henrybit/HiDataLinker
Turn on public access, allow your laptop IP in the security group, attach the CA bundle, then query from a free MIT client.