Impact Backup on the System or Users
Hi everyone, I am researching about s3 backup and a question is what is the impact on the system or users? I think with backup solutions (s3 versioning, replications, aws backup, custom solution like EMR or Lambda) we have high request (PUT/GET) rates . can it cause throttling or potential higher write latency due to overhead? am I right? Does it make any difference between the solutions I named? Thanks
- Language
- English
asked 2 years ago215 views
- Newest
- Most votes
- Most comments
You won’t see any impact to the system. S3 is a service shared amongst all AWS accounts.
You can use cross account s3 replication.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication-walkthrough-2.html
You can also use AWS backup to back the bucket up to a vault in another account. It’s in a vault and not another . One would have to restore the backup in another account.
Note, the bucket in the other account has to be named uniquely.
So I can not use it (cross account) for s3 versioning, batch replications and custom solution like EMR or Lambda. am I right? but with AWS account and live replication (CRR) I can do it
Enable delete markers.. This may be your solution https://docs.aws.amazon.com/AmazonS3/latest/userguide/delete-marker-replication.html Or am i missing what your trying to achieve?
I am just researching and write the pros and cons, try to find the answer which one support copy data across Account
Relevant content
asked 4 years ago
thanks. do you know with solutions like s3versioning, s3 batch replication, aws backup, custom solution like EMR or Lambda can we copy backup to another aws account or not? which one support this?
Answered under another answer