Docs

Torch Object Storage

Same-region replication

Same-account same-region replication

TOS supports same-account same-region replication, which allows you to automatically copy objects across buckets within the same region and account. This topic explains how to configure a rule for this type of replication.

Prerequisites

Before configuring a same-account same-region replication rule for the first time, you must grant TOS permissions to read all objects from the source bucket and to write objects to the destination bucket. If your bucket uses server-side encryption with KMS keys (SSE-KMS), you must also authorize TOS to access Key Management Service (KMS). Otherwise, the rule cannot be executed.

warning

To authorize TOS to access KMS, navigate to the SRR page and click Click to Authorize under the KMS and read/write authorization section. Then, confirm by clicking OK in the box that appears. After authorization, TOS automatically creates the ServiceRoleforReplicationAccessTOS role, granting it permissions to access KMS and read and write objects in the source and destination buckets.

To create the ServiceRoleforReplicationAccessTOS role, your account must have the iam:ListAttachedRolePolicies, iam:CreateRole, and iam:AttachRolePolicy permissions. If the SRR page shows No permission, you must first grant your account the iam:ListAttachedRolePolicies, iam:CreateRole, and iam:AttachRolePolicy permissions. Then, proceed with read/write and KMS authorizations. For instructions, see Configuring IAM policies.

Creating a rule for same-account same-region replication

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.

In the left navigation pane, select Fault tolerance and disaster recovery > SRR.

On the SRR page, click Create rule. Set the following parameters in the box that appears:

Parameter	Description
Source bucket location	The region of the source bucket is displayed by default and cannot be changed.
Source bucket	The name of the source bucket is displayed by default and cannot be changed.
Destination bucket owner type	Select Select a bucket in this account.
Region of the destination bucket	The region of the destination bucket is displayed by default and cannot be changed.
Destination bucket	Select the name of the bucket where the replicas will be stored. warning The versioning status of the source and destination buckets must be consistent—either both are enabled or both are disabled. If either is suspended, same-account same-region replication is not supported.
Destination storage type	Select the storage type for the replica: Inherit target bucket: The replica's storage type will match the destination bucket's default storage type. Inherit source object: The storage type of the replica will be consistent with that of the source object. Custom: Select a storage type for the replica manually. warning Some storage types have a minimum billable object size. If the size of a replica does not meet the minimum size requirement for the selected storage type, storage costs will be calculated based on the minimum billable object size. For more information, see Storage type.
Scope	Specify the scope of the data that will be replicated: Entire bucket: Copy all objects in the bucket to the destination bucket. Specify prefix: Copy all objects that match the specified prefix to the destination bucket. Select Specify prefix and enter the desired prefix(es). Only objects with the prefix(es) will then be replicated. The restrictions are as follows: If this field is left empty, all objects in the bucket will be replicated. Up to ten prefixes can be added. Length must be between 1 and 1,024 characters. tip Follow these guidelines when specifying a prefix: Prefixes can contain Chinese characters, letters, numbers, and common symbols. Prefixes cannot start with a forward slash (/) or backslash (\). Consecutive forward slashes (/) are not allowed. ".." cannot be used as a directory name.
Tag	Enter the desired tag(s). Only objects containing the specified tag(s) will be replicated. Click Add row to set the tag key and value. The restrictions are as follows: Up to ten tags can be added. The key length cannot exceed 128 characters. The value length cannot exceed 256 characters. Both the key and the value are case-sensitive. Valid characters include uppercase and lowercase letters, numbers, spaces, and the special symbols _ .: / = + -. warning Tags and prefixes have an "OR" relationship. If both are configured, objects matching either the tag rules or the prefix rules will be replicated. Using tags and the historical objects synchronization feature simultaneously is not supported. If you want to use tags to filter objects, do not enable Sync historical object.
Sync historical object	Select whether to synchronize objects that exist in the source bucket before the rule takes effect: On: Existing objects will be synchronized to the destination bucket. Off: Only objects uploaded after the rule takes effect will be synchronized. Existing objects will not be synchronized.
Synchronous delete tag	Select whether to synchronize deletion marks: On: Deletion marks will be synchronized to the destination bucket. Off: Only objects uploaded to the source bucket will be synchronized. Deletion marks will not be synchronized. warning Deletion mark synchronization is only supported for buckets with versioning enabled. This feature is currently in closed beta. Please contact your account manager for access. Using tags and the deletion mark synchronization feature simultaneously is not supported. If you want to use tags to filter objects, do not enable Synchronous delete tag.
Synchronize deleted objects	Select whether to synchronize the deletion of objects from the source bucket to the destination bucket: On: When an object is deleted from the source bucket, it will also be deleted from the destination bucket. Off: Only object uploads will be synchronized, not deletions. warning Enabling this option will synchronize deletion operations from the source bucket to the destination bucket. For example, if you delete an object in the source bucket or if a lifecycle rule triggers a deletion, the corresponding object in the destination bucket will also be deleted. Proceed with caution. When synchronous object deletion is enabled, TOS automatically ensures eventual consistency of data between the source and destination buckets. However, if you set up bidirectional replication rules between multiple buckets and then delete an object in a destination bucket during replication, TOS cannot guarantee the eventual consistency of data across those buckets. This feature is currently in closed beta. Please contact your account manager for access.

Once you have finished configuring, click Create.

Depending on the size of your objects, the replication process may take anywhere from a few minutes to several hours. You can check the replication state of existing objects and the last sync time on the SRR page.

tip

The last sync time refers to the completion time of the most recently replicated object. Since SRR tasks run concurrently, objects uploaded to TOS before the last sync time may not be replicated.

Disabling a rule for same-account same-region replication

On the SRR page, toggle off the switch under the Rule Status column of the rule you want to disable.

Other operations

Edit a rule for same-account same-region replication: On the SRR page, click Edit in the Actions column of the rule you want to modify.

Delete a rule for same-account same-region replication: On the SRR page, click Delete in the Actions column of the rule you want to remove, and confirm the deletion by clicking Delete in the box that appears.

Last updated: 2026.02.03 16:10:50