For more information about access logs, see Access Logs.
Whether you invalidate objects by using the Cloud Front console or the Cloud Front API, the requirements and limitations for specifying objects are the same.
For more information, see Configuring Cloud Front to Cache Objects Based on Cookies.
If you configured Cloud Front to forward a whitelist of headers to your origin and to cache based on the values of the headers, Cloud Front edge caches might contain several versions of the object.
For more information about the charges for invalidation, see Paying for Object Invalidation.
To control the versions of objects that are served from your distribution, you can either invalidate objects or give them versioned file names.
You can submit a specified number of invalidation paths each month for free.
If you submit more than the allotted number of invalidation paths in a month, you pay a fee for each invalidation path that you submit.
If you want to invalidate selected objects but your users don't necessarily access every object on your origin, you can determine which objects viewers have requested from Cloud Front and invalidate only those objects.
To determine which objects viewers have requested, enable Cloud Front access logging.
You cannot copy an existing invalidation, update the invalidation paths, and save the updated invalidation without running it.
Important If you copy an invalidation that is still in progress, update the list of invalidation paths, and run the updated invalidation, Cloud Front will not stop or delete the invalidation that you copied.
To display information about an invalidation using the Cloud Front console In addition to the invalidation methods provided by Cloud Front, several third-party tools provide ways to invalidate objects. If you're invalidating objects individually, you can have invalidation requests for up to 3,000 objects per distribution in progress at one time.