0e594899_ublic_cloud___yet_another_blog__Feature
The bucket name you choose must be unique across all existing bucket names in Amazon S3 Bucket names must comply with the following requirements: Can contain lowercase letters, numbers, periods (.), underscores (_), and dashes (-) Must start with a number or letter Must be between 3 and 255 characters long Must not be formatted as an IP address (e.g., 30%.255.5.4) To conform with DNS requirements, AWS recommend following these additional guidelines when creating buckets: Bucket names should not contain underscores (_) Bucket names should be between 3 and 63 characters long Bucket names should not end with a dash Bucket names cannot contain two, adjacent periods Bucket names cannot contain dashes next to periods [Azure Blob Storage] The container name must be unique within a storage account The container name must be a valid DNS name, conforming to the following naming rules: Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character. Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted in container names. All letters in a container name must be lowercase. Container names must be from 3 through 63 characters long. Avoid blob names that end with a dot (.), a forward slash (/), or a sequence or combination of the two. [GCP Cloud Storage] Every bucket must have a unique name across the entire Google Cloud Storage namespace Bucket names must contain only lowercase letters, numbers, dashes (-), underscores (_), and dots (.). Names containing dots require verification Bucket names must start and end with a number or letter Bucket names must contain 3 to 63 characters. Names containing dots can contain up to 222 characters, but each dot-separated component can be no longer than 63 characters Bucket names cannot be represented as an IP address in dotted-decimal notation (for example, 192.168.5.4) Bucket names cannot begin with the “goog” prefix Bucket names cannot contain “google” or close misspellings of “google” If creating a bucket with a custom domain ( e.g ending .com, .co.uk etc) then Domain name verification will be part of the process For DNS compliance and future compatibility, you should not use underscores (_) or have a period adjacent to another period or dash [Feature] 
Bucket naming
Devops and the Public cloud | yet another blog
Feature