Welcome to Voyager Help

Use the Search field below or select a Category from the list at the left

Deploying Voyager to Amazon Web Services and Microsoft Azure


Voyager can now be deployed to Amazon Web Services (AWS) and Microsoft Azure cloud infrastructures. 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. Both Amazon Web Services and Microsoft Azure offer memory-optimized servers.

Amazon Web Services

  • 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)

Microsoft Azure

  • Minimum: DS12 v2 (4 vCPU, 28 GB RAM) with P10 Azure Disk (128 GB SSD)
  • Recommended: DS13 v2 (8 vCPU, 56 GB RAM) with P20 Azure Disk (512 GB SSD)

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.

See this article for steps to install, configure and license Voyager.

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.

For managing access in Microsoft Azure, refer to the documentation on Network 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.


Q: What are the costs for deploying Voyager in the cloud?

A: The costs for deploying Voyager in the cloud include infrastructure costs and Voyager licensing costs. Infrastructure costs include the hourly rate for virtual machines running in Amazon EC2 or Azure Virtual Machines and also any data storage and data transfer costs.

Q: How is Voyager licensed when deploying to the cloud?

A: Voyager is licensed in the same way as other deployments. A valid machine key is required to generate a license key. Please contact Voyager Support in order to acquire a license key.

Q: Are there any limitations on the content that is discoverable by Voyager when running in the cloud?

A: No. As long as the Voyager server has connectivity to content repositories, then Voyager will be able to discover, extract and index the content.

Q: Can Voyager index content stored in cloud storage services?

A: Yes. New at Voyager 1.9.9 is the capability to index content stored in Amazon S3. The Cloud Storage location is capable of indexing 1800+ file formats.

Q: If Voyager is running in AWS, are there additional AWS costs to index content stored in S3?

A: If Voyager is running in the same AWS region as the S3 content, then no data transfer costs will be incurred. There will still be costs for running Voyager on a virtual machine in Amazon EC2.

Q: If Voyager is running on-premise, can content in Amazon S3 be indexed?

A: Yes, but in this case Data Transfer Out costs will be incurred in order to copy the content to the Voyager server and store it temporarily for extraction and indexing.

Q: Is there a pre-built AMI for Voyager in AWS?

A: At this time, Voyager does not provide an AMI in AWS with the Voyager software pre-installed and configured.

Q: Is there a VM images for Voyager in Azure?

A: At this time, Voyager does not provide a VM image in Azure with the Voyager software pre-installed and configured.

Web Design and Web Development by Buildable