fix: use intelligent tiering#108
Open
infracost-autofix[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💰 Infracost opened this pull request as part of the following campaign:
Policy: AWS S3 - consider using Intelligent-Tiering or adding a lifecycle policy
Reduce S3 storage costs by enabling Intelligent-Tiering or setting up a lifecycle policy to move or delete older data. Intelligent-Tiering is ideal when data access patterns are unpredictable - it automatically moves objects between storage tiers to optimize costs without impacting performance. It's best suited for objects larger than 128KB that are stored for at least 30 days, and there's a small monitoring fee that's typically offset by savings.
For more predictable workloads, use lifecycle policies to transition objects to cheaper storage classes like Glacier. For example, storing 1TB in the Standard class costs about $23/month, while Glacier Flexible Retrieval can bring that down to just $3.60/month—a potential 84% saving.
Risk: Medium
Misconfigured lifecycle rules could prematurely delete older objects that are still needed for recovery or compliance.Deployment details: no downtime expected, see AWS docs for details
Lifecycle rules apply in-place to buckets without service interruption.Next steps:
✅ Deploy this change before the campaign deadline: June 31
💬 Doesn't apply? Close the PR with a comment
🛠️ Needs changes? Check out the branch to rebase or adjust