This document describes what COS will and will not replicate after you enable cross-bucket replication for a bucket.
In a source bucket with cross-bucket replication enabled, COS will replicate the following:
- If you specify an object version to delete in the source bucket by specifying a version ID, COS will not replicate this delete operation.
- If you add a bucket-level configuration such as a lifecycle rule to the source bucket, COS will not replicate any resulting object operations.
If an object is deleted from a source bucket with cross-bucket replication enabled, the following will happen:
In a source bucket with cross-bucket replication enabled, COS will not replicate the following:
- The cross-bucket replication of object data between buckets is not transitive. If you set two cross-bucket replication rules, one of which sets bucket A as the source bucket and bucket B as the destination bucket, and the other sets bucket B as the source bucket and bucket C as the destination bucket, then the object data added to bucket A will be replicated only to bucket B but not to bucket C.
- For example, if you update the lifecycle configuration of the source bucket, COS will not apply this configuration to the destination bucket synchronously.
- If you configure a lifecycle rule only for the source bucket, COS will add delete markers to expired objects there, but the markers will not be replicated to the destination bucket. For the destination bucket to delete these expired objects as well, you need to configure the same lifecycle rule for the destination bucket.