Update CreateBucketCommand documentation to clarify client usage

[willsp]

Describe the issue

Describe the documentation update
The documentation for the CreateBucketCommand in the S3 JavaScript client should be updated to include important information about client usage.

Proposed changes

1. Add a note emphasizing that using regional clients is preferred over the global client when creating buckets.
2. Include a warning that creating buckets in opt-in regions using the global client is not supported.

Suggested location for the update
These additions should be placed in a prominent position within the CreateBucketCommand documentation, preferably near the top of the page or in a "Best Practices" or "Important Notes" section.

Rationale
This information is crucial for developers to understand the best practices and limitations when using the CreateBucketCommand, especially in different AWS regions.

Thank you for considering this documentation update.

Links

https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/s3/command/CreateBucketCommand/

[zshzbh]

Hey @willsp ,

You can find the global client here - https://github.com/aws/aws-sdk-js-v3/blob/main/UPGRADING.md#s3-global-client-region-redirects

[zshzbh]

I will create a ticket to the service team to ask them update the doc.

Thanks!

[zshzbh]

Since this thread is public, I also want to clarify -

Amazon S3 creates buckets in a Region that you specify. Amazon S3 supports global buckets, which means that each bucket name must be unique across all AWS accounts in all the AWS Regions within a partition. A partition is a grouping of Regions. AWS currently has three partitions: aws (Standard Regions), aws-cn (China Regions), and aws-us-gov (AWS GovCloud (US)).

After a bucket is created, the name of that bucket cannot be used by another AWS account in the same partition until the bucket is deleted.Ref

So you can only create a s3 bucket with a specific region instead of a global s3 bucket.

The global client mentioned in this issue referred to this part

[aBurmeseDev]

Since there's no action item for SDK team and this repo is dedicated for JS SDK related issues, we're going to close this now. I'll keep it posted here when service team responds or feel free to reach out to service team directly via AWS Support.