The workspaces were created identically with the CloudFormation automation provided by databricks. So both workspaces for instance allow access via DB cli and api, so the issue of routing from the public internet is not an issue, at least to the workspace.

When I curl the sql endpoint both respond.

But with the us-east-2 server:

Traceback (most recent call last):

 File "/Users/marcussimonsen/work/analytics/db_sql_connector.py", line 4, in <module>

   connection = sql.connect(

 File "/Users/marcussimonsen/work/analytics/.venv/lib/python3.8/site-packages/databricks/sql/__init__.py", line 50, in connect

   return Connection(server_hostname, http_path, access_token, **kwargs)

 File "/Users/marcussimonsen/work/analytics/.venv/lib/python3.8/site-packages/databricks/sql/client.py", line 129, in __init__

   self._session_handle = self.thrift_backend.open_session(

 File "/Users/marcussimonsen/work/analytics/.venv/lib/python3.8/site-packages/databricks/sql/thrift_backend.py", line 444, in open_session

   response = self.make_request(self._client.OpenSession, open_session_req)

 File "/Users/marcussimonsen/work/analytics/.venv/lib/python3.8/site-packages/databricks/sql/thrift_backend.py", line 373, in make_request

   self._handle_request_error(error_info, attempt, elapsed)

 File "/Users/marcussimonsen/work/analytics/.venv/lib/python3.8/site-packages/databricks/sql/thrift_backend.py", line 241, in _handle_request_error

   raise network_request_error

databricks.sql.exc.RequestError: Error during request to server