Connection to EC2 (t2.micro) Works Temporarily, Then Permanently Timesout

0

I've set up a very basic Ubuntu 16.04 t2.micro EC2 instance in the ap-southeast-1 region. I am able to connect to it via SSH between the time that the instance is started and just before the status changes to "2/2 checks passed." Afterwards, anytime I try to connect to the instance via SSH, the error message "ssh: connect to host xxx.compute-1.amazonaws.com port 22: Operation timed out" is printed.

If I stop the instance, then start it back up, I am able to temporarily connect to the machine via SSH (as soon as the instance appears as "running"). But once the status changes to "2/2 checks passed," I am no longer able to connect to the machine via SSH. This only happens to any instance I create in the us-east-1 region.

I've checked all the documentation, and every security group inbound setting has port 22 exposed to 0.0.0.0/0, and all VPC gateway/subnet/routes/ACL settings look perfect.

If I set up the same type of instance in any other region, I do not encounter this issue whatsoever.

I found a thread mentioning the same issue, almost verbatim https://forums.aws.amazon.com/thread.jspa?threadID=298751&tstart=25, and staff member who replied to the thread mentions that the cause is an "administrative issue on the account."

Is this a known issue? Could it be an issue with my account? Is the cause mentioned in the thread post the same for my account?

질문됨 5년 전222회 조회
1개 답변
0
수락된 답변

Hello,

I am sorry to hear about the issue that you are experiencing. Yes, I would like to confirm that the reason why you are unable to connect to your instance is caused by an administrative issue with your account. I have created an internal ticket for our service team to remedy this situation. I will inform you as soon as I receive an update.

Regards,
awstomas

AWS
답변함 5년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