Timeout when connecting to an EC2 using ssh (and ping) from Windows 10. How can I get my *account _really_ reactivated*?

0

System: I work with a laptop with Windows 10 pro installed. System: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz; 16.0GB. My type of AWS account is ‘AWS Academy Learner Lab’.

Steps followed: I have installed putty for windows, version 0.78. I start the three instances that I have created (two of them with Amazon Linux 2 Kernel 5.10; and the other one, Ubuntu). I set up putty parameters. When trying to access any of the three instances created, I get the following error: “PuTTY Fatal Error. Network error: Connection timed out” I am also unable to connect using the Windows ssh command: ssh -i "xxxxxx.pem" ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com Error obtained: ssh: connect to host ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com port 22: Connection timed out I can't even ping any of the instances: ping ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com Which gives me the following error message: Pinging ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com [54.197.142.255] with 32 bytes of data: Timeout for this request. Timeout for this request. Timeout for this request. Timeout for this request.

After reading many forums (Google, StackOverflow, AWS, etc.), I’ve ruled out that it is an instance configuration problem, since in that case I would get an error of lack of permissions to access the AMI; but the point is that it is not accessible. A StackOverflow user had a similar problem (https://stackoverflow.com/questions/55212032/cant-ssh-into-aws-ec2-instance): Question: “I can't SSH into my EC2 instances - I am getting a timeout error. (…)” Auto-response: “This issue was an account issue. I had reactivated my old account but somehow it was still flagged as 'isolated' within AWS. I had access to the AWS console, but I couldn't SSH into anything. As a user, there is no way to see this yourself. I had to post on the AWS developer forums where an AWS developer was able to see that my account was 'isolated' and submitted a ticket on my behalf. I am now able to SSH into my EC2 instance with no problem.

So, it seems that the problem is due to the fact that last year I registered my AWS account (although I did not use it), and I’ve reactivated it this now; but the system is having problems to really reactivate it. How can I get my account really reactivated?

1 Answer
0

Hi there,

Terribly sorry to hear you're facing this problem. Please reach out to our Account & Billing support team, as they'd gladly look into this with you.

If you're able to login to your account, please create a support case via your Support Center.

Feel free to make use of this contact form to reach them if you face any issues creating a support case: https://support.aws.amazon.com/#/contacts/aws-account-support.

Kind regards,

— Rafeeq C.

AWS
EXPERT
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions