I'm unable to provision the current AMI, ami-735bbf17. Elasticfox gives me the error InvalidManifest, with details:

Registered machine image manifest for ami-7e5bbf17 and manifest in S3 differ. Has the image been rebundled but not re-registered?

Is the AMI being rebundled?

Comments

dreed47’s picture

I get the same error. I'd like to make use of this ami. Is there any ETA on when it will be re-registered?

annlewis’s picture

Status: Active » Closed (fixed)

Hi folks,

This AMI's manifest got corrupted last week, so we have rebundled the AMI and you can find it with ID ami-2a8a6d43. This AMI also contains a fix for the connect-ebs script issue reported in issue 354346.

We'll be removing the previous corrupted version shortly.

Ann Lewis