Bucket is the carrier of objects, which can be understood as the "container" for storing objects, and this "container" has no upper limit of capacity. Objects are stored in buckets in a flat structure with no concept of folders and directories. You can choose to store objects in one or multiple buckets.
A bucket can contain any number of objects, but one root account can create only up to 200 buckets.
A bucket name consists of BucketName and APPID connected by a hyphen (-). For example, in the bucket name
examplebucket-1250000000, examplebucket is the user-defined string, and 1250000000 is the system-generated numeric string (APPID). In API and SDK samples, the naming format of a bucket is
The following are examples of valid bucket names:
Region is where a COS IDC is located. COS allows you to create buckets in different regions. You can select the region closest to the location where your business is deployed for the buckets so as to reduce latency and cost and meet the compliance requirements.
For example, if your business is distributed in South China, creating buckets in the Guangzhou region can accelerate object uploads and downloads. For more information on regions, please see Regions and Access Endpoints.
A region must be specified when a bucket is created and cannot be modified once specified. All objects in the bucket are stored in the IDC in the region. You cannot set regions for objects.
A bucket provides two types of permissions by default: public and user.
Public permissions include "Private Read/Write", "Public Read/Private Write", and "Public Read/Write". You can modify bucket access permissions in Permission Management of the bucket in the COS console. For more information, please see Basic Concepts of Access Control.
The root account has all the permissions of the bucket by default (i.e., full access). In COS, sub-accounts can be added to read/write data, read/write permissions, and have the full access.
You can manage buckets and configure attributes of buckets in various methods such as the Tencent Cloud console, tools, APIs, and SDKs. For example, you can set a bucket for hosting a static website or set access permission to a bucket. The following documents describe how to configure some features. For more information on bucket configuration, please see Bucket Overview.