All Documents
Current Document
Content is empty
If you don't find the content you expect, please try another search term
Found 0 result in total
Content is empty
If you don't find the content you expect, please try another search term
Last updated：2021-09-14 16:18:03
This PUT operation will create a new bucket for the user. The user needs to be a registered user and use valid Access Key ID authentication to send the request. No anonymous request will be allowed to create a user bucket. Users will be the owners of their creation bucket, with the highest permissions.
We recommend that all storage space names follow DNS naming conventions.
Note: If you use the KS3 management console, the storage name must be DNS compliant in all regions.
DNS compliant storage space names enable customers to benefit from new features and operational improvements, and support virtual managed type access to storage space. There is only one unified naming method for storage space. DNS compliant storage name rules are as follows:
The storage space name must be at least 3 characters long and cannot exceed 63 characters.
The storage space name must be a series of one or more labels, which can be connected with hyphens (-). Storage space names can contain lowercase letters, numbers, hyphens (-), and cannot contain periods (.). The storage space name must start and end with a lowercase letter or number.
The following example is a valid storage space name:
The following example is an invalid storage name:
When users use this interface to create a space, they can grant other users or groups permission to operate on the space. The following lists two authorization methods implemented by request headers.
x-kss-acl request header to specify a predefined 'ACL'.x-kss-grant-read,x-kss-grant-write and x-kss-grant-full-control request headers to specify specific access rights.PUT / HTTP/1.1
Host: {BucketName}.{endpoint}
Content-Length: {length}
Date: {date}
Authorization: {SignatureValue}
<CreateBucketConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<LocationConstraint>{BucketRegion}</LocationConstraint>
</CreateBucketConfiguration>Note:
The interface does not use request parameters.
This interface can use common request headers. For more information, please click Public request headers.
Users can specify the bucket type through the x-kss-bucket-type request header, NORMAL for non archive storage Bucket, ARCHIVE for archive storage Bucket.
| Name | Description | Necessity |
|---|---|---|
| x-kss-bucket-type | Used to specify bucket type. Type: StringDefault value: NORMAL Valid value: NORMAL ARCHIVE Constraints: None |
No |
The user can use the following header to set a preset ACL for the bucket
| Name | Description | Necessity |
|---|---|---|
| x-kss-acl | Used to set predefined permissions for an object. Type: String Default value: private Valid value: private public-read public-read-writeConstraints: None |
No |
Users can use the following headers to set detailed ACL for buckets
| Name | Description | Necessity |
|---|---|---|
| x-kss-grant-read | Grant READ permission to several users. Type: String Default: None Constraints: None |
No |
| x-kss-grant-write | Grant WRITE permission to several users. Type: String Default: None Constraints: None |
No |
| x-kss-grant-full-control | Grant FULL_CONTROL to several users. Type: String Default: None Constraints: None |
No |
The value of the above header value is a comma separated authorization list. The format of each authorization information is type = value. The current type supports ID:
For example, to grant WRITE permission to two users with ID 1234578 and 3344211: x-kss-grant-write:id="1234578",id="3344211"
| Name | Description | Necessity |
|---|---|---|
| CreateBucketConfiguration | Container for user space configuration information. Type: Container Parent node: None |
No |
| LocationConstraint | Specifies the region where the user space will be created. Type: String Valid value: BEIJING SHANGHAI HONGKONG GUANGZHOU RUSSIA SINGAPORE Default: BEIJINGParent node: CreateBucketConfiguration |
No |
This interface can use all common response headers. For more information, please click Public response headers.
The interface does not return the corresponding content.
The interface does not return any special errors.
Request example
PUT / HTTP/1.1
Host: ks3-example.ks3-cn-beijing.ksyuncs.com
Content-Length: 0
Date: Fri, 26 Dec 2014 06:30:04 GMT
Authorization: authorization stringResponse example
HTTP/1.1 200 OK
Date: Fri, 26 Dec 2014 06:30:04 GMT
Content-Length: 0
Connection: close
Server: TenginePure Mode