Amazon S3 Glacier and Replicatication

Amazon S3 Glacier and Replicatication

Amazon S3 Glacier and Replication 

v  Logging & Events:

Amazon S3 bucket logging provides detailed information on object requests and requester even if they use your root account. Log events are records of activity recorded by the application or resource being monitored. 

Differentiate: logging and events:

An “event” is any one record returned from an index or search. It could be a single log, or a single record that contains a count of logs, or a single record that says “100”. A “log” is a specific type of event, specifically documenting that something happened at a particular time.

Buy the best book for AWS- AWS Certified Solutions Architect Study Guide- by Ben Piper and David Clinton, Google Cloud Certified – Professional Cloud Architect” by Dan Sullivan


v  Amazon S3 Glacier:

Amazon S3 Glacier (S3 Glacier) is a secure and durable service for low-cost data archiving and long-term backup. With S3 Glacier, you can store your data cost effectively for months, years, or even decades. Amazon S3 Glacier stores your infrequently used data as an archive. An archive can include only one file or a combination of files. While individual archives are limited to 40 terabytes max, there’s no limit to how much data you can store in S3 Glacier as a whole.

S3 Glacier


 Amazon Glacier is extremely low cost, secure, and durable storage service for data archiving and backup. It is designed to keep the cost low and optimized for the cold data where the retrieval time is 3 to 4 hours. Within Glacier, the user can reliably store the small and large amount of data.
Buy the best book for AWS- AWS Certified Solutions Architect Study Guide- by Ben Piper and David Clinton, Google Cloud Certified – Professional Cloud Architect” by Dan Sullivan

v  Versioning & lifecycle Policy:

Versioning is a means of keeping the multiple forms of an object in the same S3 bucket. Versioning can be used to retrieve, preserve and restore every version of an object in S3 bucket. For example, bucket consists of two objects with the same key but with different version ID’s such as photo.

S3 Lifecycle

The lifecycle defines two types of actions:

·       Transition actions: When you define the transition to another storage class. For example, you choose to transit the objects to the Standard IA storage class 30 days after you have created them or archive the objects to the Glacier storage class 60 days after you have created them.

·        Expiration actions: You need to define when objects expire, the Amazon S3 deletes the expired object on your behalf.

Suppose a business generates a lot of data in the form of test files, images, audio, or videos and the data is relevant for 30 days only. After that, you might want to transition from standard to standard IA as storage cost is lower. After 60 days, you might want to transit to Glacier storage class for the long time archival. Perhaps you want to expire the object after 60 days completely, so Amazon has a service known as Lifecycle Management, and this service exist within the S3 bucket.

Lifecycle policies:

Lifecycle Policy

·        Use Lifecycle rules to manage your object: You can manage the Lifecycle of an object by using a Lifecycle rule that defines how Amazon S3 manages objects during their lifetime.

·        Automate transition to tiered storage: Lifecycle allows you to transition objects to the Standard IA storage class automatically and then to the Glacier storage class.

·        Expire your objects: Using the Lifecycle rule, you can automatically expire your objects.

 v  Cross-region Replication:

With cross-region replication, every object uploaded to an S3 bucket is automatically replicated to a destination bucket in a different AWS region that you choose. For example, you can use cross-region replication to provide lower-latency data access in different geographic regions.


 The AWS S3 – Cross-region replication (CRR) allows you to replicate or copy your data in two different regions. There are many possible scenarios where setting up cross-region replication will prove helpful. Some of them are
enlisted below:

1.  Improving latency and enhancing availability: If you are running a big organization with customers all around the world then making objects available to them with low latency is of great importance. By setting up cross-region replication you can enable your customers to get objects from S3 buckets which are nearest to their geographic location.

2.  Disaster recovery: Having your data in more than one region will help you prepare and handle data loss due to some unprecedented circumstances.

3.  To meet compliance requirements: Sometimes just to meet compliance requirements you will need to have a copy of your data in more than one region and cross-region replication can help you achieve that.

4. Owner override: With AWS S3 object replication in place you can maintain the same copy of data under different ownership. You can change the ownership to the owner of the AWS destination bucket even if the source bucket is owned by someone else.

Leave a Reply

Your email address will not be published. Required fields are marked *