100 Days of DevOps — Day 44-S3 Cross Region Replication(CRR)

Welcome to Day 44 of 100 Days of DevOps, Focus for today is S3 Cross Region Replication

What is Cross-Region Replication

Cross-region replication (CRR) enables automatic, asynchronous copying of objects across buckets in different AWS Regions. Buckets configured for cross-region replication can be owned by the same AWS account or by different accounts.

Features and Limitations

  • It only replicates the object at the point of enabling replication, all the object before that can’t be replicated.
  • Cross region replication by default only replicates un-encrypted objects or objects which encrypted using SSE-S3(Server-Side Encryption with Amazon S3-Managed Keys)
  • SSE-C(Server-Side Encryption with Customer-Provided Keys) are not supported and SSE-KMS requires some extra configuration.
  • By default ownership and ACL are replicated and maintained but we can always customize it.
  • The storage class is maintained by default.
  • Lifecycle events are not replicated
  • When the bucket owner has no permissions, objects are not replicated.
  • Cross region replication is uni-directional i.e from source to destination, not the other way i.e if I delete the file at the destination it will not be deleted at Source.

Create a source and destination bucket in two different regions under the same account

  • Versioning must be enabled in both the bucket to configure Cross Region Replication
  • Any object that resides in the bucket before versioning is enabled will not be replicated

Step1: Create Source Bucket

  • Once the bucket is created

Step2: Enable versioning

Step3: Create a destination bucket

Step4: Enabled Cross Region Replication

Step5 : Test

  • Go back to your Source S3 bucket(my-source-s3-bucket-to-test-crr) and try to upload some files
  • Wait for a few mins, you will see the same file replicated to the destination bucket
  • Terraform code to automate the above setup
  • The above example shows how to perform cross region replication between the same account but what would be the case if both source and the destination account is different, in that case, you need to add a bucket policy
  • Add the following bucket policy on the destination bucket to allow the owner of the source bucket to replicate objects. Be sure to edit the policy by providing the AWS account ID of the source bucket owner and the destination bucket name
  • Few more things you can change on the destination end
  • To replicate your data into a specific storage class in the destination bucket, select Change the storage class for the replicated object(s). Then choose the storage class that you want to use for the replicated objects in the destination bucket. If you don’t select this option, the storage class for replicated objects is the same class as the original objects.
  • To change the object ownership of the replica objects to the destination bucket owner, select Change object ownership to destination owner. This option enables you to separate object ownership of the replicated data from the source. If asked, type the account ID of the destination bucket.
  • When you select this option, regardless of who owns the source bucket or the source object, the AWS account that owns the destination bucket is granted full permission to replica objects.
  • GitHub Link

Looking forward from you guys to join this journey and spend a minimum an hour every day for the next 100 days on DevOps work and post your progress using any of the below medium.

Reference

AWS Community Builder, Ex-Redhat, Author, Blogger, YouTuber, RHCA, RHCDS, RHCE, Docker Certified,4XAWS, CCNA, MCP, Certified Jenkins, Terraform Certified, 1XGCP