We have a policy of naming S3 buckets to correspond with the appropriate domain name, e.g. www.sitename.com. When I attempt to configure the AmazonBlobProvider to make use of a bucket with that convention, it throws an error:
The provided bucket name does not conform with AWS requirements. Bucket names must be at least 3 and no more than 63 characters long and only lower case characters, numbers and dashes (-) are allowed. In addition the name cannot begin or end with a dash.
From what I can tell, this simply isn't true. Both dots and uppercase letters can be used in bucket names in the Amazon web console, with no ill effects. Perhaps the restrictions on bucket name have changed/been relaxed over time?
In any case, is there a chance this will be fixed in a future version of the AmazonBlobProvider?
We have a policy of naming S3 buckets to correspond with the appropriate domain name, e.g. www.sitename.com. When I attempt to configure the AmazonBlobProvider to make use of a bucket with that convention, it throws an error:
The provided bucket name does not conform with AWS requirements. Bucket names must be at least 3 and no more than 63 characters long and only lower case characters, numbers and dashes (-) are allowed. In addition the name cannot begin or end with a dash.
From what I can tell, this simply isn't true. Both dots and uppercase letters can be used in bucket names in the Amazon web console, with no ill effects. Perhaps the restrictions on bucket name have changed/been relaxed over time?
In any case, is there a chance this will be fixed in a future version of the AmazonBlobProvider?
Thanks!