E-MapReduce:Access open-source component UIs with an SSH tunnel

Key authentication

ssh -i <path_to_private_key_file> -N -L <local_port>:<master_node_name>:<component_port> root@<master_node_public_ip>

Parameters:

• -i: Specifies the private key file for authentication.

• -N: Do not execute a remote command. Use this option to only forward ports.

• -L: Specifies local port forwarding. Forwards traffic from the specified local port to the specified remote host and port on the master node.

• <path_to_private_key_file>: The local path to your private key file. For more information, see Manage SSH key pairs.

• <local_port>: An unused port on your client machine. For example, 8156.

• <master_node_name>: The Node Name of the master node, found on the Nodes tab of the cluster details page. For more information, see Obtain the node name. For example, master-1-1.

• <component_port>: The port of the open-source component. For more information, see Default ports of open-source components. For example, the YARN UI port is 8088.

• <master_node_public_ip>: The Public IP Address of the master node, found on the Nodes tab of the cluster details page. For more information, see Obtain the public IP address of a node.

Password authentication

ssh -N -L <local_port>:<master_node_name>:<component_port> root@<master_node_public_ip>

Parameters:

• -N: Do not execute a remote command. Use this option to only forward ports.

• -L: Specifies local port forwarding. Forwards traffic from the specified local port to the specified remote host and port on the master node.

• <local_port>: An unused port on your client machine. For example, 8156.

• <master_node_name>: The Node Name of the master node, found on the Nodes tab of the cluster details page. For more information, see Obtain the node name. For example, master-1-1.

• <component_port>: The port of the open-source component. For more information, see Default ports of open-source components. For example, the YARN UI port is 8088.

• <master_node_public_ip>: The Public IP Address of the master node, found on the Nodes tab of the cluster details page. For more information, see Obtain the public IP address of a node.

Key authentication

ssh -i <path_to_private_key_file> -N -D <local_port> root@<master_node_public_ip>

Parameters:

• -i: Specifies the private key file for authentication.

• -N: Do not execute a remote command. Use this option to only forward ports.

• -D: Specifies dynamic port forwarding. Starts a SOCKS proxy server on the specified local port.

• <path_to_private_key_file>: The local path to your private key file. For more information, see Manage SSH key pairs.

• <local_port>: An unused port on your client machine. For example, 8157.

• <master_node_public_ip>: The Public IP Address of the master node, found on the Nodes tab of the cluster details page. For more information, see Obtain the public IP address of a node.

Password authentication

ssh -N -D <local_port> root@<master_node_public_ip>

Parameters:

• -N: Do not execute a remote command. Use this option to only forward ports.

• -D: Specifies dynamic port forwarding. Starts a SOCKS proxy server on the specified local port.

• <local_port>: An unused port on your client machine. For example, 8157.

• <master_node_public_ip>: The Public IP Address of the master node, found on the Nodes tab of the cluster details page. For more information, see Obtain the public IP address of a node.

Command line (Chrome)

1. Open a terminal and navigate to the installation directory of Google Chrome on your client machine.

   Operating system	Default installation directory
   macOS X	/Applications/Google\ Chrome.app/Contents/macOS
   Linux	/usr/bin/google-chrome
   Windows	The default paths for 64-bit and 32-bit systems are: C:\Program Files\Google\Chrome\Application\ C:\Program Files (x86)\Google\Chrome\Application\

   Note

   The default installation directory for Chrome varies by operating system.

2. Configure Google Chrome to use the local SOCKS proxy and launch the browser. Ensure the port matches the one that you specified in Step 1.

   Note

   The following examples use port 8157.

   macOS X

   ./Google\ Chrome --proxy-server="socks5://localhost:8157" --host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE localhost" --user-data-dir=/tmp/

   Linux

   chrome --proxy-server="socks5://localhost:8157" --host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE localhost" --user-data-dir=/tmp/

   Windows

   chrome --proxy-server="socks5://localhost:8157" --host-resolver-rules="MAP * 0.0.0.0 , EXCLUDE localhost" --user-data-dir=c:\\tmppath\\

Chrome extension

A browser extension lets you manage and switch proxy settings without affecting regular browsing.

1. Install the SwitchyOmega extension for Chrome.

2. Open the extension's configuration page. Click New profile, enter a Profile name (for example, SSH tunnel), and select PAC Profile for the profile type.

3. In the PAC Script editor, enter the following code.

   Note

   This example uses port 8157.

   function regExpMatch(url, pattern) {
     try {
       return new RegExp(pattern).test(url);
     } catch (ex) {
       return false;
     }
   }
   
   function FindProxyForURL(url, host) {
     if (shExpMatch(url, "*localhost*")) return "SOCKS5 localhost:8157";
     if (shExpMatch(url, "*emr-header*")) return "SOCKS5 localhost:8157";
     if (shExpMatch(url, "*emr-worker*")) return "SOCKS5 localhost:8157";
     if (shExpMatch(url, "*master*")) return "SOCKS5 localhost:8157";
     if (shExpMatch(url, "*core*")) return "SOCKS5 localhost:8157";
     return 'DIRECT';
   }

4. In the left navigation pane, click Apply changes.

5. In the upper-right corner of your browser, click the SwitchyOmega icon and select the SSH tunnel profile you just created.