Overview
A bucket can be understood as a container for storing objects and serves as a virtual partition for organizing data. A single bucket can hold an unlimited number of objects. Each bucket has explicit regional attributes, with one bucket corresponding to one region. All data within a bucket is stored in Tencent Cloud-managed data centers within that region. Every bucket has a globally unique name and provides a distinct internet address (access domain name) for accessing objects. Users can view or download objects via the access domain name.
Preparations
2. Has operational permissions for COS. The primary account has all permissions by default, and sub-accounts need to authorize COS service permissions on demand through CAM. Creating a bucket
If your account has no bucket, you cannot upload files to the Tencent Cloud LighthouseCOS(LHCOS) service. You can create an LHCOS bucket via the console to store files.
Note:
1. LHCOS bucket names have global uniqueness within the account, and users cannot assign identical names to the same bucket (including LHCOS buckets and COS buckets).
2. LHCOS is subject to quantity limits on buckets. A single primary account can create up to 200 buckets (including LHCOS buckets and COS buckets), each with a unique name.
Operation Steps
2. On the bucket card page, click Create Bucket.
3. In the Create Bucket dialog box that is displayed, configure the following information:
Region: It is recommended to select the same region as the Lighthouse instance you need to use to avoid cross-region data transfer.
Bucket name: Once created, the name cannot be modified and is globally unique.
4. After confirming the information, click Create to complete the bucket creation.
Empty the bucket
You can clear all files and file fragments in the bucket via the console.
Note:
1. Emptying the bucket will delete all files and file fragments within it. Once deleted, the data cannot be recovered or accessed. Please carefully evaluate before emptying.
2. If your bucket contains a large amount of data, emptying it via the console may be slow or fail due to network issues. Files already deleted cannot be recovered. You may retry the bucket emptying operation.
Operation Steps
2. On the bucket card page, select the specified bucket, then choose More > Empty Data on the far right.
3. In the Empty Bucket dialog box that is displayed, click OK to proceed.
Deleting a bucket
You can delete the specified bucket via the console. After deletion, the associated configurations and files within the bucket cannot be recovered. Please proceed with caution.
Note:
Before the bucket deletion operation is performed, all files and associated configurations within the bucket must be emptied.
Operation Steps
2. On the bucket card page, select the specified bucket, then choose More > Delete on the far right.
3. In the Delete Bucket dialog box that is displayed, click OK to proceed.
Set bucket access permissions
You can set or modify the bucket's access permissions via the console. COS supports two types of permissions:
Public permissions: Private read-write, Public read and private write, and Public read-write.
Private read-write: Only the creator of the bucket and authorized accounts have read-write permission for the objects in the bucket. Other individuals do not have these permissions. The default bucket access permission is private read-write, which is recommended.
Public read and private write: Anyone (including anonymous visitors) has read permission for objects in the bucket, but only the bucket creator and authorized accounts have write permission for objects in the bucket.
Public read-write: Anyone (including anonymous visitors) has read-write permissions for objects in the bucket. This option is not recommended.
User permissions: The primary account has all permissions (that is, full control) for the bucket by default. Additionally, COS supports adding sub-accounts with permissions such as data read, data write, permission read (granting users access to read "bucket access permissions"), permission write (granting users access to modify "bucket access permissions"), and even the highest permission level of full control.
Data read: Has read access to files and file metadata (including file permissions, types, and so on) within the bucket.
Data write: Has the permission to write, copy, and delete files within the bucket.
Permission read: Grants read access to "bucket permissions".
Permission write: Grants permission to modify "bucket permissions".
Full control: Has read and modify permissions for files and file metadata (including file permissions, types, and so on) within the bucket.
Note:
When the bucket is set to private read-write or has granted permissions to specified accounts, requests for objects require including a signature for authentication. For details about signatures, see Request Signature. When a bucket is set to public read and private write or public read-write, requests for objects do not require a signature. Anonymous users can directly access objects via links, which may expose your data to leakage risks. Please exercise caution when configuring these settings.
Operation Steps
2. On the bucket card page, go to the specified bucket page and switch to the Property Settings tab.
3. Click the radio button for Public Permission to modify the bucket's public access settings.
4. Click Add User to grant file read and write permissions to specified sub-users or other Tencent Cloud primary accounts.
5. Click Save to complete the bucket access permission settings.
View storage monitoring
You can view the bucket's monitoring data through the console. Supported monitoring metrics include: storage capacity, public network downstream traffic, and number of objects.
Operation Steps
2. On the bucket card page, go to the specified bucket page and switch to the Storage Monitoring tab.
3. Select the desired time range as needed.