CloudFront invalidation of path when using S3 static website default index #49

merged 4 commits into from Feb 19, 2013


None yet
5 participants

joseprio commented Apr 18, 2012

Recently, a modification for CF invalidation was added so it was possible to invalidate files from a custom origin CF distribution that used S3 as custom origin.

Unfortunately, s3cmd wouldn't invalidate the path in CF when the uploaded file in S3 is the default index.

So, I modified it to automatically retrieve the default index name, detect if the invalidation path uses it and modify the query accordingly.

I also added two new flags to modify this behavior:

  • --cf-invalidate-default-index: to force invalidation of default index file
  • --cf-no-invalidate-default-index-root: to disable the invalidation of the default index file path

jtriley commented May 9, 2012

+1 I also ran into this when using s3cmd to sync and invalidate a static website via cloudfront/s3

sud0n1m commented Jan 15, 2013

+1 Same issue here. Looks like no movement merging this in. I guess best plan is to build from your fork?

mludvig merged commit e364d9f into s3tools:master Feb 19, 2013

Very cool! Thanks for fixing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment