List of Features

The requests that are sent by users to OBS must comply with REST specifications and contain required header parameters. If a request is successfully processed, OBS returns a success response. If the request fails to be processed, OBS returns an error response that contains the cause of the error. As containers for data storage in OBS, buckets have the following features:

Table 1 OBS features

Feature

Brief Description

Basic bucket operations

Creating buckets, deleting buckets, obtaining bucket lists, and listing objects in a bucket

Basic object operations

uploading objects, downloading objects, copying objects, and uploading an object in multiple parts.

Control permissions

Object ACL, bucket ACL, and bucket policies

Data transmission

OBS supports the data transfer protocols.

Data protection mechanisms

Bucket versioning control and server-side encryption

Storage classes

This section describes the storage classes of buckets and objects.

Object lifecycle management

Guides and instructions on object lifecycle management

Static website hosting

Guides and instructions on static website hosting

Cross-region replication

Guides and instructions on cross-region replication

Event notification

Sends event notifications through SMN or FunctionGraph.

Logging

This topic describes how to manage bucket logs.

Monitoring

This topic describes how to view OBS monitoring metrics.

OBS has two generations of hardware architecture, OBS 2.0 and OBS 3.0. Any newly created bucket will be stored in OBS 3.0 by default, but the previously created buckets are still stored in OBS 2.0. OBS 3.0 provides more features than the OBS 2.0, Table 2 shows the differences.

Table 2 Comparison of features between OBS 3.0 and OBS 2.0

Feature

OBS 3.0

OBS 2.0

Object storage classes

Available

N/A

Federated authentication

Available

N/A

IAM agency

Available

N/A

Image processing

Available

N/A

Cross-region replication

Available

N/A

Other features and basic functions that are not listed here are available with both OBS 2.0 and OBS 3.0.

You can use OBS Console or the HeadBucket operation to check whether the bucket is stored in OBS 2.0 or OBS 3.0. The checking methods are listed as follows:

Method 1: Log in to OBS Console and check the bucket summary.

If the Bucket Version is 3.0, the bucket is stored in OBS 3.0. If no value is displayed for Bucket Version, the bucket is stored in OBS 2.0.

Method 2: Send the API request (HeadBucket) to check the bucket version.

Example request

HEAD / HTTP/1.1
Host: bucketname.obs.cn-north-4.myhuaweicloud.com
Accept: */*
Date: Thu, 07 Jun 2018 02:23:25 GMT
Authorization: auth string

Example response:

HTTP/1.1 200 OK
Server: OBS
x-obs-request-id: BF2600000163D80E4C5F20FDD5BD0085
Content-Type: application/xml
x-obs-version: 3.0
x-obs-id-2: 32AAAQAAEAABAAAQAAEAABAAAQAAEAABCS8wS9l00ll4oMWmdniV7XmdAvfewrQq
Date: Thu, 07 Jun 2018 02:23:25 GMT
Content-Length: 0

In this response, x-obs-version: 3.0 indicates that the bucket is stored in the OBS 3.0. If this header does not exist or the value of this header is displayed otherwise, the bucket is stored in the OBS 2.0.