Home > ... > Amazon Elastic Compute Cloud > Amazon Machine Images (AMIs)

Ubuntu 9.04 Jaunty Server 64-Bit (Large, Extra Large Instances)

Printer Friendly

Save to del.icio.us

A clean, base install of Ubuntu 9.04 Jaunty for large and extra large instance types, built by Eric Hammond as part of the Alestic.com series [update 2009-10-11]

Submitted By:	Eric Hammond
AMI ID:	ami-eef61587
AMI Manifest:	alestic-64/ubuntu-9.04-jaunty-base-64-20091011.manifest.xml
License:	Public
Operating System:	Linux/Unix

Pick the Right Release

For a complete list of the Debian and Ubuntu AMIs available in this series including AMIs in the European EC2 region, please see the following web page:

http://alestic.com

Selecting the correct Ubuntu AMI image for your needs will improve your EC2 experience.

Description

This AMI is a clean, base install of Ubuntu 9.04 Jaunty 64-bit, built by Eric Hammond. This 64-bit AMI is for running on the 64-bit instance sizes including: m1.large, m1.xlarge, c1.xlarge . For the 32-bit sizes, please see the 32-bit Ubuntu 9.04 Jaunty server AMI

Features

Features include:

Ubuntu 9.04 Jaunty 64-bit with upgraded packages (as of 2009-10-11)

Amazon EC2 AMI tools (1.3-34544 20071010) installed and patched for Ubuntu

Uses Amazon's newer 2.6.21 kernel (2.6.21.7-2.fc8xen-ec2-v1.0)

Includes 2.6.21 kernel modules
Defaults to Ubuntu archive mirrors inside of EC2, hosted by RightScale.

Alestic PPA added to software sources so packages can be installed easily including ec2-consistent-snapshot.

runurl utility from Alestic PPA pre-installed for use in user-data scripts.

openssh-server installed

On first boot, runs instance user-data script if it starts with #!

Generate new ssh host keys on first boot and output fingerprints

ca-certificates installed to support SSL in ec2-bundle-upload

/etc/apt/sources.list for jaunty main restricted universe multiverse

/etc/event.d/tty[2-6] removed to avoid error messages in logs

Shadow passwords enabled

root password locked

ssh PasswordAuthentication disabled

10GB root (/) partition

Network: DHCP on eth0, loopback on lo, simple /etc/hosts with localhost

root ssh public key creditials retrieved from instance parameters or ephemeral store on startup (standard Amazon EC2 ssh access for public AMIs)

Added "UseDNS no" to /etc/ssh/sshd_config as recommended by http://docs.amazonwebservices.com/AWSEC2/2007-03-01/DeveloperGuide/public-ami-guidelines.html

Comment appended to /etc/motd

Locale en_US, Timezone UTC

Support

If you use or are thinking of using this AMI, please subscribe to the ec2ubuntu Google Group where you will find out about updates to the Ubuntu AMIs and tips for running Ubuntu on Amazon EC2.

To subscribe, send an email mesage to ec2ubuntu-subscribe@googlegroups.com

Support is also available through the above forum with a growing number of folks in the community using Ubuntu on EC2 (and a good core of folks willing to answer questions).

Build Process

Advanced users may consult the following page for information on how this AMI was built and to get instructions for building their own.

http://alestic.com

History

Use new 2.6.21 kernel, ramdisk, and kernel modules from Amazon (security fix)

Add Alestic PPA to apt sources on Ubuntu

Install runurl from Alestic PPA

Pin the ec2-ami-tools package version so it does not get downgraded

All packages upgraded to latest versions

ami-5b46a732 - alestic-64/ubuntu-9.04-jaunty-base-64-20090804.manifest.xml

Upgrade EC2 AMI tools to 1.3-34544

Improve security by running host key regeneration after RNG initialization.

All packages upgraded to latest versions

ami-1f749276 - alestic-64/ubuntu-9.04-jaunty-base-64-20090614.manifest.xml

Switch to Ubuntu archive mirror inside of EC2, hosted by RightScale.

Improve apt sources to failover through Ubuntu archive mirrors in multiple availability zones if one or two of them are unavailable.

Upgrade EC2 AMI tools to 1.3-31780

All packages upgraded to latest versions

