Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have created a private AMI from the image I had running from my other EC2 instance. When I create the instance using that private AMI, it boots up fine but when I restart the newly created instance, it stops responding. I can't even connect through SSH into it.

How can I see what is going wrong?

share|improve this question

migrated from Jun 19 '11 at 21:20

This question came from our site for professional and enthusiast programmers.

Is your EC2 instance connected to EBS for persistence? If it is not it can not be stopped and started. See Elastic Block Store section on this page: – Terrell Plotzki Jun 19 '11 at 17:07
Root device on the AWS console shows as EBS – ed1t Jun 19 '11 at 17:09
Were you able to ping the server? Also, share the kind of error you get & the way your created your AMI? Confirm when you created your EBS AMI should have content in /etc/fstab. – RakeshS Jun 20 '11 at 5:14

You can get the system log, which will be helpful for knowing whats wrong.

enter image description here

Also make sure that the Security rules allows you to connect through ssh .

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.