Floability-cli suggests a command to create an SSH tunnel in order to access the notebook (which is running in an AWS machine) from a remote (say, local) machine. However, the IP address shown with the suggested command is not correct. It shows the public IP, whereas it needs to use the private IP to create the proper SSH tunnel.
For example,
Floability-cli suggests: ssh -L localhost:8888:localhost:8888 ubuntu@172.31.36.110
The correct one would be: ssh -L localhost:8888:localhost:8888 ubuntu@35.93.201.79
Here, 172.31.36.110 is the public IP of the AWS head node, while 35.93.201.79 is its private IP.
Floability-clisuggests a command to create an SSH tunnel in order to access the notebook (which is running in an AWS machine) from a remote (say, local) machine. However, the IP address shown with the suggested command is not correct. It shows the public IP, whereas it needs to use the private IP to create the proper SSH tunnel.For example,
Floability-cli suggests:
ssh -L localhost:8888:localhost:8888 ubuntu@172.31.36.110The correct one would be:
ssh -L localhost:8888:localhost:8888 ubuntu@35.93.201.79Here, 172.31.36.110 is the public IP of the AWS head node, while 35.93.201.79 is its private IP.