Comments on: Create EBS Boot AMI

By: rodney

rodney — Wed, 21 Sep 2011 01:52:19 +0000

Hi Leo,

Did you check the security groups?
If you can paste on http://pastie.org/ the console logs, that would be helpful also.

By: Leo123

Leo123 — Tue, 20 Sep 2011 17:04:02 +0000

Hi Rodney,

Thanks for the tutorial. The whole process works for me almost without errors.

However, when I try to connect the instance using the public address, I got timeout error. I also tried to ping it but failed.

Please advise. Thanks.

By: rodney

rodney — Wed, 05 Jan 2011 06:08:27 +0000

Hi Kaustubh,

Glad it work for you.

By: Kaustubh P

Kaustubh P — Tue, 04 Jan 2011 13:20:41 +0000

Nvm, I did not specify the architecture, while registering the ami. Also I cant ssh into the instance, I guess the answer lies in one of the comments.
Thanks for the awesome guide Keep up the good work!

By: Kaustubh P

Kaustubh P — Tue, 04 Jan 2011 13:05:20 +0000

I used your method to create a Debian Squeeze amd64 ami, and I can only launc a micro, small and high-cpu instance. Any idea why that could be happening?

By: Michael

Michael — Tue, 30 Nov 2010 04:12:59 +0000

@rodney: sure, the Debian image worked perfectly fine. The issue was (and still is) the kernel, as I wrote in my post on 27 September 2010, 9:32 pm (see above). The solution was to use Amazon’s default kernel version 2.6.16-xenU. With this kernel /dev/urandom works and therefore the SSH server can be started during boot process.

In short: following this guide (for Ubuntu), you can easily set up a Debian lenny image as an EBS Boot AMI, too.

By: rodney

rodney — Mon, 29 Nov 2010 10:40:24 +0000

@Bob:
We’re you able to get your AMI running with SSH?

@Michael:
Was the Debian image working good?

Cheers!

By: Michael

Michael — Thu, 18 Nov 2010 00:31:50 +0000

Hey Bob!
As rodney suggested: check security groups and the output of the boot process (system log at AWS console). Maybe you have the same issue I had (unable to start SSH server), see my post above (Michael on 20 September 2010, 9:17 pm).

By: rodney

rodney — Tue, 16 Nov 2010 07:22:09 +0000

Hmm.. A possible for Lucid AMI.

Assuming you already have the rsync’ed EBS volume, just mount the volume to any instance, edit the /etc/fstab and snapshot.

Then register it as a new AMI.

By: rodney

rodney — Tue, 16 Nov 2010 07:14:17 +0000

Bob,

I assume security groups for your instance is setup correctly i.e open port 22.

Try to check for the console output for errors. Have you specified the correct ramdisk/kernel for your new AMI?

What AMI are you trying to bundle? Distro and version.

This link can help you: http://alestic.com/2009/08/ec2-connectivity