If the Tetra Data Hub host can be reached from anywhere in the enterprise network, theoretically you only need one and create as many connectors on this Data Hub as you want. Of course, depending on your location and team, you may want to create separate ones so it's easier to manage.
- Please make sure the network requirements are met. If you need to set up a proxy, please refer to the proxy setup guide.
- Open the command line on the Tetra Data Hub machine, on CentOS, RedHat and Ubuntu v18.04 and up run
systemctl status amazon-ssm-agentto see if the SSM agent is running. On older versions of Ubuntu, run
service amazon-ssm-agent status.
- Open the command line on the Data Hub machine, type
docker psto see if there is any Docker container running (TetraScience connectors are run in Docker containers).
- Check SSM agent logs to see if there is any error: /var/log/amazon/ssm/amazon-ssm-agent.log and /var/log/amazon/ssm/errors.log
The core components of the Tetra Data Hub leverage AWS technologies, such as AWS IoT and AWS SSM agent (https://github.com/aws/amazon-ssm-agent). Data uploaded by the Data Connectors follow AWS IoT best practices - connectors are only given very restrictive, temporary credentials for uploading data to the platform. Communication from a Tetra Data Hub is only initiated outbound; TetraScience will never send commands directly to a Tetra Data Hub.
Please refer to this link: https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-proxy-with-ssm-agent.html. Note that these steps must be repeated whenever the proxy settings change.
Yes, the Tetra Data Hub will autostart when the server restarts.
- Click the Hamburger Menu on Tetra Data Platform.
- Select Data Sources, then Data Hub.
- The online/offline status indicator appears next to the data hub entry.
It will expire after 24 hours after the Tetra Data Hub is created. You then need to create a new Tetra Data Hub and run the new installation script. The activation code can only be used once.
Updated 4 months ago