Go back

How to Deploy TrueConf Server on AWS

April 14, 2022
Anthony Baadzhy

Anthony Baadzhy

The software deployment on the virtual machine of a cloud provider (PaaS service) is quite a popular way of using different services, including video conferencing. TrueConf Server can also be installed on a virtual machine (VM) of any available provider.

This article will explain how to deploy TrueConf Server on Amazon Web Services (AWS) cloud.

After you create an AWS account, you will be able to use the service for 750 hours/year for free. After 12 months, you will need to pay for the services. Learn more about the free plan restrictions in the official documentation.

Create a virtual machine

  1. Click the Create an AWS Account button on the Amazon AWS home page. Log in with your account or create a new one.
  2. Choose Services → Compute → EC2 in your profile page.
  3. Type your operating system name in the search box, for example, Debian, and press Enter.
  4. Set the bit rate of the created VM on the right side of the page. To do this, choose 64-bit (x86) and click the Select button.
  5. Choose the type of configuration you want based on the system requirements and click Next: Configure Instance Details. For example, a free account is available with the following configuration:
    Instance t2.micro
    Virtual CPUs 1
    CPU credits per hour 6
    Memory (GB) 1
    Storage EBS only
    Network performance From low to medium

    If you want to create a more powerful VM, switch to the necessary paid plan.

  6. If necessary, edit the configuration information and click Next: Add Storage. You can read each parameter description in the AWS Documentation. In this article we take t2.micro instance from the table above as an example.
  7. On the Step 4: Add Storage page you can:
    • add new storage and file system
    • choose the type of volume and change its size
    • set the number of input/output operations per second (IOPS) if the volume supports this
    • configure the volume encryption if necessary.

    Click Next: Add Tags after changing the repository settings.

  8. You can assign your own metadata to each instance in the form of tags for easier filtering and management. Tags allow you to categorize AWS resources in different ways, for example by purpose, owner, or environment. This is helpful when you have many resources of the same type. Click Next: Configure Security Group after configuring the tags.
  9. Configure the security group on the Configure Security Group page to define firewall rules for your instance. These rules determine which incoming network traffic comes to your instance while all other traffic is ignored.
    0.0.0.0/0 source rules allow all IP addresses to access your instance. We recommend you to configure security group rules, so that only specific IP addresses can get access to it.

    You can add rules based on your needs. Open ports 80 (HTTP) and 443 (HTTPS) to provide Internet access for your AWS instance. Read which ports does TrueConf Server use in our article.

    Click the Review and Launch button after configuring the security group.

  10. Check the instance details. Click the Launch Instances button if all the settings are correct. If you want to edit details, go to the previous page by clicking Previous.
  11. Create a new key pair if you have not used AWS before and have not created any instances. To do this:
    1. Choose Create a new key pair from the drop-down list.
    2. Specify the encryption type in the Key pair type block (we recommend RSA).
    3. Enter the key pair name in the Key pair name field.
    4. Click the Download Key Pair button. After that, a new key pair will be generated and the private key (*.pem) will be downloaded.
    Save the private key file with the *.pem extension in a secure and accessible place. You will need this file when starting the virtual machine. You will not be able to re-download the file after it has been created. If you lose access to the file, you will need to generate a new key pair.
  12. Click Launch Instances. The Launch Status page will open. Click the View Instances button to go to your instance. You will see the status of the virtual machine in the Instances tab:
    How to Deploy TrueConf Server on AWS 1
  13. When 2/2 checks passed is displayed in the Status Check field, connect your key pair. Right click on this status and choose Connect.
  14. Choose the SSH client tab. You will see a step-by-step guide for connecting to your server.

Connect to virtual machine

  1. To access your VM, use the console ssh utility, which is available for all modern operating systems, including Windows 10+, Linux, and macOS.
  2. Connect to your instance at the specified public DNS address. In the terminal, run the command (you can copy it from the SSH client tab):

    where path-to-your-private-key is the path to your private key file.

    Please note that the SSH connection will not be established if the private key file is stored in a directory accessible to other operating system users. Move the file to C:\User\.ssh\ for Windows or run the command chmod 400 key.pem to change the visibility for Linux.

TrueConf Server deployment

TrueConf Server deployment on AWS is similar to physical server deployment. In case of difficulties, follow our instructions:

Please note that the TrueConf Server control panel is only accessible from the local network after installing the server on the remote virtual machine. To get external access, you need:

    1. Edit the file opt/trueconf/server/etc/webmanager/opt/local_only_admin_24.conf  as shown below:

      where x.x.x.x is your external IP address.
    2. Restart the TrueConf Server web service with the command systemctl restart trueconf-web
Please note that you will not be able to get admin access to the TrueConf Server control panel if you change your external IP address until you edit the local_only_admin_24.conf file again. Therefore, we recommend you to use a computer with a static IP address to operate the virtual machine. Besides, adding an external dynamic IP address is not considered secure, because another person in the IP pool can access the control panel, for example, if your ISP uses NAT.

Still have questions? Please contact our support team directly via online chat.

Sign up for newsletter