Cloudfront Invalidations

  • Resolved chicagosam

    (@chicagosam)


    4 years, 8 months ago

    Hi,

    This post is specific to Cloudfront Invalidations.

    Background: Initially, I had set up W3TC to use the rich API with the user/pass combo sent to Cloudfront API. Then I noticed a bill of around $15 from AWS indicating that I went over the allotted 1,0000 free invalidation requests by some 2,000 requests. So, I started digging around this forum and saw that others were also experiencing the same issue.

    I know the following questions have been asked before, but it’s been so long since those questions were asked, and in fact, I could not really get to know what the solution is, and if at some point W3TC will completely allow the disabling of sending invalidation requests to Cloudfront?

    Questions:

    1. If I switch from using the Cloudfront API to using the generic mirror and then click (I suppose manually) the purge pages button, would invalidation requests be sent to Cloudfront?

    2. Even after switching to a generic mirror, there seems to be about an average of 50 invalidation requests to images (which have not been modified in months..). The question is, would enabling the switch to only purge manually solve this issue?

    Thanks in advance!
    Sam

Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    4 years, 8 months ago

    Hello @chicagosam,

    I am sorry about the issue you are having and I am happy to assist you with this.

    We built “Only purge CDN manually” because of the problems with invalidation requests on CloudFront causing huge bills. If it’s enabled, you can click the purge CDN button in W3 Total Cache to send invalidation requests, otherwise, all changes will be detected automatically and an invalidation request will be sent immediately.
    I hope this helps.

Viewing 1 replies (of 1 total)
  • The topic ‘Cloudfront Invalidations’ is closed to new replies.