I was chatting with Kevin Boyd (aka Beryllium) on the ##aws Freenode IRC channel about the challenge of invalidating a large number of CloudFront objects (35,000) due to a problem where the cached copies of the objects were out of date and the system had not been designed with versioning in the object path or name.
In addition to the work to perform all of these invalidations (in batches of up to 1,000 in each request with at most 3 request outstanding) there is also the issue of cost. The first thousand CloudFront invalidations are free in a month, but the remainder of the invalidations in this case would cost $170 (at $0.005 for each object).
It occurred to me that one could take advantage of the on-demand nature of AWS by using the following approach:
Create a new CloudFront distribution, set up exactly like the existing distribution (except that the new distribution caches would be empty).
Change the application to point to the new CloudFront distribution domain when referring to the objects.
Step 2 consists of a simple DNS change, assuming that you use your own domain name (e.g., cdn.example.com) when referring to the CloudFront objects in your web site or application, and where that domain name is a CNAME reference to the actual CloudFront distribution.
As soon as this is completed (preferably with a short DNS TTL) then the new CloudFront distribution will be hit by clients and will be filled up with the new versions of the objects.
After a while, you would then destroy and stop paying for the original CloudFront distribution that is no longer being referenced or used.
Simply replacing the CloudFront distribution effectively “invalidates” all of the objects at once, with no charges for invalidation requests and very little effort.
Once again, AWS wins with the principles of on-demand, pay for what you use, throw away what you don’t need.