Hello @tylerlindell
Thank you for your inquiry and I am happy to assist you with this.
Sending a new object version is also a kind of invalidation.
Can you please clarify what you want to achieve?
Thanks!
Invalidation is happening a lot and it looks to be happening on images specifically. it seems like they are being directly invalidated which is ringing up the bill. I have it set to only invalidate manually – but that’s being ignored or disregarded when it comes to images for some reason. I recently removed the {uploads-dir} from the automatically upload files as well as removed *.jpg;*.png;*.gif from the list of file types to update because the invalidations seem to be heavily focused on images.
I use a different app to manage image -> cdn which uses object versioning and it has never invalidated anything which has allowed my cloudfront bill to be acceptable, once I started using this plugin though… it’s like the lid has come off and cash is spilling out specifically wrt CloudFront invalidations.
I want to use object versioning because the cost seems to be much more negligible than directly asking for an invalidation.
Here are the docs regarding object invalidation using cloudfront: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/UpdatingExistingObjects.html
What are your thoughts?