Cloud & Platform

Bucket Name Validator

Checks names against the provider rules before the create call does it for you.

Loading the tool…

Processing happens locally in your browser. What you paste or load is processed by this page and is not uploaded to a server. Nothing is stored unless you use a control that says it stores something, and you can clear anything this site has kept from the privacy page.

How to use this tool

  1. Paste the names you are considering, one per line.
  2. Pick the provider. The rules genuinely differ — Azure allows no dots at all.
  3. Select Validate names.
  4. Settle the name before you create anything. A bucket cannot be renamed, only copied and deleted.

What bucket name validator does

Bucket naming rules are stricter than they look and the consequences are permanent. A bucket name is global, it is part of a DNS name, and it cannot be renamed — only copied to a new bucket and deleted, which for a large dataset is a project rather than a fix.

The rule that catches people is the dot. A name with a dot in it is legal on S3 and it will create successfully, but virtual-hosted HTTPS access to it breaks, because the wildcard certificate does not cover a further label — so the bucket works from the CLI and fails from a browser. That and the reserved prefixes and suffixes, the IP-address form, the length bounds and the Azure ban on dots and consecutive hyphens are all checked here, per provider.

Frequently asked questions

A dot is legal and the bucket will create, but virtual-hosted HTTPS access to it breaks: the wildcard certificate covers one label under s3.amazonaws.com, and a dot in your name adds another. The result is a bucket that works from the CLI and fails in a browser with a certificate error, which is a confusing thing to debug and impossible to fix without copying the data to a new name.

No, on any of the three providers. The only route is to create a bucket with the new name, copy everything across, repoint every consumer and delete the old one — which for a large dataset means an egress bill, a migration window and a period where both exist. This is why the naming decision deserves five minutes now.

On S3 and Google Cloud Storage the namespace is shared across every customer, so a name someone else took is unavailable to you, and a create call can fail simply because the name is popular. Azure is different: container names only have to be unique within a storage account, and the account name is the globally unique part.

Usually yes, along with something you own such as an organisation prefix, because the namespace is global and short generic names are long gone. A pattern like org-domain-purpose-environment gives you a name that is available, sortable in a console listing and immediately readable in a policy — which matters more than brevity for a name nobody types by hand.