-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The bucket naming rules conflict when docking with minio #4143
Comments
do you know the doc for s3 bucket naming convention? |
Of course, is there anything wrong with my expression? Can you point out the mistakes |
I do not see any user mistake here. Just want to know the "official" s3 bucket naming convention. |
The Amazon S3 bucket that you use to store CloudTrail log files must have a name that conforms with naming requirements for non-US Standard regions. Amazon S3 defines a bucket name as a series of one or more labels, separated by periods, that adhere to the following rules: The bucket name can be between 3 and 63 characters long, and can contain only lower-case characters, numbers, periods, and dashes. Each label in the bucket name must start with a lowercase letter or number. The bucket name cannot contain underscores, end with a dash, have consecutive periods, or use dashes adjacent to periods. The bucket name cannot be formatted as an IP address (198.51.100.24). information sources:https://docs.amazonaws.cn/en_us/awscloudtrail/latest/userguide/cloudtrail-s3-bucket-naming-requirements.html |
working on a pr to fix this issue https://github.com/seaweedfs/seaweedfs/pull/4189/files |
When uploading buckets through java minio, minio prompts me that the buckets to be transferred do not conform to the naming rules of S3 buckets
My bucket name is 10000_ test
However, it cannot be used in the S3 naming specification_ To name it. aws-cli passed the name, but the seaweedfs server did not verify the bucket name
So I suggest checking the incoming bucket name on the seeweedfs server to ensure that the system has stronger compatibility
The text was updated successfully, but these errors were encountered: