Overview
This Guidance shows how you can gain granular insights into the access patterns of objects stored in Amazon Simple Storage Service (Amazon S3) and use those insights to optimize storage costs and energy usage. It helps you identify objects that have not been accessed for a specified period and transition those objects to cheaper storage classes, realizing cost savings by storing infrequently accessed data in more affordable tiers. Additionally, you can configure rules to automatically delete objects that have not been accessed within a set time frame, helping to optimize storage by removing data that is no longer needed. These new capabilities provide better visibility and control over Amazon S3 object lifecycle management, so you can reduce storage costs and energy expenditures by aligning your storage strategies with your object access patterns.
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Deploy with confidence
Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs.
Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages