Re: Saving a custom AMI

From: Justin Riley <no email>
Date: Tue, 19 Apr 2011 00:03:38 -0400

Hi Chris,

I apologize for the delay. You're right that capital letters are an issue. StarCluster attempts to validate the bucket name based on the rules defined here:

http://docs.amazonwebservices.com/AmazonS3/latest/dev/index.html?BucketRestrictions.html

This states that bucket names should consist of only "lowercase letters, numbers, periods (.), underscores (_), and dashes (-)". That being said Amazon also recommends for DNS purposes that the name does not contain underscores. However, looking at the code I believe StarCluster will still allow you to create buckets with underscores in the name assuming it's not the first character. Have you tried using the underscores with only lower-case letters?

~Justin


On Apr 17, 2011, at 7:32 PM, Chris Diehl wrote:

> 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
>
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
Received on Tue Apr 19 2011 - 00:03:42 EDT