Create and Manage OSS Buckets

A bucket is a container in OSS for storing objects. After you create a bucket, you can view its usage and number of objects, and configure access control, compliance retention, and cross-origin access rules as needed.

​

Create Bucket

1. Log in to the GPU Cloud console.
2. Go to STORAGE > Object Storage.
3. At the top of the page, select the target region and ensure that the type is High Performance. After a bucket is created, it belongs to the selected Region. When accessing it later through the S3 Protocol, use the Endpoint corresponding to that Region.
4. On the Buckets tab, click Create Bucket.
5. Configure Buckets parameters.

   Parameter	Description
   Region	The region to which the bucket belongs, determined by the currently selected region.
   Bucket Name	The name of the bucket. The system populates the name prefix; you need to enter the custom portion of the name.
   Versioning	Whether to enable versioning. When enabled, the bucket can retain multiple versions of objects.
   Size	The bucket capacity quota. GiB, TiB, PiB, or EiB can be selected as the unit.

6. Click Confirm. Return to the Buckets list and verify that the new bucket has been created.

​

View the Buckets List

To verify that a bucket was created successfully or view its used capacity and object count, select a region and type on the Buckets tab to view buckets within the corresponding scope. The page displays the number of buckets, used capacity, and total number of objects. The list provides the following information:

​

Configure Access Permissions

On the Access Control tab in the console, you can use Add Directory Policy to configure access permissions for specific path prefixes in a bucket.

1. In the Buckets list, locate the target bucket and click Settings.
2. Open the Access Control tab, then click Add Directory Policy.
3. Enter the directory policy information.

   Parameter	Description
   Directory	The bucket path prefix for which to set access permissions.
   Permission Type	Select admin, rewrite, readonly, or writeonly.
   Policy Name	The name of the directory policy.
   User	Select the user to whom this directory policy will be applied.

4. Click Confirm.

​

Configure Object Protection Period

To prevent objects from being deleted before the end of the retention period, you can enable compliance retention and set a retention period. Before enabling or adjusting it, confirm your business’s data retention requirements.

1. In the Buckets list, locate the target bucket and click Settings.
2. Open the Compliance Retention tab to view the current retention period status.
3. Click Edit, enable compliance retention as needed and set the protection period, then click Confirm.
4. Verify that the retention period status and protection period displayed on the page meet your expectations.

​

Configure Cross-Origin Access Rules

When a web application needs to access OSS objects in a browser, the browser determines whether to allow the request based on cross-origin resource sharing (CORS) rules. You can add rules in Cross-Origin Access Configuration for a bucket to allow specified web origins to access the bucket using specified methods and request headers. Cross-origin access rules affect only browser cross-origin validation and do not replace bucket access permissions or authentication.

1. In the Buckets list, locate the target bucket and click Settings.
2. On the Overview tab, locate CORS Configuration, and then click Create Rule.
3. Configure the rule.

   Configuration Item	Description
   Origin	The web origins allowed to initiate cross-origin requests. Enter a domain name or IP address; a port number is allowed, for example, https://example.com or http://192.0.2.10:8080. Enter one origin per line, separated by line breaks. Each line can contain at most one wildcard *, and up to 1,000 entries can be specified.
   Methods	The HTTP methods that the origin is allowed to use. Select GET, HEAD, PUT, POST, or DELETE based on how the web application accesses the resource. For example, if objects are read only in a browser, select GET or HEAD.
   Allow-Headers	Request headers allowed in browser cross-origin requests. If requests include authentication headers or custom request headers, enter the corresponding request header names. Enter one request header name per line, separated by line breaks. Up to 1,000 entries can be specified. If there are no special requirements, set this parameter to *.
   Expose-Headers	Response headers that browser JavaScript is allowed to read. If the frontend needs to read specific response headers, enter the corresponding response header names. Enter one response header name per line, separated by line breaks. Wildcards * are not allowed.
   Max-Age	The duration, in seconds, for which the browser caches preflight request results. During the cache lifetime, identical cross-origin requests can reduce the number of preflight requests.

4. Click Confirm to submit the rule.

​

Delete Buckets

Locate the target bucket in the Buckets list, click Delete, and then follow the prompts to confirm the deletion.

​

Next Actions

To access Buckets through the command line, first configure ossctl, then use ossctl to upload and download OSS objects.