If I understand correctly, every insert or update will clear the cache for that table?
That's what my searching online has found, I don't know if that's true though or if I should be regularly reseting the cache.
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.
If you want to invalidate multiple objects such as all of the objects in a directory or all of the objects whose names begin with the same characters, you can include the wildcard, see Invalidation paths.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.Queries that happened a month ago are probably no longer useful now.So if it's storing those query results then it's completely worthless because chances are no one is going to run that same exact query again.If your Cloud Front distribution triggers a Lambda function on viewer request events, and if the function changes the URI of the requested object, you must invalidate both URIs to remove the object from Cloud Front edge caches: If you configured Cloud Front to forward cookies to your origin, Cloud Front edge caches might contain several versions of the object.
When you invalidate an object, Cloud Front invalidates every cached version of the object regardless of its associated cookies.
If you set it to on demand, then you have to explicitly state which queries you want cached when you issue them.
Important You can invalidate most types of objects that are served by a web distribution, but you cannot invalidate media files in the Microsoft Smooth Streaming format when you have enabled Smooth Streaming for the corresponding cache behavior.
I haven't touched anything such as reseting query cache for the year that the game has been up, I'm working with about 5000-1million rows depending on the table.
Everything is being updated constantly and things being inserted into the tables.
In addition, you cannot invalidate objects that are served by an RTMP distribution.