Skip to main content

AWS S3 Cross Region Replication

What are the constraints to enable S3 cross region replication?

To enable cross region replication, you should have two buckets:

Bucket 1 - should be in region A

Bucket 2 - should be in region B

Versioning should be enabled in both the buckets for replication.

Can you create same region replication?

Yes

Can you create cross account replication?

Yes

Can you replicate a subset of objects using replication?

Yes, you can limit the scope of the replication rules to specific prefixed/tags etc., You can also apply the rules to all the objects in the bucket

What is the expected delay in copying the files from the source to destination buckets in S3 replication?

A few seconds.

Can you replicate only the new objects?

The new objects can be replicated after enabling the replication rule. However, the already existing objects can also be replicated by enabling Replicate existing objects option.

Comments

Post a Comment

Popular posts from this blog

GoLang - How to check if key exists in map?

package main import "fmt" var m map[string]string func main() { m = make(map[string]string) m["foo"] = "abc" if val, ok := m["foo"]; ok { fmt.Println("foo found -", val) } else { fmt.Println("foo not found") } if val, ok := m["bar"]; ok { fmt.Println("bar found -", val) } else { fmt.Println("bar not found") } } Output: foo found - abc bar not found
Post a Comment
Read more

How to delete commits in Git?

Suppose you have 3 commits with SHAs as follows: HEAD~0 --> Commit 3 ccccccc HEAD~1 --> Commit 2 bbbbbbb HEAD~2 --> Commit 1 aaaaaaa If you want to remove the last two commits (i.e., commits 2 and 3) and make Commit 1 as the latest commit, run the following commands: git reset --hard aaaaaaa git push origin HEAD --force Now, the commit history would be as follows: HEAD~0 --> Commit 1 aaaaaaa
Post a Comment
Read more

How to fix the error - botocore.exceptions.ProfileNotFound: The config profile (AnyProfileName) could not be found?

This occurs when you do aws configure in cmd. It is caused by setting the following environment variable: AWS_PROFILE = AnyProfileName Removing this environment variable is the fix. After removing, if you do aws configure , aws would be configured for the default profile rather than AnyProfileName .
Post a Comment
Read more