Support » Plugin: W3 Total Cache » Amazon Cloudfront Invalidations

  • I have this plugin running on two sites that use Amazon Cloudfront for the CDN. On May 3, one site started sending invalidations to Cloudfront. At first there were anywhere from a few to 1000 invalidations per day. Starting May 19, there were 7000 invalidations per day. Amazon charges $0.005 per invalidation after 1000, so I ended up with a $500 bill for Cloudfront for May.
    I have disabled the CDN for now, so it stopped. As far as I can tell, W3 Total Cache was the only plugin updated around that time, and the only one that should affect CDN.
    I saw another post which said to use the generic setting instead of the Cloudfront setting, so I will give that a try. Is there anything else I can do to make sure this doesn’t happen again?

    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • For what it’s worth, here are the plugins that did update on May 3, when the problem started:
    May 3 06:54 w3-total-cache/
    May 3 06:54 flowpaper-lite-pdf-flipbook/
    May 3 06:54 enable-media-replace/
    May 3 06:54 advanced-nocaptcha-recaptcha/

    Plugin Support gidomanders

    (@gidomanders)

    It is W3 that generates the invalidation requests, but we’re working on an option to only invalidate on manual purges. So for now the generic mirror works good enough, but in a future release you can use the CloudFront specific CDN option again.

    you guys ruined my AWS bill. I have a massive $100 bill in just 2 days. This is shameful on you guys.

    Plugin Support gidomanders

    (@gidomanders)

    We’re very sorry to hear that. We’re working on the solution to be released as soon as possible.

    I have had the same issue with the plugin. This was on a simple WooCommerce site with a few thousand products. Notice it incurred over $6,000 in fees.

    Amazon CloudFront Invalidations $6,485.76
    $0.000 per URL – first 1,000 URLs / month.1,000 URL$0.00
    $0.005 per URL – over 1,000 URLs / month.1,297,151 URL$6,485.76

    We are experiencing the same issue now, it cost us 150$ in about only 1 hour.
    Cost hundreds of $ when W3TC invalidating Cloudfront CDN records.

    Is there a option to purge CDN manually instead of let it done by w3tc automatically?

    Plugin Support gidomanders

    (@gidomanders)

    @hileon I’m very sorry that we’re causing such bills. We’re working on an option to only send invalidation requests when you click the purge button and we’ll add a notification about the possible costs of invalidation requests when that option is not enabled.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.