Logging onto Cloud

Overview

Teaching: 5 min
Exercises: 5 min
Questions
  • How do I connect to an AWS instance?

Objectives
  • Log onto to a running instance

  • Log off from a running instance

Important Note

This lesson covers how to log into, and out of, an already running Amazon instance.

If you’re returning post-workshop and want to launch your own instance, use launching cloud instances on your own

Background to AWS

Setting up a new AWS instance requires a credit card, an AWS account, and up to a day of verification time, but you’ve already spent most of this workshop working in the cloud! To save time, your instructor launched a remote computer (instance) for you prior to the workshop, and connected it to our lesson data. You’ve already logged into it at least once, but now that you’re more comfortable with the command line, lets go back and talk about how it all works.

We have a pre-configured copy of the data needed for this workshop that is always available to attach to a new instance on Amazon, as long as you have an account, and the log-in credentials to open it.

To access the pre-configured workshop data, you’ll need to use our log-in credentials (user name and password). These credentials will be supplied by your instructor.

But first, you need a place to log into! To find the instance that’s attached to that data, you’ll need something called an IP address. Your instructor should have given this to you at the beginning of the workshop.

An IP address is essentially the numerical version of a web address like www.amazon.com

Recall that cloud computing is about choice. You can rent just a single processor on a large computer for a small project, or you can rent hundreds of processors spread across multiple computers for a large project. In either case, once you rent the collection of processors, Amazon will present your rental to you as if it was a single computer. So, the physical computers that host your instances don’t really move, but every time you launch a new instance, it will have a new IP address.

So, each time you launch a new instance, the IP address changes, but your Log-in Credentials don’t have to.

Connection Protocols

We will use a protocol called Secure Shell (SSH) that, as the name implies, provides you with a secure way to use a shell. In our case, the shell will be running on a remote machine. This protocol is available for every operating system, but sometimes requires additional software.

Logging onto a cloud instance

Please select the platform you wish to use for the exercises:

Connecting using PC

Prerequisites: You must have an SSH client. There are several free options but you should have installed PuTTY.exe at the begining of the workshop, and we’re going to continue using that.

  1. Open PuTTY
  2. Paste in the ‘Host Name (or IP address)’ section the IP address provided by your instructor (or the IP address of an instance you have provisioned yourself)

    Keep the default selection ‘SSH’ and Port (22)

    The location of the Host Name, Port, and Connection Type fields in the PuTTY Configuration

  3. Click ‘Open’

    You will be presented with a security warning

    Screenshot showing a security warning after opening a PuTTY session.

  4. Select ‘Yes’ to continue to connect
  5. In the final step, you will be asked to provide a login and password

    Note: When typing your password, it is common in Unix/Linux not see any asterisks (e.g. `**) or moving cursors. Just continue typing

    Screenshot of a command line window demonstrating how to type passwords in Unix/Linux

You should now be connected!

Connecting using Mac/Linux

Mac and Linux operating systems will already have terminals installed.

  1. Open the terminal

    Simply search for ‘Terminal’ and/or look for the terminal icon

    terminal icon

  2. Type the following command substituting ip_address by the IP address your instructor will provide (or the IP address of an instance you have provisioned yourself)

     $ ssh dcuser@ip_address
    

    Be sure to pay attention to capitalization and spaces

  3. You will receive a security message that looks something like the message below

     The authenticity of host 'ec2-52-91-14-206.compute-1.amazonaws.com (52.91.14.206)' can't be established.
     ECDSA key fingerprint is SHA256:S2mMV8mCThjJHm0sUmK2iOE5DBqs8HiJr6pL3x/XxkI.
     Are you sure you want to continue connecting (yes/no)?
    
  4. Type yes to proceed
  5. In the final step, you will be asked to provide a login and password

    Note: When typing your password, it is common in Unix/Linux not see any asterisks (e.g. ****) or moving cursors. Just continue typing.

You should now be connected!

Logging off a cloud instance

Logging off your instance is a lot like logging out of your local computer: it stops any processes that are currently running, but doesn’t shut the computer off. AWS instances acrue charges whenever they are running, even if you are logged off.

If you are completely done with your AWS instance, you will need to terminate it after you log off. Instructions for terminating an instance are here: launching cloud instances on your own.

To log off, use the exit command in the same terminal you connected with. This will close the connection, and your terminal will go back to showing your local computer:

dcuser@ip-172-31-62-209 $ exit

Amandas-MacBook-Pro-3 $

Logging back in

Internet connections can be slow or unstable. If you’re just browsing the internet, that means you have reload pages, or wait for pictures to load. When you’re working in cloud, that means you’ll sometimes be suddenly disconnected from your instance when you weren’t expecting it. Even on the best internet connections, your signal will occasionally drop, so it’s good to know the above SSH steps, and be able to log into AWS without looking up the instructions each time.

In the next section, we’ll also show you some programs that you can use to keep your processes going even if your connection drops. But for now, just practice logging on and off a few times.

Key Points

  • You can use one set of log-in credentials for many instances

  • Logging off an instance is not the same as turning off an instance