Enterprise docs

data.world bridge

The data.world Bridge provides a customer-hosted connectivity hub where connections are outbound-only, short-lived, and highly secure. It is powered by Trustgrid, and trusted by banks, healthcare companies, and many other organizations with very strict security and compliance needs.

Customer-hosted metadata collectors and the technical lineage server do not require inbound connectivity, however data virtualization / federated query and data.world-hosted metadata collection does. The data.world Bridge enables a secure, outbound-only method for brokering those connections.

The data.world Bridge is provided by data.world, and can be implemented as a hardware appliance or a software virtual appliance (image support for AWS, vSphere, Microsoft Azure, and Google Cloud Platform).

data.world handles the Application, Gateway Node, and Cloud Management aspects. Customer responsibility is only the Edge Node(s) and connection to the Database (which represents the databases, BI tools, etc. that is desired to connect to data.world).

We recommend a high availability (HA) implementation, and will provide up to 2 nodes for customers if they are using the data.world Bridge.

dataworld_bridge.png

If you firewall outbound traffic to the internet, or if there will be a firewall between the nodes and your servers, please be sure that the necessary firewall rules are in place to allow traffic from the data.world Bridge. Please contact support with any questions regarding the necessary firewall rules.

If your environment involves multiple VLANs, prepare the desired switch ports to allow access to the correct VLAN.

Standard (one node)

1 Public IP Address

1 Private IP Address

2 DNS Servers

HA (two nodes)

2 Public IP Addresses

2 Private IP Addresses

1 Private IP Address for Cluster IP

2 DNS Servers

4 vCPU (or equivalent)

4 GB RAM

30 GB disk space

For detailed instructions on how to install the data.world Bridge, see the supplemental documentation materials.