Refer to the exhibit. What could be the reason that the administrator cannot access the EC2 instance?

Question

Exhibits

Options

• AYou must elevate the permissions to access the EC2 instance
• BYou must run the chmod 400 Staging-key.peracommand before accessing the instance.
• CThere is no . pem key created on in Amazon Web Services (AWS)
• DThe directory location of the . pem file is incorrect.

• A
  8% (2)
• B
  4% (1)
• C
  13% (3)
• D
  75% (18)

Explanation

The reason the administrator cannot access the EC2 instance could be: D. The directory location of the .pem file is incorrect. SSH Key Location: When initiating an SSH connection to an AWS EC2 instance, you must specify the private key file (.pem file) location that corresponds to the public key used when the instance was launched. The error "Warning: Identity file Staging-key.pem not accessible: No such file or directory" indicates that the SSH client cannot find the .pem file at the specified location. Correct File Path: The administrator needs to ensure that the path to the Staging-key.pem file is correctly specified when running the SSH command. If the file is not in the current directory from which the command is executed, the full or relative path to the file must be provided.

No community discussion yet for this question.