Instant hardware access
Scalability
Cost savings
Accessibility
Suggested cloud license setup
Instructions at a glance
To install Intella on a public cloud platform, follow these steps:
Create two VMs: the Intella Server VM that will host Intella Connect or Intella Investigator and the lower spec'd Licence VM. The two machines need to be in the same subnet and must be able to see each other over the network. (see the manual for exact ports)
Install Intella on the Intella Server VM
Follow the instructions in the Intella installation guide to install Intella Connect or Investigator. For hardware specifications you can follow the same requirements from this article: https://support.vound-software.com/help/en-us/8-installation/66-selecting-a-computer-to-host-your-vound-softwareInstall the license key on the License VM
Follow the instructions from the support team on how to install the license on the License VM.Configure the Intella Server VM to use the license being broadcast from the License VM
Open the Intella License Manager on the Intella Server VM and configure it to use the license on the License VM.Start using Intella
Once you have configured the Intella Server VM to use the license, you can start using Intella to process and search your data.
Tips for a successful installation
Here are some additional tips for a successful Intella installation on a public cloud platform:
Use a high-performance VM configuration for the Intella Server VM.
Use a cloud firewall or VPN to protect your Intella environment from unauthorized access.
Involve a cloud infrastructure expert because every public cloud has a steep learning curve when it comes to understanding all facets.
Detailed instructions
This is a step-by-step guide on how to install Intella Investigator or Intella Connect on Amazon Web Services (AWS). This shows what practical steps are needed to achieve what is described in the above instructions overview.
Important note: The following procedures aim to provide a general understanding of setting up an instance of Intella Connect or Intella Cloud on Amazon Web Services (AWS). However, it is important to note that this guide does not cover aspects such as OS security, firewall configurations, and infrastructure fortification, as these largely rely on your expertise and specific objectives.
While we have focused on AWS, similar steps will be required on different cloud providers.
We are going to create this:
Make sure you have an AWS account. https://aws.amazon.com
Sign in to AWS console at following URL: https://eu-north-1.signin.aws.amazon.com/
Once logged in, choose the region in which instances will be started. It is recommended to choose the region closest to you.
From services tab, choose Compute and EC2:
Click on Launch instance:
In the "Launch an instance" window, type in the name “IntellaConnect”. Make sure that minimum requirements are met as described in https://vound.info/connect-admin-manual#_system_requirements_and_recommended_configuration
Select a supported Windows OS, such as Windows Server 2022. Instance type needs to satisfy minimum requirements, such as 32GB RAM. The general purpose instance type t2.2xlarge meets this requirement.
Note that this guide uses 50 GB disk space, but this can be changed based on demand.
Scroll down to key pair section and click on "Create new key pair"
Fill in the name “IntellaConnectKeyPair” and click "Create key pair"
This will save a file CALLED “IntellaConnectKeyPair.pem” to the local disk based on browser preference. Make sure to note the location of where it was downloaded on your system:
Click on "Launch instance"
The instance “IntellaConnect” will now appear in the dashboard. Your newly set up instance may take a few minutes for it to transition to running state. Once in running state, select the instance and click "Connect"
Choose the RDP Client tab and click "Download remote desktop file" this will download a file that can be used to easily configure your RDP connection.
This will download the RDP file locally in the browser.
Locate the RDP file in Windows Explorer and double click on it to launch your RDP client so you can access the newly created AWS instance for further configuration.
Click “Connect” which will show following window:
The password can be retrieved by switching back to AWS console from step 10. Click on “Get password”
Click “Upload private key file” and locate the “IntellaConnectKeyPair.pem” file from step 8. Click on “Decrypt password”
Copy paste the password and continue logging in from step 12.
Click Yes on the above screen.
Now your AWS instance is configured and you have Desktop access. Proceed to install Intella Connect or Intella Investigator.
Once logged in, open browser and navigate to https://www.vound-software.com/software-downloads and download Intella Connect installer
Double click on the installer and follow the wizard to install Intella Connect. It is recommended to first install it NOT as Windows service at this moment, because currently the license is missing.
The license will be available once it is set up on a separate instance. To do that follow steps 4. to 18. again, to prepare an instance with installed Intella Connect.When configuring the new instance to be launched, make sure to check the VPC ID and Subnet ID
In the “Launch an instance” window, scroll down to “Network settings”, choose “edit” and then select the same VPC and Subnet ID as the other instance.
Intella Connect on this instance will not be run or used, but it was needed in order to install the licensing system.
The following steps will refer to one instance as “Intella Connect” instance and second as “Licensing” instance.
To configure the Licensing instance:
Reach out to Vound Software support for a license if you do not already have one. Install the license on this instance and once this has been done, it is expected to be available at http://localhost:1947/_int_/devices.html
On the Licensing instance there will be changes made in the Sentinel Admin Control Center (SACC). The first setting is located in the 'Access from Remote Clients' tab which can be accessed at this link: http://localhost:1947/_int_/config_from.html. Make sure that the setting for 'Allow Access from Remote Clients' is checked. Click Submit if you have made changes.
The second setting is in the Basic Config page (http://localhost:1947/_int_/config.html). Make sure that the setting for 'Allow Remote Access to ACC' is checked. Click Submit if you have made changes. When prompted, set a password for remote access.
To configure the Intella Connect instance:
You now need to configure the ACC so that the Intella Connect instance can access the Licensing instance to pick up a license. The first setting is the same as shown at step 3 for the local system (above). In the Basic Config page (http://localhost:1947/_int_/config.html), make sure that the setting for 'Allow Remote Access to ACC' is checked.
The second settings are located in the 'Access to Remote License Manager' tab (http://localhost:1947/_int_/config_to.html).
(i) Check the setting for 'Allow Access to Remote Licenses'.
(ii) Check the setting for 'Broadcast Search for Remote Licenses'.
(iii) Enter the IP address for the local system in the 'Remote License Search Parameters' field. Once done, click Submit.To test the communication between the Intella Connect instance and the Licensing instance, open a browser on the cloud system, and type the following in the Address bar: http://localhost:1947/_int_/devices.html. Verify that you can view the network license key which is plugged into the local system. If you can see the network dongle, then this verifies that the Intella Connect instance is able to communicate with Licensing instance at a HASP level.
Start Intella Connect. It is expected to receive the license from the Licensing instance.