Tetra Hub

Tetra Hub is the on-premises software component of the Tetra Data Platform (TDP). It facilitates secure data transfer between the TDP and Connectors and Agents, which can each pull or receive data from individual data sources. A single Tetra Hub can integrate with many Connectors and Agents, allowing it to interact with many data sources.

To set up a Tetra Hub, you must first create one in the TDP user interface. Then, download the preconfigured installer and install the Tetra Hub on a local machine or a virtual machine (VM) on your network. After installation, the Tetra Hub automatically activates and connects to the TDP. You can then configure the Tetra Hub’s data connectors through the TDP user interface based on your organization’s requirements.

Tetra Hub Versions

There are two Tetra Hub versions: Hub v2 and Hub v1 (previously Tetra Data Hub). Tetra Hub v1 is on a deprecation track.

For more information, see Tetra Hub v1 Deprecation.

🚧

IMPORTANT

For new deployments, Hub v2 should be installed, except for the following use cases:

Key Differences Between Hub v2 and Hub v1

The following table shows the differences between Hub v2 and Hub v1 (previously Tetra Data Hub) based on the use cases that they serve.

Use CaseHub v2Hub v1
Releasing new Connector functionalities or patches independent of a TDP upgradeYesNo
Acting as a proxy for Tetra Agents that don’t have access to the internetYesYes—by using a Generic Data Connector (GDC)
Acting as a proxy for Tetra IoT AgentsYesNo
Hosting Pluggable ConnectorsYesNo
Hosting Legacy ConnectorsNoYes
Facilitating on-premises HTTP requests from pipelinesNo

Note: This functionality is currently in development and testing for Hub v2.
Yes
Requires SSM AgentYes (used slightly less)Yes
Requires allow-listed endpointsYes (see Tetra Hub v2 Allow List Endpoints)Yes (see Tetra Hub v1 Allow List Endpoints)
Requires an allow-listed TDP endpointYesNo

📘

NOTE

To transfer data to the TDP securely, Tetra Hub v1 uses AWS Systems Manager and AWS IoT. Hub v2 uses Amazon Elastic Container Service (Amazon ECS) as well as AWS Systems Manager. For more information, see the Security Considerations section.

Tetra Hub v2 References

For more information about Hub v2, see the following topics:

Tetra Hub v1 References

For more information about Tetra Hub v1 see the following topics:

Security Considerations

Keep in mind the following security considerations when using a Tetra Hub.

AWS SSM Agent is Required When Using a Tetra Hub

The AWS Systems Manager Agent (SSM Agent) is a hard requirement of the Amazon ECS agent that Tetra Hub v1 and Hub v2 use to securely orchestrate TDP containers on host servers that are on-premises. AWS Systems Manager lets you remotely and securely manage on-premises servers and virtual machines (VMs) in your hybrid environment.

The SSM Agent is Amazon software that runs on your Amazon Elastic Compute Cloud (Amazon EC2) instances and your hybrid instances that are configured for AWS Systems Manager. The agent processes requests from the Systems Manager service in the cloud, and then runs them on the local server as specified in the request. The SSM Agent then sends status and execution information back to the Systems Manager service.

For more information, see Working with SSM Agent in the AWS documentation.

Network Segmentation

If you have concerns with SSM Agents running in your network, it's recommended that you implement network segmentation—an architectural approach that divides a computer network into subnets, or network segments. Network access control lists (ACLs) can then be implemented on the network boundaries to ensure Tetra Hub isolation. This setup reduces the impact of a compromised Hub by segmenting it from other resources on your network.

The TetraScience team can partner with your networking team to help ensure proper implementation. For more information, contact your customer success manager (CSM). Also, see Control traffic to subnets using network ACLs in the AWS documentation.