Connect Aiven to Excel, Sheets and AI

Every Aiven service gets its own port

Most managed Postgres runs on 5432 and most managed MySQL runs on 3306. Aiven does neither, and it shapes how this card behaves.

• The port is per service — a five-digit number Aiven allocates, not a well-known one. The card ships with the port field empty rather than prefilling a value that would be wrong.
• Because the port carries no engine signal, pasting a bare host and port is not enough to tell PostgreSQL from MySQL. Paste the whole Service URI and the scheme settles it.
• The defaults that can be prefilled are: the database defaultdb and the user avnadmin, which is what a fresh Aiven service starts with.
• A connection pool has its own port too, and its own name — on Aiven the pool name goes in the Database field.

Two engines, and they are not identical underneath

The card looks the same whichever engine you pick, but what the agent does with it differs, and it is worth being precise rather than reassuring.

• On PostgreSQL, TLS is enforced for .aivencloud.com hosts whatever the checkbox says. A string that lost its sslmode in the clipboard still travels encrypted.
• On MySQL the checkbox is real. It is on by default and should stay on — turn it off and the connection is unencrypted, with nothing to override it.
• Either way the traffic is encrypted but the certificate chain is not verified. Aiven's CA download is not wired into this card, and there is no field to upload it.
• Pooling adaptations are PostgreSQL-only. On a Postgres pool the agent turns off prepared statements and skips the session reset, which is what a transaction pooler needs; on MySQL the mode is recorded but changes nothing.

Paste the Service URI, not the pieces

Four fields and a per-service port is more than anyone should retype, so the card is built around the string.

• The postgres:// and mysql:// URI forms both parse, and the scheme is what tells the card which engine you meant.
• Anything with the wrong scheme is rejected rather than half-parsed into the wrong fields.
• A password with leading or trailing whitespace is flagged. It is a clipboard artifact and it fails as an ordinary authentication error, which sends people looking for the wrong problem.
• The pasted URI is never stored. It is read once to fill the form and then dropped, so the password lives in one place rather than two.

-- PostgreSQL on Aiven, read-only
SELECT   c.name,
         COUNT(o.id)   AS orders,
         SUM(o.amount) AS revenue
FROM     public.customers AS c
JOIN     public.orders    AS o ON o.customer_id = c.id
WHERE    o.placed_at >= now() - interval '30 days'
GROUP BY c.name
ORDER BY revenue DESC;