Installing Voyager on AWS EC2 using Marketplace AMI

Voyager can now be deployed to Amazon Web Services (AWS) cloud infrastructure. Benefits of deploying Voyager in the cloud include:

• Dedicating larger servers with more computing power for discovery and extraction jobs and replicating the index to smaller servers to handle user search requests

• Deploying high-availability configurations across data centers

• Indexing of cloud-hosted objects, databases and file systems — eliminates data transfer costs

• Ability to increase and decrease capacity to meet demand — saves costs by reducing idle servers

System Sizing Recommendations

To run Voyager Search in the cloud, it is generally recommended to use memory-optimized servers that have a high memory-to-core ratio. Amazon Web Services offer memory-optimized servers.

• Minimum: r3.xlarge (4 vCPU, 30.5 GB RAM) with 100GB EBS General Purpose SSD (gp1)

• Recommended: r3.2xlarge (8 vCPU, 61 GB RAM) with 500GB EBS General Purpose SSD (gp1)

Installation and Configuration

Installation and configuration of Voyager Search in the cloud is straightforward and follows similar steps as installing Voyager Search on a physical server or other virtual server.

Licensing of Voyager when deployed to a cloud server remains unchanged compared to traditional licensing when deploying to on-premise physical or virtual servers.

To begin, contact your systems administrator to launch a new server in your organization’s cloud account. Be sure the systems administrator provides RDP access to the new server.

First, use this article for steps to install, configure and license Voyager Server.

Then, use this article for steps to install, configure and license HQ.

After installation, we recommend you follow the following post-configuration steps to ensure a properly configured Voyager Search on the cloud server.

Required Post-Configuration Steps

Configuring the Firewall

If access to Voyager beyond the virtual cloud network is required, the firewalls on the server and in the virtual cloud network will require the following TCP ports to be opened to the relevant audience:

• TCP Port 80: HTTP access

• TCP Port 443: HTTPS access

For managing access to Amazon Web Services, refer to the documentation on Security Groups.

Setting the Voyager URL

Most cloud providers assign a private hostname and public hostname to each server. After Voyager is installed, the Voyager URL will need to be set to the public hostname of the server.

To set the Voyager URL to the public hostname of the server, follow the steps in this article.

Questions?

Have questions regarding Voyager in the cloud? Check out our FAQs.

Installation Guide for AWS ECS

Step 1. From the Launch this software screen, select Launch through EC2 from the dropdown menu and select the Launch button.

Open

From the EC2 console, confirm the following settings are correct:

Amazon Machine Image (AMI)

Step 2. Name your instance and confirm that the AMI and its details are correct.

Open

Instance Type

Step 3. Select an instance type that aligns with the performance requirements and resource recommendations for your Voyager Search deployment. Ensure the instance provides adequate CPU, memory, and storage throughput based on expected workload and indexing volume.

Open

Key Pair (login)

Step 4. Choose an existing key pair or create a new one.

Open

Network Settings

This Voyager API uses the following TCP ports:

Step 5: Depending on Ec2 Settings the ports may auto configure. If not, create a new security groups with the above ports open to all traffic.

Open

Configure Storage

Open

Advanced Details

Step 6: Next, expand the Advanced Details section and scroll to the User Data - Optional section. Add the following options:

This script sets the Voyager and HQ urls to the Public IPv4 DNS address.

Open

Launch Instance

Step 7: Once all the settings above are correct, select Launch Instance.

Step 8: From the EC2 Dashboard, locate the newly created Voyager instance and note the Public IPv4 DNS address.

Step 9: Login to your Voyager instance using the following credentials: