AWS : S3 : Bucket Naming Convention

Bucket Name Rules

1.    Can contain lowercase letters , number and periods and hyphens(-) ( not capital letters ??check?? )

2.    Must not contain underscore (_) (use - instead)

3.    Must start with number or letter

4.    Must not end with hyphen (-) Nor with dot(.)

5.    Must be between 3 to 63 characters long

6.    Must not be formatted as IP address

7.    Cannot contain two adjacent periods

8.    Cannot contain dashes next to period. (ex : my-.bucket.com is invalid)

The following examples are valid bucket names:

●     myawsbucket

●     my.aws.bucket

●     myawsbucket.1

The following examples are invalid bucket names:

• .myawsbucketBucket name cannot start with a period (.).
• my..examplebucketThere can be only one period between labels. 
•  myawsbucket.Bucket name cannot end with a period (.). 

Challenges with Non–DNS-Compliant Bucket Names

The US East (N. Virginia) region currently allows more relaxed standards for bucket naming, which can result in a bucket name that is not DNS-compliant. For example,  MyAWSBucket is a valid bucket name, even though it contains uppercase letters. If you try to access this bucket by using a virtual-hosted–style request (http://MyAWSBucket.s3.amazonaws.com/yourobject), the URL resolves to the bucket myawsbucket and not the bucket  MyAWSBucket. In response, Amazon S3 will return a "bucket not found" error.

To avoid this problem, we recommend as a best practice that you always use DNS-compliant bucket names regardless of the region in which you create the bucket.