Hi, I had huge problems using the http://alestic.com/
images, and migrating the US images to the west.
I might not understand all the problems I ran into, but I think I do.
Since you people are so nice to try to bundle up my favorite releases,
I'm giving back with my information. I don't promise all of it's
The problems I had fell into three categories (one not the fault of
anyone on this list)
1) the API tools and AMI tools bundled with those images are several
versions behind, and don't support --location us-west-1 .
Perniciously, the tools don't have clear errors when there's a data
center they don't support (try migrating or registering in a location
like 'foobie' and see the inscrutable errors). And, the version of the
tools in the Ubuntu repository is too far behind to pick up the us-
west-1 changes. The hand-install route is a little painful, with
Amazon's README instructions slightly off the mark. Once I had these
tools to current, life was exceptionally good.
2) There is a massive lack of documentation regarding the ec2-migrate-
bundle and AKIs. When migrating a bundle, you need to choose the
correct AKI in the new location, but getting a list of AKIs is like
pulling hen's teeth (fiddly and error prone). Amazon's method requires
getting a list of AKIs through an ec3- API call, but that list doesn't
give any guidance between the three recent version 64-bit fedora-core
derived AKIs - and which AKIs require ARI, and which. There's a note
on one of the EC2 pages about being careful your AKI matches your boot
image, and how you should read the release notes for a given AKI, but
there's no source of these release notes from Amazon. If Amazon is
going to release AKIs to the community, there should be a location
where you can list the AKIs and get somewhat detailed release notes
(known issues like security holes and driver support), *or* people
providing community AMIs need to specify the AKIs the AMI is intended
to work with - because I need to specify AKI numbers when doing the
3) The s3cmd tools I've been using (python version) don't support
bucket creation in the us-west-1 location. I suspect this is the same
FAIL as the ec2- API and AMI tools not understanding a new location
(wouldn't everyone just pass through to the REST calls?). I'm not sure
the Ruby s3cmd calls Amazon prefers is any better, perhaps it is. I
eventually got a proper us-west-1 bucket by doing a migrate into an
empty bucket, so I can now use that bucket for everything. Python
s3cmd at least will 'info' and tell me where my bucket is.
I'm not asking for fixes, just telling you my experiences. As EC2 will
likely be adding more datacenters every year (multiple? Singapore
+ ???), we're all getting to understand how these tools need some
better work. The biggest hang-up from my perspective is tools that
don't require revs when new data centers come online (maybe we're
already there; we won't know until Singapore comes online and the
tools either work or don't).
> Hi there
> first of all "Hi" to everybody, I'm new to this forum and new to AWS in
> general (yeah, yet another newbie).
> I would like to set up EC2 instances with Ubuntu images in region
> "US-WEST-1" but when I view all available AMIs for this region with
> ubuntu as a platform I see none. I am able to play with instances in
> "US-EAST-1" though.
> Does this mean the Ubuntu AMIs have simply not been uploaded to region
> US-WEST-1 yet?
> Ah yeah, and I will be asking some questions about setting up a MySQL
> server with Ubuntu and EBS some time soon too; just in case you already
> can recommend a good image to start with. I thought maybe Ubuntu 9.04
> Jaunty might make sense as Eric Hammond created a nice tutorial for this