fix: use cloudwatch retention policy #96
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
![infracost-autofix[bot]](https://avatars.githubusercontent.com/in/882199?s=60&v=4){kind=small}
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 Cloudwatch - consider using a retention policy to reduce storage costs
Use a retention policy to avoid retaining logs indefinitely and accumulating storage costs. For example, if an application generates 5GB of logs daily, in a year without retention, you'd store 1.8TB of logs. In the AWS US East (N. Virginia) region, where storage costs $0.03 per GB per month, you'll incur a cumulative yearly cost of ~$802. This cost will continually grow as more logs are added.Risk: Medium
Improper retention could delete logs needed for compliance or debugging.Deployment details: no downtime required, see AWS docs for details
Retention policies apply in‑place to log groups without service disruption. AWS may take up to 72 hours to delete expired events after changing retention.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