Reduce redundant CloudFront invalidation paths#309
Open
carlospolop wants to merge 1 commit into
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
2 participants
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.
Created by Hermes.
Problem
CloudFront invalidations are the top wiki-account cost driver. In the last 15 days, the cloud HackTricks distribution invalidated 375 paths across 171 batches, including repeated explicit
/en/sitemap.xmland translated/<lang>/sitemap.xmlpaths.Change
/<lang>/*and/en/*./<lang>/sitemap.xml,/en/sitemap.xml, and/en/robots.txtpaths because they are already covered by the wildcard invalidation./sitemap.xmland/robots.txtwhere needed.Safety
CloudFront wildcard invalidation paths cover all objects below the prefix, so this preserves cache refresh behavior while reducing billable invalidation paths.
Validation