OK, I don't blame you, Amazon recommends this for DNS purposes anyway so using dashes instead of underscores is the way to go.
~Justin
On Apr 19, 2011, at 12:27 AM, Chris Diehl wrote:
> Hi Justin,
>
> No worries! I appreciate your reply.
>
> I have not tried it with underscores. I read somewhere that using dashes instead of underscores was the way to go. That worked for me so I didn't experiment further...
>
> Chris
>
> On Mon, Apr 18, 2011 at 9:03 PM, Justin Riley <justin.t.riley_at_gmail.com> wrote:
> 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
>
>
> <ATT00001..c>
Received on Tue Apr 19 2011 - 00:30:05 EDT
This archive was generated by
hypermail 2.3.0.