Which of the following is a valid, available S3 general purpose bucket name, assuming it has not already been taken by another AWS account?
- my-company-logs-2026
- logs..backup
- 192.168.10.5
- My-Company-Logs
Why A? And why not the others?
Correct answer: A. my-company-logs-2026
AWS's general purpose bucket naming rules require names to be 3 to 63 characters long, to consist only of lowercase letters, numbers, periods, and hyphens, to begin and end with a letter or number, to avoid two adjacent periods, and to avoid the format of an IP address; names must also be unique across every AWS account within the same partition, since general purpose buckets share a single global namespace. A name using only lowercase letters, numbers, and hyphens that begins and ends alphanumerically, such as one appending a year, satisfies every one of these rules and is a valid candidate name if not already taken. The option containing uppercase letters and mixed case is invalid because bucket names must be entirely lowercase; S3 will reject it outright regardless of availability. The option with two consecutive periods is explicitly disallowed, since bucket names must not contain two adjacent periods. The option formatted as four dot-separated numeric octets is explicitly disallowed because it matches the format of an IP address, which S3's naming rules specifically forbid regardless of whether such a name is otherwise free.
Source: AWS S3 documentation: General purpose bucket naming rules — length, allowed characters, IP-address format prohibition, and global uniqueness