I know it takes longer and more resources, but does doing a full disable/enable in Cloudfront invalidate all the files? Sometimes it seems safer to just do everything than rely on the developers sending us an exactly list of files. (We have a static HTML site with javascript code hosted in S3 and exposed via Cloudfront.)
I tried the disable/enable yesterday, but today, people were saying it looks their code changes were not being used on the website.
Great feature in the future would be to invalidate all files changed since the last validation. That should be easy for them to do.
When I invalidate, I use the '/*' specifier, and it invalidates everything. Works every time for us.
There would be some nominal increase in processing time and cost, but I don't believe it is significant.