Anyway mysql workbench client can be made "proxy" aware?
We have started to use Google Cloud SQL, 2nd gen
Presently all outbound traffic is restricted to port 80/443 on our corporate network via a proxy only.
We will shortly be testing a SOCKS Proxy solution to allow port 3306.
I am aware of the the TCP/IP over SSH option in MYSQL Workbench (where we need an additional SSH Remote host potentially in the cloud or on premise), which we are also investigating,
Is there anyway we can simply make the mysql workbench client recognise the cloudsql directly via the socks proxy? Has anyone come up with alternatives in a corporate infrastructure?
-- We have started to use Google Cloud SQL, 2nd gen
Presently all outbound traffic is restricted to port 80/443 on our corporate network via a proxy only.
We will shortly be testing a SOCKS Proxy solution to allow port 3306.
I am aware of the the TCP/IP over SSH option in MYSQL Workbench (where we need an additional SSH Remote host potentially in the cloud or on premise), which we are also investigating,
Is there anyway we can simply make the mysql workbench client recognise the cloudsql directly via the socks proxy? Has anyone come up with alternatives in a corporate infrastructure?
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/073d8d1c-3ff7-4cbd-8e14-3d542b4e0481%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment