Unable to connect to the ec2 instance that had already been worked before, the abnormal behavior only the CPU utilization was very high, due to the docker image build ![Enter image description here](/media/postImages/original/IMtD5Kb0vcQSSLQmpFx088hg) I have checked the following: security group SSH port subnet routing table firewall is disabled

Unable to connect to EC2 instance

Unable to connect to the ec2 instance that had already been worked before, the abnormal behavior only the CPU utilization was very high, due to the docker image build Enter image description here I have checked the following: security group SSH port subnet routing table firewall is disabled

주제

컴퓨팅

태그

아마존 EC2 네트워크 보안

언어

English

Karim

질문됨 5달 전174회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

Hello.

If the EC2 security group or network ACL is not the cause, the EC2 CPU load may be the problem.
Please restart EC2 and check if you can SSH.
If you check the EC2 system log, you will probably see some errors.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-console.html#instance-console-console-output

전문가

Riku_Kobayashi

답변함 5달 전

Karim
5달 전
I have restart it, facing the same issue, the only way to connect to it through the serial connection, inside the machine I'm trying to ping any server it's fully isolated

Unable to connect to EC2 instance

관련 콘텐츠