Remote Development Using VS Code and SSH with AWS EC2

Remote Development Using VS Code and SSH with AWS EC2

How to Perform Remote Code Development Using VS Code on a Remote AWS EC2 Instance via SSH

Remote development has become a crucial tool for developers, enabling the convenience of coding and deploying directly to remote environments. In this blog, I’ll walk you through the process of setting up Visual Studio Code (VS Code) to develop remotely on an AWS EC2 instance using SSH. By the end of this guide, you’ll be able to connect to your EC2 instance from VS Code and develop code as if you were working locally.

Prerequisites

  1. AWS EC2 Instance: Ensure that you have an EC2 instance up and running on AWS.
  2. VS Code: Make sure you have the latest version of VS Code installed on your local machine.
  3. OpenSSH: You should have OpenSSH installed on your local machine (both macOS and Linux have it preinstalled, but Windows users might need to enable it manually).
  4. SSH Key Pair: Ensure that you have the SSH key pair (.pem file) generated when creating your EC2 instance.
  5. AWS Security Group Configuration: Ensure that port 22 (SSH) is open in your EC2 instance’s security group.

Step-by-Step Guide to Connect VS Code to AWS EC2 Using SSH

Step 1: Obtain your AWS Credentials and SSH Key(s)

When you launch an EC2 instance, you are prompted to create or use an existing SSH key pair to securely connect to the instance. In this section, we’ll cover two scenarios: using the SSH key pair you created during instance setup and generating a new key pair if needed. Both methods will allow you to access your EC2 instance securely via SSH.

Scenario 1: Using the SSH Key Pair Created During EC2 Instance Setup

1.1.1. Locate Your Key Pair (.pem File):

  • When you first launched your EC2 instance, AWS prompted you to either create a new SSH key pair or use an existing one. If you created a new key pair, AWS would have provided you with a .pem file. This file is crucial for connecting to your EC2 instance.
  • Make sure you have the .pem file downloaded on your local machine. It should be stored securely, as this is your private key to access the instance.

1.1.2. Set the Correct Permissions:

  • To ensure your SSH key is secure and usable, you need to set the correct permissions on the .pem file. Open your terminal and run the following command:
chmod 400 /path/to/your-key.pem
  • Replace /path/to/your-key.pem with the actual path where your key pair file is stored.

1.1.3. Connect to Your EC2 Instance:

  • Once your key permissions are set, you can use the following SSH command to connect to your instance:
ssh -i /path/to/your-key.pem ec2-user@your-instance-public-ip
  • Make sure to replace /path/to/your-key.pem with the path to your private key file and your-instance-public-ip with the public IP of your EC2 instance.

Scenario 2: Generating a New SSH Key Pair and Associating It with a Running EC2 Instance

If you don’t have access to the original .pem file or want to use a different key pair, you can generate a new SSH key and associate it with an existing EC2 instance.

Generate a New SSH Key Pair

1.2.1. Open your terminal (macOS/Linux) or Git Bash (Windows) and run the following command to generate a new key pair:

ssh-keygen -t rsa -b 4096 -f ~/.ssh/new-ec2-key
  • The -t option specifies the type of key, and -b 4096 defines the key length for extra security.
  • The -f flag specifies the file name and location where the key pair will be saved. In this example, it will be saved as new-ec2-key in the ~/.ssh directory.

1.2.2. You will now have two files:

  • new-ec2-key: This is your private key. Keep this file secure.
  • new-ec2-key.pub: This is your public key. You’ll upload this to your EC2 instance.
Associate the New Public Key with the Running EC2 Instance

1.2.1. Connect to the EC2 Instance (with an existing key or through the AWS EC2 Instance Connect feature) and run the following command to create a directory for SSH keys:

mkdir -p ~/.ssh

1.2.2. Upload the New Public Key to the ~/.ssh/authorized_keys file on the EC2 instance. You can use the scp command to copy the public key from your local machine to the EC2 instance:

scp -i /path/to/old-key.pem ~/.ssh/new-ec2-key.pub ec2-user@your-instance-public-ip:/home/ec2-user/new-ec2-key.pub
  • Replace /path/to/old-key.pem with the path to the existing SSH key you used to access the instance, and your-instance-public-ip with your EC2 instance’s public IP.

1.2.3. Add the New Public Key to Authorized Keys:

  • SSH into your EC2 instance using the existing SSH key and run:
cat ~/new-ec2-key.pub >> ~/.ssh/authorized_keys

1.2.4. Set Correct Permissions:

  • Ensure the permissions are set correctly for the .ssh directory and the authorized_keys file:
chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

1.2.5. Connect with the New Key:

  • Now you can SSH into your EC2 instance using the new key pair:
ssh -i ~/.ssh/new-ec2-key ec2-user@your-instance-public-ip

Step 2: Install the VS Code Remote Development Extension

You may need to install the Remote Development extension for VS Code if it is not already installed.

2.1. Open VS Code and click on the Extensions icon in the sidebar (or press Ctrl+Shift+X). 2.2. Search for Remote - SSH by Microsoft. 2.3. Click Install to add the extension to VS Code.

Step 3: SSH Into Your EC2 Instance Locally (Optional)

Before configuring SSH in VS Code, it’s a good idea to test your connection via the terminal:

