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

We have a group of instances in an Amazon VPC we use for our live environment.

We have a big release to do and want to test that the deployment will run smoothly.

I have created a second VPC, created instances of the same size on the same private ips and then removed their original volumes and attached new volumes that were created from snapshots of the live environment.

Unfortunately none of the instance will allow me to connect. They start running fine, but I don't get any system logs appear and can't connect.

The only thing I can think of is that the new instance was created from a new AMI as the old one is deprecated due to new security fixes.

Is this a problem? If so can I fix it in any way? And if this isn't a problem, does anyone have any ideas how I can fix it?

share|improve this question
up vote 1 down vote accepted

You may be better off creating your own AMIs from those snapshots and launching the new instances from those AMIs.

I've had the same problem when trying to swap root volumes in the past.

share|improve this answer
This is exactly what I was trying when you sent this reply and it worked! Thanks :) I then retested the old snapshots and they now work on the instances based on the AMIs, so for all future tests I can snapshot and attach new volumes, without having to AMI them again, which seems to put the server into a busy state while it is done! – Remmus Nov 24 '11 at 17:58

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.