Installation

  • 5 minute(s) read
Prev Next

1. Introduction

You can install the Verax Control Center directly from your cloud provider’s marketplace. Today, the Verax Control Center is available through both AWS and Azure marketplaces. The Verax Control Center is deployed on a standalone virtual machine in your cloud provider account.

2. General Prerequisites and Network Requirements

  1. Ensure that your VM meets the following:

    1. Prerequisites

    2. Network Requirements

3. AWS Installation Instructions

You can find the Verax Control Center installation on the AWS Marketplace here.

AWS Prerequisites

Enable Sonnet model access:

  • Go to https://{REGION}.console.aws.amazon.com/bedrock/home?region={REGION}#/modelaccess

  • Enable Claude 3 Sonnet.

Supported Model and AWS Regions

Verax uses Anthropic’s Claude 3 Sonnet foundation model (anthropic.claude-3-sonnet-20240229-v1) in Amazon Bedrock. The following AWS Regions, all of which support this model, are used by Verax:

  • us-east-1

  • us-west-2

  • eu-west-2

  • eu-central-1

Initiating the Installation

Within the AWS Marketplace listing for the Verax Control Center, scroll down to Resources > Links and click on the relevant installation link.

The AWS Marketplace listing redirects you to a CloudFormation template. You must configure the template in order to deploy the Verax Control Center AMI.

Create Stack

Once you click on the AWS Marketplace link, you will be forwarded to CloudFormation, where you will need to create a stack with the Verax CloudFormation template.

  1. Under Prerequisite - Prepare template, ensure that Choose an existing template is selected.

  2. Under Specify template > Template source, ensure that Amazon S3 URL is selected.

  3. The Amazon S3 URL field is automatically populated with the Verax template URL.

  4. Click Next.

Specify stack details

Under Specify stack details, set the following:

  1. Under Provide a stack name, enter a unique name for the stack that identifies it as Verax.

  2. Under Parameters, enter the following:

    Note: You must enter the fqdn, sslCert864, and sslKey864 parameters to use your own certificate. If you don’t provide the parameters, you can connect to the server IP with a certificate generated by Verax.

    1. Under fqdn, enter your DNS domain name system path.

    2. Under publicSubnetAz, select the subnet within which you want to launch the Verax Control Center VM. Only supported subnets are shown.

    3. Under publicSubnetid, select a corresponding subnet ID. Only supported values are shown.  

    4. Under sshKeyName, enter the name of the ssh key name if you want to use an ssh key with to access the Verax Control Center VM. Set this up if you want to connect to the instance via SSM.  

    5. Under sslCert864 and sslKey864 enter the certificate and key for an SSL certificate. Follow the instructions here, copy the output string and use it in the cfn template.

    6. Click Next.

The stack will be created. You can review the creation process in the Resources tab.

The following resources are created during installation:

  • Elastic IP (optional)

  • An EC2 instance

  • A launch template

  • A volume mounted to the EC2 instance

  • A role (cloudformation stack name—InstanceRole) with the following policies:

    • AmazonSSMManagedInstanceCore

    • AWSMarketplaceMeteringRegisterUsage

    • CloudWatchAgentServerPolicy

    • An inline policy to allow Bedrock access with the following permissions:

      • bedrock:InvokeModel

      • bedrock:ListFoundationModels

Note: Your default VPC security group is attached to the launched instance.

Accessing the Verax Control Center after installation

After installation, you can access the Verax Control Center by navigating to the Elastic IP address through Port 3000 (ex: 50.17.183.33:3000). The Verax Control Console opens and you can proceed to log in as shown here.

4. Azure Installation Instructions

You can find the Verax Control Center installation on the Azure Marketplace here.

Supported Model and Azure Regions

Verax uses the GPT-4o-mini model with standard deployment in Azure. The following Azure Regions, all of which support this model, are used by Verax:

  • East US (eastus)

  • West US 3 (westus3)

  • Sweden Central (swedencentral)

Initiating the Installation

Within the Azure Marketplace listing for the Verax Control Center, choose a plan and click Create.

The Azure Marketplace listing redirects you to a portal, where you need to configure the deployment of the Verax Control Center application.

Basics

Under Basics, set the following:

  1. Select the relevant Subscription and Resource group where you want to deploy Verax.

  2. Select the Azure Region where you want to deploy Verax. Only supported regions are shown.

  3. Under Managed Application Details > Application Name, enter a unique name for the application that identifies it as Verax.
    The Managed Resource Group field is populated automatically.

  4. Click Next.

Network settings

Under Network settings, set the following:

  1. Under Create public IP, check the box if you want to create a public IP for the application.

  2. Click Next.

VM Config

Under VM Config, set the following:

  1. Under Virtual machine size, choose the machine size you want to use for the Verax Control Center.

  2. Under OS disk size, choose the disk size. The minimum value is 50 GB.

  3. Under Database disk size, choose the database disk size. The minimum value is 256 GB.

  4. Under SSH public key source, you can either choose to Generate new key pair or Use existing key stored in Azure.

    1. If you’re using an existing key, then choose the key under Stored Keys.

  5. Click Next.

Application Config

Under Application Config, set the following:

  1. Under FQDN, enter your DNS domain name system path.

  2. Under SSL Certificate and SSL Private Key select the certificate and key for an SSL certificate. Follow the instructions here and upload the relevant files.

  3. Click Next.

Note: You must enter the FQDN, SSL Certificate, and SSL Private Key parameters to use your own certificate. If you don’t provide the parameters, you can connect to the server IP with a certificate generated by Verax.

Review + create

Under Review + create, review the settings, and if everything is correct, click Create.

Azure will initialize and submit the deployment of the Verax Control Center application.

  • Note: To see the Verax app operations details in Azure, click on Operation details after app deployment.

  • Note: To see the Verax app parameters and outputs in Azure, click on Settings > Parameters and Outputs under the Verax app.

  • Note: To see all the resources created by the Verax app in Azure, click on the resource group.

    Learn more about Azure OpenAI Service Deployment types.

Accessing the Verax Control Center after installation

Once deployment is complete, go to your Managed Resource Group, where you will find the IP address associated with the Verax Control Center application.

You can access the app through Port 3000 (ex: 50.17.183.33:3000). The Verax Control Center then opens and you can proceed to log in as shown here.

5. Creating an SSH Certificate

You should generate a certificate through your web service in the same way you generate certificates for other purposes and upload that certificate here.

  1. The certificate key must be RSA-2048 in Base64 format.

    1. The key.pem file and cert.pem file must first be created and then converted to Base64 format.

  2. Sample command for generating a self-signed certificate in openssl:

    openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -sha256 -days 3650 -nodes -subj "/C=XX/ST=StateName/L=CityName/O=CompanyName/OU=CompanySectionName/CN=CommonNameOrHostname"

  3. Then, do the following:

    1. on MAC: 

      base64 -i key.pem

      base64 -i cert.pem

    2. on Linux: 

      base64 -w0 key.pem

      base64 -w0 cert.pem

    3. Copy the output string and use it as instructed.