A bucket is a container that is used to store objects in Object Storage Service (OSS). Before you upload an object to OSS, you must create a bucket.
- When you create a bucket, you are charged only for the storage of objects in the bucket and the traffic generated when the objects are accessed. For more information, see Overview.
- The capacity of the bucket is scalable. You do not need to purchase the capacity before you use the bucket.
- You can use an Alibaba Cloud account to create up to 100 buckets in the same region.
- A bucket name must be globally unique within OSS. For more information about the naming conventions of buckets, see Bucket naming conventions.
- After a bucket is created, its name, region, storage class, and redundancy type cannot be modified.
- OSS does not impose limits on the capacity of a bucket.
- Log on to the OSS console.
- In the left-side navigation pane, click Buckets. On the Buckets page, click Create Bucket.
- In the Create Bucket panel, configure parameters described in the following table.
Parameter Required Description Bucket Name Yes Specify the name of the bucket that you want to create. The name must meet the following requirements:
- The bucket name must be globally unique in Alibaba Cloud OSS.
- The name can contain only lowercase letters, digits, and hyphens (-).
- The name must start and end with a lowercase letter or a digit.
- The name must be 3 to 63 characters in length.
Region Yes Select a region for the bucket.
To access OSS from an Elastic Compute Service (ECS) instance over an internal network, select the region in which the ECS instance is located. For more information, see OSS domain names.Note You must complete real-name registration on the Real-name Registration page before you create a bucket in a region inside the Chinese mainland.
Endpoint Yes The public endpoint of the region at which the bucket is located. Storage Class Yes Select a storage class for the bucket.
- Standard: provides highly reliable, highly available, and high-performance object storage services that can handle frequent data access. Standard storage is ideal for storing images for social networking and sharing applications and storing data for audio and video applications, large websites, and big data analysis.
- IA: provides high-durability storage services at a cost lower than Standard. Infrequent Access (IA) objects have a minimum storage period of 30 days and a minimum billable size of 64 KB. You can access IA objects in real time. However, you are charged data retrieval fees when you access IA objects. IA storage is suitable for data that is infrequently accessed, such as once or twice a month.
- Archive: provides high-durability storage services at a cost lower than Standard and IA. Archive objects have a minimum storage period of 60 days and a minimum billable size of 64 KB. You must restore an Archive object before you can access it. The restoration takes approximately 1 minute. When you restore Archive objects, you are charged data retrieval fees. Archive storage is ideal for data that needs to be stored for a long period of time, such as archival data, medical images, scientific materials, and video footage.
- Cold Archive: provides high-durability storage services at a cost lower than Standard, IA, and
Archive. Cold Archive objects have a minimum storage period of 180 days and a minimum
billable size of 64 KB. You must restore a Cold Archive object before you can access
it. The amount of time required to restore a Cold Archive object depends on the object
size and the restoration mode. When you restore Cold Archive objects, you are charged
data retrieval fees. Cold Archive storage is ideal for storing cold data over an ultra-long
period of time. Such data includes data that must be retained for an extended period
of time due to compliance requirements, raw data that is accumulated over an extended
period of time in the big data and AI fields, retained media resources in the film
and television industries, and archived videos from the online education industry.
Cold Archive storage is not supported only in the following regions: China (Nanjing - Local Region), South Korea (Seoul), and Thailand (Bangkok).
For more information about storage classes, see Overview.
OSS-HDFS No If you want to access OSS by using JindoSDK to build a data lake, enable the OSS-HDFS service. Before you enable OSS-HDFS, you must click Authorize and then follow the on-screen instructions in the panel to grant RAM users permissions to access OSS-HDFS.Notice
- OSS-HDFS is supported only in the following regions: China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Zhangjiakou), and Singapore (Singapore).To apply for a trial, contact technical support. OSS-HDFS cannot be disabled after it is enabled. Exercise caution when you enable OSS-HDFS.
- OSS-HDFS cannot be enabled for Archive or Cold Archive buckets.
ZRS No Specify the redundancy type of the bucket. Valid values:
- Activate: After this feature is enabled, OSS data is stored in zone-redundant storage (ZRS)
mode. ZRS uses the multi-zone mechanism to distribute user data across three zones
within the same region. Even if one zone becomes unavailable due to failures such
as power outages and fires, the data is still accessible.
Notice ZRS is supported only in the following regions: China (Shenzhen), China (Beijing), China (Hangzhou), China (Shanghai), China (Hong Kong), Singapore (Singapore), and Indonesia (Jakarta). You are charged extra fees for ZRS. This feature cannot be disabled after it is enabled. Exercise caution when you enable this feature.
For more information about ZRS, see ZRS.
- Not Activated: After ZRS is disabled, the redundancy type of the objects in the bucket is locally redundant storage (LRS). LRS stores the copies of each object across different devices within the same zone. This way, OSS ensures data reliability and availability even if two storage devices are damaged at the same time.
Versioning No Select whether to enable versioning. Valid values:
- Activate: If you enable versioning for a bucket, objects that are overwritten or deleted in the bucket are stored as previous versions. Versioning allows you to recover objects in a bucket to a previous version, and protects your data from being accidentally overwritten or deleted. For more information, see Overview.
- Not Activated: If you disable versioning for a bucket, objects that are overwritten or deleted in the bucket are not recovered.
ACL Yes Select the bucket ACL. Valid values:
- Private: Only the bucket owner can perform read and write operations on objects in the bucket. Other users cannot access the objects in the bucket.
- Public Read: Only the bucket owner can perform write operations on objects in the bucket. Other
users, including anonymous users, can perform only read operations on the objects
in the bucket.
Warning All users on the Internet can access the objects in the bucket. This may result in unexpected access to the data in your bucket and unexpectedly high fees. Exercise caution when you set your bucket ACL to Public Read.
- Public Read/Write: All users, including anonymous users, can perform read and write operations on the
objects in the bucket.
Warning All users on the Internet can access objects in the bucket and write data to the bucket. This may result in unexpected access to the data in your bucket and unexpectedly high fees. If a user uploads prohibited data or information, your legitimate interests and rights may be infringed. We recommend that you do not set your bucket ACL to Public Read/Write except in special cases.
Encryption Method No Select whether to enable server-side encryption for the bucket.Note Server-side encryption cannot be enabled only in the China (Nanjing - Local Region) region.
- Encryption Method: Select an encryption method for the bucket.
- None: Server-side encryption is disabled.
- OSS-Managed: Keys managed by OSS are used to encrypt objects in the bucket. OSS uses data keys to encrypt objects. In addition, OSS uses regularly rotated master keys to encrypt data keys.
- KMS: The default customer master key (CMK) stored in Key Management Service (KMS) or
the specified CMK is used to encrypt and decrypt data.
Before you use SSE-KMS, you must activate KMS. For more information, see Activate KMS.
- Encryption Algorithm: Only 256-bit Advanced Encryption Standard (AES-256) is supported.
- CMK: You can set this parameter if Encryption Method is set to KMS. You can configure the following parameters for a CMK:
- alias/acs/oss: The default CMK stored in KMS is used to encrypt different objects and decrypt the objects when the objects are downloaded.
- CMK ID: The keys generated by a specified CMK are used to encrypt different objects and the specified CMK ID is recorded in the metadata of the encrypted object. Objects are decrypted when they are downloaded by users who are granted decryption permissions. Before you specify a CMK ID, you must create a normal key or an external key in the same region as the bucket in the KMS console. For more information, see Import key material.
Real-time Log Query No If you want to query OSS access logs of the last seven days free of charge, set Real-time Log Query to Activate.
For more information about real-time log query, see Real-time log query.
If you do not need to query real-time logs, keep the default setting, which is Not Activated.
Scheduled Backup No If you want to back up your OSS data on a regular basis, set Scheduled Backup to Activate. OSS automatically creates a backup plan to back up data once a day by using Hybrid Backup Recovery (HBR). The generated backup objects are stored for one week.Notice
- The scheduled backup feature is supported only in the following regions: China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), China (Zhangjiakou), China (Hong Kong), Singapore (Singapore), Australia (Sydney), Indonesia (Jakarta), and US (Silicon Valley).
- Scheduled backup cannot be configured for buckets whose storage classes are IA, Archive or Cold Archive.
- The backup and restoration of symbolic links, Archive and Cold Archive objects, and the access control lists (ACLs) of objects are not supported.
- If HBR is not activated or HBR is not authorized to access OSS, scheduled backup plans cannot be created.
For more information, see Configure scheduled backup.
If you do not need to back up your OSS data on a regular basis, keep the default setting, which is Not Activated.
Hierarchical Namespace No If you want to rename a directory or an object, enable the hierarchical namespace feature for the bucket in which the directory or object is stored.Notice You can enable the hierarchical namespace feature for a bucket only when you create the bucket. The hierarchical namespace feature cannot be disabled after it is enabled for a bucket. After you enable this feature for a bucket, some OSS features are no longer supported for the bucket. For more information about the features that are not supported for a bucket for which the hierarchical namespace feature is enabled, see Hierarchical namespace.
- Click OK.