
In the following example, replace the example key with your SSH public key.
#Openssh debian update
If the signature of the SSH public key isn't present in the output, then update the authorized_keys file to allow your SSH key. On your local computer, verify the SSH public key.ĥ. Change the user name according to your specific AMI. In this example, ec2-user is the user name. The following is an example of the ls -ld command and the resulting output. authorized_keys file permission, /home/ec2-user/.ssh/authorized_keys, for example, should be (0600/-rw-).ssh directory permission, /home/ec2-user/.ssh, for example, should be (0700/drwx-). User's home directory, /home/ec2-user/, for example, should be (0700/drwx-).Linux home directory, /home, for example, should be (0755/drwxr-xr-x).The following is a list of the correct permissions: Use the ls -ld command to make sure that the permissions of the files under the home directory are correct. For more information on Session Manager and a complete list of prerequisites, see Setting up Session Manager.ģ. Note: Installation of the SSM Agent is required to use this method. This method updates permissions and injects your SSH public key into the authorized_keys file.

Method 2: Use AWS Systems Manager Session Manager to log in to the instance and make corrections Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.
#Openssh debian serial
For information on configuring the EC2 Serial Console for Linux, see Configure access to the EC2 Serial Console. If your instance is unreachable and you haven’t configured access to the serial console, then follow the instructions in Method 2, 3, or 4. Also, every instance using the serial console must include at least one password-based user. Then, create AWS Identity and Access Management (IAM) policies granting access to your IAM users. You can access the serial console using the Amazon EC2 console or the AWS Command Line Interface (AWS CLI).īefore using the serial console, grant access to it at the account level.

The serial console connects to your instance without the need for a working network connection. The serial console helps you troubleshoot boot issues, network configuration, and SSH configuration issues. If you activated EC2 Serial Console for Linux, then you can use it to troubleshoot supported Nitro-based instance types. There are four methods for performing these tasks: Verify that the file permissions within the operating system are correct and that the correct SSH public key is in the authorized_keys file Resolution Verify that you're using the correct user name for your AMIįor a list of valid user names, see Error: Server refused our key or No supported authentication methods available.
