Use SSH Tunneling to access Ambari web UI, ResourceManager, JobHistory, NameNode, Oozie, and other web UI’s

Source: https://azure.microsoft.com/en-us/documentation/articles/hdinsight-linux-ambari-ssh-tunnel/

Original Author: Larry Franks

Excerpts

ssh tunnel command

ssh -C2qTnNf -D 9876 user-name@machine-name

This creates a connection that routes traffic to local port 9876 to the cluster over SSH. The options are:

• D 9876 – The local port that will route traffic through the tunnel.
• C – Compress all data, because web traffic is mostly text.
• 2 – Force SSH to try protocol version 2 only.
• q – Quiet mode.
• T – Disable pseudo-tty allocation, since we are just forwarding a port.
• n – Prevent reading of STDIN, since we are just forwarding a port.
• N – Do not execute a remote command, since we are just forwarding a port.
• f – Run in the background.

Use the -i parameter and specify the path to the private SSH key.

For using Putty to setup the tunnel follow the source link.

Browser configuration

Setup browser based proxy switching tool such as foxy proxy suggested in source link.

Key configurations below,

• Proxy server – localhost:9876
• Proxy type – socks / socks 5
• Auto routing configuration
  • URL wildcard – *management-node-hostname* (rule for routing to the proxy server)

Finally, open the URLs as you would on the remote machines’ browser.

http://ambari-management-node-hostname:8080/