Docs

Torch Object Storage

Getting Started

Getting started with TOS using the console

This topic provides a quick start guide for TOS. It includes steps for creating buckets and uploading, downloading, and sharing objects through the console.

Prerequisites

Before you begin using TOS, make sure you have signed up for a Volcano Engine account and completed real name verification. For instructions, see Account registration and Real Name Verification.

Step 1: Activate TOS

The first time you use TOS, you need to activate the service to access its full functionality.

Log in to the TOS console. In the dialog box, check the box that says I have read and agree to Storage products and service terms and click Activate Now.

tip

Skip this step if you have activated TOS.

Step 2: Create a bucket

Buckets are containers that hold your files or objects in TOS. You must create a bucket before uploading any objects.

In the left navigation pane, click Buckets. Then, in the upper-left corner of the displayed page, click Create bucket.

Set the bucket parameters and click Create.

Parameter			Description
Basic configurations	Name	Enter the name of the bucket. After you create the bucket, you cannot change its name. The bucket name must: Be globally unique within TOS, meaning no duplication is allowed across all regions and accounts. Consist only of numbers, hyphens (-), and lowercase letters (a-z). Start and end with a number or letter. Be between 3 and 63 characters long.
		Region	Select the region where you want to create a bucket. After you create a bucket, you cannot change its region.
		Versioning	Enable this feature to keep historical versions of overwritten and deleted objects.
		Bucket policy	The following options are available for the bucket policy: Private (Default): Only the bucket owner and authorized accounts have read and write permissions to objects. This is the recommended setting. Public read: All users have read access to objects and will incur data transfer charges. Allowing all users to read objects can cause data leaks and financial losses. We recommend setting the policy to Private instead. Public read/write: All users have full read and write access to objects and will incur data transfer charges. Allowing all users to read and write objects can cause data leaks and financial losses. We recommend setting the policy to Private instead. To enable more granular access control, configure bucket ACLs, bucket policies, and IAM policies after creating the bucket.
		Object ACL default policy	Enable Object ACL default policy to ensure newly uploaded objects inherit the bucket's ACL by default. If Object ACL default policy is not enabled, the object ACL policy will default to Private. tip For details on the relationship between object ACL and bucket ACL, see Managing object permissions using bucket ACLs.
		Project	(Optional) Select the project to which the bucket belongs from the drop-down list. tip A project is a virtual concept that comprises a set of resources, users, and roles. It provides a unified view of and access to resources, as well as control over user and role permissions within the project. For more information, see Resource management. To create a project, click Create new projects on the right. This will take you to the IAM console.
