Connect MySQL HeatWave to Excel, Sheets and AI

OCI is private, AWS is public, and it changes where the agent goes

HeatWave is sold as one product but deployed in two shapes, and the difference decides your install location rather than your connection settings.

• On OCI, a HeatWave DB system lives inside your VCN and is not reachable from the internet. Put the agent on a Compute instance in that same VCN and point it at the private endpoint.
• On AWS, HeatWave exposes a public TLS endpoint. The agent can run anywhere that can reach it, including on your own hardware.
• Either way the agent only makes outbound connections. There is no inbound rule to add, no ingress to open on the VCN and no VPN between your network and ours.
• The connection settings themselves do not change between the two. Same port, same fields, same driver — only the endpoint and the sensible agent location differ.

TLS is the checkbox, and it is on by default

Worth being precise about, because HeatWave's two deployment shapes have genuinely different exposure.

• Use SSL is on by default, and while it is on the connection is encrypted — the agent asks MySQL for a required TLS session.
• Turn it off and the agent will attempt an unencrypted connection. Nothing here overrides that based on the endpoint, so the checkbox is the whole mechanism.
• That matters most on AWS, where the endpoint is public. Over the public internet, leaving TLS on is not optional in any practical sense.
• Encryption is not certificate verification. The agent requires TLS but does not validate the server's certificate chain, so treat it as protection against eavesdropping rather than proof of what you reached.

Underneath it is MySQL, which is the point

HeatWave's analytics engine is Oracle's business. What reaches Query Streams is a MySQL connection.

• The agent connects with a standard MySQL driver and runs ordinary read-only SQL. Nothing about the query path is HeatWave-specific.
• MySQL has no separate schema layer, so the database is the qualifier. That is what a cross-source reference carries.
• Cross-database queries on one HeatWave connection work the way they do on any MySQL server, so a single connection can reach more than one database.
• A read-only user is worth creating. Query Streams will not write, but the safest way to guarantee that is at the database rather than in the tool.

-- Ordinary MySQL, read-only, over TLS
SELECT   c.name,
         COUNT(o.id)   AS orders,
         SUM(o.amount) AS revenue
FROM     customers AS c
JOIN     orders    AS o ON o.customer_id = c.id
WHERE    o.placed_at >= NOW() - INTERVAL 30 DAY
GROUP BY c.name
ORDER BY revenue DESC;