Configuring the TIE Server on AWS

Note

In some cases, the configuration process might take up to 30 minutes to complete. Check the tie.log for status updates and errors, if any. If the process does not complete within this time, you might need to run the configuration process again.

1. On the EC2 dashboard, select Instances.

2. Select the newly created TIE Server from the list, then click Connect.

3. On the Session Manager tab, click Connect.

   Note

   While TIE Server supports traditional SSH access, we recommend using Session Manager for the initial configuration. Once the initial setup is complete, you can utilize SSH for further administration tasks if desired.

   To connect through SSH, use the credentials "ec2-user" as the username and the key pair previously configured for your TIE Server instance.

4. Once logged in, run the following command to obtain root access.

   1. sudo su

   sh-4.2$ sudo su

   [root@ip-10-0-41-163 bin]#

5. You are logged in as the root user now. Run the following command to start the configuration process.

   1. configure-tie.sh

   [root@ip-10-0-41-163 bin]# configure-tie.sh

6. Follow the steps below to set up the process.

   1. On the TIE Server End user License Agreement page, click I agree.

      Note

      If you do not accept the license, the VM will be switched off.

   2. Select the default network device shown, then click Ok.

   3. For IP address assignment, select DHCP.

   4. Provide the ePO server details.

      For port configuration in Trellix ePO – On-prem server, see KB66797.

   5. Select the services to be run on this TIE Server. (Both TIE and DXL can be run on the same server).

      Note

      If you have selected to install the DXL Broker on this instance, confirm the DXL communication port. Also, ensure that the assigned security group is configured accordingly.

   6. On the Appliance Startup page, all components must show DONE to continue.

      

7. Check the transition status in the “/tmp/reconfig-tie.log” file. To speed up the transition process, you can also give the commands to fetch and apply the latest policy from the ePO.

8. Give the command below to check the TIE services status.

   1. TIE Server - systemctl start|stop|restart tieserver

   2. PostgreSQL server - systemctl start|stop|restart tieserver-postgresql

9. Once all the TIE Server services have started, run the vacuuming commands to initialize the TIE database.

   This step only needs to be performed once for the Primary TIE Server and is not required when bringing up an additional Secondary TIE Server.

   1. tieserver-vacuum

   2. tieserver-vacuum-full