Tetra Hub and Data Hub
Tetra Hub and Data Hub are the on-premises software components of the Tetra Data Platform (TDP). they facilitate secure data transfer between the TDP and Connectors and Agents, which can each pull or receive data from individual data sources. A single Hub can integrate with many Connectors and Agents, allowing it to interact with many data sources.
To set up a Tetra Hub or Data Hub, you must first create one in the TDP user interface. Then, download the preconfigured installer and install the Hub on a local machine or a virtual machine (VM) on your network. After installation, the Hub automatically activates and connects to the TDP. You can then configure the Hub’s data connectors through the TDP user interface based on your organization’s requirements.
Hub Versions
There are two Hub versions: Tetra Hub and Tetra Data Hub. Tetra Data Hub is on a deprecation track.
For more information, see Tetra Data Hub Deprecation.
IMPORTANT
For new deployments, Hub should be installed, except for the following use cases:
- Tetra Solace Connector integrations
- Facilitating on-premises HTTP requests from pipelines if AWS PrivateLink or an API gateway doesn't meet your requirements
Key Differences Between Hub and Data Hub
The following table shows the differences between Hub and Data Hub based on the use cases that they serve.
| Use Case | Hub | Data Hub |
|---|---|---|
| Releasing new Connector functionalities or patches independent of a TDP upgrade | Yes | No |
| Acting as a proxy for Tetra Agents that don’t have access to the internet | Yes | Yes—by using a Generic Data Connector (GDC) |
| Acting as a proxy for Tetra IoT Agents | Yes | No |
| Hosting Pluggable Connectors | Yes | No |
| Hosting Legacy Connectors | No | Yes |
| Facilitating on-premises HTTP requests from pipelines | No Note: This functionality is currently in development and testing for Hub. | Yes |
| Requires SSM Agent | Yes (used slightly less) | Yes |
| Requires allow-listed endpoints | Yes (see Tetra Hub Allow List Endpoints) | Yes (see Tetra Data Hub Allow List Endpoints) |
| Requires an allow-listed TDP endpoint | Yes | No |
NOTE
To transfer data to the TDP securely, Tetra Data Hub uses AWS Systems Manager and AWS IoT. Hub uses Amazon Elastic Container Service (Amazon ECS) as well as AWS Systems Manager. For more information, see the Security Considerations section.
Tetra Hub References
For more information about Hub, see the following topics:
- Tetra Hub
- Create and Install a Tetra Hub
- Add a Connector to a Tetra Hub
- Add an Agent to a Tetra Hub
- Tetra Hub System Requirements
- Tetra Hub Proxy Settings
- Tetra Hub Allow List Endpoints
Tetra Data Hub References
For more information about Tetra Data Hub see the following topics:
- Create and Install a Tetra Data Hub
- Add a Connector to a Tetra Data Hub
- Add an Agent to a Tetra Data Hub
- Tetra Data Hub System Requirements
- Tetra Data Hub Proxy Settings
- Tetra Data Hub Allow List Endpoints
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 Data Hub and Hub 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.
Updated 15 days ago