S3 version control When enabled all existing objects are retained and a new version is created with a new version ID Must be enabled for cross region replication Protection from unintended user deletes or application failures New version of the object with every upload Retrieval of deleted objects is easy and you can roll back to previous versions of the object S3 provides DELETE API to delete an object. If the bucket in which the object exists is version controlled, then you are able to specify the version of the object that you want to delete. The other versions of the Object still exist within the bucket If you do not specify the version, and just pass the key name, Amazon S3 will delete the object and return the version ID Then the object will not appear on the bucket In the case where the bucket is Multi-factor authentication (MFA) enabled, then the DELETE request will fail if we do not specify the current MFA token Youi cannot disable versioning on a version-enabled bucket in Amazon S3 once it has been configured, however, you can suspend it which has the same effect Suspending Versioning: You can suspend the versioning on a bucket in S3. Once suspending versioning, S3 will stop creating new versions of the object. It stores the object with null version ID On overwriting an existing object, it replaces the object with null version ID Any existing versions of the object still remain in the bucket. But there will be no more new versions of the same object except for the null version ID object PrepAway - Pass Your Next Certification Exam Fast!
S3 cross region replication Use Cross Region Replication of S3 to make copies of an object across buckets in different AWS Regions Copying occurs automatically and is asynchronous Configure cross region replication in the source S3 bucket to enable CRR creates exact replicas of the objects from the source to destination buckets in different regions Use cases of Cross Region Replication are: Geopolitical separation compliance: When laws/ regulatory requirements that data be stored at geographical separated locations. This can be accomplished using AWS Regions that are spread across the world Failover: To reduce the probability of system failure due to complete blackout in a region. Use Cross-Region Replication in such a scenario to maintain operations by having data available in other regions. Reduce network latency: When the data is being accessed from multiple geographies, you can replicate objects in the geographical Regions that are closer to end customer. Security: remote replicas managed by separate AWS accounts Deletes and lifecycle actions are not replicated 1:1 replication between any 2 regions Enable versioning on the source bucket to perform Cross Region Replication Versioning must be enabled on both the source and destination buckets Create an IAM role to grant S3 permission to copy objects on users behalf Cross-region replication is a bucket-level feature that enables
You've reached the end of your free preview.
Want to read all 369 pages?
- Fall '19
- AWS, Amazon Elastic Compute Cloud