--- title: "Access a cluster node with SSH" slug: "hadoop-chadoop-3-2" updated: 2026-09-17T09:18:06Z published: 2026-09-17T09:18:06Z canonical: "guide.ncloud-docs.com/hadoop-chadoop-3-2" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Access a cluster node with SSH Available in Classic You can submit management tasks or applications through NAVER Cloud Platform's Cloud Hadoop console or web UI (Ambari, Hue, etc.). However, SSH connection to the cluster node is required to run the client directly. Note If you access SSH through the public domain or public IP of a cluster, you can access the edge node of the cluster. Other nodes can be accessed from the edge node through SSH. [See 2. Connect to cluster node](/docs/en/hadoop-chadoop-3-2#2-%ED%81%B4%EB%9F%AC%EC%8A%A4%ED%84%B0-%EB%85%B8%EB%93%9C-%EC%A0%91%EC%86%8D). ## Preliminary tasks To access a cluster node, the following tasks and preparations need to be made. | Item | Description | Guide | | --- | --- | --- | | Configure ACG | Add the IP and port 22 of the device to access the cluster's ACG settings - Access source: User's static IP (Can be entered by clicking **[myIp]**) | [Firewall settings (ACG)](/docs/en/compute-compute-2-3) | | Authentication key | Private key (.pem) required for access to the cluster | [Manage authentication key for direct cluster access](/docs/en/hadoop-chadoop-3-1#%ED%81%B4%EB%9F%AC%EC%8A%A4%ED%84%B0-%EC%A7%81%EC%A0%91-%EC%A0%91%EC%86%8D-%EC%9D%B8%EC%A6%9D%ED%82%A4-%EB%B3%80%EA%B2%BD) | | Public domain | Public domain address needed for accessing the relevant cluster node Can be viewed from the **Public domain** item in the cluster details | [Check cluster details](/docs/en/hadoop-chadoop-3-1#%ED%81%B4%EB%9F%AC%EC%8A%A4%ED%84%B0-%EC%83%81%EC%84%B8-%EC%A0%95%EB%B3%B4-%ED%99%95%EC%9D%B8) | | Public IP | Public IP required for access to the cluster node The details of the cluster can be viewed from **Public IP** | [Check cluster details](/docs/en/hadoop-chadoop-3-1#%ED%81%B4%EB%9F%AC%EC%8A%A4%ED%84%B0-%EC%83%81%EC%84%B8-%EC%A0%95%EB%B3%B4-%ED%99%95%EC%9D%B8) | ### Add the public IP to ACG To add a fixed IP to the cluster's ACG: 1. From the NAVER Cloud Platform console's Classic environment, navigate to **Menu** > **All Services** > **Compute** > **Server** > **ACG**. 2. Select the ACG of the cluster you want to access and click **[Set ACG]**. 3. Enter the following 4 information items and add ACG Rule: - Protocol: TCP - Access source: IP of the local device that communicates with SSH - Allowed port: 22 - Note (optional) ![chadoop-2-1-117_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/chadoop-2-1-117_en.png?sv=2026-02-06&spr=https&st=2026-10-27T17%3A39%3A42Z&se=2026-10-27T18%3A39%3A42Z&sr=c&sp=r&sig=NCRvPeyd5Km5r1a3pGs%2FsX4ndz4j2OcOwDvCPkJ4Cww%3D) ## SSH connection in the mac OS This section describes the access method using iTerm2. Even if other programs are used, the same action generates the same outcome. ``` chmod 400 ssh -i sshuser@ ``` ## SSH connection in Windows This section describes the access method using the PuTTY client. Even if other programs are used, the same action generates the same outcome. Follow the steps below in order: - [1. Convert authentication key (pem)](/docs/en/hadoop-chadoop-3-2#1-%EC%9D%B8%EC%A6%9D%ED%82%A4-pem-%EB%B3%80%ED%99%98) - [2. Connect to cluster node](/docs/en/hadoop-chadoop-3-2#2-%ED%81%B4%EB%9F%AC%EC%8A%A4%ED%84%B0-%EB%85%B8%EB%93%9C-%EC%A0%91%EC%86%8D) ### 1. Convert authentication key (.pem) PuTTY doesn't natively support the private key format (.pem) generated by Cloud Hadoop. You can use the PuTTYgen application provided by PuTTY to convert the authentication key into the format (.ppk) used by PuTTY. The private key must be converted to this format (.ppk) before PuTTY can be used to connect to the master node. 1. Run PuTTYgen. ([Download PuTTYgen](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html)) 2. Select **RSA** in **Type of key to generate** and click **[Load]**. 3. Select the authentication key (*.pem) and then click **[Open]**. - To find a file in PEM format, select the option that allows you to see files of all types. - The PEM file is the file name of the authentication key that is currently applied to the cluster. This PEM file must be stored on the user's local PC. - If the PEM file is missing, the authentication key for connection can be changed from the **Console > Manage server access > Manage authentication key for direct cluster connection** menu. (See [Manage authentication key for direct cluster connection](/docs/en/hadoop-chadoop-3-1#%ED%81%B4%EB%9F%AC%EC%8A%A4%ED%84%B0%EC%A7%81%EC%A0%91%EC%A0%91%EC%86%8D%EC%9D%B8%EC%A6%9D%ED%82%A4%EB%B3%80%EA%B2%BD)) 4. Check the details on the Completion confirmation popup and then click **[OK]**. 5. Click **[Save private key]** and save it as a file of .ppk format available in PuTTY. - If PuTTYgen displays a warning message about saving a key without a password, click **[Yes]**. - Save it using the same name as the previously generated authentication key. PuTTY automatically adds the .ppk file extension. ### 2. Connect to cluster node 1. Run PuTTY. ([Download PuTTY](http://www.putty.org/)) 2. Select **Session** in the **Category** window and enter info in each of the settings fields as below. - **Host Name (or IP address)**: `sshuser@DNS` (Enter the public domain or public IP of the relevant cluster into `DNS` of `sshuser@DNS`) - **Port**: `22` 3. In the **Category** window, select **Connection > SSH** to expand, and then click the **Auth** item. 4. Click **[Browse]** to select the PPK file created by converting the PEM file, and then click **[Open]**. 5. Check if connection to the edge node has been established successfully as follows: ![chadoop-2-1-116_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/chadoop-2-1-116_en.png?sv=2026-02-06&spr=https&st=2026-10-27T17%3A39%3A42Z&se=2026-10-27T18%3A39%3A42Z&sr=c&sp=r&sig=NCRvPeyd5Km5r1a3pGs%2FsX4ndz4j2OcOwDvCPkJ4Cww%3D) Note You can check the private IP and host name of each node in **Ambari UI > Hosts**. For more information on how to access Ambari UI, see the [Ambari UI](/docs/en/hadoop-chadoop-3-4#ambari-ui-%EC%A0%91%EC%86%8D) guide. - Connect to the edge node and enter ssh {master node host name} or ssh {master node Private IP} to access the master node (for example, m-001, m-002). ![chadoop-2-1-node](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/chadoop-2-1-node.png?sv=2026-02-06&spr=https&st=2026-10-27T17%3A39%3A42Z&se=2026-10-27T18%3A39%3A42Z&sr=c&sp=r&sig=NCRvPeyd5Km5r1a3pGs%2FsX4ndz4j2OcOwDvCPkJ4Cww%3D) - Data nodes (for example, dn-001, dn-002) can also be accessed in the same way as the master node. Connect to the edge node and connect ssh {data node host name} or ssh {data node private IP}. ![chadoop-2-1-node2](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/chadoop-2-1-node2.png?sv=2026-02-06&spr=https&st=2026-10-27T17%3A39%3A42Z&se=2026-10-27T18%3A39%3A42Z&sr=c&sp=r&sig=NCRvPeyd5Km5r1a3pGs%2FsX4ndz4j2OcOwDvCPkJ4Cww%3D)