A Tetra Hub v2 must be installed on a network server or virtual machine (VM) that is dedicated to TetraScience. The network server or VM that you install a Hub on must allow TetraScience to remotely reboot the local or virtual machine.
To install a Tetra Hub v2, a network server or VM must meet the following system requirements.
Tetra Hub v2 supports 64-bit versions of the following platforms:
- Ubuntu 18.04 and higher versions (excluding Unbuntu 22.04)
- RedHat 7.5 and higher versions
- CentOS 7 and higher versions
Network servers and VMs must meet the following minimum hardware requirements:
- 2+ GHz processor
- 8 GB RAM required, 16 GB RAM recommended
- 50+ GB available disk space
- 4+ CPUs
Admin (sudo) access to the network server or VM is required.
Your environment must meet the following network access and bandwidth requirements:
- Outbound internet access (or access to a proxy that can provide it) is required.
- At least one port must be available for each Connector.
- A network bandwidth of at least 100 Mbps is required (1000 Mbps is recommended).
Keep in mind the following when setting up a Tetra Hub v2:
- Tetra Hub v2 uses the AWS Systems Manager Agent (SSM Agent).
- The instance running the Hub and SSM Agent must have outbound internet access, or access to a proxy that can provide it. Outbound internet access allows the SSM Agent to connect to AWS service endpoints. For more information, see Setting up AWS Systems Manager and AWS service endpoints in the AWS Documentation.
- During installation, the Hub gets registered as an SSM instance within the TDP AWS account. The hub can’t also be registered as an SSM instance in any other AWS account. For TDP v3.6.x and higher, the Hub v2 installer automatically detects this issue and fixes it, if allowed. For TDP v3.5.x and earlier, you must remove the existing SSM registration key prior to Hub installation. For more information, see Troubleshoot Hub v2 Installation Issues.
- The Hub’s host server can’t have its own Amazon Elastic Compute Cloud (Amazon EC2) instance role. If there is an existing AWS Identity and Access Management (IAM) role, the Hub’s Amazon ECS service will attempt to use it. The Hub’s Amazon ECS instance registration process fails when this happens. As a workaround, customers can detach the Amazon EC2 IAM role from the Amazon EC2 instance, and then rerun the Hub installation script. For more information, see Troubleshoot Hub v2 Installation Issues.
- All outbound communication from the SSM Agent to AWS Systems Manager and Amazon EC2 uses HTTPS.
- Inbound internet access isn't required.
- Tetra Hub v2 provides agents with proxies that have network access to the Hub, but not to the Tetra Data Platform (TDP) or AWS endpoints. Both require one or more ports. These ports can be configured in the TDP user interface, and must be available on the Tetra Hub machine before agents can connect.
The TDP uses server-side encryption for Amazon Simple Storage Service (Amazon S3).
Tetra Hub v2 requires a consistent and accurate time reference. You can use existing Network Time Protocol (NTP) sources or Amazon Time Sync Service.
Tetra Hub v2 supports proxy settings. For more information, see Tetra Hub v2 Proxy Settings.
Tetra Hub v2 uses several endpoints that must be added to the network server’s or VM’s allow list. For more information, see Tetra Hub v2 Allow List Endpoints.
Updated about 1 month ago