New ask Hacker News story: GCP Bucket Name Restrictions
GCP Bucket Name Restrictions
5 by eeegnu | 1 comments on Hacker News.
I was creating a bucket on GCP and noticed what I thought was an odd restriction[0]: > Bucket names cannot begin with the "goog" prefix. > Bucket names cannot contain "google" or close misspellings, such as "g00gle". I'm mostly just curious about the motivation behind these restrictions. My guess is that it's to avoid buckets that make it seem like they're owned by google, but there doesn't seem to be equivalent restrictions on azure[1] or aws[2] (they do disallow the prefix "xn--" and the suffix "-s3alias", but these seem functional.) Is there some other reasoning? [0] https://ift.tt/3yDAiYb [1] https://ift.tt/3GYAROW [2] https://ift.tt/3E96Iuw
5 by eeegnu | 1 comments on Hacker News.
I was creating a bucket on GCP and noticed what I thought was an odd restriction[0]: > Bucket names cannot begin with the "goog" prefix. > Bucket names cannot contain "google" or close misspellings, such as "g00gle". I'm mostly just curious about the motivation behind these restrictions. My guess is that it's to avoid buckets that make it seem like they're owned by google, but there doesn't seem to be equivalent restrictions on azure[1] or aws[2] (they do disallow the prefix "xn--" and the suffix "-s3alias", but these seem functional.) Is there some other reasoning? [0] https://ift.tt/3yDAiYb [1] https://ift.tt/3GYAROW [2] https://ift.tt/3E96Iuw
Comments
Post a Comment