E-MapReduce:Create an SSH tunnel to access web UIs of open source components

Prerequisites

• An EMR cluster is created. For more information, see Create a cluster.

• Your on-premises server is connected to the master node of the cluster. You can turn on Assign Public Network IP during cluster creation to associate an elastic IP address (EIP) with your cluster. You can also assign a fixed public IP address or an EIP address to the master node of your cluster in the ECS console after the cluster is created. For more information, see Bind an ENI.

Obtain the name and the public IP address of the master node

1. Go to the Nodes tab.

   1. Log on to the EMR console.

   2. In the top navigation bar, select the region in which your cluster resides and select a resource group based on your business requirements.

   3. On the EMR on ECS page, find the desired cluster and click Nodes in the Actions column.

2. On the Nodes tab, find the master node group and click the icon.

3. In the Node Name/ID and Public IP Address columns, view the name and public IP address of the master node.

   

Enable dynamic port forwarding

Create an SSH tunnel to allow communication between a port of your on-premises server and the master node of an EMR cluster. Run the on-premises SOCKS proxy server that listens on the port. The port data is forwarded to the master node of the EMR cluster by using the SSH tunnel.

1. Create an SSH tunnel.

   Important

   Keep your on-premises server running after the tunnel is created. No responses are returned.

   • Use a key:

     ssh -i <Storage path of the key file> -N -D 8157 root@<Public IP address of the master node>

   • Use a username and a password:

     ssh -N -D 8157 root@<Public IP address of the master node>

   Parameter description:

   • 8157: Port 8157 is used in this example. You can replace this port with an unoccupied port on your on-premises server in actual configuration.

   • -D: Dynamic port forwarding is enabled. Start the SOCKS proxy process to listen on the port.

   • <Public IP address of the primary node>: For more information about how to obtain the public IP address of the master node, see Obtain the name and the public IP address of the master node.

   • <Storage path of the key file>: the path where the key file is stored.

2. Configure the Google Chrome browser.

   You can use one of the following methods to configure the Google Chrome browser:

   • Use the CLI

     1. Open the CLI and go to the local installation directory of the Google Chrome browser client.

        The default installation directory of Google Chrome depends on the operating system.

        Operating system	Default installation directory of Google Chrome
        macOS X	/Applications/Google\ Chrome.app/Contents/macOS
        Linux	/usr/bin/google-chrome
        Windows	C:\Program Files (x86)\Google\Chrome\Application\

     2. Run the following command in the default installation directory of Google Chrome:

        Windows and Linux

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

        Mac OS X

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

        Parameter description:

        • /tmp/: For Windows, replace /tmp/ with a path similar to /c:/tmppath/. For Linux and Mac OS X, the format of a temporary file path is /tmp/.

        • 8157: Port 8157 is used in this example. You can replace this port with an unoccupied port on your on-premises server in actual configuration.

     3. Enter http://<Name of the master node>:<Port number> in the address bar of the browser and press Enter to access a specific web UI.

        For more information about the ports of components, see Common ports of services. For more information about how to obtain the name of the master node, see Obtain the name and the public IP address of the master node.

        For example, enter http://emr-header-1:8088 in the address bar of the browser and press Enter to access the web UI of YARN.

   • Use a Google Chrome extension

     Extensions allow you to easily manage and use proxies in your web browser. You can use an extension to browse web pages and access web UIs at the same time.

     1. Add the Google Chrome extension Proxy SwitchyOmega.

     2. Click this extension and select Options from the shortcut menu.

     3. On the SwitchyOmega page, click New profile in the left-side navigation pane. In the New Profile dialog box, enter a profile name, such as SSH tunnel, in the Profile name field, select PAC Profile, and then click Create.

     4. Enter the following content in the PAC Script editor:

        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';
        }

     5. In the left-side navigation pane, click Apply changes to complete the configurations.

     6. Open Google Chrome. Click the SwitchyOmega extension. Then, select the created SSH tunnel.

     7. Enter http://<Name of the master node>:<Port number> in the address bar of the browser and press Enter to access a specific web UI.

        For more information about the ports of components, see Common ports of services. For more information about how to obtain the name of the master node, see Obtain the name and the public IP address of the master node.

        For example, enter http://emr-header-1:8088 in the address bar of the browser and press Enter to access the web UI of YARN.

Enable local port forwarding

You can use the local port forwarding method to forward data on a port of the master node to the local port and access the web application interface running on the master node. The SOCKS proxy is not required.

1. Run the following command on your on-premises server to create an SSH tunnel:

   Important

   Keep your on-premises server running after the tunnel is created. No responses are returned.

   • Use a key:

     ssh -i <Storage path of the key file> -N -L 8157:<Name of the master node>:8088 root@<Public IP address of the master node>

   • Use a username and a password:

     ssh -N -L 8157:<Name of the master node>:8088 root@<Public IP address of the master node>

   Parameter description:

   • -L: Local port forwarding is enabled. You can specify a local port to forward data to the remote port that is hosted on the on-premises web server of the master node.

   • 8088: the port that is used to access ResourceManager on the master node. You can replace this port based on your business requirements.

     For more information about the ports of components, see Common ports of services. For more information about how to obtain the name of the master node, see Obtain the name and the public IP address of the master node.

   • 8157: Port 8157 is used in this example. You can replace this port with an unoccupied port on your on-premises server in actual configuration.

   • <Public IP address of the primary node>: For more information about how to obtain the public IP address of the master node, see Obtain the name and the public IP address of the master node.

   • <Storage path of the key file>: the path where the key file is stored.

2. Keep your on-premises server running. Open a browser, enter http://localhost:8157/ in the address bar of the browser, and then press Enter.

Common ports of services

References

For more information about how to access the web UIs of open source components in the EMR console, see Access the web UIs of open source components.