Please complete the required turnover for withdrawal Casino Plus.Claim Your Free 999 Pesos Bonus Today

Resolved Thorsten :-)
(@per4mance)

5 years, 1 month ago
Hi,

I read this article https://www.ads-software.com/support/topic/amazon-cloudfront-invalidations/ and I do not get the content right.

My website has plugin W3 Total Cache v0.12.0 and my AWS CloudFront works after extended the W3 Total Cache function with FSD CDN and Type Amazon CloudFront.

Each time I upload an image as admin for an article, WordPress is generating several image sizes of each image what’s normal. This is the moment when AWS is creating “Invalidations”, five invalidation for each file. But I do not know why this happens, because each file is accessible via CloudFront. I didn’t delete my cache or CDN or anything else.

Here is one example of the original file https://cdnaws.schlossschule.org/wp-content/uploads/2020/01/ssi-bb-theater-aula-764398.jpg with these invalidations:

https://cdnaws.schlossschule.org/wp-content/uploads/2020/01/ssi-bb-theater-aula-764398-624×325.jpg
https://cdnaws.schlossschule.org/wp-content/uploads/2020/01/ssi-bb-theater-aula-764398-300×156.jpg
https://cdnaws.schlossschule.org/wp-content/uploads/2020/01/ssi-bb-theater-aula-764398-150×150.jpg

In total AWS created, for one image I uploaded, 5 invalidations. You can imagine what will happen when I doing this with 1,000 images.

I asked AWS and received in return this:
Invalidating is removal of a file from CloudFront edge caches before it expires. More info can be found at the link below:
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html.

But this is no help for me because I don’t want to remove images before cache expires. And WordPress did a “file versioning” as recommend by the help article above. Is there anything wrong with W3 Total cache? I appreciate any help because I don’t want to get charged by this behavior.

Regards
- This topic was modified 5 years, 1 month ago by Thorsten :-).
- This topic was modified 5 years, 1 month ago by Thorsten :-).

Viewing 2 replies - 16 through 17 (of 17 total)

← 1 2

instintnet
(@instintnet)

5 years ago

ok @per4mance

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

thank you very much ??

tylerlindell
(@tylerlindell)

4 years, 9 months ago

Sadly, I too have faced this same issue of a surprise bill for invalidation. It would be interesting to see a message pop up saying.. “Wait! before you spend a load of cash through trying to clear your cache, we’ll save you the trouble. You can go ahead with this invalidation (see here for pricing), or we can add object versioning (free), or you might want to check this box over here that’ll protect you from a big surprise bill later on.”

I realize this sounds a little sarcastic, but it sounds like that might be a nice feature to keep customers from being surprised. I recently paid for Pro W3TC hoping to make my page faster.. so far so good but now I must pay double+ to learn how to use it… I’m frustrated that this happened but it would be really nice to see little helpful notes like this sometime to save people the hassle in the future.

Viewing 2 replies - 16 through 17 (of 17 total)

← 1 2

The topic ‘W3 Total Cache, AWS Cloudfront & Invalidations’ is closed to new replies.