By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

EC2 Instance No Response after Force Stop

0

EC2 Instance No Response after Force Stop

Hi, my instance id is i-05a6f6d14e4f20d8e. My instance was stuck in a stopping state, thus I tried force stop on it. Unfortunately, after it has been stopped, I could not connect to the instance using cygwin or FileZilla. Following is my timed out message: "ssh: connect to host ec2---*-.us-west-1.compute.amazonaws.com port **: Connection timed out" Can someone take a look at this please?

Topics
Compute
Tags
Amazon EC2
Language
English
AWS-User-2646245
asked 3 years ago404 views
1 Answer
0

If you stopped the EC2 instance, it will no longer be connectable until you start it again.

If your instance is stuck in a stopping state for a long period of time, there could be an issue and you should submit a ticket to have this looked at.

profile pictureAWS
EXPERT
Chris_G
answered 3 years ago
  • Brettski-AWS EXPERT
    3 years ago

    Also note that if your instance was assigned a Public IP (not an Elastic IP) then it will receive a new Public IP when it is restarted which will require you to use a different DNS name to connect to it.

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

Relevant content