|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
After you launch your instance, you can connect to it and use it the way that you'd use a computer sitting in front of you.
It may take a couple of minutes after launch for your running instance to finish provisioning so that you can connect to it. Check that your instance has passed its status checks - you can view this information in the Status Checks column on the Instances page. If you receive an error while attempting to connect to your instance, see Troubleshooting Connecting to Your Instance.
The following instructions explain how to connect to your instance using PuTTY, a free SSH client for Windows.
Download and install PuTTY from the PuTTY download page. Be sure to install the entire suite.
Get the ID of the instance
You can get the ID of your instance using the Amazon EC2 console (from the Instance ID column). If you prefer, you can use the describe-instances (AWS CLI) or ec2-describe-instances (Amazon EC2 CLI) command.
Get the public DNS name of the instance
You can get the public DNS for your instance using the Amazon EC2 console (check the Public DNS column; if this column is hidden, click the Show/Hide icon and select Public DNS). If you prefer, you can use the describe-instances (AWS CLI) or ec2-describe-instances (Amazon EC2 CLI) command.
Locate the private key
You'll need the fully-qualified path of the
.pem file for the key pair that you specified when you launched the instance.
Enable inbound SSH traffic from your IP address to your instance
Ensure that the security group associated with your instance allows incoming SSH traffic from your IP address. For more information, see Authorizing Network Access to Your Instances.
Your default security group does not allow incoming SSH traffic by default.
PuTTY does not natively support the private key format (.pem) generated by Amazon EC2. PuTTY has a tool named PuTTYgen, which can convert keys to the required PuTTY format (.ppk). You must convert your private key into this format (.ppk) before attempting to connect to your instance using PuTTY.
To convert your private key
Start PuTTYgen (for example, from the Start menu, click All Programs > PuTTY > PuTTYgen).
Under Type of key to generate, select SSH-2 RSA.
Click Load. By default, PuTTYgen displays
only files with the extension
.ppk. To locate your
select the option to display files of all types.
.pem file and click Open.
Click OK to dismiss the confirmation dialog box.
Click Save private key to save the key in the format that PuTTY can use. PuTTYgen displays a warning about saving the key without a passphrase. Click Yes.
A passphrase on a private key is an extra layer of protection, so even if your private key is discovered, it can't be used without the passphrase. The downside to using a passphrase is that it makes automation harder because human intervention is needed to log on to an instance, or copy files to an instance.
Specify the same name for the key that you used for the key pair (for example,
my-key-pair). PuTTY automatically adds the
.ppk file extension.
Your private key is now in the correct format for use with PuTTY. You can now connect to your instance using PuTTY's SSH client.
To start a PuTTY session
(Optional) You can verify the RSA key fingerprint on your instance by using one of the
following commands on your local system (not on the instance). This is useful if you've
launched your instance from a public AMI from a third party. Locate the
KEY FINGERPRINTS section, and note the RSA fingerprint (for example,
1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f) and compare it to the fingerprint of the instance.
SSH HOST KEY FINGERPRINTS section is only available after the first boot of
Start PuTTY (from the Start menu, click All Programs > PuTTY > PuTTY).
In the Category pane, select Session and complete the following fields:
In the Host Name box, enter
Be sure to specify the appropriate user name for your AMI. For example:
For an Amazon Linux AMI, the user name is
For a RHEL5 AMI, the user name is either
For an Ubuntu AMI, the user name is
For a Fedora AMI, the user name is either
For SUSE Linux, the user name is
root don't work, check with the AMI provider.
Under Connection type, select SSH.
Ensure that Port is 22.
In the Category pane, expand Connection, expand SSH, and then select Auth. Complete the following:
.ppk file that you generated for your key pair,
and then click Open.
(Optional) If you plan to start this session again later, you can save the session information for future use. Select Session in the Category tree, enter a name for the session in Saved Sessions, and then click Save.
Click Open to start the PuTTY session.
If this is the first time you have connected to this instance, PuTTY displays a security alert dialog box that asks whether you trust the host you are connecting to.
(Optional) Verify that the fingerprint in the security alert matches the fingerprint that you obtained in step 1. If these fingerprints don't match, someone might be attempting a "man-in-the-middle" attack. If they match, continue to the next step.
Click Yes. A window opens and you are connected to your instance.
If you specified a passphrase when you converted your private key to PuTTY's format, you must provide that passphrase when you log in to the instance.
The PuTTY Secure Copy client (PSCP) is a command-line tool that you can use to transfer files between your Windows computer and your Linux instance. If you prefer a graphical user interface (GUI), you can use an open source GUI tool named WinSCP. For more information, see Transferring Files to Your Linux Instance Using WinSCP.
To use PSCP, you'll need the private key you generated in Converting Your Private Key Using PuTTYgen. You'll also need the public DNS address of your Linux instance.
The following example transfers the file
Sample_file.txt from a Windows
computer to the
/usr/local directory on a Linux instance:
C:\>pscp -i C:\Keys\my-key-pair.ppk C:\Sample_file.txt user_name@public_dns:/usr/local/Sample_file.txt
WinSCP is a GUI-based file manager for Windows that allows you to upload and transfer files to a remote computer using the SFTP, SCP, FTP, and FTPS protocols. WinSCP allows you to drag and drop files from your Windows machine to your Linux instance or synchronize entire directory structures between the two systems.
To use WinSCP, you'll need the private key you generated in Converting Your Private Key Using PuTTYgen. You'll also need the public DNS address of your Linux instance.
Download and install WinSCP from http://winscp.net/eng/download.php. For most users, the default installation options are OK.
At the WinSCP login screen, for Host name, enter the public DNS address for your instance.
For User name, enter the default user name for your AMI. For Amazon Linux AMIs, the user name is
ec2-user. For Red Hat AMIs the user name is
root, and for Ubuntu AMIs the user name is
Specify the private key for your instance. For Private key, enter the path to your private key, or click the " " button to browse for the file. For newer versions of WinSCP, you need to click Advanced to open the advanced site settings and then under SSH, click Authentication to find the Private key file setting.
WinSCP requires a PuTTY private key file (
You can convert a
.pem security key file to the
.ppk format using PuTTYgen. For more information, see Converting Your Private Key Using PuTTYgen.
(Optional) In the left panel, click Directories, and then, for Remote directory, enter the path for the directory you want to add files to. For newer versions of WinSCP, you need to click Advanced to open the advanced site settings and then under Environment, click Directories to find the Remote directory setting.
Click Login to connect, and click Yes to add the host fingerprint to the host cache.
After the connection is established, in the connection window your Linux instance is on the right and your local machine is on the left. You can drag and drop files directly into the remote file system from your local machine. For more information on WinSCP, see the project documentation at http://winscp.net/eng/docs/start.