Directions for using a custom AMI for an N2W Worker

Summary

Some customer's environment may require modifying the N2W Worker AMI, to align with internal policies that are beyond N2W support (specific tools, hardening etc.). 
This KB article outlines the steps for using a custom AMI to launch N2W worker instances.

Note: Any changes to the N2W Worker AMI are made at the customer's discretion. N2W cannot support these changes, nor can we predict their outcome or impact.

Description

Please follow the below steps:

1. On the AWS console, in the same region as the Worker, search for public AMI’s with the name, CPMWorkerMachine, as shown below:
   
2. Launch an instance from the latest N2W Worker AMI and give it a meaningful name, for example: N2WWorker2.1
3. On the AWS console create an image from Worker instance you created in step 2 and give the AMI  a meaningful name, for example: My N2WS Worker

4. SSH into your N2W server using your private key and the username, cpmuser 
5. Navigate to the following path /cpmdata/conf 
6. Create or edit the file cpmserver.cfg, and add the entry below
   [worker]
   worker_image_name=<Name of the AMI to use that you created in step 4>
   worker_image_owner=<AWS Account number of the account where the AMI was created>
7. when no backup is running, restart apache server:
   sudo service apache2 restart

Confirmation Steps

You can run a Worker test from your N2W console or you can wait until the next Worker operation occurs and check your AWS console to see if the worker AMI that is being used is correct.