3.1. Open a terminal window. 3.2. Run the following command (replace ec2-user and your-instance-public-ip with your actual instance user and public IP):

ssh -i /path/to/your-key.pem ec2-user@your-instance-public-ip

3.3. If successful, you’ll see a welcome message on your terminal from your EC2 instance. If not, double-check your IP, security group settings, and key path.

Step 4: Configure SSH in VS Code

4.1. Open VS Code, and click on the ‘Open a Remote Window’ icon at the bottom left-hand corner of the window

Open a Remote Window

4.2. Select ‘Connect to Host’

Connect to Host

4.3. Select ‘Configure SSH Hosts…’

Connect to Host

4.4. VS Code will prompt you to choose a file where the SSH configuration will be saved, or use an existing file. Select the .ssh/config file for your user. On Linux it will be /home/<username>/.ssh/config. On Windows it will be C:/Users/<username>/.ssh/config.

Select the SSH config file

Use the following file content, replacing the Hostname, User, and IdentifyFile with your specific host information:

Host <nickname>
    HostName <your-ec2-ip-address or hostname>
    User ec2-user
    IdentityFile ~/.ssh/labsuser.pem

Example:

Host aws-ec2
    HostName ec2-3-22-20-2002.us-east-2.compute.amazonaws.com
    User ubuntu
    IdentityFile ~/.ssh/aws-ec2-demo.pem

4.5. Save the file.

Step 5: Connect to a Remote Host (SSH)

5.1. When you click on the Open a Remote Window icon at the bottom left-hand corner again and choose Connect to Host, you will see aws-ec2 listed. You can get to the same place using the the Command Palette (press Ctrl+Shift+P or Cmd+Shift+P on macOS) and select or type Remote-SSH: Connect to Host….

5.2 From the list of hosts, choose the EC2 instance you just configured.

Connect to Host

5.3 If your SSH key has a passphrase, you’ll be prompted to enter it when connecting. Enter the passphrase, and VS Code will establish the SSH connection to the EC2 instance.

5.4. Once connected, VS Code will automatically install its VS Code Server on your EC2 instance. This process happens behind the scenes, and you should see a series of progress notifications.

Step 6: Start Coding!

Once the VS Code Server is installed, the remote connection is established. Now, you can open files, folders, and even entire projects on your EC2 instance as if they were on your local machine.

You can now:

  • Navigate to the Explorer in VS Code.
  • Click Open Folder.
  • Select the folder you want to work with on the remote EC2 instance.

Step 7: Closing the SSH Connection

To close the connection, simply close the VS Code window or manually disconnect by using the Command Palette and selecting Remote-SSH: Close Remote Connection.

Conclusion

That’s it! You are now connected to your AWS EC2 instance via SSH using VS Code. This allows you to edit files, run code, and perform development tasks as if you were working on a local machine. Remote development can greatly streamline your workflow when working with cloud environments like AWS EC2.

Happy coding!

Tags:

vLLM Recipe: RedHatAI/Qwen3.6-35B-A3B-NVFP4 on DGX Spark

vLLM Recipe: RedHatAI/Qwen3.6-35B-A3B-NVFP4 on DGX Spark

This is a vLLM Recipe - a production-ready Docker Compose configuration for running open-weight models on local hardware. It documents the exact setup, configuration rationale, and benchmark results so you can get a model running quickly. You are welcome to change the parameters to suit your workloads. This worked for me, so I hope you find it helpful.

This recipe covers Qwen3.6-35B-A3B-NVFP4 - a Mixture-of-Experts model with 35B total parameters but only ~3B active at inference - quantized to NVFP4 by Red Hat AI and running on the NVIDIA DGX Spark (my GigaByte AI Top Atom) with a GB10 Blackwell GPU and 128 GB of unified CPU/GPU memory.

Read More
Is Your Application Really Using Persistent Memory? Here’s How to Tell.

Is Your Application Really Using Persistent Memory? Here’s How to Tell.

Persistent memory (PMEM), especially when accessed via technologies like CXL, promises the best of both worlds: DRAM-like speed with the durability of an SSD. When you set up a filesystem like XFS or EXT4 in FSDAX (File System Direct Access) mode on a PMEM device, you’re paving a superhighway for your applications, allowing them to map files directly into their address space and bypass the kernel’s page cache entirely.

But here’s the crucial question: after all the setup and configuration, how do you prove that your application’s data is physically residing on the PMEM device and not just in regular RAM? I’ve run into this question myself, so I wrote a small Python script to get a definitive answer using SQLite3 as an example application. However, before we proceed with the script, let’s examine how you can verify this manually.

Read More
Understanding Memory Usage with `smem`

Understanding Memory Usage with `smem`

Memory management is crucial for Linux administrators and developers, especially when optimizing performance for resource-intensive applications. While tools like top and htop are commonly used to monitor system performance, they often don’t provide enough detail regarding memory usage breakdown. This is where smem comes into play.

What is smem?

smem is a command-line tool that reports memory usage per process and provides better insight into shared memory than most traditional tools, taking shared memory pages into account. Unlike top or htop, which primarily display RSS (Resident Set Size), smem can also show USS (Unique Set Size), which is a better metric for understanding how much memory would be freed if a particular process were terminated. This blog will guide you through using smem, explaining these critical memory metrics and providing comparisons to more familiar tools.

Read More