Advanced settings	Multi-AZ Redundancy	Select whether to enable Multi-AZ Redundancy. If you enable multi-AZ redundancy, TOS will store your data across multiple availability zones in the same region. This ensures that your storage service will be stable even if one zone fails. Learn more in Multi-AZ redundancy. tip Multi-AZ redundancy is currently only available in China (Beijing), China (Shanghai), China (Guangzhou), and Asia Pacific (Johor). For buckets with hierarchical namespace enabled, check the console to see if multi-AZ redundancy is available. Multi-AZ storage costs more than single-AZ storage. Once enabled, multi-AZ redundancy cannot be disabled. For details on how much it costs to store data in more than one AZ, check out Storage.
		Default storage type	Configure the storage type for the bucket. The storage types available in TOS are as follows: Standard Storage (Default): High availability, reliability, and performance, suitable for frequently accessed data. Infrequent Access Storage: Designed for less frequently accessed data with a minimum storage duration of 30 days. Intelligent Tiering: Automatically moves data between tiers based on how it is accessed, ideal for data with unpredictable access patterns. Flashback Archive: Optimized for rarely accessed data with a minimum storage duration of 90 days. Archive: Suited for long-lived, rarely accessed data with flexible latency requirements. The minimum storage duration is 90 days. Cold Archive: Suited for long-lived, rarely accessed data with flexible latency requirements. The minimum storage duration is 180 days. Deep Cold Archive: Cost-effective storage for extremely cold data with ultra-long retention needs. The minimum storage duration is 180 days. tip Cold Archive is only supported in China (Beijing), China (Shanghai), and China (Guangzhou). Deep Cold Archive is only supported in China (Beijing), China (Shanghai), and China (Guangzhou). Deep Cold Archive is currently in closed beta. Please contact your account manager for access. For more information, see Storage type. If you have enabled multi-AZ redundancy, you can only choose the storage type from the following options: Standard Storage (Multi-AZ), Infrequent Access Storage (Multi-AZ), and Flashback Archive (Multi-AZ). For more information on multi-AZ, see Multi-AZ redundancy.
		Server-Side encryption	Configure the server-side encryption method for the bucket. Once configured, all objects uploaded to the bucket will automatically inherit its encryption settings, unless otherwise specified. The available encryption options are: None: No encryption applied. SSE-TOS: TOS-managed encryption. Objects are encrypted automatically upon upload and decrypted during download using TOS-hosted keys. For more information, see Server-side encryption. SSE-KMS: Uses keys managed by Volcano Engine's Key Management Service (KMS) to encrypt and decrypt objects. For more information, see Server-side encryption. tip SSE-TOS and SSE-KMS are only available in China (Beijing), China (Shanghai), China (Guangzhou), China (Hong Kong), Asia Pacific (Johor), and Asia Pacific (Jakarta). If you are using SSE-KMS for server-side encryption for the first time, you must first activate KMS. Although activating KMS is free, using the service incurs charges. Using SSE-KMS for server-side encryption generates API call fees, and creating KMS keys generates key management fees. These fees are charged by KMS. For more information, see Key Management Billing Description.
		Encryption algorithm	Select the encryption algorithm for the key. Options include AES256 and SM4. tip This parameter only appears when SSE-KMS or SSE-TOS is selected for Server-Side encryption. The AES-256 algorithm is only available in China (Beijing), China (Shanghai), China (Guangzhou), China (Hong Kong), Asia Pacific (Johor), and Asia Pacific (Jakarta). The SM4 algorithm is only available in China (Beijing), China (Shanghai), and China (Guangzhou).
		Encryption Key Type	Custom Key is selected by default. tip This parameter only appears when SSE-KMS is selected for Server-Side encryption.
		Key Project	Select the project to which the custom key belongs. The system will then display the available custom keys under that project. To create a new project, click Create new projects. For more information, see Project management. tip This parameter only appears when SSE-KMS is selected for Server-Side encryption.
		Custom Key	Select a KMS key. TOS uses this key to encrypt objects in the bucket on the server. To use a new key, first create one by following the Key Management Quick Start guide. tip This parameter only appears when SSE-KMS is selected for Server-Side encryption.
		Log analysis	Select whether to enable Log analysis. TOS offers free real-time queries of the most recent seven days of TOS activity through the log analysis feature, which is based on Torch Log Service (TLS). Once you have enabled log analysis, you can query and analyze access logs for your bucket in real time. By default, logs are saved for seven days. This period is customizable. However, TLS will charge you extra for logs kept beyond seven days. For more information on TLS pricing, see TLS Billable items. warning First-time users must grant TOS permission to access Volcano Engine TLS. Learn more in Log analysis.
		RenameObject	Select whether to enable RenameObject. Once you have enabled RenameObject, you can rename objects by calling the RenameObject API. Learn more in Using RenameObject. tip RenameObject does not work with versioning. You cannot use this feature if versioning is enabled on your bucket.
		Tag	Add one or more tag to your bucket. For more information, see Tagging buckets.
		Retention policy	Select whether to enable the retention policy feature. For more information, see Configuring WORM retention.

Step 3: Upload an object to the bucket

warning

Before uploading any objects, make sure you have created a bucket.

In the left navigation pane, click Buckets.

In the top menu bar, select the project of the bucket you want to manage.

On the Buckets page, click the bucket you want to manage.

On the Objects page, click Upload file.

Set the object parameters on the Upload file page.

