0
votes

I have setup create an AMI from a EBS-backed Official Ubuntu Image to running a web server.

I have follow the guide below carefully from the link below.

http://www.elastician.com/2009/12/creating-ebs-backed-ami-from-s3-backed.html

http://jimmyg.org/blog/2007/amazon-ec2-for-people-who-prefer-debian-and-python-over-fedora-and-java.html

After successfully of registering the AMI, an AMI identifier will be shown.

I tried start the new AMI, but all the setting (Apache, Django, Data, etc) are not in the new AMI itself. Anyone know how can I creating a persistent AMI?

Thanks!

2
Did you install these before registering the new AMI? I'm not clear on what you're expecting. Fortunately, as it is EBS backed, you can install what you need and simply stop the instance, rather than terminate it. Still, if you didn't install the software before registering the AMI, then that software won't be in the AMI and won't be there when you launch an instance. - Iterator
Yeah, I did the install before I register the new AMI. Still the data is loss when I start the new AMI - Ezylryb

2 Answers

0
votes

You can do it from EC2-API. It's possible via AWS Management Console, specially when you have EBS backed image.

  1. Log into AWS Management console > EC2 tab > Instances
  2. select the instance that you have all your software installed.
  3. click Instance Action, select Create Image (EBS AMI).

wait, and see the new AMI is ready under AMI menu. You can instatiate it, it will have your software.

Beware: certain directories like /tmp, /mnt and some more are not included in AMI.

0
votes

Might be a weak answer but I just used the AWS web interface at http://aws.amazon.com/console/. I create EBS-backed AMI's all the time and new instances from them, containing all the software I installed from the cloned instance with no problem.

Instance storage is a little more tricky, but it looks like you're using EBS anyways.