instintnet

ok @per4mance

Well then we will re-activate it with this box checked and daily track the costs of Cloudfront…

thank you very much ??

ok, @per4mance and @vmarko. For another domain that we also have with Cloudfront we have already checked the “Only purge CDN manually” box.

And @vmarko, it is essential to indicate the invalidations that you have commented? Or having the box checked is enough? And if we have to indicate these rules, do we have to do it in the CDN > “Custom file list” section of the plugin? Or in the Cloudfront configuration?

I’m sorry, but we’re still lost and we don’t want to waste your time either. We are already investigating with the information you have provided.

Thank you very much to both of you

Hi, @per4mance

First of all, thank you very much for your help. We are still digesting the news of the payment we must pay now.

On the other hand, we have proceeded to deactivate everything, both the Cloudfront distribution and the CDN functionality of the plugin until we understand if we can use it without having surprises of this type.

And referring to what you say, we had already activated what you show us in the screenshot …: ((

We don’t understand how in only one month we have received by surprise a bill of $1,053.10 in concept of “Amazon CloudFront Invalidations”… it’s due to the module W3 Total Cache???? Can someone explain to us how without knowing it we just lost 1,000 dollars? Amazon Cloudfront Invalidations – February bill