Parameter	Description
Upload to	Specify the TOS bucket directory to which the object will be uploaded. Current Directory: Uploads the object to the current directory. Specified Directory: Customizes the directory name and upload the object to this directory. When naming the directory, be aware of the following: Directory names can contain Chinese characters, letters, numbers, and common symbols. You can use forward slashes (/) to quickly create subfolders. However, the folder name cannot start with a forward slash (/) or backslash (\) and cannot contain consecutive forward slashes (/). .. cannot be used as a directory name.
To be uploaded	Select or drag and drop files or folders from your local device. tip You cannot have duplicate filenames in the same bucket. If you upload a file with the same name as an existing file, the system will process it according to the following rules: If versioning is disabled: The uploaded file will replace the existing file. If versioning is enabled: The uploaded file will become the latest version, and the existing file will be kept as a previous version. For more information, see Versioning.
Advanced settings	Storage type	Expand Advanced settings to specify the storage type for the object to be uploaded. By default, objects use the storage type of the bucket they are stored in. The options are as follows: Inherit Bucket (Default): Objects use the storage type of the bucket they are stored in. Standard Storage: High availability, reliability, and performance, suitable for frequently accessed data. Intelligent Tiering: Designed for data with unpredictable access patterns, which will incur object monitoring charges. For more information, see Intelligent Tiering. Infrequent Access Storage: Designed for frequently accessed data with a minimum storage duration of 30 days. Flashback Archive: Optimized for rarely accessed data with a minimum storage duration of 90 days. Archive: Suited for long-term storage of rarely accessed data with a minimum storage duration of 90 days. You need to restore data in Archive before reading it. Cold Archive: Suited for long-lived, rarely accessed data with flexible latency requirements. The minimum storage duration is 180 days. You need to restore data in Cold Archive before reading it. Deep Cold Archive: Cost-effective storage for extremely cold data with ultra-long retention needs. The minimum storage duration is 180 days. You need to restore data in Deep Cold Archive before reading it. tip Cold Archive is only supported in China (Beijing), China (Shanghai), and China (Guangzhou). Deep Cold Archive is only supported in China (Beijing), China (Shanghai), and China (Guangzhou). Deep Cold Archive is currently in closed beta. Please contact your account manager for access. For more information, see Storage type. If you have enabled multi-AZ redundancy for the bucket, you can only choose the storage type from the following options: Inherit Bucket, Standard Storage (Multi-AZ), Intelligent Tiering (Multi-AZ), Infrequent Access Storage (Multi-AZ), and Flashback Archive (Multi-AZ). For more information on multi-AZ, see Multi-AZ redundancy.
		Server-Side encryption	Expand Advanced settings to configure the server-side encryption method. The available encryption options are: Inherit Bucket Encryption Configuration (Default): An object gets the server-side encryption method from its bucket. You can find the server-side encryption method of the bucket in the Basic information section of the bucket's Overview page. You can also change the bucket's server-side encryption method. For instructions, see Setting bucket encryption. None: No encryption applied. SSE-TOS: TOS-managed encryption. Objects are encrypted automatically upon upload and decrypted during download using TOS-hosted keys. For more information, see Server-side encryption. SSE-KMS: Uses keys managed by Volcano Engine's Key Management Service (KMS) to encrypt and decrypt objects. For more information, see Server-side encryption. tip SSE-TOS and SSE-KMS are only supported in China (Beijing), China (Shanghai), Asia Pacific (Johor), and Asia Pacific (Jakarta). You can only set the server-side encryption method when uploading objects. You cannot change the encryption settings of uploaded objects. If you are using SSE-KMS for server-side encryption for the first time, you must first activate KMS. Although activating KMS is free, using the service incurs charges. Using SSE-KMS for server-side encryption generates API call fees, and creating KMS keys generates key management fees. These fees are charged by KMS. For more information, see Key Management Billing Description.
		Encryption algorithm	Expand Advanced settings and select the encryption algorithm for the key. Options include AES256 and SM4. tip The encryption algorithm parameter only appears when SSE-KMS or SSE-TOS is selected for Server-Side encryption. The AES-256 algorithm is only supported in China (Beijing), China (Shanghai), Asia Pacific (Johor), and Asia Pacific (Jakarta). The SM4 algorithm is only supported in China (Beijing) and China (Shanghai).
		Encryption Key Type	Expand Advanced settings to set the encryption key. The default setting is Custom Key. tip This parameter only appears when SSE-KMS is selected for Server-Side encryption.
		Custom Key	Expand Advanced settings and select a key created in KMS. If you have not created a key yet, proceed to the KMS console to do so. For instructions, see Key Management Quick Start. tip This parameter only appears when SSE-KMS is selected for Server-Side encryption.
		Metadata	Expand Advanced settings and click Add Field to configure object metadata. For more information on user-defined object metadata, see Managing object metadata.
		Access permission	The following options are available when setting the access control list (ACL) policy for objects to be uploaded to the bucket: Inherit bucket: An object inherits the permissions from its bucket, meaning the object's ACL will mirror the bucket's. For details on the relationship between object ACL and bucket ACL, see Managing object permissions using bucket ACLs. tip To allow newly uploaded objects to automatically adopt the bucket's ACL policy, turn on the Object ACL default policy switch. For instructions, see Enabling objects to automatically apply bucket ACL. Private (Default): Only the object owner and authorized accounts have read and write permissions. This is the recommended setting. Public read: All users, including those making anonymous requests, can read the object. However, only the owner and authorized accounts can modify it. Public read/write: All users, including those making anonymous requests, can have full read and write access to the object.

tip

After setting the parameters and adding the files, you can view the list of files that will be uploaded on the Upload file page.

To cancel the upload of a selected file, click Remove in the Actions column. To cancel the upload of all files, click Clear list above the file list.

Do not refresh or close the page while uploading. Otherwise, the upload task will be interrupted and the list will be cleared.

Verify the files you want to upload, and click Upload.

Then, you are redirected to the Task progress management page. To view task progress and status, you can also click Task center in the upper-right corner of the console.

Step 4: Download an object

After uploading an object to a bucket, you can download the object to your local computer via the console. Objects will be saved to your browser's default download location.

In the left navigation pane, click Buckets.

In the top menu bar, select the project of the bucket you want to manage.

On the Buckets page, click the name of the bucket.

On the Objects page, click Download in the Actions column of the object you want to download.

Step 5: Share an object

From the TOS console, you can obtain a publicly accessible URL for an uploaded object and share it with third parties for downloading or previewing the object.

In the left navigation pane, click Buckets.

In the top menu bar, select the project of the bucket you want to manage.

On the Buckets page, click the bucket you want to manage.

On the Objects page, click Details in the Actions column of the object you want to share.

In the Basic information section of the panel that appears, click the copy button next to the URL field.

Last updated: 2026.10.22 14:12:37