Skip to content

Connecting to AAC Environment

This document provides a step-by-step guide for users on how to connect to the AAC environment using MobaXterm and PuTTY with a private key.

Prerequisites

  • Ensure you have access to the AAC environment.
  • Obtain your private key file .
  • Install MobaXterm or PuTTY on your computer.

Using MobaXterm

Step 1: Open MobaXterm

  • Launch MobaXterm from your desktop or start menu.

Step 2: Create a New Session

  • Click on the "Session" icon in the top left corner.
  • Select "SSH" from the session options as shown in below.

Step 3: Configure SSH Settings

  • Remote host: Enter the hostname of the AAC environment.
  • Specify username: Enter your username (e.g.,testuser ) as shown in above. This will be provided by AMD team upon your onboard completion.

Step 4: Use Your Private Key

  • Check the box labeled "Use private key."
  • Click on the "..." button next to the private key field as shown in above.
  • Navigate to and select your private key file.

Step 5: Start the Session

  • Click on "OK" to save your session settings.
  • Double-click the session you just created to connect.

Step 6: Verify Connection

  • Once connected, you should see a terminal window where you can run commands on the AAC environment.

Using PuTTY

Step 1: Open PuTTY

  • Launch PuTTY from your desktop or start menu.

Step 2: Configure Host Name

  • In the "Host Name" field, enter the hostname of the AAC environment (e.g., aac1.amd.com).
  • Ensure the "Port" is set to 22 (default for SSH).

Step 3: Set Up SSH Key Authentication

  • In the left sidebar, navigate to Connection > SSH > Auth.
  • Click on "Browse" under "Private key file for authentication."
  • Locate and select your private key file (convert .pem to .ppk if necessary using PuTTYgen).

Step 4: Go Back to Session

  • Return to the "Session" category in the left sidebar.

Step 5: Connect

  • Click "Open" to start the session.

Step 6: Log In

  • A terminal window will open. Enter your username when prompted.

Important Note

When accessing the Jump Host, please be aware that no custom port (other than the standard port 22) has been provided as part of your login instructions. This means that your initial login will route you through the Jump Host.

However, if a custom port (other than 22) is mentioned in your instructions, it implies that you are being directed to access the GPU node directly rather than through the jump host.