![]() ![]() Designed for 99.99% availability over a given year.Resilient against events that impact an entire Availability Zone.Designed for durability of 99.999999999% of objects across multiple.Low latency and high throughput performance.You really don't need to copy the S3 files to any EC2 instance or something like that, Amazon S3 Standard has been designed for durability of 99.999999999% of objects across multiple Availability Zones, do you know what it means? Amazon by itself replicates the S3 objects in other AZ of your region to guarantee this durability. If replication and versioning doesn't suffice for my backup, looking at more traditional options like setting up a daily job to save to an EC2 instances local file system periodically.Īlso adding MFA to the bucket is ruled out for now, as I am setting up the system using CloudFormation and don't think its supported. I am aware that deletes on the objects are not propagated to the destination bucket, however not really able to understand the case when bucket itself gets deleted, whether that gets replicated. ![]() ![]() It is suggested that replication can be used for backup also. I am trying to address the case when say someone accidentally deleted the S3 bucket or someone turns off versioning by mistake and complete or partial data needs to be restored(versioning being turned off is unlikely as its a prerequisite for replication). I have versioning enabled on the bucket, and planning on turning on replication too to increase durability. I was looking for a daily backup option for the data in my S3 bucket. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |