Cloud Server GPUs

Launching the Server

There are AMIs on the Amazon Cloud Marketplace for both the open-source and Professional versions of RStudio Server. You can find them here:

• Open Source: https://aws.amazon.com/marketplace/pp/B0785SXYB2

• Professional: https://aws.amazon.com/marketplace/pp/B07B8G3FZP

You should launch these AMIs on the p2.xlarge instance type. This type includes a single GPU whereas other GPU-based images include up to 16 GPUs (however they are commensurately much more expensive). Note that you may need to select a different region than your default to be able to launch p2.xlarge instances (for example, selecting “US East (Ohio)” rather than “US East (N Virginia)”).

Accessing the Server

After you’ve launched the server you can access an instance of RStudio Server running on port 8787. For example:

http://ec2-18-217-204-43.us-east-2.compute.amazonaws.com:8787

Note that the above server address needs to be substituted for the public IP of the server you launched, which you can find in the EC2 Dashboard.

The first time you access the server you will be presented with a login screen:

Login with user id “rstudio-user” and password the instance ID of your AWS server (for example “i-0a8ea329c18892dfa”, your specific ID is available via the EC2 dashboard).

Then, use the RStudio Terminal to change the default password using the passwd utility:

Your EC2 deep learning instance is now ready to use (the tensorflow, tfestimators, and keras R packages along with their pre-requisites, including the GPU version of TensorFlow, are installed as part of the image).

See the sections below for discussion of various ways in which you can make your EC2 instance more secure.

Limiting Inbound Traffic

The EC2 instance is by default configured to allow access to SSH and HTTP traffic from all IP addresses on the internet, whereas it would be more desirable to restrict this to IP addresses that you know you will access the server from (this can however be challenging if you plan on accessing the server from a variety of public networks).

You can see these settings in the Security Group of your EC2 instance:

Edit the Source for the SSH and HTTP protocols to limit access to specific blocks of IP addresses.

Using HTTPS

By default the EC2 instance which you launched is accessed over HTTP, a non-encrypted channel. This means that data transmitted to the instance (including your username and password) can potentially be compromised during transmission.

There are many ways to add HTTPS support to a server including AWS Elastic Load Balancing, CloudFlare SSL, and setting up reverse proxy from an Nginx or Apache web server configured with SSL support.

The details of adding HTTPS support to your server are beyond the scope of this article (see the links above to learn more). An alternative to this is to prohibit external HTTP connections entirely and access the server over an SSH Tunnel, this option is covered in the next section.

SSH Tunnel

Using an SSH Tunnel to access your EC2 instance provides a number of benefits, including:

1. Use of the SSH authentication protocol to identify and authorize remote users

2. Encrypting traffic that would otherwise be sent in the clear

Note that SSH tunnel access as described below works only for Linux and OS X clients.

ssh -i "my-security-key.pem" ubuntu@my-ec2-server-address

Please login as the user "ubuntu" rather than the user "root".

# Configure RStudio to only allow local connections 
sudo /bin/bash -c "echo 'www-address=127.0.0.1' >> /etc/rstudio/rserver.conf"

# Restart RStudio with new settings
sudo rstudio-server restart

ssh -N -L 8787:localhost:8787 -i my-security-key.pem ubuntu@my-ec2-server-address