Logging into Course Compute
Choose one of two options to complete the hands-on exercises in this course:
Compute Options
- Using AWS: Launch a virtual computer (an EC2 instance) in the Amazon cloud, then connect to it from your computer.
- Using Docker: Run a prebuilt course image locally on a computer with Docker installed.
Using AWS
You will first launch an EC2 instance from the course’s preconfigured Amazon Machine Image (AMI), then log in using SSH. For background on cloud computing and AWS terminology, see Introduction to AWS.
Launching an AWS instance
You will need an AWS account: your own, one provided by your institution, or an IAM user account assigned for a live course. The steps below use the live course account; the process is similar for personal or institutional accounts.
For live course participants: Wait until you are in the classroom and instructed to launch your instance. Running AWS instances costs money. Each student should launch their own instance.
Sign in and open the EC2 console
-
Sign in to AWS using the URL and credentials provided by your instructors, or use your own AWS account.
- Search for and select EC2 to open the EC2 console.
- Set the region to N. Virginia (us-east-1).
-
Select Launch instances.

Configure your instance
- Name and tags: Give your instance a recognizable name, such as
Firstname_Lastname. -
Application and OS Images (Amazon Machine Image): Under My AMIs, search for and select
cshl-seqtec-2026.
- Instance type: Select
m6a.xlarge. - Key pair (login): Select the course key pair, such as
cshl_2026_student, or create a new key pair and save the downloaded key file somewhere you can find it. You will need the matching private key file to log in. -
Network settings: Select the existing security group SSH/HTTP/Jupyter/Rstudio - with outbound rule, or create one with SSH and HTTP access.

-
Configure storage: Confirm that two volumes are listed.

-
Advanced details: Enable Termination protection.

Launch and find your public IP address
- Review the Summary, then select Launch instance.
- Select View all instances and wait for your instance to finish initializing.
-
Select your instance, then choose Connect. On the EC2 Instance Connect tab, find and copy your Public IP address.

- Follow the instructions below to log in from your computer.
Logging in to your own AWS EC2 instance
Before you connect, have the following ready:
- Your private key file: For Terminal or PowerShell, use
cshl_2026_student.pem(or the key file matching the key pair you selected when launching your instance). - Your instance’s public IP address or public DNS name: Copy this from the EC2 console.
- The instance user name:
ubuntu. This is the Linux user on the instance, separate from your AWS console user name.
Connect only to your own instance. If two students use the same instance, they may overwrite each other’s files or interfere with each other’s work.
Choose the instructions for your computer:
Mac/Linux
- Open a terminal. On a Mac, go to Applications → Utilities → Terminal.
-
Restrict access to your private key file:
chmod 400 "/path/to/cshl_2026_student.pem" -
Connect to your instance using SSH:
ssh -i "/path/to/cshl_2026_student.pem" ubuntu@YOUR_PUBLIC_IP
Replace /path/to/cshl_2026_student.pem in both commands with the actual path to your downloaded key file. Replace YOUR_PUBLIC_IP with your instance’s public IP address or public DNS name.
For example, if your key is in the Downloads folder on a Mac:
chmod 400 "$HOME/Downloads/cshl_2026_student.pem"
ssh -i "$HOME/Downloads/cshl_2026_student.pem" ubuntu@YOUR_PUBLIC_IP
Here, -i specifies the private key file, ubuntu is the user on the instance, and the value after @ identifies the instance to connect to.
When you are done using this session, you may type “exit” in your Terminal to log out of this instance on your laptop.
Remember to “Stop” your instance when you no longer need it to prevent unnecessary billing. At the end when this instance is no longer needed, you may “Terminate” it.
Windows
Choose one of the following tools to connect to your instance:
PowerShell
Open PowerShell and connect using the downloaded .pem key file:
ssh -i "C:\path\to\cshl_2026_student.pem" ubuntu@YOUR_PUBLIC_IP
Replace C:\path\to\cshl_2026_student.pem with the actual path to your key file and YOUR_PUBLIC_IP with your instance’s public IP address or public DNS name. The chmod step above applies to Mac/Linux only.
If PowerShell does not recognize ssh, install the Windows OpenSSH Client or use PuTTY as described below.
PuTTY
To configure PuTTy, start PuTTy and do the following:
- Fill in the “Host name” field with your ip address.

