Skip to main content
OSS is an object storage service provided by GPU Cloud for storing and accessing object data. You can store datasets, model files, training outputs, log archives, and other unstructured data in OSS Buckets. Use the console to create and manage buckets. To access object data, use an SDK or command-line tool that supports the S3 protocol.

​
Applicable Scenarios

OSS is suitable for storing data that does not rely on POSIX file system semantics and for reading and writing objects through the S3 protocol or command-line tools. Common scenarios include:
  • Upload training datasets, model files, or inference input data.
  • Download training outputs, model weights, or log archives.
  • Access object data from a local environment, CES instance, or automated scripts.
  • Archive unstructured data that does not need to be mounted as a local directory.
If your workloads require multiple CES instances or workloads in a CKS cluster to share read and write access to the same data through local directories, the GPFS file system may be more suitable.

​
Core Concepts

​
Access Method

​
Usage workflow

1

Create or Select a Bucket

First, create a high-performance bucket in the console, or select an existing bucket. When creating a bucket, confirm parameters such as the region, Bucket Name, Versioning, and size.When creating a bucket, only new high-performance buckets are supported. Existing standard buckets can continue to be maintained, but new standard buckets cannot be created. For more information, see Create and manage OSS buckets.
2

Configure access control, compliance retention, and cross-origin access rules

Based on business access methods and data protection requirements, configure access control, compliance retention, or cross-origin access rules in the bucket settings as needed.
  • To grant specified users access to a specific path prefix, add a directory policy on the Access Control tab.
  • To prevent objects from being deleted before the end of the protection period, configure Compliance Retention.
  • When a web application needs to access bucket resources across origins from a browser, configure cross-origin access rules on the Overview tab.
3

Prepare Access Credentials and Tools

Before accessing object data through the S3 SDK, ossctl, or other command-line tools, prepare Access Keys and configure the tool using the Endpoint corresponding to the Region where the Buckets are located.If you use ossctl, first Configure ossctl.
4

Upload, Download, or List Objects

After configuring the tool, you can use ossctl or other tools that support the S3 protocol to upload objects, download objects, list objects, or upload and download directories.For instructions on using ossctl to access objects, see Upload and Download OSS Objects Using ossctl.
5

View usage and maintain data security

During use, you can view bucket usage and the number of objects in the console, and adjust access permissions, cross-origin access rules, or retention policies as business needs change.Before deleting an object or bucket, ensure that any data to be retained has been backed up or migrated.

​
Security and Data Protection

  • Store your Access Key and Secret Key securely. Do not include them in public code repositories, images, script templates, or logs.
  • If an access key is compromised, disable or delete the key as soon as possible, and create a new access key.
  • Deleting objects or Buckets may result in unrecoverable data loss. Before performing a delete or overwrite operation, ensure that any data to be retained has been backed up or migrated.