Our team has run into issues lately getting our production environment to respect file changes on production following a deployment. We can confirm the S3 holding the files in question is the same between production and stage instances and when uploading to our stage environment via Kentico we kick off an upload to S3. The file is then retrievable and seen once the cache expires. So stage is comparatively fine. We've not deployed admin to production, just the front facing site, so when we synchronize changes to production we are unable to clear the internal Kentico cache on Production. Our best resolution thus far has been to cycle the EC2 instances hosting the site but having to basically restart the site when there's a file change isn't a reasonable solution.
In Kentico's Settings > System > Performance we do have 'Server content caching', 'Server file caching', and 'Client caching' set at 0 minutes in an attempt to halt all internal caching from Kentico and just use the external file stores, but this doesn't seem to operate as expected.
I do see in the Kentico documentation (see relevant link below) the following:
"If your project uses external file storage (such as Azure Blob Storage or Amazon S3), you need to clear the cache manually after making changes to files or wait for the cache to expire. The automatic clearing of the server-side file cache does not work for files in external storage."
This would indicate that AWS hosting isn't supported by Kentico and some mechanism is required to let Kentico know there's a new file (or in our case not to cache the files at all).
Please provide recommended use case to trigger cache clear within Kentico when an external file is changed. Ideally without needing to refresh the server instances.
Environment
Xperience by Kentico version: 31.5.0
.NET version: 10
Execution environment: Private cloud (AWS)
Link to relevant Xperience by Kentico documentation