From ca0ab8347552f4d3e2d4998068fd2b504250c387 Mon Sep 17 00:00:00 2001 From: Alex Yarosh <alexandra@metabase.com> Date: Wed, 13 Mar 2024 13:24:44 -0600 Subject: [PATCH] cloud doesn't support vpn (#40090) --- docs/databases/ssh-tunnel.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/databases/ssh-tunnel.md b/docs/databases/ssh-tunnel.md index 1f16148e540..443a7731e6c 100644 --- a/docs/databases/ssh-tunnel.md +++ b/docs/databases/ssh-tunnel.md @@ -17,6 +17,8 @@ In general, there are two basic use cases for an SSH tunnel: Sometimes when a data warehouse is inside an enterprise environment, direct connections are blocked by security devices such as firewalls and intrusion prevention systems. Bastion hosts offer the option to first connect to a computer on the edge of the protected network, then, from that bastion host computer, establish a second connection to the data warehouse within the internal network, essentially patching these two connections together. Using the SSH tunneling feature, Metabase can automate this process. +> [Metabase Cloud](https://www.metabase.com/cloud/) does not currently support VPN connections to databases. To connect to databases in private networks, you can instead use SSH tunneling. + ## How to use SSH tunneling When connecting though a bastion host: -- GitLab