Function Overview

OBS provides a bunch of tools, including OBS Browser+ and obsutil, for data migration and management in different scenarios.

You can use these tools for OBS resource management, including creating buckets, mounting parallel file systems, and uploading and downloading objects.

OBS provides REST APIs that support HTTP/HTTPS methods. You can call these APIs to create, modify, and delete buckets, as well as to upload, download, and delete objects.

OBS provides SDKs for secondary development. The SDKs are available in the following programming languages: Java, Python, C, Go, BrowserJS, .NET, Android, iOS, PHP, and Node.js.

Buckets are containers that store objects in OBS.

Each bucket has its own attributes, such as the access permission, storage class, and region. You can specify these attributes when creating buckets. You can also configure advanced attributes.

OBS provides easy bucket management. You can conveniently create, list, search for, view, and delete buckets.

An object is the basic data unit stored in OBS.

It consists of file data and the metadata that describes attributes of the object. Data uploaded to OBS is stored in buckets as objects.

You can perform the following operations on objects: upload, download, listing, searching, resumable transfer, and multipart operations.

Parallel File System (PFS), provided by OBS, is a high-performance file system, with access latency in milliseconds. PFS supports TB/s-level bandwidth and millions of IOPS, which is ideal for processing high-performance computing (HPC) workloads.

You can call the OBS API to read data from a parallel file system, so that you can process the files and directories in parallel file systems online the same way you operate local file systems.

OBS provides the Standard, Infrequent Access, and Archive storage classes for buckets and objects, which meet different requirements for storage performance and cost.

The Standard storage class features low access latency and high throughput. It is therefore ideal for storing a massive number of hot files (frequently accessed every month) or small files (less than 1 MB). Its application scenarios include big data analytics, mobile apps, hot videos, and social apps.

The Infrequent Access storage class is ideal for storing data that is accessed infrequently (less than 12 times a year) and has quick response requirements. Its application scenarios include file synchronization, file sharing, and enterprise backup. It provides the same durability, access latency, and throughput as the Standard storage class but at a lower cost. However, the Infrequent Access storage class has lower availability than the Standard storage class. The Archive storage class is ideal for archiving data that is rarely accessed (once a year on average). Its application scenarios include data archiving and long-term data backups.

The Archive storage class is secure, durable, and inexpensive, and can be used to replace tape libraries. However, it may take hours to restore data from the Archive storage class. When creating a bucket, you can specify a storage class for it. When uploading an object, you can also specify a storage class for it. You can also use the lifecycle management rules to change storage classes for buckets and objects.

OBS uses IAM permissions, bucket/object policies, and ACLs to manage permissions.

You can grant different access permissions to different accounts and users, and configure bucket/object policies or ACLs to control read and write permissions for buckets and objects.

You can bind a domain name to an OBS bucket and use the domain name to access data in the bucket.

For example, if you need to migrate files from a website to OBS while keeping the website address unchanged, you can bind the website domain name to an OBS bucket.

Static websites usually contain static web pages and scripts that can run on clients, such as JavaScript and Flash.

You can upload the content files of a static website to an OBS bucket, grant anonymous users with the read permission to these files, and configure static website hosting for the bucket to host them. When the configuration takes effect, the static website can be accessed through the access domain name of the bucket.

Cross-origin resource sharing (CORS) is a browser-standard mechanism provided by the World Wide Web Consortium (W3C). It defines the interaction methods between client-side web applications in one origin and resources in another. For general web page requests, website scripts and contents in one origin cannot interact with those in another because of Same Origin Policies (SOPs). OBS supports CORS rules and allows resources in OBS to be accessed across origins.

You can use JavaScript and HTML5 to develop web applications that can directly access resources in OBS, without using proxy servers.

You can also use the dragging function of HTML5 to upload files directly to OBS (with the upload progress displayed) or update OBS content using web applications.

External web pages, style sheets, and HTML5 applications hosted in different origins can access web fonts or pictures stored in OBS, implementing resource sharing.

Some websites steal links from other websites to increase their own content and reduce costs. Link stealing not only damages the interests of the original websites but is also a strain on their servers. OBS provides URL validation to solve this problem.

URL validation is based on the Referer header field in HTTP requests. You can also configure whitelists and blacklists to bolster access security.

You can share a file stored in OBS with all users by using a temporary URL. File sharing is temporary, so all shared URLs are valid for only a short period of time.

You can configure this function on OBS Console or OBS Browser+, or you can configure a bucket policy or object policy to grant permanent access permissions to other users.

OBS provides server-side encryption for objects that you uploaded. Your objects are encrypted into ciphertext before they are stored on the server. When objects are downloaded, they will be decrypted on the server side first.

Server-side encryption significantly improves data security.OBS provides server-side encryption with SSE-KMS.

