How To Test Connectivity from a CPM Worker to AWS endpoints
The Following Steps will help you Test the outgoing connection from the CPM Worker to AWS endpoints OR the CPM Server if you need to test to ensure that the Worker can reach the CPM server once it launches.
Launch Worker
First, ensure the CPM Worker instance is running in your AWS EC2 console. If it is, you can proceed with this test. If it is not, please run the S3 copy or FLR (explore) again and wait for the CPM worker to launch in your AWS EC2 console. It will Be named "CPMWorkerMachine"
For the duration of the test, you should enable Termination Protection for this instance.
Now Obtain the IP address of the worker instance and connect to it using SSH/Putty. The IP address is found in the details of the CPMWorkerMachine in your EC2 console.
Configure Putty to connect to the Worker
Configure Putty to connect to the IP/hostname of the CPM WorkerMachine you just looked up. This is done in the same way you would use Putty to connect to the CPM Instance, using the CPM key. However to login to any CPM Worker instance please use the username "Ubuntu".
If you have not connected to your CPM instance with putty yet, you will need to install putty and convert the private key using the steps in the AWS documentation found here in this link
Connect to the Worker
Once you have the key converted to a .ppk file and you have putty configured to connect to the CPMWorkerMachine, make the connection using Putty, you will see a window similar to the image below.
Run Tests
Once logged in, you can run the wget command to test connectivity to any endpoint in AWS. See the example below. A link to AWS Endpoints can be found here - https://docs.aws.amazon.com/general/latest/gr/rande.html
(you may need to replace "us-east-1" with the name of your region)
If it is successful, you will see the "200 OK" message.
EBS endpoint: wget https://ebs.us-east-1.amazonaws.com/
(you may need to replace "us-east-1" with the name of your region)
If it is successful, you will see the "connected" message followed by "403 Forbidden".
OR if you need to test connectivity from the Worker to the CPM instance run the following.
wget --no-check-certificate https://cpmip/
If the connection fails, you will need to determine why the worker cannot establish a connection to the AWS endpoints. This is usually caused by the Worker being launched in a VPC or subnet that does not allow the connection.
S3 networking and bucket requirements can be found here - https://docs.n2ws.com/user-guide/appendix-a-recommended-configuration-for-copy-to-s3
Related Articles
How to create and configure an EBS Endpoint for CPM Workers
This article will provide step-by-step instructions on how to create and configure an EBS Endpoint for CPM workers (v3.1 and up) Step 1: Let's say that you have created this VPC for your workers: In this example, we allocated IPv4 addresses ...How to test the worker configuration from UI
Background: This document explains the steps to test a CPM Worker configuration. This can help reduce errors during S3 copy and File-Level restores by being able to confirm the settings used for these jobs are successfully able to connect. Worker ...Installation or upgrade of CPM may fail with the error "Can't connect to AWS: Wrong credentials or connectivity issue: "AccessKeyID""
Installation or upgrade of CPM may fail with the error "Can't connect to AWS: Wrong credentials or connectivity issue: "AccessKeyID"" After ensuring that the JSON permissions files have been updated, confirm that you have connectivity to the AWS ..."Worker did not establish connection" and "worker did not complete initializing" errors during S3 and FLR
During S3 operations, you may encounter the message "Worker i-... did not establish connection" in the log of an S3 copy or S3 restore operation. Error - Worker i-1234567890abcdef did not establish connection - terminating operation During File Level ...N2WS 3.1.x - worker reported error: failed processing segment 0 : Failed to load blocks meta-data
Issue summary When running copy to S3 on version 3.1 it might fails with below error: Issue description and troubleshooting This error is usually caused by communication issues with the EBS Direct API endpoint. In version 3.1 we have started to use ...