Automate - Configure Cloud Compute Engine - AWS

Owned by Ryan Best (Unlicensed)
Oct 03, 2024
3 min read

 

The material in this document is for informational purposes only. This guide assumes that the most recent version of Rampiva Automate is in use unless otherwise noted in the prerequisites. The products it describes are subject to change without prior notice, due to the manufacturer’s continuous development program. Rampiva makes no representations or warranties with respect to this document or with respect to the products described herein. Rampiva shall not be liable for any damages, losses, costs or expenses, direct, indirect or incidental, consequential or special, arising out of, or related to the use of this material or the products described herein.

Introduction

Utilize this article when configuring your Amazon Web Service (AWS) resource pools.

Prerequisites - AWS

  • Amazon EC2 Subscription

  • Pre-configured Virtual Machine(s)

  • Complete Nuix Installation

  • Rampiva Engine Service Installation

  • AWS Firewall and Virtual Machine Access to Port 443

Instructions

A. Configure the Rampiva Resource Pool

1

Obtain an Access Key and Secret Key for the account that Rampiva Automate will use to connect to AWS.

https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys.

2

Create a new Resource Pool in Rampiva Automate with the following options:

  • Settings - the keys and AWS region in which the AMIs were created:

  • Engine - The settings for the main Engine which will run the job:

    • Nuix License Source: The License Source from which the main Engines will acquire licenses.

    • Target Workers: The number of Nuix workers that the Main Engines will attempt to acquire a license for, if available.

    • Min Workers: The minimum number of Nuix workers required to initialize the Main Engines.

    • Instance Idle Action:
      Terminate / Delete - this will delete the instance on which the main Engine ran.

    • Force Idle Actions Between Jobs: Checked - this will start a fresh instance for the Main Engine for each new Job.

    • Virtual Machine Source: Launch Template ID

    • Launch Template ID: The ID of the main Engine template created previously.

    • Max Concurrent Instances: The maximum number of EC2 instances running at the same time with the main Engine role. This is equivalent to the maximum number of parallel Jobs.

  • Remote Workers - The settings for the Remote Workers which will participate to jobs:

    • Use Remote Workers: Checked

    • Nuix License Source: The License Source from which the Remote Workers will acquire licenses.

    • Target Workers: The number of Nuix workers that the Remote Workers will attempt to acquire a license for, if available.

    • Min Workers: The minimum number of Nuix workers required to initialize each Remote Worker instance.

    • Instance Idle Action:
      Terminate / Delete - this will delete the instance on which the Remote Workers ran.

    • Virtual Machine Source: Launch Template ID

    • Launch Template ID: The ID of the Remote Worker template created previously.

    • Max Concurrent Instances: The maximum number of EC2 instances running at the same time using the Remote Workers role.

  • Whitelisted Certificate Fingerprints - the certificate fingerprint recorded when setting up the Engine Server image.

Ensure that they Rampiva Engine config.yml on each AWS virtual machine has been updated with the Rampiva Scheduler apiSecret value. Refer to the https://rampiva.atlassian.net/l/c/YeVukAAQ Knowledge Base article for further information.

3

Queue a test Job and monitor the Resource Pool log as well as the status of the Instances in the EC2 AWS console.