You try to connect via SSH to a newly created Amazon EC2 instance and get one of the
following error messages:
“Network error: Connection timed out” or “Error connecting to [instance], reason: ->
Connection timed out: connect,”
You have confirmed that the network and security group rules are configured correctly and
the instance is passing status checks. What steps should you take to identify the source of
the behavior? Choose 2 answers
A.
Verify that the private key file corresponds to the Amazon EC2 key pair assigned at launch.
B.
Verify that your IAM user policy has permission to launch Amazon EC2 instances.
C.
Verify that you are connecting with the appropriate user name for your AMI.
D.
Verify that the Amazon EC2 Instance was launched with the proper IAM role.
E.
Verify that your federation trust to AWS has been established.
Explanation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnectin
g.html
Both A & C will give you “Permission denied (publickey).”
Since federation trust has nothing to do with ssh access, the answers are B & D (either the instance not launched or
B & D make no sense as they talk about launching the instance and the question already states that the instance is passing health checks (meaning it’s already online). A connection timeout occurs with some SSH terminals by trying the wrong pem keys, though the specifics of what error is relayed to you depend on the OS of the instance and what the terminal tries.