Re: Saving a custom AMI

From: Chris Diehl <no email>
Date: Sun, 17 Apr 2011 16:32:39 -0700

Hi All,

So I discovered the problem. It turns out S3 folder names that have capital
letters or underscores will cause this problem. Using a folder name with all
lowercase letters and dashes worked just fine.

Chris

On Fri, Apr 15, 2011 at 9:13 AM, Chris Diehl <diehl_at_alumni.cmu.edu> wrote:

> Hi All,
>
> I've been trying to save a custom AMI this morning with StarCluster and I
> keep getting the following error.
>
> $ starcluster createimage i-8a84f2e5 custom_starcluster_image AMI_Instances
> StarCluster - (http://web.mit.edu/starcluster)
> Software Tools for Academics and Researchers (STAR)
> Please submit bug reports to starcluster_at_mit.edu
>
> cli.py:1079 - ERROR - bucket name AMI_Instances is not valid
>
> I created an AMI_Instances bucket on S3 and *thought* I had configured
> permissions properly. But with everything I've tried, I come up with the
> same result.
>
> Any thoughts on what I should check would be greatly appreciated!
>
> Chris
>
Received on Sun Apr 17 2011 - 19:33:00 EDT