ami-bc5eb9d5 - alestic-64/ubuntu-9.04-jaunty-base-64-20090423.manifest.xml

All packages upgraded to latest versions (Initial Release)

ami-ee57b087 - alestic-64/ubuntu-9.04-jaunty-base-64-20090418.manifest.xml

Disable ssh PasswordAuthentication by default to improve security

All packages upgraded to latest versions (Release Candidate)

ami-b51ff8dc - alestic-64/ubuntu-9.04-jaunty-base-64-20090329.manifest.xml

All packages upgraded to latest versions (Beta release)

ami-df36d1b6 - alestic-64/ubuntu-9.04-jaunty-base-64-20090313.manifest.xml

All packages upgraded to latest versions

ami-d7fe19be - alestic/ubuntu-9.04-jaunty-desktop-20090215.manifest.xml

All packages upgraded to latest versions

ami-0d5db964 - alestic-64/ubuntu-9.04-jaunty-base-64-20081222.manifest.xml

Original (Alpha) release

Discussion

The 5 most recent discussion messages. View full discussion.

optrip

Posts: 7
Registered: 9/15/08

Ubuntu 9.04 Jaunty Server 64-Bit (Large, Extra Large Instances)
Posted: Aug 13, 2009 6:53 PM PDT

I created an instance based on this image. When I was ready to bundle new image from the instance after install my servers, the ec2-bundle-vol give me the following message at the end:

Generating digests for each part...
Digests generated.
Unable to read instance meta-data for product-codes
Creating bundle manifest...
ec2-bundle-vol complete.

But the image manifest files were created (under /mnt). I then went ahead try to upload image use ec2-upload-bundle, the command failed immediately and give the following message:

The specified bucket is not S3 v2 safe (see S3 documentation for details):
<my_bucket_name>
Are you sure you want to continue? [y/N]y
/usr/lib/site_ruby/ec2/amitools/uploadbundle.rb:271:in `read': failed to allocate memory (NoMemoryError)
    from /usr/lib/site_ruby/ec2/amitools/uploadbundle.rb:271:in `upload_bundle'
    from /usr/lib/site_ruby/ec2/amitools/uploadbundle.rb:271:in `open'
    from /usr/lib/site_ruby/ec2/amitools/uploadbundle.rb:271:in `upload_bundle'
    from /usr/lib/site_ruby/ec2/amitools/uploadbundle.rb:323:in `main'
    from /usr/local/lib/site_ruby/1.8/ec2/amitools/tool_base.rb:201:in `run'
    from /usr/lib/site_ruby/ec2/amitools/uploadbundle.rb:342

Any idea what I might have done wrong? Oh, and when I tried to create the bundle, I specified "-r x86_64" option.

Thanks,

optrip

Posts: 7
Registered: 9/15/08

Re: Ubuntu 9.04 Jaunty Server 64-Bit (Large, Extra Large Instances)
Posted: Aug 13, 2009 6:55 PM PDT

in response to: optrip

never mind. I gave the wrong file name to upload.

ksops

Posts: 7
Registered: 10/13/09

Re: Ubuntu 9.04 Jaunty Server 64-Bit (Large, Extra Large Instances)
Posted: Oct 13, 2009 10:43 AM PDT

in response to: optrip

We've used ami-5b46a732 as our base AMI. We added puppet client, Splunkd, and configured pam.d for our environment to the base image and rebundled into an AMI for our own purposes. The new instances are planned to be part of a cluster of existing servers running Ubunut 8.04. The existing servers have been running for a while with similar configurations, except they do not have puppet and Splunkd installed. The AMI that we rebundled seems to be having intermittent problems on start-up. On an experiment, we spun up 5 instances using our rebundled AMI. Two of the instances came up fine, and we were able to login. The remaining three came up, but we're not able to login. I diff'ed the console output of a failed instanced and a working instance, and the failed instance stopped at the point where dbus is starting up. The last thing I see in the console output of the failed instanced is "Starting kernel log daemon", afterwhich, dbus is supposed to start up, then sshd. There are no other errors.

This rebundled AMI is probably about two weeks old, and I noticed today that you've put a new AMI up with upgraded packages. Is there any reason for the upgrade, in relation to my problem with dbus? Is dbus really the source of the instances failing to start up properly?

Reviews

Write a Review


Be the first to review this.

Welcome, Guest