When a Tetra Hub v1 (previously Tetra Data Hub) machine is behind a proxy, TetraScience must perform additional configuration to ensure that both installations and the Hub, are working properly.
To set the proxy settings:
- Step 1 - Configuring environment variables for the
rootaccount can be manual (because usually, network administrators prepare environment variables for the proxy as part of machine setup), or can be configured through the installation script.
- Step 2 - Configure Amazon SSM client proxy settings can only be configured through an installation script. Manual changes are necessary only when debugging or resolving possible proxy issues.
The Amazon SSM client that drives Hub v1 uses the
root account on a dedicated Linux machine. Therefore, TetraScience configures the shell environment variables to be persistent between sessions. This means that the environment variables are available all the time, such as when the Hub server is restarted, or when a new root session is created. As a result, TetraScience cannot configure environment variables temporarily whenever we create a new session. Instead, we must configure it in the root's user profile. The file that needs to change depends on the Linux distribution used for the Hub.
- For Ubuntu, TetraScience edits the
- For RedHat based Linux distributions, TetraScience edits the
These lines are added to the previously mentioned files:
After this step, TetraScience ensures that the settings are applied. We either:
- Restart the connection
- Restart the Hub server
- (Ubuntu) Invoke command
- (Red Hat)Invoke
source /root/.bash_profile(Red Hat)
TetraScience verifies if the proxy settings environment variables are configured by invoking the shell command
After we have verified the proxy settings, we execute the Hub installation script.
The Hub v1 installer script generates a log file. If the installation was not successful, then the installer provides a short error and path to the log file to review more detailed messages. Please review the log file and verify that the proxy settings were configured properly.
If the activation fails, then TetraScience returns to the Hub v1 machine and reviews the Amazon SSM client log. The log is stored at:
/var/log/amazon/ssm/amazon-ssm-agent.log. TetraScience can execute a command such as
tail /var/log/amazon/ssm/amazon-ssm-agent.logand verify that no messages display, such as
unable to resolve address https://*.amazonservices.com, or
unable to connect to https://*.amazonservices.com. However, if these messages do display, then please check the Amazon SSM client proxy settings once more
Updated 3 months ago