[AWS] How To Test Connectivity from a N2W Worker to AWS endpoints

Summary

The following procedures will assist you in testing the outbound connection from the N2W Worker to AWS endpoints or the N2W Server. This is necessary to verify that the Worker can communicate with the N2W Server upon launch.

Description

Launch the Worker

First, confirm that the N2W Worker instance is running in your AWS EC2 console. If it is active, you may proceed with the test. If it is not, please initiate the S3 copy or FLR (explore) process again and wait for the N2W Worker to launch in your AWS EC2 console. The instance will be named "CPMWorkerMachine".

For the duration of the test, it is recommended to enable Termination Protection for this instance.

Next, obtain the IP address of the Worker instance and connect to it using SSH or Putty. The IP address can be found in the details section of the CPMWorkerMachine in your EC2 console.

Configure Putty to Connect to the Worker

Configure Putty to connect to the IP address or hostname of the N2W WorkerMachine you identified. This process is similar to connecting to the N2W Instance, using the N2W key. However, to log in to any N2W Worker instance, please use the username "Ubuntu".

If you have not previously connected to your N2W instance using Putty, you will need to install Putty and convert the private key by following the steps outlined in the AWS documentation available at the following link:

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-methods.html

Connect to the Worker

Once you have converted the key to a .ppk file and configured Putty to connect to the CPMWorkerMachine, establish the connection using Putty. You should see a window similar to the example below.

Execute Connectivity Tests

After logging in, you may use the wget command to test connectivity to any AWS endpoint. Refer to the example below. A list of AWS Endpoints can be found here: https://docs.aws.amazon.com/general/latest/gr/rande.html

S3 endpoint: wget https://s3.us-east-1.amazonaws.com/

(You may need to replace "us-east-1" with your specific region.)

If 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 your specific region.)

If successful, you will see the "connected" message followed by "403 Forbidden".

Alternatively, if you need to test connectivity from the Worker to the N2W instance, execute the following command:

wget --no-check-certificate https://cpmip/

If the connection fails, you must investigate the cause preventing the Worker from establishing a connection to the AWS endpoints. This issue is typically due to the Worker being launched in a VPC or subnet that does not permit the necessary connections.

Requirements for S3 networking and bucket configuration can be found here: https://docs.n2ws.com/user-guide/appendix-a-recommended-configuration-for-copy-to-s3