- In the left hand categories,under the Connection category choose Data. In the auto-login username field write
ubuntu.

- In the left hand categories, in the Connection category next to SSH click on the +. Click on Auth. In the private-key file for authentication field, hit browse and find the
cshl_2026_student.ppkcertificate that you downloaded above.

- In the left hand categories, click on Session. In the Saved Sessions field write Amazon node and click save.

- Now that Putty is configured, all you have to do is start putty and double-click on “Amazon node” to login.
File system layout on AWS instance
When you log in, you will notice that you have one directory already: “workspace”.
- The “workspace” directory is where we will keep all files and analysis results for this course.
Transferring files between your computer and AWS
Choose the direction you want to transfer files:
- Download files from the instance to your computer.
- Upload files to the instance from your computer.
Download files from the instance
- To copy files from an instance, use scp in a similar fashion (in this case to copy a file called nice_alignments.bam):
scp -i cshl_2026_student.pem ubuntu@[your ip address or dns name]:nice_alignments.bam .
- Everything created in your workspace on the cloud is also available by a web server on your cloud instance. Simply go to the following in your browser:
http://[your ip address]/ (e.g. http://3.81.96.131)
or http://[your dns name] (e.g. http://ec2-3-81-96-131.compute-1.amazonaws.com)

Upload files to the instance
If you would like to upload your data to the AWS instance, use the example scp command below. Be sure to replace the variables below with the local path to your data, MY_DATA, and the amazon instance IP, YOUR_IP_ADDRESS.
scp -i cshl_2026_student.pem __MY_DATA__ ubuntu@[your ip address or dns name]:/
Doing this course with AWS outside of a workshop
If you are trying to do this course on your own using the online materials only, of course an AWS EC2 instance has not been set up for you. If you have access to an AWS account though you can can start with the same Amazon AMI we use to create instances for each student. Currently this is:
Name: cshl-seqtec-2026 available in the US East, N. Virginia region (us-east-1).
We typically use an instance type of m6a.xlarge. For detailed instructions on how we created the AMI and configure each instance, please refer to the AWS Setup page.
Basic introduction to your AWS EC2 instance
Once you are logged into your EC2 instance using ssh, the following commands can be used to explore basic information about the machine
#How are storage volumes mounted?
lsblk
#How much storage space in being used for various mount points?
df -h
#Detailed description of hardware
lshw
#See active resource usage right now with "top". Use "1" to see all CPUs individually. Use "q" to exit
top
Using Docker
We have built Docker images with all the software tools needed for this course already installed. This allows the hands-on exercises to be performed on your own desktop or laptop, or anywhere that has Docker installed. The commands below download an image and run it as an interactive Docker container.
Choose an image
There are two course images. Use the one that matches the course you are taking:
| Image | Use it for | Download size |
|---|---|---|
griffithlab/rnaseq-toolkit |
The RNA-seq bioinformatics course (the lessons on this site) | ~1.6 GB |
griffithlab/seqtec |
The CSHL Advanced Sequencing Technologies & Bioinformatics Analysis (SeqTec) course | ~2 GB |
- rnaseq-toolkit has the tools for bulk RNA-seq analysis: alignment (HISAT2), quantification and assembly (StringTie, kallisto, htseq-count), QC (FastQC, fastp, MultiQC, RSeQC, Picard), samtools, bedtools, regtools, and R with DESeq2, edgeR, ballgown, sleuth and related packages.
- seqtec has everything in rnaseq-toolkit, plus tools for the other parts of the SeqTec course: variant analysis (BWA, GATK, bcftools, htslib) and single-cell analysis in R (Seurat, scran, tidyverse and related packages).
Both images also run a small web server so you can view files from your workspace in a browser.
Both images are built for Intel/AMD (x86_64) computers. They also run on Apple Silicon Macs (M1 and later), where Docker Desktop emulates x86, so some steps will be slower. On those Macs Docker prints a warning that the image’s platform (linux/amd64) doesn’t match your computer’s. This is expected and safe to ignore, or you can add --platform linux/amd64 to the docker pull and docker run commands below to silence it.
Install Docker
First you will need to install Docker. Typically this involves installing Docker Desktop. Once installed, start Docker and open a terminal application. Explanations of how to open a terminal are given above in the Using AWS section. At the terminal, you can test that your Docker installation is working with docker --help.
Run the rnaseq-toolkit image
- Pull the image to your local Docker client from the griffithlab repository:
docker pull griffithlab/rnaseq-toolkit:latest - Set up a local workspace directory for the course. If you change the path used here in Step 2, make sure to update the path to the workspace directory accordingly in Step 3.
mkdir -p /tmp/rnabio-workspace - Start a Docker container from the image you pulled above.
-vtells Docker to mount your workspace directory inside the container as/workspace. In the course,/workspaceis the base directory for nearly all commands and steps. Note: this runs the container interactively, opens port 8080, and gives you a bash shell prompt inside the container.docker run -it -p 127.0.0.1:8080:8080 -v /tmp/rnabio-workspace:/workspace griffithlab/rnaseq-toolkit:latest
While the container is running, you can browse the files in your workspace at http://localhost:8080. This is how you will view HTML reports (e.g. from FastQC and MultiQC) in your web browser.
Optionally, to enable Docker functionality within the container (for running other bioinformatics containers):
# Mount the Docker socket to enable host Docker engine access
docker run -it -p 127.0.0.1:8080:8080 -v /tmp/rnabio-workspace:/workspace -v /var/run/docker.sock:/var/run/docker.sock griffithlab/rnaseq-toolkit:latest
Run the seqtec image
- Pull the image to your local Docker client from the griffithlab repository:
docker pull griffithlab/seqtec:latest - Set up a local workspace directory for the course. If you change the path used here in Step 2, make sure to update the path to the workspace directory accordingly in Step 3.
mkdir -p /tmp/seqtec-workspace - Start a Docker container from the image you pulled above. As with rnaseq-toolkit,
-vmounts your workspace directory inside the container as/workspace, and the container runs interactively, opens port 8080, and gives you a bash shell prompt inside the container.docker run -it -p 127.0.0.1:8080:8080 -v /tmp/seqtec-workspace:/workspace griffithlab/seqtec:latest
While the container is running, you can browse the files in your workspace at http://localhost:8080. This is how you will view HTML reports (e.g. from FastQC and MultiQC) in your web browser.
Optionally, to enable Docker functionality within the container (for running other bioinformatics containers):
# Mount the Docker socket to enable host Docker engine access
docker run -it -p 127.0.0.1:8080:8080 -v /tmp/seqtec-workspace:/workspace -v /var/run/docker.sock:/var/run/docker.sock griffithlab/seqtec:latest
Notes for both images
- You are logged in as the
ubuntuuser, with passwordlesssudo. - Only one container at a time can use port 8080. If
docker runreports that the port is already allocated, exit (ordocker stop) the other course container first. - Anything you save outside
/workspaceis lost when the container exits. Keep your work in/workspace, which is stored on your computer. /tmpon your computer may be cleared when it restarts. To keep your work longer, use a workspace directory somewhere else (e.g. in your home directory) in Steps 2 and 3.- To leave the container, type
exit. To start working again later, rerun thedocker runcommand from Step 3. Your files in the workspace directory will still be there.
The Docker session should now be ready for the Unix tutorial and practical exercises.