Cross-bucket replication enables the automatic, asynchronous replication of incremental objects from a source bucket to a destination bucket. During replication, COS may also automatically replicate the object operations in the source bucket, such as PUT Object or DELETE Object. You can choose to enable or disable this feature as needed. For more information, see Overview.
Before enabling cross-bucket replication, make sure that both the source and destination buckets have enabled versioning.
If versioning is not enabled for both the source and destination buckets, enable it first and then configure the cross-bucket replication rule.
|Source Region||The region where your source bucket resides.|
|Apply To||Indicates which objects will be replicated from the source bucket. The default option is **The whole bucket**. If a prefix is specified, only objects with this prefix will be replicated, such as files prefixed with `logs/`.|
|Resource Path||Path of your source bucket.|
|Destination Bucket||The bucket to store the replicated objects. It can be in the same region as the source bucket. You can select only one bucket under the current account in each region.|
|Destination Storage Class||Storage class of the replicas. The storage class will be the same as that of the source objects by default. You can also select a different storage class.|
|Sync Delete Marker||If you try to delete an object from a versioning-enabled bucket without specifying a version ID, COS will add a delete marker to the object. If you select this option, cross-bucket replication will copy this delete marker to the destination bucket. Regardless of whether the delete marker is copied, the object will not be deleted from the destination bucket. You can always access a noncurrent version of the object by specifying its version ID. For more information, see Overview.|
- Once the rule is created, you can enable/disable it under Status, or edit it under Operation.
- If you set Applied to to The whole bucket in your first rule, you will be unable to add any new rules. In this case, you may choose to edit it, or simply delete it and add a new one.
- If you set Applied to to Specific resources in your first rule, you can edit it and change this setting to The whole bucket if needed.
You can disable a cross-bucket replication rule using either of the following two options:
- When cross-bucket replication is disabled, in-progress cross-bucket replication operations cannot proceed and will be aborted.
- When cross-bucket replication is re-enabled for a bucket, it only applies to objects created after that time point.