A user is trying to connect to a running EC2 instance using SSH. However, the user gets an Unprotected Private Key File error. Which of the below mentioned options can be a possible reason for rejection?
A.
The private key file has the wrong file permission
B.
The ppk file used for SSH is read only
C.
The public key file has the wrong permission
D.
The user has provided the wrong user name for the OS login
Suggested Answer:A🗳️
While doing SSH to an EC2 instance, if you get an Unprotected Private Key File error it means that the private key file's permissions on your computer are too open. Ideally the private key should have the Unix permission of 0400. To fix that, run the command: chmod 0400 /path/to/private.key
When connecting to an EC2 instance using SSH, the private key file (.pem file) must have the correct file permissions. Typically, the permissions should be set to 400 or 600, meaning only the owner can read or write to the file.
If the file permissions are too permissive (e.g., 644 or 664), SSH may reject the private key file for security reasons, resulting in the "Unprotected Private Key File" error.
A. The private key file has the wrong file permission
upvoted 2 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
albert_kuo
2 days, 15 hours agoawscertified
1 year, 8 months ago