[ec2-beta] ami-1cc0e868 in EU-West seems corrupt

Eric Hammond ehammond at thinksome.com
Mon Apr 27 19:32:34 BST 2009


Based on 1.5 years of experience releasing over 400 public AMIs, I came
to the conclusion that it's best not to list AMI ids in static documents
like emails.

Instead I always direct folks to find the latest AMIs at particular web
page which can be updated easily with the most recent and most correct
AMI ids.

Once exception is if a particular bug is being tracked down, in which
case it's nice to know the specific AMI id involved.

Eric Hammond
ehammond at thinksome.com

Chuck Short wrote:
> HI Pedro,
> The image was corrupt for both intrepid i386 and amd64 was corrupt. I 
> have regenerated the AMI id please use the updated:
> canonical-cloud-eu/ubuntu-intrepid-20090422-i386    ami-80c0e8f4
> canonical-cloud-eu/ubuntu-intrepid-20090422-amd64 ami-84c0e8f0
> The documentation on the wiki has already been updated to reflect this 
> change.
> Sorry about this, I will be investigating why this happened.
> Regards
> chuck
> Pedro Sanchez Pernia wrote:
>> Hello there,
>> I can't launch an instance with the new AMI ami-1cc0e868 i386 
>> Intrepid, once selected this is error:
>> "The requested instance type's architecture (i386) does not match the 
>> architecture in the manifest for aki-40c0e834 (x86_64)"
>> Txs Pedro

More information about the Ec2-beta mailing list