Differences
This shows you the differences between the selected revisions of the page.
| 2016-08-28 | 2017-02-22 | ||
| The Amazon EC2 CLI predates alternative AWS command line tools ... We recommend that you use the alternative AWS tools instead (martin) | https for docs.aws.amazon.com (martin) | ||
| Line 4: | Line 4: | ||
| Before starting you should: | Before starting you should: | ||
| * [[guide_install|Have WinSCP installed]]; | * [[guide_install|Have WinSCP installed]]; | ||
| - | * [[http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/launching-instance.html|Have Amazon EC2 instance running]]; | + | * [[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/launching-instance.html|Have Amazon EC2 instance running]]; |
| - | * [[http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html|Have enabled inbound SSH traffic from your IP address to your instance]]; | + | * [[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html|Have enabled inbound SSH traffic from your IP address to your instance]]; |
| - | * Have your [[http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html|key pair]] ready; | + | * Have your [[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html|key pair]] ready; |
| ~~AD~~ | ~~AD~~ | ||
| Line 14: | Line 14: | ||
| * Host name: Check //Public %%DNS%%// column on //Instances// page of Amazon EC2 console. Note that the public DNS may change when instance is restarted. | * Host name: Check //Public %%DNS%%// column on //Instances// page of Amazon EC2 console. Note that the public DNS may change when instance is restarted. | ||
| * Host key fingerprint: On the first connect you will be prompted to [[ssh_verifying_the_host_key|verify server host key]]. | * Host key fingerprint: On the first connect you will be prompted to [[ssh_verifying_the_host_key|verify server host key]]. | ||
| - | * You can locate key fingerprint in server's initial start log, when host keys are generated.((Using ''cloud-init'' script.)) Use //Actions > Get System Log// command on //Instances// page of Amazon EC2 console: \\ \\ &screenshotpict(ec2_hostkey) \\ \\ Alternatively use ''[[http://docs.aws.amazon.com/cli/latest/reference/ec2/get-console-output.html|aws ec2 get-console-output]]'' command. \\ Look for RSA (or DSA) key fingerprint. WinSCP does not support ECDSA keys. | + | * You can locate key fingerprint in server's initial start log, when host keys are generated.((Using ''cloud-init'' script.)) Use //Actions > Get System Log// command on //Instances// page of Amazon EC2 console: \\ \\ &screenshotpict(ec2_hostkey) \\ \\ Alternatively use ''[[https://docs.aws.amazon.com/cli/latest/reference/ec2/get-console-output.html|aws ec2 get-console-output]]'' command. \\ Look for RSA (or DSA) key fingerprint. WinSCP does not support ECDSA keys. |
| * If you did not save the fingerprint on the first instance run, but you have another EC2 instance that you can connect to safely (you know its fingerprints), you can connect to the target instance using private IP from the trusted instance. Staying within private Amazon network keeps you safe from [[wp>Man-in-the-middle_attack|man-in-the-middle attacks]]. When on the trusted instance terminal, you can use following commands to collect fingerprints: \\ <code> | * If you did not save the fingerprint on the first instance run, but you have another EC2 instance that you can connect to safely (you know its fingerprints), you can connect to the target instance using private IP from the trusted instance. Staying within private Amazon network keeps you safe from [[wp>Man-in-the-middle_attack|man-in-the-middle attacks]]. When on the trusted instance terminal, you can use following commands to collect fingerprints: \\ <code> | ||
| $ ssh-keyscan <target_instance_private_ip> > ec2key | $ ssh-keyscan <target_instance_private_ip> > ec2key | ||
| Line 46: | Line 46: | ||
| ===== [[vpc]] Connecting to EC2 instance in VPC ===== | ===== [[vpc]] Connecting to EC2 instance in VPC ===== | ||
| - | To connect to an EC2 instance in an Amazon VPC, you can tunnel through a [[http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_NAT_Instance.html|NAT instance]]. | + | To connect to an EC2 instance in an Amazon VPC, you can tunnel through a [[https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_NAT_Instance.html|NAT instance]]. |
| For details, see a guide to [[guide_tunnel|connecting to an SFTP server which can be accessed via another server only]]. | For details, see a guide to [[guide_tunnel|connecting to an SFTP server which can be accessed via another server only]]. | ||
| Line 54: | Line 54: | ||
| * Guide to [[guide_automation|automating operations]] (including upload); | * Guide to [[guide_automation|automating operations]] (including upload); | ||
| * [[faq_su|How do I change user after login (e.g. su root)?]] | * [[faq_su|How do I change user after login (e.g. su root)?]] | ||
| - | * [[http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html|Official guide for connecting using PuTTY/WinSCP]]; | + | * [[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html|Official guide for connecting using PuTTY/WinSCP]]; |
| * Guide to [[guide_google_compute_engine|connecting to Google Compute Engine server with SFTP]]; | * Guide to [[guide_google_compute_engine|connecting to Google Compute Engine server with SFTP]]; | ||
| * Guide to [[guide_microsoft_azure|connecting to Microsoft Azure Service with SFTP or FTPS]]. | * Guide to [[guide_microsoft_azure|connecting to Microsoft Azure Service with SFTP or FTPS]]. | ||