Why should you care?

PostgresVerse cloud mandates TLS so credentials and row data never cross public WiFi in plaintext.

See it live — copy this example

Run in pgAdmin or psql.

# psql with SSL
psql "host=db.postgresverse.com port=5432 dbname=PostgresVerse user=api_reader sslmode=require"

-- inside session
SELECT ssl_is_used(), ssl_version();

Run Example »

This lesson uses terminal or setup steps. Run commands on your computer — the live editor appears on coding lessons.

What happened?

• sslmode=require forces encrypted connection.
• ssl_is_used confirms handshake succeeded.
• ssl_version shows TLS level negotiated.

Practice next

1. Obtain server cert or use cloud provider CA bundle.
2. Connect with sslmode=require from laptop.
3. Run ssl_is_used(); should be true.
4. Compare latency ssl vs non-ssl on LAN — usually negligible.
5. Rotate cert and document app trust store update.

Remember

hostssl in pg_hba enforces TLS clients. sslmode verify-full checks hostname. Managed clouds expose CA download for clients.

PostgresVerse TLS mandate

Security disables non-SSL hba rows; mobile backend uses RDS CA in connection string.

Outcome: Pen test finds no plaintext postgres protocol on wire.