Same-region replication (SRR) automatically and asynchronously replicates object creation, updates, and deletions from a source bucket to destination buckets within the same region in near real-time.
Use cases
When regulations prohibit data from leaving a country or region, configure SRR rules to store replicas in multiple destination buckets within the same region. Replicated objects retain the same names, versioning information, content, and metadata (creation time, owner, user metadata, and ACLs).
Features
SRR provides the following capabilities:
-
Data replication between buckets in the same region
SRR replicates data from a source bucket to multiple destination buckets in the same region. Up to 100 rules per bucket are supported by default. A bucket can serve as both source and destination in different rules.
To configure more than 100 SRR rules, contact technical support.
-
Near real-time data replication
Object creation, deletion, and modification operations replicate from source to destination in near real-time.
-
Data consistency
By default, OSS ensures eventual consistency between the source and destination buckets. However, writing an object with the same name directly to the destination bucket during replication breaks this guarantee.
-
Historical data migration
SRR replicates data written after a rule takes effect. You can also replicate pre-existing historical data to the destination bucket.
-
Track replication progress
View the timestamp of the latest replication and track progress for existing data replication.
-
Versioning
SRR ensures eventual consistency between versioning-enabled source and destination buckets. If a rule replicates only added and modified data, version-specific deletions are not replicated, but delete markers are.
-
Replication of encrypted data
SRR replicates both unencrypted objects and objects encrypted with SSE-KMS or SSE-OSS.
-
Event notification
Set event types to
ObjectReplication:ObjectCreated,ObjectReplication:ObjectRemoved, andObjectReplication:ObjectModifiedto receive notifications when objects are added, modified, deleted, or overwritten during SRR tasks. Process real-time OSS object changes with event notifications.
Usage notes
Billing rules
These rules apply to both same-account and cross-account SRR.
-
SRR traffic between source and destination buckets is free.
NoteSRR traffic does not consume the default OSS bandwidth.
-
OSS counts requests generated by SRR but does not charge for them.
-
Replicating Archive objects does not trigger restoration or incur retrieval fees.
Replication duration
SRR replicates data asynchronously in near real-time. Replication takes minutes to hours depending on data size. If replication is slow, check for bandwidth throttling and submit a ticket to increase bandwidth if needed.
To check SRR replication bandwidth over the Internet: In the OSS console, click Buckets and select the destination bucket. Choose and check the Used Bandwidth section. Used Bandwidth.
Data overwriting
If you configure an SRR rule for two buckets, a replicated object may overwrite an object with the same name in the destination bucket.
Limitations
-
Source and destination buckets must have the same versioning status (both unversioned or both versioning-enabled).
-
You cannot change the versioning status of buckets with a configured SRR rule.
-
Cold Archive and Deep Cold Archive objects cannot be replicated, even if restored.
-
Appendable objects cannot be replicated to buckets with Cold Archive or Deep Cold Archive storage class.