Platform For AI:Remote connection: Direct SSH connection

Find connection endpoints

On the DSW page, click the instance name to open instance details. On the Instance Configuration tab, in the Access Configuration section, find the Public Endpoint and VPC Endpoint.

Prerequisites

• Completed Steps 1--4

• SSH key pair generated without a passphrase

Steps

1. In the local terminal, install remote_ikernel and add a remote kernel:

   Replace root@*.*.*.*:1024 with the actual host address. If the private key is not in the default path, use --host="-i /your/path/example_rsa root@*.*.*.*:1024".

      pip install remote_ikernel
   
      remote_ikernel manage --add \
        --kernel_cmd="ipython kernel -f {connection_file}" \
        --name="Remote Python" \
        --interface=ssh \
        --host=root@*.*.*.*:1024

   Output when the remote kernel is added successfully:

      Added kernel ['rik_ssh_root_121_40_*_*_1024_remotepython']: SSH root@121.40.*.*:1024 Remote Python.

   To view the remote kernel configuration:

      remote_ikernel manage --show

2. In VS Code, open a notebook file. Click kernel selection in the top-right corner. Search for and select "Remote Python".

   

Differences between direct SSH and ProxyClient

PyCharm and other IDE support

Yes. Any IDE using native SSH protocol is supported. IDEs like PyCharm may automatically download and install server-side components onto the instance. Verify the instance has public internet access for this to work.

Troubleshoot SSH connection failures

SSH connection issues typically stem from network misconfiguration, authentication errors, or missing server-side setup. Identify whether the issue is with the VPC or public network path.

Public connection fails or times out

First, try connecting through the VPC endpoint from within the same VPC. If VPC connection works, the issue is in NAT gateway configuration:

• Multiple NAT gateways in VPC: Verify the instance's vSwitch routes to the correct NAT gateway. See Deployment solutions for multiple Internet NAT gateways in the same VPC for routing table configuration.

• Single NAT gateway: Use the Self-service Troubleshooting tool. Enter the local public IP, the instance's EIP, and the public port to analyze reachability.

VPC connection fails

• SSH server not running: When using custom images, confirm that openssh-server is installed, running, and enabled. See Step 3.

• Security group blocking traffic: Verify the security group allows inbound traffic on TCP port 22 from the source IP.

• If these steps do not resolve the issue, contact your business manager for assistance.

Connection times out (general)

• Direct SSH over internet: Verify the Internet NAT gateway and security group rules. Check the correct port is open.

• Direct SSH over VPC: Verify security group rules allow traffic between instances. Try enabling private DNS resolution service for the VPC.

"Permission denied" or "Server refused our key" error

• Public key mismatch: Verify the public key (.pub file content) was copied completely and correctly into the instance's SSH configuration.

• Wrong private key: Verify the SSH command uses the matching private key. If the private key is not in the default location (~/.ssh/id_rsa), specify the path with the -i flag:

    ssh -i /path/to/your/private_key root@...

VS Code connection fails

• Confirm the Remote - SSH extension is installed and enabled.

• When adding a new host, verify the full SSH command is correct, including user, host, and port (for example, ssh root@xx.xx.xx.xx -p 1024).

• If VS Code fails, run the same SSH command in the local terminal. Terminal error messages provide more specific diagnostic details.

Find public IP address for SSH

The public IP is the elastic IP address (EIP) associated with the Internet NAT gateway:

1. On the DSW instance list page, click the instance name to open the configuration page.

2. In the Network Information section, click the link next to Elastic IP Address. The EIP console opens and displays the IP address.

Multiple SSH users on DSW instance

No. DSW does not natively support multiple, isolated user accounts for SSH. By default, all SSH connections use the root user. Creating new users manually within the operating system is not officially supported and may lead to unexpected behavior.

Project files not visible after VS Code connection

The IDE opens the home directory (/root) by default after SSH login. Project files are typically on a separate mounted data disk. In the IDE, use File > Open Folder... to navigate to /mnt/workspace or the appropriate working directory.