When uploading an object, you can choose whether to enable server-side encryption.

OBS supports bucket encryption. After a bucket is encrypted, all objects uploaded to the bucket are automatically encrypted.

You can enable the default encryption when creating a bucket or for an existing bucket. OBS encrypts only the objects uploaded after the default encryption function is enabled. The statuses of objects uploaded to the bucket before the default encryption function is enabled remain unchanged.

Lifecycle management allows you to configure rules to automatically delete objects or transition objects between storage classes at a scheduled time.
With lifecycle management, you can:
Regularly delete uploaded log files that are meant to be retained for only a specific period of time (one week or one month).
Transition documents that are seldom accessed to the Infrequent Access or Archive storage class or delete them.
Schedule the deletion of a large number of objects from a bucket.

OBS provides tags for you to identify and classify OBS buckets.

If you add tags to a bucket, charging data records (CDRs) generated for it will be labeled with these tags. You can classify CDRs according to the tags for detailed cost analysis. For example, if you have an application that uploads its running data to a bucket, you can tag the bucket with the application name. CDRs of this bucket will then also be labeled with this tag, so that you can analyze the storage costs of the application.

OBS provides the bucket inventory function to help you manage objects. A bucket inventory rule enables the system to periodically scan objects according to specific configurations, list objects with their properties (such as metadata, size, modification time, and storage class in CSV files), and store inventory files in specified buckets.

You can enable logging for buckets for analysis or auditing to analyze the characteristics, types, and trends of access requests sent to your buckets. With logging enabled, OBS automatically logs access requests for the bucket, and writes the generated log files to the specified bucket (or target bucket).

OBS provides the AppendObject API for you to write additional data to an appendable object in a specified bucket.

An object created by calling the AppendObject API is an appendable object, while an object created by calling the PutObject API is a normal object (not appendable). A normal object's content can only be read and not modified. In scenarios where data is continuously generated in real time, you can upload and store data as appendable objects in a bucket, so that newly generated data can be contiguously written to the objects and can be read upon being successfully written.

Object metadata is a set of name-value pairs that describe the object, and are used for object management.

The metadata is classified into the following types: system-controlled and user-controlled. Metadata such as Last-Modified is controlled by the system and cannot be modified, but metadata such as ContentLanguage and Expires are user-controlled and can be modified.

You can add, modify, or delete user-controlled metadata for uploaded objects.

You can set the bucket storage quota to limit the maximum amount of data that can be stored in a bucket. The maximum value is 2⁶³-1, in bytes. By default, the quota of a newly created bucket is not limited.

OBS can upload data in multiple parts. Data upload may fail and fragments may be generated in the following and other possible scenarios: poor network conditions; disconnection between OBS server and your local end; interruption during upload; device faults; unexpected power-off.

Fragments are stored in OBS buckets. It is recommended that you regularly clear fragments to free up storage space.

Enterprise project is a method for managing resources and services in a unified manner. Resources and services in different regions can be added to the same enterprise project. For example, you can create several enterprise projects based on your company's divisions or projects, and then add your cloud resources and services to these enterprise projects accordingly.

When creating a bucket, you can specify an enterprise project to which the bucket will belong, to facilitate bucket resource and permission management.

OBS can store multiple versions of an object in the same bucket, so that you can quickly search for and restore different versions of an object. This function guarantees data restoration in the event of accidental deletion or application error.

Versioning is disabled by default. If you upload an object to a bucket that already has an object with the same name, the original object in the bucket will be overwritten by the newly uploaded object. If you need to retain versions of an object in a bucket, enable versioning for the bucket.

With the IAM agency function, you can delegate your resource operation permissions to other HUAWEI CLOUD service accounts that are more professional and efficient to let them perform O&M operations on your behalf.

You can also authorize other cloud services or HUAWEI CLOUD accounts to manage your OBS resources. For example, to implement cross-region replication in OBS, you need to grant permissions to the OBS service account to help you copy objects from the source bucket to the destination bucket.

When using OBS, you may send PUT and GET requests continuously, which generates upload and download data traffic, and you may receive error responses from the server. Cloud Eye can perform automatic and real-time monitoring for your buckets. It triggers alarms and notifications for operations, making it easy for you to understand your bucket access requests, data traffic, and error responses, so that you can optimize or plan resource usage.

Cloud Trace Service (CTS) is a log audit service provided by HUAWEI CLOUD. CTS collects, stores, and queries records of operations on buckets and objects in OBS, facilitating security analysis, compliance audit, resource tracking, and fault locating.

By default, objects stored in the Archive storage class need to be restored before being downloaded. However, if you enable the direct reading function for a bucket, you can directly download Archive objects from the bucket without restoring them in advance. Direct reading is a billable function.