IDC User Guide
  • Welcome!
  • 🚀Getting started
  • Core functions
  • Frequently asked questions
  • Support
  • Key pointers
  • Publications
  • IDC team
  • Acknowledgments
  • Jobs
  • Tutorials
    • Python notebook tutorials
    • Slide microscopy
      • Using QuPath for visualization
  • Data
    • Introduction
    • Data model
    • Data versioning
    • Organization of data
      • Files and metadata
      • Resolving CRDC Globally Unique Identifiers (GUIDs)
      • Clinical data
      • Organization of data, v2 through V13 (deprecated)
        • Files and metadata
        • Resolving CRDC Globally Unique Identifiers (GUIDs)
        • Clinical data
      • Organization of data in v1 (deprecated)
    • Downloading data
      • Downloading data with s5cmd
    • Data release notes
    • Data known issues
  • DICOM
    • Introduction to DICOM
    • DICOM data model
    • Original objects
    • Derived objects
      • DICOM Segmentations
      • DICOM Radiotherapy Structure Sets
      • DICOM Structured Reports
    • Coding schemes
    • DICOM-TIFF dual personality files
    • IDC DICOM white papers
  • Portal
    • Getting started
    • Exploring data and cohorts
      • Exploring imaging data
      • Viewing collections, studies, and series
      • Understanding cohorts
    • Cohort manifests
    • Visualizing images
    • Proxy policy
    • Viewer release notes
    • Portal release notes
    • Portal known issues
  • API
    • Getting Started
    • IDC API Concepts
    • Manifests
    • Accessing the API
    • Endpoint Details
    • V1 API
      • Getting Started
      • IDC Data Model Concepts
      • Accessing the API
      • Endpoint Details
      • Release Notes
  • Cookbook
    • Colab notebooks
    • BigQuery
    • Looker dashboards
      • Dashboard for your cohort
      • More dashboard examples
    • ACCESS allocations
    • Compute engine
      • 3D Slicer desktop VM
      • Using a BQ Manifest to Load DICOM Files onto a VM
      • Using VS Code with GCP VMs
      • Security considerations
    • NCI Cloud Resources
Powered by GitBook
On this page
  • Prerequisites
  • Step 1: Install "Remote - SSH" extension
  • Step 2: Populate SSH config files
  • Step 3: Connect to host

Was this helpful?

Edit on GitHub
Export as PDF
  1. Cookbook
  2. Compute engine

Using VS Code with GCP VMs

PreviousUsing a BQ Manifest to Load DICOM Files onto a VMNextSecurity considerations

Last updated 3 years ago

Was this helpful?

Visual Studio Code has a useful feature of allowing you to develop code on a remote VM from the convenience of your desktop. You can follow the steps below to configure your development environment for this task.

Prerequisites

  • ``gcloud SDK installed on your computer

  • Visual Studio Code installed on your computer

  • A GCP VM you want to use for code development is up and running

Step 1: Install "Remote - SSH" extension

Step 2: Populate SSH config files

Run the following command to populate SSH config files with host entries for each VM instance you have running

$ gcloud compute config-ssh

Step 3: Connect to host

If the previous step completed successfully, you should see the running VMs in the Remote Explorer of VS Code, as in the screenshot below, and should be able to open a new session to those remove VMs.

Note that the SSH configuration may/will change if you restart your VM. In this case you will need to re-configure (re-run step 2 above).