Creating a Bucket
This section describes how to create a bucket on OBS Console. A bucket is a container that stores objects in OBS. Before you can store data in OBS, you must create a bucket.
An account (including all IAM users under this account) can create a maximum of 100 buckets and parallel file systems. You can use the fine-grained access control of OBS to properly plan and use buckets. For example, you can create folders in a bucket based on object prefixes and use fine-grained permission control to isolate permissions between departments.
Procedure
- In the navigation pane of OBS Console, choose Object Storage.
- In the upper right corner, click Create Bucket. The Create Bucket page is displayed. For details, see Figure 1.
- Configure bucket parameters.
Table 1 Bucket parameters Parameter
Description
Region
Geographic area where a bucket resides. For low latency and faster access, select the region nearest to you. Once the bucket is created, its region cannot be changed.
Bucket Name
Name of the bucket. A bucket name must be unique across all accounts and regions. Once a bucket is created, its name cannot be changed.
According to the globally applied DNS naming rules, an OBS bucket name:
- Must be unique across all accounts and regions. The name of a deleted bucket can be reused for another bucket or a parallel file system at least 30 minutes after the deletion.
- Must be 3 to 63 characters long. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed.
- Cannot start or end with a period (.) or hyphen (-), and cannot contain two consecutive periods (..) or contain a period (.) and a hyphen (-) adjacent to each other.
- Cannot be formatted as an IP address.
NOTE:
When you access OBS through HTTPS using virtual hosted-style URLs, if the bucket name contains a period (.), the certificate verification will fail. To work around this issue, you are advised not to use periods (.) in bucket names.
Default Storage Class
Storage classes of a bucket. Different storage classes meet different requirements for storage performance and costs.
- The Standard storage class is for storing a large number of hot files or small files that are frequently accessed (multiple times per month on average) and require quick retrieval.
- The Infrequent Access storage class is for storing data that is less frequently accessed (less than 12 times per year on average) and requires quick retrieval.
- The Archive storage class is for archiving data that is rarely accessed (once a year on average) and has no requirements for quick retrieval.
For details, see Storage Classes.
Bucket Policy
Controls read and write permissions for buckets.
- Private: No access beyond the bucket ACL settings is granted.
- Public Read: Anyone can read objects in the bucket.
- Public Read and Write: Anyone can read, write, or delete objects in the bucket.
Server-Side Encryption
After you enable server-side encryption for the bucket, any object you upload to it will inherit the KMS encryption from the bucket by default.
After you enable server-side encryption for the bucket, any object you upload to it will be encrypted with the obs/default key by default. You can also click Create KMS Key to create a key on the DEW console. Then select the created key on OBS Console for encryption.
Direct Reading
Direct reading allows you to directly download objects from the Archive storage class without restoring them first. Direct reading is a billable function. For details, see Product Pricing Details.
No matter which default storage class you select, you can enable direct reading for your bucket. For example, if you select the Standard storage class and enable direct reading for your bucket, you can directly download objects stored in the Archive storage class from your bucket.
Tags
Optional. Tags are used to identify and classify buckets in OBS. Each tag is represented by a key-value pair.
For more information, see Tags.
- Click Create Now.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.