OBS Document en
OBS Document en
6.5.1
OBS
Issue 01
Date 2019-06-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
Contents
1 Quick Start...................................................................................................................................... 1
1.1 Overview........................................................................................................................................................................ 1
1.2 Concepts......................................................................................................................................................................... 1
1.3 Creating a User............................................................................................................................................................... 2
1.4 Creating a Bucket........................................................................................................................................................... 2
1.5 Uploading Objects.......................................................................................................................................................... 6
1.6 Downloading Objects..................................................................................................................................................... 9
1.7 Deleting Objects........................................................................................................................................................... 11
1.8 Deleting a Bucket......................................................................................................................................................... 13
1.9 Reference...................................................................................................................................................................... 14
2 Infographics..................................................................................................................................15
3 User Guide.................................................................................................................................... 17
3.1 Object Storage Service (OBS)...................................................................................................................................... 17
3.1.1 Introduction............................................................................................................................................................... 17
3.1.1.1 What Is Object Storage Service?............................................................................................................................ 17
3.1.1.2 Related Concepts.................................................................................................................................................... 20
3.1.1.3 Product Advantages................................................................................................................................................ 22
3.1.1.4 Application Scenarios.............................................................................................................................................22
3.1.1.5 Implementation Principles...................................................................................................................................... 24
3.1.1.6 Relationships with Other Cloud Services............................................................................................................... 26
3.1.1.7 User Roles and Permissions................................................................................................................................... 28
3.1.1.8 Key Indicators.........................................................................................................................................................32
3.1.1.9 Restrictions............................................................................................................................................................. 33
3.1.1.10 Accessing and Using OBS....................................................................................................................................33
3.1.2 Operation Process...................................................................................................................................................... 34
3.1.3 Creating a Bucket...................................................................................................................................................... 37
3.1.4 Usage......................................................................................................................................................................... 41
3.1.4.1 Uploading an Object............................................................................................................................................... 41
3.1.4.2 Downloading an Object.......................................................................................................................................... 44
3.1.5 Bucket Management.................................................................................................................................................. 44
3.1.5.1 Modifying a Bucket Quota..................................................................................................................................... 44
3.1.5.2 Viewing Bucket Information.................................................................................................................................. 45
1 Quick Start
1.1 Overview
1.2 Concepts
1.3 Creating a User
1.4 Creating a Bucket
1.5 Uploading Objects
1.6 Downloading Objects
1.7 Deleting Objects
1.8 Deleting a Bucket
1.9 Reference
1.1 Overview
Object Storage Service (OBS) is an object-based storage service. It provides massive, secure,
highly reliable, and low-cost data storage capabilities.
You can create buckets, upload objects, download objects, delete objects, and delete buckets
on ManageOne Operation Portal. This document gives an introduction of OBS and describes
how to complete the following tasks using ManageOne.
You can find more details about OBS functions and FAQs on the homepage of OBS.
1.2 Concepts
You need to understand some basic concepts before using OBS.
OBS stores data as objects in buckets. An object is a basic unit of data storage in OBS. An
object is a combination of the file data and its metadata (related properties). Data uploaded to
OBS is stored in buckets as objects.
If you want to store files (objects) in OBS, upload the files to OBS buckets. After uploading a
file, you can configure access permissions for the object and bucket.
A bucket is a container for storing objects. You can own one or more buckets. For each
bucket, you can specify the region where the bucket and its objects reside, control access to
the bucket, and view access logs related to the bucket and its objects.
For more information about OBS, see OBS User Guide.
Click here to start learning.
Before using OBS, you need to obtain the VDC administrator account or VDC operator
account. If no accounts are available, contact the operation administrator to create a VDC and
VDC administrator, and then use the VDC administrator account to create a VDC operator.
For details, see Operation Help Center > Dividing Cloud Resources.
After a role is registered, you can create a bucket. A bucket is a container for storing objects
in OBS. Each object is stored in a bucket. Before you store data in OBS, you need to create a
bucket. This section describes how to create a bucket.
Prerequisites
You have obtained a VDC administrator account or a VDC operator account for logging in to
ManageOne Operation Portal.
Context
Two types of administrators, OBS administrator and OBS limited administrator, can create
buckets.
For details about user roles and permissions, see 3.1.1.7 User Roles and Permissions.
Procedure
Step 1 Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
Step 4 Click Create Bucket in the upper right corner of the page.
Bucket Click Add. On the page that is displayed, select users as the bucket_ad
Manager administrators of the bucket. A maximum of 10 min
administrators can be added.
The added bucket administrators have the full control over
the bucket except configuring bucket policies.
NOTE
l When a URL is used to access a bucket, the bucket name is a part of the URL. According to DNS
standards, a URL does not support uppercase letters and cannot be used to access a bucket whose
name contains uppercase letters. Therefore, a bucket name can contain only lowercase letters, digits,
hyphens (-), and periods (.) For example, if you attempt to access bucket MyBucket using a URL,
bucket mybucket will be accessed instead, causing an access error.
l An OBS administrator creates a shared bucket by default.
----End
After a bucket is created, you can upload objects to the bucket. By uploading objects, you can
save local files or folders to OBS.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal.
l At least one bucket has been created.
l If you want to use a user-defined key to encrypt objects to be uploaded, create a key
using KMS. Uploading KMS-encrypted objects is not supported in the Region Type III
scenario.
Context
l These files can be text, image, video, or any other types.
l A file up to 5 GB can be uploaded using OBS Console. A maximum of 100 files can be
uploaded at a time. A file larger than 5 GB can be uploaded using an API or a third-party
tool.
l A file name cannot exceed 1023 bytes. The total length of a file name is the sum of the
length of its own and the length of its upper-level directories. Levels of directories are
automatically separated by slashes (/). For example, if the upper-level folder of file01 is
folder01, the file name length is the length of folder01/file01.
l OBS supports server-side encryption with KMS-managed keys (DEW-KMS) using an
interface. The object to be uploaded can be encrypted on the server using the key
provided by the key management server. You need to create a key using KMS or use the
default key provided by KMS. Then you can use the key to encrypt the object on the
server when uploading the object OBS. After server-side encryption is enabled, data of
the object uploaded to OBS is encrypted on the server before being stored. When the
object is downloaded, data is decrypted on the server first.
l OBS does not allow cross-tenant or anonymous users to access objects encrypted using
KMS.
Procedure
Step 1 Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
NOTE
You can also click the folder to be operated and then click Upload File.
Step 7 Click Add File or Add Folder, select the file or folder to be uploaded, and click OK.
NOTE
Step 8 Optional: Select KMS encryption and select a key name from the drop-down list.
OBS provides a default key named obs/default. You can use the default key or click Create
KMS Key to customize a key to encrypt and upload the object.
l You can also click Upload Task in the lower left corner of the page to view and manage
the uploaded task.
l You can click Suspend or Suspend All Tasks to suspend one or all tasks in Uploading
or Waiting state.
l If the upload task fails or the upload task is manually suspended, you can click Continue
to restart the upload.
NOTE
l You cannot suspend or continue the upload of a file less than or equal to 5 MB.
l Do not exit the console during the upload. Otherwise, the task will be interrupted and cannot be
restored.
----End
Follow-up Operations
After an object is successfully uploaded, you can view the encryption status of the object in
the object list. The status may be Encrypted or Unencrypted.
For an encrypted object, you can click the object name to view its Encryption Type, Key
Name, and Key ID.
NOTE
After uploading files to a bucket, you can download the files to a local host if necessary.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal.
l At least one bucket has been created.
l At least one file has been uploaded.
l Ensure that DNS server IP addresses are correctly configured on the client environment
for OBS domain name resolution. Contact the administrator to obtain the IP addresses
from parameters TDNS-TNTP01-TENANT and TDNS-TNTP02-TENANT in the
parameter summary file xxx_export_all_EN.xlsm.
NOTE
l In an ECS environment, ensure that the DNS server IP address of the ECS is the same as that
of the VPC associated with the ECS.
l If you access OBS from the Internet, ensure that the DNS server IP address of the Internet has
been configured on the client.
Procedure
Step 1 Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
Step 6 In the row where the file resides, click Download and download the file as prompted.
----End
If objects stored in OBS are no longer needed, you can delete the objects to free up the storage
space. You can delete a single object or delete objects in batches.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal.
l At least one bucket has been created.
l At least one file has been uploaded.
Context
Deleting unnecessary objects saves space and costs.
Some files uploaded to OBS need to be periodically deleted. You can use the lifecycle
management function of OBS to periodically delete these files. For details about the lifecycle
management function, see 3.1.10 Lifecycle Management.
Procedure
Step 1 Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
Step 6 Select the file you want to delete, and click Delete on the right.
You can also select multiple files and click Delete above the list to batch delete them.
----End
You can delete a bucket as required. If you want to use the same bucket name, do not delete
the bucket. You are advised to clear and retain the bucket.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal.
l The bucket to be deleted is empty.
l You are the bucket owner.
Procedure
Step 1 Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
Step 4 Click Delete in the row where the bucket to be deleted is located.
NOTE
l Before deleting a bucket, ensure that all objects in the bucket have been deleted.
l The interval between deleting a bucket and creating another bucket with the same name varies
according to application scenarios.
----End
1.9 Reference
The preceding sections describe how to perform basic tasks of OBS.
For more details about OBS, see Object Storage Service User Guide, which describes the
complete product functions and operation guide of the OBS Console.
2 Infographics
3 User Guide
3.1.1 Introduction
Definition
Object Storage Service (OBS) is a cloud storage service that provides capabilities for massive,
secure, reliable, and cost-effective data storage. With OBS, you can easily create, modify, and
delete buckets, as well as uploading, downloading, and deleting objects.
Object storage devices and services are becoming increasingly popular in research and
markets, providing a viable alternative to established block and file storage services. OBS is a
cloud storage service that can store unstructured data such as documents, images, and
audiovisual videos, combining the advantages of block storage (direct and fast access to
disks) and file storage (distributed and shared).
The OBS system and a single bucket do not have restrictions on the total data volume and
number of objects, providing users ultra-large capacity to store files of any type. OBS can be
used by common users, websites, enterprises, and developers.
As an Internet-oriented service, OBS provides web service interfaces over Hypertext Transfer
Protocol (HTTP) and Hypertext Transfer Protocol Secure (HTTPS). Users can use OBS
Console or a browser to access and manage data stored in OBS on any computer connected to
the Internet anytime, anywhere. In addition, OBS supports SDK and API interfaces, which
enable users to easily manage data stored in OBS and develop various upper-layer service
applications.
Functions
OBS provides the following functions:
l Basic Bucket Operations
Create, view, and delete buckets in a specific region.
l Basic Object Operations
Create folders and manage objects, including uploading, downloading, and deleting
objects.
l Permission Control
Control access to OBS using bucket policies and bucket/object ACLs.
l Versioning
Multiple versions of an object can co-exist in a bucket.
l Logging
Bucket access requests can be recorded in logs for request analysis and log audit.
l Lifecycle Management
Lifecycle rules can be set for buckets so that expired objects are automatically deleted.
l Static Website Hosting
Website attributes can be set for buckets to implement static website hosting. Web page
redirection can be set to redirect bucket requests to the specified hosts.
l Cross-Origin Resource Sharing
Cross-Origin Resource Sharing (CORS) rules are supported, allowing resources in OBS
to be accessed across domains.
l URL Validation
URL validation is provided to prevent object links of OBS from being stolen by other
websites.
Data access mode Data access is limited Data access is Data access on the
within the internal limited within the public network is
network of a data internal network of a allowed to meet
center. data center. requirements of
Internet
applications.
Bucket
A bucket is a container that stores objects in OBS. OBS provides flat storage in the form of
buckets and objects. Unlike the conventional multi-layer directory structure of file systems,
all objects in a bucket are stored at the same logical layer.
In OBS, each bucket name must be unique and cannot be changed. When a bucket is created,
its access control list (ACL) is generated by default. The items in the ACL include
permissions of authorized users such as the read (READ), write (WRITE), and full control
(FULL_CONTROL) permissions. Only authorized users can perform bucket operations, such
as creating, deleting, viewing, and configuring the bucket ACL. A user can create a maximum
of 100 buckets. However, the number and total size of objects in a bucket are not restricted.
Users do not need to worry about system scalability.
OBS is a service based on the REST (Representational State Transfer) style HTTP and
HTTPS protocols. You can locate resources using URL (Uniform Resource Locator).
Figure 3-1 illustrates the relationship between buckets and objects in OBS.
Object
An object is a basic data storage unit of OBS. It consists of file data and metadata that
describes the attributes. Data uploaded to OBS is stored into buckets as objects.
An object consists of data, metadata, and a key.
l A key specifies the name of an object. An object key is a string ranging from 1 to 1024
characters in UTF-8 format. Each object in a bucket must have a unique key.
l Metadata describes the object. Metadata contains system metadata and user metadata.
All the metadata is uploaded to OBS as key-value pairs.
– System metadata is automatically generated by OBS and is used for processing
object data. It includes object attributes such as Date, Content-length, Last-
modify, and Content-MD5.
– User metadata is specified by users to describe objects when they upload the
objects.
l Data is the content contained by an object.
Generally, objects are managed as files. However, OBS is an object-based storage service and
it does not involve the file and folder concepts. For easy data management, OBS provides a
method to simulate virtual folders. By adding a slash (/) in an object name, for example, test/
123.jpg, you can simulate test as a folder and 123.jpg as the name of a file under the test
folder. However, the key remains test/123.jpg.
On the OBS management console, users can directly use folders as they used to do.
AK/SK
Access Key ID (AK)/Secret Access Key (SK) is an authentication certificate pair. OBS
(compatible with Amazon S3 APIs) authenticates requests using AKs and SKs. Tenants and
users use AKs and SKs to access the system. OBS (compatible with Amazon S3 APIs)
identifies tenants and users based on the AKs and SKs.
l An AK corresponds to only one tenant or user. A tenant or user can have two AKs at the
same time. OBS (compatible with Amazon S3 APIs) identifies a tenant or user accessing
the system based on the AK.
l A tenant or user generates authentication information based on the SK and request
header. An SK corresponds to an AK.
Region
A region is where the OBS data center is located. When creating a bucket, the user can
specify a region where the bucket resides based on the expected cost, response latency, and
request source. The specified region cannot be changed after the bucket is created.
After a bucket is created, all objects uploaded to the bucket are stored in the data center of the
region.
Endpoint
Endpoint indicates the domain name used by OBS to provide services. OBS provides services
in HTTP RESTful API mode. Different domain names are required for accessing different
regions. The endpoints required for accessing the same zone through the intranet and extranet
are different.
Quota
Quota restricts the resources that a user can use. Quota is the upper limit of available
resources and storage capacity.
OBS allows you to set quotas for tenants and buckets.
l Tenant quota: The administrator can set capacity quotas for tenants to limit the upper
limit of storage space that can be used by the tenants.
l Bucket quota: An OBS administrator can set a capacity quota for a bucket to limit the
upper limit of storage space of the bucket.
Video surveillance
OBS provides large storage capacity for video surveillance solutions and applies to massive
and unstructured video data to meet requirements for storing high quality video data.
Figure 3-3 shows the architecture.
Logical Architecture
Figure 3-4 shows the logical architecture of OBS.
Workflow
Figure 3-5 shows the OBS workflow.
Image OBS can provide backend storage for image files of IMS.
Manage
ment
Service
(IMS)
Key KMS provides central management and control capabilities of CMKs for
Manage Object Storage Service (OBS). It is perfectly suited for server-side encryption
ment on OBS.
Service
(KMS)
Cloud Description
Service
Name
l One of VDC
management
permission,
read-only
permission, and
operator
permission
l OBS
management
permission
NOTE
If you want to
use the function
of uploading
objects in
encrypted mode,
select Key
Management
Service
Management
Permission.
OBS limited Customized l One of VDC A user with this permission can
administrator management perform any operations on OBS
permission, resources except for
read-only configuring quota and logging.
permission, and
operator
permission
l All cloud
service read-
only permission
l OBS limited
management
permission
OBS read- VDC read-only l VDC read-only A user with these permissions
only user administrator permission can query the usage of OBS
l All cloud resources. Specifically, the user
service read- can only read OBS resources.
only permission
Table 2 lists the operations that users in different roles can perform.
Managing Yes No No No
bucket quotas
Managing Yes No No No
exclusive
bucket policies
Managing Yes No No No
logging
Viewing No No No Yes
buckets
3.1.1.9 Restrictions
The restrictions on OBS are as follows:
l Web UI
Log in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios) as
a tenant user and select the cloud service on the Console menu.
l API
If you want to integrate the cloud service into third-party systems for secondary
development, use the API mode.
Table 3-7 lists the operators and user interfaces (UIs) required for each step.
Prerequisites
You have obtained a VDC administrator account or a VDC operator account for logging in to
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
Context
Two types of administrators, OBS administrator and OBS limited administrator, can create
buckets.
For details about user roles and permissions, see 3.1.1.7 User Roles and Permissions.
Procedure
Step 1 Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
Step 4 In the upper right corner of the page, click Create Bucket and set related parameters. For
details, see Table 3-8.
Parameter Description
Bucket Click Add. On the Add page that is displayed, select users as the
Manager administrators of the bucket. A maximum of 10 administrators can be
added.
The added bucket administrators have the full control over the bucket
except configuring bucket policies.
NOTE
l When a URL is used to access a bucket, the bucket name is a part of the URL. According to DNS
standards, a URL does not support uppercase letters and cannot be used to access a bucket whose
name contains uppercase letters. Therefore, a bucket name can contain only lowercase letters, digits,
hyphens (-), and periods (.) For example, if you attempt to access bucket MyBucket using a URL,
bucket mybucket will be accessed instead, causing an access error.
l An OBS administrator creates a shared bucket by default.
l When an exclusive bucket is created, the system automatically generates two exclusive bucket
policies by default. The two policies are displayed on the top of the bucket policy list to identify the
access mode of the bucket. An OBS administrator can view and manage exclusive bucket policies in
the bucket policy list. For details, see 3.1.7.5 Configuring a Bucket Policy.
----End
3.1.4 Usage
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
l If you want to upload encrypted objects, you must have the management permission of
the key management service. For details, see the permission configuration of the user-
defined OBS administrator in 3.1.1.7 User Roles and Permissions.
l If you want to use a user-defined key to encrypt objects to be uploaded, create a key
using KMS. Uploading KMS-encrypted objects is not supported in the Region Type III
scenario.
Context
l Any types of files can be uploaded, such as the text, image, and video.
l A file up to 5 GB can be uploaded using OBS Console. A maximum of 100 files can be
uploaded at a time. A file larger than 5 GB can be uploaded using an API or a third-party
tool.
l The total length of a file name cannot exceed 1023 bytes. The total length of a file name
is the sum of the length of its own and the length of its upper-level directories. Levels of
directories are automatically separated by slashes (/). For example, if the upper-level
directory of file01 is folder01, the file name length is calculated based on folder01/
file01. In the Windows operating system, the length of a file name must be fewer than
260 characters and that of a directory name must be fewer than 248 characters.
l OBS supports server-side encryption with KMS-managed keys (SSE-KMS) using an
interface. The object to be uploaded can be encrypted on the server using the key
provided by the key management server. You need to create a key using KMS or use the
default key provided by KMS. Then you can use the key to encrypt the object on the
server when uploading the object OBS. After server-side encryption is enabled, data of
the object uploaded to OBS is encrypted on the server before being stored. When the
object is downloaded, data is decrypted on the server first.
l OBS does not allow cross-tenant or anonymous users to access objects encrypted using
KMS.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket where you want to upload the object.
Step 5 Click Add File or Add Folder, select the file or folder to be uploaded, and click OK.
NOTE
l You can also drag the file to the list directly. When using Internet Explorer of any version, you
cannot drag a file to upload it or upload a folder. When using Firefox earlier than 52.0.1, you cannot
drag a file to upload it. When using Firefox earlier than 54.0.1, you cannot upload a folder.
l Do not upload a file larger than 5 GB or upload more than 100 files at a time. Otherwise, the upload
may fail.
l An uploaded folder is not created as an object but is displayed as a directory. The number of folders
is not calculated to the number of objects.
l If an access denial message is displayed when you are uploading a file, the possible causes are as
follows:
– The access permissions for the bucket are restricted by the ACL. For example, the user has no
write permission for the bucket. For details about how to configure an ACL for a bucket, see
3.1.7.4 Configuring ACL Permissions for a Bucket.
– The access permissions for the bucket are restricted by the bucket policies. For example, the
bucket cannot be written or the user does not have the write permission for the bucket. For
details about bucket policies, see 3.1.7.5 Configuring a Bucket Policy.
Step 6 Optional: Select KMS encryption and select a key name from the drop-down list.
OBS creates a default key named obs/default. You can use the default key or click Create
KMS Key to customize a key to encrypt and upload the object.
l You can also click Upload Task in the lower left corner of the page to view and manage
the uploaded task.
l You can click Suspend or Suspend All Tasks to suspend one or all tasks in Uploading
or Waiting state.
l If the upload task fails or the upload task is manually suspended, you can click Continue
to restart the upload.
NOTE
l You cannot suspend or continue the upload of a file less than or equal to 5 MB.
l Do not exit the console during the upload. Otherwise, the task will be interrupted and cannot be
restored.
----End
Follow-up Procedure
After an object is successfully uploaded, you can view the encryption status of the object in
the object list. The status may be Encrypted or Unencrypted.
For an encrypted object, you can click the object name to view its Encryption Type, Key
Name, and Key ID.
NOTE
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
l At least one file has been uploaded.
l If you want to upload encrypted objects, you must have the management permission of
the key management service. For details, see the permission configuration of the user-
defined OBS administrator in 3.1.1.7 User Roles and Permissions.
l Ensure that DNS server IP addresses are correctly configured on the client environment
for OBS domain name resolution. Contact the administrator to obtain the IP addresses
from parameters TDNS-TNTP01-TENANT and TDNS-TNTP02-TENANT in the
parameter summary file xxx_export_all_EN.xlsm.
NOTE
If you access OBS from the Internet, ensure that the DNS server IP address of the Internet has
been configured on the client.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 3 In the row where the file resides, click Download and download the file as prompted.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 3 In the Basic Information area, click Setting to modify the bucket quota.
Step 4 Enter a value for Quota Limited (GB).
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 3 In the Monitoring Statistics area, view the monitoring statistics of the bucket.
Table 3-9 lists monitoring statistics.
Number of objects Number of objects stored in the bucket, including all object
versions.
Step 4 In the Basic Information area, view basic information of the bucket.
Table 3-10 describes basic information about a bucket.
Access Domain Name Domain name of the bucket, which is used when the bucket is
accessed by domain name directly.
The format of the domain name is bucket name.endpoint.
NOTE
If the DNS server IP address is not configured on the client, you can
change the access domain name of the bucket to endpoint/bucket name.
----End
Prerequisites
You have obtained a VDC administrator account or a VDC operator account for logging in to
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
Context
Data is uploaded to OBS in multipart mode. In the following common and other scenarios, an
upload fails and fragments are generated. You need to delete these fragments to free up
storage space.
l The network is in poor conditions, and the connection to the OBS server is interrupted
frequently.
l The upload task is manually suspended.
l The device is faulty.
l The device is powered off suddenly.
Fragments generated due to an upload failure are stored in OBS. You can delete the fragments
manually or continue the upload.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 3 Select the fragment that you want to delete and click Delete next to it.
You can also select multiple fragments and click Delete above the list to batch delete them.
Step 4 Optional: Select the fragment that you want to continue the upload and click Continue.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l The bucket you want to delete is empty.
l You are the bucket owner.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
l Before deleting a bucket, ensure that all objects in the bucket have been deleted.
l At least 30 minutes later after a bucket is deleted, you can create a bucket with the same name in
another VDC at least 30 minutes later.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Context
There are no file and folder concepts in OBS. For easy data management, OBS provides a
method to simulate virtual folders. In OBS, a special object named folder name/ is added and
displayed as a folder on OBS Console. You can also upload an object by adding a folder on
OBS Console. The object name is a complete path with the folder directory. Levels of
directories are separated by slashed (/). OBS Console recognizes / and displays the object as a
folder. In this case, no special object named folder name/ is created.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 5 In the Folder Name text box, enter a name for the folder.
l The name cannot contain special characters \/:*?"<>|.
l The name cannot start or end with a period (.)
l The name cannot exceed 1023 bytes.
The length of a folder name is the sum of the length of its own and the length of its
upper-level directories, and cannot exceed 1023 bytes. Levels of directories are
automatically separated by slashes (/). For example, if the upper-level directory of the
folder01 file is folder02, the file name length is calculated based on folder02/folder01/.
NOTE
l When a folder is created, it is created as an object and is added to the number of objects.
l If an access denial message is displayed when you are creating a folder, the possible causes are as
follows:
– The access permissions for the bucket are restricted by the ACL. For example, the user has no
write permission for the bucket. For details about how to configure an ACL for a bucket, see
3.1.7.4 Configuring ACL Permissions for a Bucket.
– The access permissions for the bucket are restricted by the bucket policies. For example, you
have no write permission on the bucket. For details about bucket policies, see 3.1.7.5
Configuring a Bucket Policy.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
l At least one file has been uploaded or a folder has been created.
Precautions
After you delete a folder, objects in the folder will be unavailable. Before performing this
operation, ensure that the objects in the folder are no longer needed.
Context
l Deleting unnecessary objects saves space and costs.
l Some files or folders uploaded to OBS need to be periodically deleted. You can use the
lifecycle management function of OBS to periodically delete these files. For details, see
3.1.10 Lifecycle Management.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 4 Select the file or folder you want to delete, and click Delete next to it.
You can also select multiple files and click Delete above the list to batch delete them.
----End
Related Operations
If versioning is enabled, a deleted object will be removed to the Deleted Objects list and a
version with the deletion mark is automatically generated.
To delete a specific version permanently, click the object and select the target version from the
Versions list. If you delete an object version with the deletion mark, the object will be
recovered. For details, see 3.1.6.3 Undeleting a File.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l The versioning function is enabled and a file has been deleted. For details about how to
enable the versioning function, see 3.1.8 Versioning.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 5 In the row where the file you want to restore resides, click Undelete on the right.
You can also click the file and delete the version with the deletion mark from the Versions
list. The object will be restored to the object list.
NOTE
If the file you want to restore is in a folder, click the folder. Open the folder, locate the row where the
deleted file resides, and click Undelete on the right.
Step 6 Optional: Select the file that you want to delete permanently and click Delete on the right to
permanently delete the object.
You can also click the file and delete the version without the deletion mark from the Versions
list to permanently delete the version.
NOTE
If all the versions of the deleted file are deleted with no historical version, you cannot undelete the file.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
l At least one file has been uploaded and the file can be accessed only using the URL.
l Ensure that DNS server IP addresses are correctly configured on the client environment
for OBS domain name resolution. Contact the administrator to obtain the IP addresses
from parameters TDNS-TNTP01-TENANT and TDNS-TNTP02-TENANT in the
parameter summary file xxx_export_all_EN.xlsm.
NOTE
If you access OBS from the Internet, ensure that the DNS server IP address of the Internet has
been configured on the client.
Context
OBS does not allow anonymous users to access objects uploaded after being encrypted using
KMS.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 6 In Public Permissions, click Edit to grant the read permission of the object to anonymous
users.
The URL is displayed on the page, which is in the format of bucket name.endpoint/object
name. After sending the URL to an anonymous user, the anonymous user can access the
object by copying the URL to the web browser.
NOTE
If the DNS server IP address is not configured on the client, you can change the access domain name of
the bucket to endpoint/bucket name and then copy it to the browser for access.
----End
If a bucket ACL and a bucket policy are used at the same time and they conflict with each
other, the bucket policy prevails.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Context
By configuring ACL permissions for an object, the object access permissions can be granted
to five types of users, as shown in Table 3-11.
Bucket owner The bucket owner refers to the tenant that creates the bucket.
By default, the bucket owner has all access rights to the bucket. It
owns the read and write permissions of the bucket ACL
permanently and this status cannot be modified.
NOTE
If the read and write permission of the bucket ACL is removed, users cannot
obtain the object list in the bucket or upload objects to the bucket. You are
not advised to change the permissions of the bucket owner.
Anonymous users Anonymous users are users not registered with OBS.
If the permissions to access an object are granted to anonymous
users, everyone can access the object without identity
authentication.
NOTE
To ensure data security, do not use the bucket ACL to grant the bucket
access permissions to anonymous users.
Specific users The bucket owner can specify resource management tenants that
can access the bucket.
After the permissions are granted to a tenant, all users who have the
OBS resource permissions of the tenant can access the bucket. To
grant different permissions to different users, you can set bucket
policies. For details, see 3.1.7.5 Configuring a Bucket Policy.
Log delivery users Log delivery users deliver access logs of the bucket and objects.
OBS does not create or upload any file to a bucket automatically.
Therefore, if you want to record access logs for a bucket, you need
to grant the permission to log delivery users who will deliver the
access logs to your specified bucket. This user group is only used to
record internal logs of OBS.
NOTICE
After logging is enabled, the bucket write permission, as well as the ACL
read permission will be enabled automatically for log delivery users of the
target bucket. If you manually disable such permissions, bucket logging
fails.
OBS supports five types of bucket access permissions, which are described in Table 3-12.
Bucket access Read Permission to obtain the object list and metadata of a
permissions bucket.
Full control Full control Permission to fully control a bucket and objects in the
bucket. A user granted with this permission possesses
all the permissions mentioned above.
NOTE
Users assigned this permission can fully control the bucket
and its objects. Exercise caution when assigning this
permission to any user.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 4 Click Edit to set ACL permissions for the owners, anonymous users, registered users, and log
delivery users for the object.
Step 5 Click Add. Enter the Tenant ID or Tenant Name of a specific user and set ACL permissions
for the user.
NOTE
l You can view the Tenant ID and Tenant Name on the My Account page after logging in to
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l If no ACL permission is specified for a new bucket, OBS automatically disables the access to the
bucket and objects in it by other users except the bucket owner.
----End
Follow-up Procedure
You can click Delete to delete the permissions of a specific user if necessary.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Precautions
Not all the users of a tenant can access the objects uploaded to an exclusive bucket by an
authorized user of the tenant. The bucket owner can access the objects only after it is
authorized to.
Context
When an exclusive bucket is created, the system automatically generates two exclusive bucket
policies by default. The two policies are displayed on the top of the bucket policy list to
identify the access mode of the bucket. OBS administrators can view and manage exclusive
bucket policies in the bucket policy list.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 6 Configure a bucket policy. For details about the parameters, see Table 3-13.
Parameter Description
Principal Indicates the ID of the tenant or user on which the bucket policy
takes effect.
l Include: Specifies the user on which the bucket policy takes
effect.
l Exclude: Specifies the user on which the bucket policy does
not take effect.
l User: Select an existing user.
l Others: Enter a valid principal.
NOTE
You can click the user name in the upper-right corner of ManageOne
Operation Portal (ManageOne Tenant Portal in B2B scenarios) and
choose My Account to view the tenant ID and user ID.
Resource Indicates the resources that the bucket policy applies to.
Resources are separated by commas (,). A wildcard character (*)
indicates all resources in the bucket. If no resource is specified,
the policy applies to the bucket and all objects in the bucket.
l Include: Specifies the OBS resources on which the bucket
policy takes effect.
l Exclude: Specifies the OBS resources on which the bucket
policy does not take effect.
The resource type is related to the action:
l When a resource is an object or object set, only the actions
related to the object can be configured.
l When the resource is a bucket, only the actions related to the
bucket can be configured.
Parameter Description
Condition Specify conditions under which the bucket policy takes effect.
For details, see 3.1.14.2 What About Details of Actions and
Conditions?.
NOTE
This parameter is valid only when Policy Mode is set to Customized.
You can view the new bucket policy in the bucket policy list.
If the policy of an exclusive bucket is edited, the access mode of the exclusive bucket will
become shared and cannot be changed back to exclusive. Exercise caution when performing
this operation.
Step 9 Select a bucket policy that is no longer used and click Delete.
If the policy of an exclusive bucket is deleted, the access mode of the exclusive bucket will
become shared and cannot be changed back to exclusive. Data in the bucket may become
insecure or cannot be accessed. Exercise caution when performing this operation.
----End
Typical Scenarios
1. Grant permissions to an OBS tenant. In the following example, the tenant (whose ID is
783fc6652cf246c096ea836694f71855) needs to be assigned the permission to obtain the
2. Grant permissions to an OBS user. In the following example, the user (whose ID is
71f3901173514e6988115ea2c26d1999) of the tenant (whose ID is
783fc6652cf246c096ea836694f71855) needs to be assigned the permission to obtain the
log management information about the logging.bucket3 bucket. You need to manually
configure the parameters. For details, see Table 3-15.
4. Limit the start time and end time of accessing objects in a bucket. In the following
example, the start time and end time of accessing all objects in bucket mybucket by all
users need to be set. You need to manually configure the parameters. For details, see
Table 3-17.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
l At least one object has been uploaded.
Context
By configuring ACL permissions for an object, the object access permissions can be granted
to four types of users, as shown in Table 3-18.
Object owners Object owners are the bucket creator and other users in the same
tenant with the bucket creator. Object owners always have the ACL
read and write permissions by default.
Anonymous users Anonymous users are users not registered with OBS.
If the access permissions for an object are granted to anonymous
users, everyone can access the object without identity
authentication.
NOTE
To ensure data security, you are not advised to grant object access
permissions to anonymous users by configuring ACL permissions.
Specific users Specific users are the resource management tenants that are granted
the access permissions by the object owners.
OBS supports the following types of object access permissions, as described in Table 3-19.
Full control Full Permission to fully control an object. A user granted with this
control permission possesses all the permissions mentioned above.
NOTE
A user granted with the full control permission can fully control an
object. Exercise caution when granting this permission to any user.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 6 Click Edit to set ACL permissions of the object for the owners, anonymous users, and
registered users.
Step 7 Click Add. Enter the Tenant ID or Tenant Name of a specific user and set ACL permissions
for the user.
NOTE
l You can view the Tenant ID and Tenant Name on the My Account page after logging in to
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l If no ACL permission is assigned for a new object, OBS automatically disables the access to the
object by users except the object owners.
l ACL permissions cannot be configured for an object encrypted using KMS.
----End
Follow-up Procedure
You can click Delete to delete the permissions of a specific user if necessary.
3.1.8 Versioning
Versioning is an effective means to restore objects that are overwritten or deleted incorrectly.
By default, versioning is disabled for new buckets in OBS. New objects will overwrite the
existing objects with the same names as the new ones in a bucket.
l When an object is uploaded, OBS automatically allocates a unique version ID for the
object. Objects with the same name are stored in OBS with different version IDs.
l An object can be downloaded by specifying a version ID. By default, the latest object is
downloaded if no version ID is specified.
l To delete an object permanently, specify the version ID. A permanently deleted object
cannot be restored. If an object is deleted with no version ID specified, OBS will
generate a deletion mark with a unique version ID for the object but will not actually
delete the object.
l The latest objects in a bucket are returned by default after a GET Object request. You can
also send a request to obtain the bucket's objects with all version IDs.
When versioning is no longer required for objects in a bucket, you can disable it. Old version
data remains in OBS. You need to manually delete unnecessary old version data.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Context
Once versioning is enabled, objects with the same name are stored in a bucket with different
version IDs.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 5 You can also select Suspend to disable versioning for objects in the bucket.
Disabling the versioning will not affect the existing historical versions of objects.
Step 6 Click OK.
----End
Follow-up Procedure
After versioning is enabled, you can go to the object details page to view, download or delete
versions of an object.
1. In the navigation tree on the left, click Objects.
2. Click the object.
3. On the Versions tab page, view all versions of the object.
4. Download and delete versions of the object.
– You can download a version of the object by clicking Download on the right of the
version.
– You can delete a version of the object by clicking Delete on the right of the version.
If you delete the latest version, the most recent version will become the latest
version.
3.1.9 Logging
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Context
Only the OBS administrator role can configure logging for a bucket. OBS restricted
administrator and read-only user roles can only view logs even when they are granted with the
permission.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
NOTE
After logging is enabled, generated logs are named in the following format:
<TargetPrefix>YYYY-mm-DD-HH-MM-SS-<UniqueString>
– <TargetPrefix> is the specified log name prefix.
– YYYY-mm-DD-HH-MM-SS indicates the date and time when the log is generated.
– <UniqueString> indicates a character string generated by OBS.
If <TargetPrefix> ends with a slash (/), logs generated in the bucket will be stored in a folder
named <TargetPrefix> to facilitate management.
For example:
– If Target Bucket is bucket and Target Prefix is bucket-log/, all logs will be stored in the
bucket-log/ folder in the target bucket. An example log file name is as follows:
2015-06-29-12-22-07-N7MXLAF1BDG7MPDV.
– If Target Bucket is bucket and Target Prefix is bucket-log, all logs are directly stored in the
target bucket. An example log file name is as follows: bucket-log2015-06-29-12-22-07-
N7MXLAF1BDG7MPDV.
The value of Target Prefix cannot exceed 254 bytes and consists of one or more folder names.
Folder names are separated by a slash (/). The naming rules are as follows:
– The target prefix cannot contain special characters \:*?"<>|.
– The target prefix cannot start with a slash (/) or contain more than two adjacent slashes (/).
– The target prefix and folder name cannot start or end with a period (.).
----End
l Some periodically uploaded files only need to be retained for one week or one month,
and can be deleted once they have expired.
l Some documents are frequently accessed in a period of time. After the period of time,
they will not be accessed and need to be deleted.
You can make lifecycle management rules to identify the objects and manage lifecycles of the
objects based on the rules.
l Configuration policy: You can specify the prefix of object names so that objects whose
names have this prefix are restricted by the rules. You can configure lifecycle
management rules for a bucket so that all objects in the bucket can be restricted by the
rules.
l Expiration time: You can specify the number of days since the last object update or a
date after which objects restricted by the rules should expire and be automatically
deleted.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
l If Object name prefix is selected and the specified prefix overlaps with the prefix specified in an
existing rule, OBS considers the two rules as one rule and disables the new rule. For example, if a
rule configured using the abc prefix exists in the system, you cannot configure a new rule containing
abc in its prefix.
l If a rule whose Applies To is set to Object name prefix has been configured, you cannot configure
a new rule whose Applies To is set to Bucket.
l If a rule whose Applies To is set to Bucket has been configured, you cannot configure a new rule
whose Applies To is set to Object name prefix.
l Expiration Time: Specifies whether the objects managed by the rule will be
automatically deleted after the last update.
l Delete After: Specifies the number of days after which objects will expire and be
automatically deleted.
NOTE
l Current Version and Historical Version are available only when Versioning is enabled. When
Versioning is enabled, uploading objects with the same name to the same path generates different
versions. The object uploaded the most recently is the Current Version, and the object uploaded
earlier is the Historical Version.
l You can configure either, both, or neither of the versions.
For example, the following files were saved in OBS on January 7, 2017:
l log/test1.log
l log/test2.log
l doc/example.doc
l doc/good.txt
The following files were saved in OBS on January 10, 2017:
l log/clientlog.log
l log/serverlog.log
l doc/work.doc
l doc/travel.txt
If the Delete After of objects prefixed with log/ is set to 1 day on January 10, 2017, objects
log/clientlog.log, log/serverlog.log, log/test1.log, and log/test2.log will be deleted from OBS
on January 12, 2017.
NOTE
The deletion of an object may be delayed after the object expires. Generally, the delay does not exceed
48 hours.
----End
Follow-up Procedure
You can edit, delete, and disable the configured rule later if necessary.
The following functions are added to the static website hosting to meet various requirements:
l Configure, view, and disable static website hosting on static websites.
l Configure, view, and delete the homepage and error pages.
l Configure, view, and delete redirection rules.
l Configure, view, and delete request redirection tasks.
If the structure, address, or file name extension of a website is changed, users will fail to
access the website using the old address (such as the address saved in folder of favorites), and
the 404 error message is returned. After redirection is configured for a website, users who
access the domain name can be redirected to the specified page to avoid 404 access errors.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
l Web page files required by the static website have been uploaded to the specified bucket.
To ensure that a hosted static website can be accessed by all users, grant the Read
permission of the bucket storing static website files to anonymous users and configure a
bucket policy allowing anonymous users to access static website files in the bucket,
ensuring that the users have sufficient access permissions for desired objects. For details
about how to configure permissions, see 3.1.7.6 Configuring ACL Permissions for an
Object.
l Ensure that DNS server IP addresses are correctly configured on the client environment
for OBS domain name resolution. Contact the administrator to obtain the IP addresses
from parameters TDNS-TNTP01-TENANT and TDNS-TNTP02-TENANT in the
parameter summary file xxx_export_all_EN.xlsm.
NOTE
l In an ECS environment, ensure that the DNS server IP address of the ECS is the same as that
of the VPC associated with the ECS.
l If you access OBS from the Internet, ensure that the DNS server IP address of the Internet has
been configured on the client.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 3 In the navigation tree on the left, click Static Website Hosting.
Step 4 Click the Static Website Hosting tab page and select Use this bucket to host a website.
Step 5 In the textbox of Default Home Page, set the default homepage.
Home Page: specifies the default homepage of the static website. When OBS Console is used
to configure static website hosting, only HTML web pages are supported. When APIs or
SDKs are used to configure static website hosting, OBS does not have such a restriction but
the Content-Type of objects must be specified.
OBS only allows files such as index.html in the root directory of a bucket to function as the
default homepage. That is, do not set the default homepage with a multi-level directory
structure (for example, /page/index.html).
Step 6 Optional: Configure Default 404 Error Page.
Default 404 Error Page: specifies the error page returned when an error occurs during static
website access.
When OBS Console is used to configure static website hosting, only HTML web pages are
supported. When APIs or SDKs are used to configure static website hosting, OBS does not
have such a restriction but the Content-Type of objects must be specified.
NOTE
When an error occurs during the access to a static website and you have configured a customized error
document for the website, the browser displays the error message and ignores the error document
returned by the OBS.
l Internet Explorer
Open Internet Explorer, choose Internet Options, and select Advanced. Find display friendly
HTTP error information and deselect the option. If the configured 404 error page contains more
than 512 characters, you do not need to set this option.
l Google Chrome and Firefox
This problem is caused by the browser settings and does not need to be modified.
Requests that comply with the redirection rules are redirected to a specific host or page.
Redirection rules are compiled in the JSON or XML format. Each rule contains a Condition
and a Redirect. The following is an example:
[
{
"Condition": {
"KeyPrefixEquals": "folder1/"
},
"Redirect": {
"HostName": "www.example.com"
}
},
{
"Condition": {
"KeyPrefixEquals": "folder2/"
},
"Redirect": {
"ReplaceKeyPrefixWith": "folder3/"
}
}
]
After the static website hosting settings take effect in OBS, you can use the following domain
names to access the static website: If you successfully access the website using the following
domain names, static website hosting is successfully configured.
https://bucket name.static website hosting domain name
http://bucket name.static website hosting domain name
----End
Related Operations
You can select Disable website hosting to disable static website hosting when needed.
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l Web page files required by the static website have been uploaded to the specified bucket.
NOTE
To ensure that a hosted static website can be accessed by all users, grant the Read permission of the
bucket storing static website files to anonymous users and configure a bucket policy allowing
anonymous users to access static website files in the bucket, ensuring that the users have sufficient
access permissions for desired objects. The configuration of static website hosting takes effect within
two minutes after the configuration.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 3 In the navigation tree on the left, click Static Website Hosting.
Step 4 Click the Static Website Hosting tab page and select Redirect requests.
Step 5 In the textbox of Redirect to, enter the bucket access domain name or URL.
NOTE
l After changing the destination address for redirection, you must manually clear the browser cache so
that requests will be redirected to the new destination address.
For example, if the original destination address for redirection is www.example.com, the system
automatically jumps to www.example.com after you access the static website hosting address (or
replicate the address to another browser). After changing the destination address for redirection to
www.test.com, you must clear the browser cache. By doing so, when you access the static website
hosting address, the system automatically jumps to www.test.com. Otherwise, the system will still
jump to www.example.com.
l If the redirection address is enabled, you must manually clear the browser cache before disabling the
static website hosting function.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one bucket has been created.
l Static website hosting has been configured.
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 3 In the navigation tree on the left, click Static Website Hosting.
Step 6 In the CORS Rule dialog box, configure Allowed Origin, Allowed Method, Allowed
Header, Exposed Header, and Cache Duration (s).
Parameter Description
Allowed Origin Specifies the origin of cross-origin requests. That is, requests from the
origin can access the bucket. This parameter is mandatory.
You can enter multiple origins. Enter one origin at one line, and at
most one wildcard character (*) is allowed for one origin. For
example:
www.example.com
*.obs.example.com
http://www.example.com
https://www.example.com
Allowed Method Specifies the method of cross-origin requests, that is, the operation
type of buckets and objects. This parameter is mandatory. The
methods include GET, POST, PUT, DELETE, and HEAD.
Allowed Header Specifies the allowed header of cross-origin requests. This parameter
is optional. Only CORS requests matching the allowed header are
valid.
You can enter multiple allowed headers (one per line) and each line
can contain one wildcard character (*) at most. Spaces and special
characters including &:< are not allowed.
Cache Duration Specifies the duration that your browser can cache CORS responses,
(s) expressed in seconds. The default value is 100. The default value is
100. This parameter is mandatory.
When Rule added successfully is displayed in the upper part of the page, the CORS
configuration is successful and will take effect in two minutes.
After CORS is successfully configured, only the addresses specified in Allowed Origin can
access the bucket in OBS using the method specified in Allowed Method. For example, if
you configure CORS parameters of bucket testbucket as follows: Allowed Origin:
www.examlple.com; Allowed Method: GET; Allowed Header: left blank; Exposed
Header: left blank; Cache Duration (s): 100, only GET requests from www.example.com are
allowed to access the bucket, there is no requirement for the request headers, and the clients
where the requests are generated can cache the requests for 100 seconds.
----End
Related Operations
You can click Edit or Delete to edit or delete a configured CORS rule based on site
requirements.
NOTE
After the Cache Duration (s) is modified, you need to manually clear the browser cache for the
modification to take effect.
Prerequisites
You have obtained a VDC administrator account or a VDC operator account for logging in to
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
Procedure
Step 1 Log in to OBS Console as a VDC administrator or a VDC operator. For details, see Logging
In to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the bucket.
Step 3 In the navigation tree on the left, click Static Website Hosting.
l Referrer format: You can enter website domain names as referrers. Referrers are
separated by newline characters. An example is provided as follows:
www.example.com
http://www.example1.com
https://www.example2.com
l When Whitelisted Referers is empty while Blacklisted Referers is not, all websites
except specified ones in the blacklist are allowed to access data in the bucket.
l When Whitelisted Referers is not empty while Blacklisted Referers is empty or not
empty, only specified websites in the whitelist are allowed to access data in the bucket.
NOTE
If the content of Whitelisted Referrers is the same as that of Blacklisted Referrers, the blacklist
takes effect. For example, if both Whitelisted Referrers and Blacklisted Referrers are set to
http://www.example.com, the access request is blocked.
l If both Whitelisted Referrers and Blacklisted Referrers are left blank, all websites can
access data in the bucket by default.
l Before determining whether a user has the four types of permissions (read, write, ACL
read, ACL write) for a bucket or objects in the bucket, check whether the user complies
with the URL validation principles of the Referrer field.
If you need to download objects in the bucket on ManageOne Operation Portal (ManageOne Tenant
Portal in B2B scenarios), configure the domain name (for example, https://console.xxx.com) of
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios) in Blacklisted Referrers.
----End
3.1.14 FAQs
Prerequisites
l You have obtained the non-OBS administrator account and password for logging in to
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l You have obtained the name of the to-be-viewed bucket and had the read or write
permission for this bucket.
Procedure
Step 1 Use a browser to log in to ManageOne as a non-OBS administrator.
l URL in non-B2B scenarios: https://address to access ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://address to access ManageOne Tenant Portal, for
example, https://tenant.demo.com
l Account password: username and password of the non-OBS administrator
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
Step 4 In the upper right corner of the page, click View Bucket.
l Only the buckets of the current tenant can be viewed. Buckets cannot be viewed across tenants.
l Historical bucket viewing records can only be saved in the current tab page. If you change the tab
page or log out, you need to query the buckets again.
----End
Table 3-22 lists the general types of conditions that you can specify in a bucket policy.
A condition can contain either of the two types of keys: general keys and action-specific keys.
For details, see Table 3-23 and Table 3-24.
ListBucket prefix Type: String. Lists objects that begin with the
specified prefix.
Procedure
Step 1 Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation Portal, for
example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
Step 2 Select your region and then project from the drop-down list on the top menu bar.
Step 3 On the navigation bar, click Console and choose Storage > Object Storage Service.
----End
3.2 HDFS
3.2.1 Introduction
Definition
Hadoop Distributed File System (HDFS) is a highly reliable, high-performance, and scalable
distributed file system. It is one of the major components of the open-source Hadoop. It is
designed to store massive volumes of data and provide high-throughput data access. It is
applicable to big data storage and large-scale dataset applications.
HDFS allows you to manage and access data in a Hadoop distributed file system. You can use
a distributed file system with unlimited capacity and performance expansion, single
namespace, multiple sharing, high reliability, and high performance without modifying
existing big data analysis applications.
HDFS meets the big data computing and storage requirements of the customers in the Internet
and finance industries. It applies to scenarios where massive data is stored and offline
computing is performed. HDFS satisfies the requirements for distributed storage performance,
capacity, and reliability in distributed computing services such as Hadoop.
Functions
HDFS provides basic namespace operations, including creating, viewing, modifying, and
deleting namespaces.
Namespace
A namespace is the basic unit of HDFS. User files and directories are stored in namespaces.
HDFS supports the traditional hierarchical file structure. Users or applications can create
directories and save the files in these directories. The hierarchy of the HDFS namespace is
similar to that of most existing file systems. Users can create, delete, move, or rename files.
Quota
Quota restricts the resources that a user can use. Quota is the upper limit of available
resources and storage capacity.
An OBS administrator can set a capacity quota for a namespace to limit the upper limit of
storage space that can be used by the namespace.
QoS
(Quality of Service) QoS allows you to effectively use existing resources to deliver high-
quality services for key applications. By configuring QoS, users can control the resources in a
better way with reduced costs and high customer satisfaction.
l Open architecture
– It provides universal and standard APIs to be efficiently compatible with the users'
current applications.
– It provides big data storage compatible with HDFS interfaces, supporting
interconnection with solutions, and providing various upper-layer service
applications.
l High performance and scalability
– The HDFS big data storage adopts a fully symmetric architecture and supports
flexible and seamless expansion.
– HDFS provides high throughput, high IOPS, and low latency for application loads.
In addition, its performance increase linearly with the capacity, meeting the
requirements for higher capacity and storage performance when service increases.
l Security and reliability
– Access keys and permission control are used to ensure secure data access, data
transmission, and validation.
– It supports high-reliability networking across multiple regions and adopts Erasure
Code (EC) data storage, ensuring high data reliability.
Architecture
Figure 3-10 shows the HDFS logical architecture.
Workflow
Figure 3-11 shows the HDFS workflow.
For details about the roles and permissions of the HDFS and OBS shared users, see 3.1.1.7
User Roles and Permissions
l Web UI
Log in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios) as
a tenant user and select the cloud service on the Console menu.
l API
If you want to integrate the cloud service into a third-party system for secondary
development, you can access the cloud service using API. For details, see Operation
Help Center.
Table 3-26 lists the operators and user interfaces (UIs) for each step.
Prerequisites
You have obtained a VDC administrator account or a VDC operator account for logging in to
ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
Context
A storage domain contains a maximum of 64 namespaces.
Procedure
Step 1 Access OBS Console as a VDC administrator or VDC operator. For details, see Logging In
to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the Namespace tab.
Step 3 In the upper right corner of the page, click Create Namespace and set related parameters.
For details, see Table 3-27.
Parameter Description
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one namespace has been created.
Procedure
Step 1 Access OBS Console as a VDC administrator or VDC operator. For details, see Logging In
to OBS Console as a VDC Administrator or a VDC Operator.
Used Storage Capacity Storage space occupied by directories and files stored in the
namespace.
Step 5 In the Basic Information area, view the basic information about the namespace.
Table 3-29 describes the basic information about the namespace.
Access Domain Name Domain name address of the namespace, which can be applied
to the scenario where the namespace is accessed directly
through the domain name.
The format of the domain name is as follows: Namespace
name .Endpoint.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one namespace has been created.
Procedure
Step 1 Access OBS Console as a VDC administrator or VDC operator. For details, see Logging In
to OBS Console as a VDC Administrator or a VDC Operator.
Step 3 Use either of the following methods to access the page for modifying configuration
parameters:
l Click Parameter Management in the row where the namespace resides.
l Click the namespace of which you want to modify parameters, and then click the
Parameter Management tab.
Step 4 Click Edit Parameter to modify the configuration parameters of the namespace.
Super User Group Specifies the name of the super user group. supergroup
The naming rule is as follows:
l The length is 3 to 32 characters.
l A name contains uppercase letters, lowercase
letters, digits, underscores (_), and hyphens
(-).
l The name can start with a hyphen or digit and
cannot start with a hyphen (-).
Duration of Files Indicates the period of time for which files are 0
Stored in the retained in the recycle bin. After this period of
Recycle Bin time, the junk files will be deleted. If the value is
0, the file recycling mechanism is disabled.
Unit: day, hour, minute
Value range:
l 0 to 2982616 days
l 0 to 71582788 hours
l 0 to 4294967295 minutes
RPC Encryption Sets whether the RPC channel of each module in Privacy
the Hadoop is encrypted. The setting takes effect
globally.
There are three RPC encryption modes:
l Privacy: Indicates that channel encryption is
enabled. The authentication, integrity, and
privacy functions are enabled.
l Integrity: Indicates that encryption is disabled
and the authentication and integrity functions
are enabled.
l Authentication: Indicates that encryption is
disabled. Only authentication packets are
required. Integrity and privacy are not
required.
NOTICE
After the configuration is modified, you need to restart
the HDFS service and upper-layer services that depend
on the HDFS, and rolling restart is not supported.
Services will be interrupted during the restart.
Therefore, exercise caution when performing this
operation.
Proxyuser Indicates the user who can proxy other user None
rights.
The naming rules of proxy users are as follows:
l The length is 3 to 32 characters.
l A name contains uppercase letters, lowercase
letters, digits, underscores (_), and hyphens
(-).
l The name can start with a hyphen or digit and
cannot start with a hyphen (-).
Groups Indicates the user groups that proxy users can None
proxy.
Naming rules:
l A name contains 3 to 32 characters.
l A name contains uppercase letters, lowercase
letters, digits, underscores (_), and hyphens
(-).
l The name can start with a hyphen or digit and
cannot start with a hyphen (-).
l Names are separated by commas (,). A
maximum of 32 names can be entered. The
asterisk (*) can be used to match all names.
NOTE
You need to configure at least one of Groups and
Users.
Users Indicates the users that proxy users can proxy. None
Naming rules:
l A name contains 3 to 32 characters.
l A name contains uppercase letters, lowercase
letters, digits, underscores (_), and hyphens
(-).
l The name can start with a hyphen or digit and
cannot start with a hyphen (-).
l Names are separated by commas (,). A
maximum of 32 names can be entered. The
asterisk (*) can be used to match all names.
NOTE
You need to configure at least one of Groups and
Users.
LDAP Mapping Indicates whether to enable the LDAP mapping. Not selected.
Policy NOTE
When Enable LDAP Mapping is selected, the
following parameters are valid.
SSL Certificate Indicates the SSL certificate file used for None
connecting to the LDAP server.
The certificate file name extension is .pem. The
file size does not exceed 4 KB.
LDAP Directory Searches for the node where the users and groups None
are located.
The value is a string of no more than 128
characters.
LDAP Login User User name for logging in to the LDAP server. None
The naming rule is as follows:
l The length is 3 to 32 characters.
l A name contains uppercase letters, lowercase
letters, digits, underscores (_), and hyphens
(-).
l The name can start with a hyphen or digit and
cannot start with a hyphen (-).
LDAP Member Indicates the filter criteria for querying LDAP &
Query Filter group users. (objectClass=us
Criteria The value is a string of no more than 128 er)
characters. (sAMAccountN
ame={0})
LDAP Group Indicates the filter criteria for querying LDAP objectClass=gro
Query Filter groups. up
Criteria The value is a string of no more than 128
characters.
Timeout Threshold Indicates the period of time after which the 10000 ms
for Connecting to connection to the LDAP server times out.
LDAP Value range: 0 to 4294967295.
Unit: ms
Timeout Threshold Indicates the period of time after which the LDAP 10000 ms
for Reading Data server reading data times out.
Value range: 0 to 4294967295.
Unit: ms
Mapping Group Specifies the name of the local mapping group. None
Name Naming rules:
l The length is 3 to 32 characters.
l A name contains uppercase letters, lowercase
letters, digits, underscores (_), and hyphens
(-).
l The name can start with a hyphen or digit and
cannot start with a hyphen (-).
NOTE
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l At least one namespace has been created.
Context
If QoS has already been configured for the namespace, this operation will overwrite the
existing QoS.
Procedure
Step 1 Access OBS Console as a VDC administrator or VDC operator. For details, see Logging In
to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click the Namespace tab.
Step 3 Use either of the following methods to access the page for modifying QoS parameters:
l Click QoS Management in the row where the namespace resides.
l Click the namespace of which you want to modify QoS parameters, and then click the
QoS Management tab.
Step 4 Click Edit QoS to modify the QoS parameters of the namespace.
Table 3-34 describes the QoS parameters.
IOPS (KB/s) Indicates the read and write times every second of 0
every KB of a disk.
Value range: 0 to 90173050474390.
----End
Prerequisites
l You have obtained a VDC administrator account or a VDC operator account for logging
in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios).
l The namespace in use or having files cannot be deleted directly.
l Only the owner of a namespace can delete the namespace.
Procedure
Step 1 Access OBS Console as a VDC administrator or VDC operator. For details, see Logging In
to OBS Console as a VDC Administrator or a VDC Operator.
Step 2 Click Delete in the row where the namespace resides.
NOTE
l If the namespace is in use or has files, you can clear the namespace or delete the namespace forcibly
as prompted.
l A namespace of the same name can be created in another VDC only after the namespace is deleted
for at least 30 minutes.
----End
4 Best Practice
Bucket Description
A bucket is a container that stores objects in OBS. OBS provides flat storage in the form of
buckets and objects. Unlike the conventional multi-layer directory structure of file systems,
all objects in a bucket are stored at the same logical layer.
In OBS, each bucket name must be unique and cannot be changed. When a bucket is created,
its access control list (ACL) is generated by default. The items in the ACL include
permissions of authorized users such as the read (READ), write (WRITE), and full control
(FULL_CONTROL) permissions. Only authorized users can perform bucket operations, such
as creating, deleting, viewing, and configuring the bucket ACL. A user can create a maximum
of 100 buckets. However, the number and total size of objects in a bucket are not restricted.
Users do not need to worry about system scalability.
As OBS is based on REST HTTP and HTTPS, you can use uniform resource locators (URLs)
to locate resources.
Introduction to AK/SK
Access Key ID (AK)/Secret Access Key (SK) is an authentication certificate pair. OBS
(compatible with Amazon S3 APIs) authenticates requests using AKs and SKs. Tenants and
users use AKs and SKs to access the system. OBS (compatible with Amazon S3 APIs)
identifies tenants and users based on the AKs and SKs.
l AK: One AK belongs to only one tenant or user, but one tenant or user can have two
AKs. OBS (compatible with Amazon S3 APIs) identifies a tenant or user accessing the
system based on the AK.
l SK: An SK together with a request header is used to generate authentication information.
An SK corresponds to an AK.
Requirement Analysis
The analysis based on user requirements is as follows:
1. OBS is an object-based massive storage service that provides secure, reliable, and low-
cost data storage capabilities. It is suitable for storing files of any type and size.
2. Users can use a third-party client to upload images and videos to buckets and download
them to a local computer. It meets users' requirements for storage and usage.
3. This document uses the third-party client OBS Browser as an example.
Configuration Roadmap
Users can upload files to a bucket on OBS Console and download the files using access keys.
The configuration roadmap is as follows:
1. Create a bucket.
2. Add access keys.
3. Connect to OBS using OBS Browser.
4. Upload files to the bucket using OBS Browser.
5. Download the file to a local computer using OBS Browser.
Figure 4-2 shows the configuration process based on the preceding analysis.
Procedure
Step 1 Create a bucket.
1. Log in to ManageOne as a VDC administrator or VDC operator using a browser.
URL in non-B2B scenarios: https://Address for accessing ManageOne Operation
Portal, for example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal, for
example, https://tenant.demo.com
2. Select your region and then project from the drop-down list on the top menu bar.
3. On the navigation bar, click Console and choose Storage > Object Storage Service.
4. Click Create Bucket in the upper right corner of the page.
Quota Limited Select No Limit. The quota of the bucket will not be limited,
(GB) but the capacity of objects that can be uploaded to the bucket
cannot exceed the available capacity quota of the bucket.
A maximum of two valid access keys can be added for each user.
4. Click OK to download the credentials.csv access key file to the local computer.
NOTE
The access key file can be downloaded only once. Keep it secure.
domain name:server port number (The HTTPS port number is 443 and the HTTP
port number is 80.)
– Access Key ID/Secret Access Key
Enter the AK/SK recorded in Step 3.1.
– Access Path
You can enter the bucket name or object path. After the login is successful, the
bucket or object is accessed.
– Remember my secret access key
This option is selected by default. If you deselect it, you must input the secret
access key each time when you log in to OBS Browser.
Step 4 Upload files to the bucket using OBS Browser.
1. Click the bucket name. On the object list page that is displayed, click Upload > Upload
File.
2. Click Select File to add the file to be uploaded to the file list, and click OK.
3. Click the task management icon in the upper right corner of the page to view the
download progress.
2. Click the task management icon in the upper right corner of the page to view the file
download progress.
----End
Service Scenario
An enterprise has a large number of files to archive but it does not want to invest much in
storage resources. Therefore, the enterprise subscribes to OBS for hosting static websites and
expects to access the static resources using user-defined domain names, as shown in Figure
4-3.
Data Planning
Table 4-2 describes the data to be planned before the configuration.
404 error page When the static website path is incorrect, error.html
the 404 error page is returned.
<html>
<head>
<title>Hello OBS!</title>
<meta charset="utf-8">
</head>
<body>
<p>Welcome to use OBS static website hosting.</p>
<p> This is the 404 error page.</p>
</body>
</html>
Configuration Roadmap
You need to create a bucket with the user-defined domain name in OBS Console to store static
website resources. Then enable static website hosting of the bucket, and create and configure
domain name hosting through the domain name registration provider. The procedure is as
follows:
Procedure
Step 1 Register a domain name.
If you do not have a registered domain name, register one with a registration provider of your
choice. In this scenario, the example domain name www.example.com is used. In practice,
replace the domain name with the one you actually planned.
The bucket name must be consistent with the user-defined domain name. Take the
www.example.com domain name in the data plan as an example. You need to create a bucket
named www.example.com by performing the following steps:
Quota Limited (GB) Select No Limit. The quota of the bucket will not be limited,
but the capacity of objects that can be uploaded to the bucket
cannot exceed the available capacity quota of the bucket.
NOTE
You cannot upload folders, upload a file larger than 5 GB, or batch upload files through OBS Console.
The website homepage file (index.html) and 404 error page (error.html) must be stored in the root
directory of the bucket.
9. Click Save.
Step 4 Configure static website hosting.
After uploading static website files, perform the following steps to set the bucket to the static
website hosting mode.
NOTE
You can also redirect all the static websites to another bucket or domain name. For details, see
Redirecting Requests to Another Host.
NOTE
You can also configure redirection rules based on service requirements to implement website
content redirection. For details, see Configuring Static Website Hosting.
5. Click OK. The configuration is complete.
Step 5 Create and configure domain name hosting.
Add an alias record to the domain name resolution of the domain name registration provider,
mapping to the static website domain name hosted by the bucket.
For example, the bucket www.example.com is located in the CN South-Guangzhou region,
and the added CNAME record is www.example.com CNAME www.example.com.obs-
website.cn-south-1.myhwclouds.com.
Step 6 Verify the configuration.
Enter www.example.com in the address bar of the browser to check whether the default
homepage can be accessed.
If the following information is displayed, the configuration is successful.
In the web browser, enter a static file access address that does not exist in the bucket, such as
www.example.com/imgs, to check whether the 404 error page can be returned.
If the following information is displayed, the configuration is successful.
----End
Service Scenario
A company department expects that internal data can be isolated between different
employees. That is, employees can only see and perform operations on the buckets and
objects they are authorized to.
Requirement Analysis
When creating a user in a VDC in the private cloud scenario, the creator is asked to select a
role for the user. Users of such roles as the preset VDC administrator and user-defined OBS
administrator have the same permissions with the OBS administrator. They cannot be
restricted to access bucket resources even if bucket policies intend to. In addition, the
capability of creating buckets in a VDC is defined by role. Therefore, roles and bucket
policies must be used together to control permissions of the employees.
Configuration Roadmap
Create a VDC with a default VDC administrator and a few non-OBS administrator users who
do not have any OBS permissions. Non-OBS administrator users must be authorized by the
VDC administrator if they want to have specific OBS permissions. By default, the VDC
administrator authorizes non-OBS administrator users to use specific buckets, but prohibits
the users from creating a bucket, changing the capacity quotas of the buckets, and accessing
other buckets. The process is as follows:
1. Create a non-OBS administrator role.
2. Create a VDC and a default VDC administrator.
3. Create non-OBS administrator users in the VDC.
4. Create a bucket and configure a bucket policy to grant permissions to non-OBS
administrators.
Procedure
Step 1 Create a non-OBS administrator role.
1. Log in to ManageOne as an operation administrator using a browser.
– URL in non-B2B scenarios: https://Address for accessing ManageOne Operation
Portal, for example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Operation
Management Portal, for example, https://admin.demo.com
– The default username of the operation administrator is bss_admin..
2. Choose Tenant > Role Management from the drop-down list box in the upper left
corner of the navigation bar.
3. In the upper right corner of the page, click Create Role.
You can select any management permissions as required except those in the OBS area.
7. Click Create.
8. Repeat Step 3.6 to Step 3.7 to create more non-OBS administrator users.
Step 4 Create a bucket and configure a bucket policy to grant permissions to the non-OBS
administrator users.
You can configure bucket access permissions for the users. In this way, different employees in
the same department can have different access permissions.
1. Log in to ManageOne as a VDC administrator using a browser.
– URL in non-B2B scenarios: https://Address for accessing ManageOne Operation
Portal, for example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Tenant Portal,
for example, https://tenant.demo.com
– Username and password: username and password of the VDC administrator
2. Select your region and then project from the drop-down list on the top menu bar.
3. On the navigation bar, click Console and choose Storage > Object Storage Service.
4. In the upper right corner of the page, click Create Bucket to create bucket obs-1234 and
configure bucket parameters.
9. Repeat Step 4.4 to Step 4.8 to configure read-only access policies for other buckets of
other non-OBS administrators.
NOTE
After the bucket policies are configured, non-OBS administrator users can use ManageOne
Operation Portal (ManageOne Tenant Portal in B2B scenarios) or a third-party client to view the
buckets they are authorized to. The users cannot obtain, view, or configure other buckets they are
not authorized to.
----End
Service Scenario
A company provisions second-level VDCs to its internal departments and requires that data
isolation between different employees and different departments. That is, employees can only
view buckets and objects authorized to them and cannot perform operations on other buckets
and objects.
Requirement Analysis
A first-level VDC needs to be created for each department. Object storage buckets need to be
created in the VDCs and be authorized to department users through the bucket policy to
control user permissions for buckets.
Configuration Impact
l OBS Console does not support bucket access across first-level VDCs. After a bucket is
authorized to a user, the user can access the bucket only through API or third-party
clients.
l The bucket administrator can view all buckets and objects in the VDC. (As shown in the
preceding figure, the administrator A can access buckets 01 and 02 and objects in the
buckets.) Therefore, a first-level VDC needs to be created for each department.
Configuration Roadmap
1. Create a VDC.
2. Create a bucket.
Procedure
Step 1 Create a VDC.
1. Log in to ManageOne as an operation administrator using a browser.
– URL in non-B2B scenarios: https://Address for accessing ManageOne Operation
Portal, for example, https://console.demo.com
URL in B2B scenarios: https://Address for accessing ManageOne Operation
Management Portal, for example, https://admin.demo.com
– The default username of the operation administrator is bss_admin..
2. Select Tenant > Tenant Management from the drop-down list box in the upper left
corner of the navigation bar.
3. Click Create Tenant in the upper right corner.
4. Create VDC obs_tenant_01 and default VDC administrator vdc_admin_01 as
prompted.
5. Repeat Step 2.4 to create a bucket for each user of the department in the new first-level
VDC.
Step 3 Configure a bucket policy.
1. In the bucket list, click the new bucket.
2. In the navigation tree on the left, click Permissions.
3. Click Bucket Policy.
4. Click Add Bucket Policy to configure the access policy for a specified user in the
department to a specified bucket.
For example, to grant the read and write permissions to bucket obs-1234 and all objects
in the bucket to user A of department 01, configure the bucket policy as follows:
Principal Select Include and Others, and enter the name of the
authorized user.
The format of an authorized user is tenant ID:user/user ID,
for example: 94f48e2d3dc04e9cab130ba912ed4efc:user/
393e529610ec4fd8871dbce4cdde5856.
NOTE
The tenant ID and user ID are the information of the authorized
user. Log in to ManageOne Operation Portal (ManageOne Tenant
Portal in B2B scenarios), click the user icon in the upper right
corner, and choose My Settings from the displayed menu. On the
My Settings page, view the tenant ID and user ID.
Resource Select Include and enter the name of specified bucket and
all objects in the bucket.
Resources are separated by commas (,). All objects in the
bucket in the format of Bucket name/* are supported. If no
resource is specified, the policy applies to the bucket and all
objects in the bucket.
5. Repeat Step 3.4 to configure bucket access policies for other users of department 01 and
other departments.
If the authorized user can use the access key to access the object storage service and upload an
object to and download an object form the bucket, the bucket is authorized successfully. For
details, see 4.1 Uploading and Downloading Files Using a Third-Party Client.
----End
Requirement Analysis
Department A and department B belong to different first-level VDCs. Example: Department
A shares data in the bucket to users in department B for download. This section describes how
to perform permission control on shared data based on the principle of least privilege.
Configuration Roadmap
In this scenario, department A administrator can use the bucket policy to control permissions
of users in department B so that they can download but cannot modify or delete the shared
data. Figure 4-4 illustrates the configuration process.
Procedure
Step 1 Create a bucket.
1. Log in to the HUAWEI CLOUD console as an administrator of department A. For
details, see 3.1.14.3 Logging In to OBS Console as a VDC Administrator or VDC
Operator.
2. Click Create Bucket in the upper right corner of the page.
3. Set bucket parameters and create bucket obs-1234 as prompted.
Principal Choose Include and User, and then select the name of the
authorized user.
Resource Select Include and enter the name of specified bucket and
all objects in the bucket.
Resources are separated by commas (,). All objects in the
bucket in the format of Bucket name/* are supported. If no
resource is specified, the policy applies to the bucket and all
objects in the bucket.
Principal Select Include and Others, and enter the name of the
authorized user.
The format of an authorized user is tenant ID:user/user ID,
for example: 94f48e2d3dc04e9cab130ba912ed4efc:user/
393e529610ec4fd8871dbce4cdde5856.
NOTE
The tenant ID and user ID are the information of the authorized
user. Log in to ManageOne Operation Portal (ManageOne Tenant
Portal in B2B scenarios), click the user icon in the upper right
corner, and choose My Settings from the displayed menu. On the
My Settings page, view the tenant ID and user ID.
Parameter Configuration
Resource Select Include and enter the name of specified bucket and
all objects in the bucket.
Resources are separated by commas (,). All objects in the
bucket in the format of Bucket name/* are supported. If no
resource is specified, the policy applies to the bucket and all
objects in the bucket.
Action Select Include, and select Get* and List* under General in
Action.
Step 4 Disable the write and delete permissions for users in department B.
1. In the bucket list, click the new bucket.
2. In the navigation tree on the left, click Permissions.
3. Click Bucket Policy.
4. Click Add Bucket Policy to configure the access policy for users in department B to a
specified bucket.
For example, to disable user test_2 in department B to write or delete bucket obs-1234
and all objects in the bucket, configure the following bucket policy parameters:
Principal Select Include and Others, and enter the name of the
authorized user.
The format of an authorized user is tenant ID:user/user ID,
for example: 94f48e2d3dc04e9cab130ba912ed4efc:user/
393e529610ec4fd8871dbce4cdde5856.
NOTE
The tenant ID and user ID are the information of the authorized
user. Log in to ManageOne Operation Portal (ManageOne Tenant
Portal in B2B scenarios), click the user icon in the upper right
corner, and choose My Settings from the displayed menu. On the
My Settings page, view the tenant ID and user ID.
Resource Select Include and enter the name of specified bucket and
all objects in the bucket.
Resources are separated by commas (,). All objects in the
bucket in the format of Bucket name/* are supported. If no
resource is specified, the policy applies to the bucket and all
objects in the bucket.
Action Select Include, and then select the following six actions of
Object from the drop-down box:
– PutObject
– PutObjectAcl
– PutObjectVersionAcl
– DeleteObject
– DeleteObjectVersion
– AbortMultipartUpload
The user in department A can upload data through OBS Console, OBS Browser, and
API&SDK. This section takes the operations on OBS Console as an example to describe how
to upload data.
After the permission is granted, users in department B can be authenticated using APIs,
SDKs, or third-party clients. This section takes OBS Browser as an example to present how to
verify that users in department B can only read the shared data.
1. Log in to OBS Browser as a department B user. For details, see Connect to OBS using
OBS Browser.
2. Click Add Bucket.
3. Select Add External Bucket and enter the name of the authorized bucket.
4. Click OK to add an external bucket.
5. Upload a file to the bucket. For details, see Upload files to the bucket using OBS
Browser.
– If the upload is successful, the write and delete permissions fail to be configured.
Check whether the bucket policy is correctly configured.
– If the upload fails, the write and delete permissions are successfully configured. Go
to Step 6.6.
6. Download a file from the bucket. For details, see Download the file to a local computer
using OBS Browser.
– If the download fails, the download permission configuration fails. Check whether
the bucket policy is correctly configured.
– If the download is successful, the download permission is configured successfully.
Go to Step 6.7.
7. Select a file to be deleted and click More > Delete on the right.
– If the file is deleted, the write and delete permissions fail to be configured. Check
whether the bucket policy is correctly configured.
– If the deletion fails, the write and delete permissions are successfully configured.
----End