Differences

This shows you the differences between the selected revisions of the page.

2024-08-19 2026-06-02
removing forgotten anchor (martin) 6.6.2 Using “username” and “hostname” as one word (martin)
Line 14: Line 14:
Collect information about your EC2 instance: Collect information about your EC2 instance:
-  * Host name: Check //Public %%DNS%%// column on //Instances// page of Amazon EC2 console. Note that the public DNS may change when instance is restarted.+  * Hostname: 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]].
    * To securely acquire a fingerprint of the host key, use EC2 web-based terminal. Go to //Actions > Connect > EC2 Instance Connect > Connect// on //Instances// page of Amazon EC2 console. In the terminal, use ''[[https://man.openbsd.org/ssh-keygen|ssh-keygen]]'' command to display a fingerprint of any number of host keys algorithms. The following example shows SHA-256 and MD5 fingerprints of Ed25519 hostkey: \\ <code bash>sudo ssh-keygen -l -f /etc/<nohilite>ssh</nohilite>/ssh_host_ed25519_key     * To securely acquire a fingerprint of the host key, use EC2 web-based terminal. Go to //Actions > Connect > EC2 Instance Connect > Connect// on //Instances// page of Amazon EC2 console. In the terminal, use ''[[https://man.openbsd.org/ssh-keygen|ssh-keygen]]'' command to display a fingerprint of any number of host keys algorithms. The following example shows SHA-256 and MD5 fingerprints of Ed25519 hostkey: \\ <code bash>sudo ssh-keygen -l -f /etc/<nohilite>ssh</nohilite>/ssh_host_ed25519_key
Line 25: Line 25:
  * Make sure //New site// node is selected.   * Make sure //New site// node is selected.
  * On //New site node//, make sure //%%SFTP%%// protocol is selected.   * On //New site node//, make sure //%%SFTP%%// protocol is selected.
-  * Enter your EC2 instance public DSN name (see above) into //Host name// box. +  * Enter your EC2 instance public DSN name (see above) into //Hostname// box. 
-  * //User name// differs with instance type: +  * //Username// differs with instance type: 
-    * For an Amazon Linux AMI, the user name is ''ec2-user''. +    * For an Amazon Linux AMI, the username is ''ec2-user''. 
-    * For a RHEL5 AMI, the user name is either ''root'' or ''ec2-user''. +    * For a RHEL5 AMI, the username is either ''root'' or ''ec2-user''. 
-    * For an Ubuntu AMI, the user name is ''ubuntu''. +    * For an Ubuntu AMI, the username is ''ubuntu''. 
-    * For an Centos AMI, the user name is ''centos''. +    * For an Centos AMI, the username is ''centos''. 
-    * For a Fedora AMI, the user name is either ''fedora'' or ''ec2-user''. +    * For a Fedora AMI, the username is either ''fedora'' or ''ec2-user''. 
-    * For SUSE Linux, the user name is ''root'' or ''ec2-user''.+    * For SUSE Linux, the username is ''root'' or ''ec2-user''.
  * Press //Advanced// button to open [[ui_login_advanced|Advanced site settings dialog]] and go to //[[ui_login_authentication|SSH > Authentication page]]//.   * Press //Advanced// button to open [[ui_login_advanced|Advanced site settings dialog]] and go to //[[ui_login_authentication|SSH > Authentication page]]//.
  * In //Private key file// box select the ''.pem'' private key file. WinSCP will need to convert the key to its ''.ppk'' format (you can then use the converted ''.ppk'' key for example with [[integration_putty|PuTTY]] SSH client).   * In //Private key file// box select the ''.pem'' private key file. WinSCP will need to convert the key to its ''.ppk'' format (you can then use the converted ''.ppk'' key for example with [[integration_putty|PuTTY]] SSH client).
Line 50: Line 50:
===== [[ssm]] Connecting using AWS SSM (Session Manager) ===== ===== [[ssm]] Connecting using AWS SSM (Session Manager) =====
-In //Host name//, specify your //Instance ID//.+In //Hostname//, specify your //Instance ID//.
Press //Advanced// button to open [[ui_login_advanced|Advanced site settings dialog]] and go to //[[ui_login_proxy|Connection > Proxy page]]//. There: Press //Advanced// button to open [[ui_login_advanced|Advanced site settings dialog]] and go to //[[ui_login_proxy|Connection > Proxy page]]//. There:

Last modified: by martin