2 Answers
- Newest
- Most votes
- Most comments
1
Sometimes this is caused by not sending the correct login id (ec2-user, ubuntu, etc) when connecting.
0
Another possible reason is incorrect permissions for user's (ec2-user, ubuntu,centos etc) home directory and SSH files (~/.ssh/). You can use the AWSSupport-TroubleshootSSH
Systems Manager Automation runbook to troubleshoot common SSH issues in EC2 Linux instances. Refer to following AWS Knowledge Centre article for further details.
https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ssh-errors-automation-workflow/
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago