The previous design pattern is a good example of distributing data across many servers through the CloudFront service. Static content is cached and serviced in an optimized manner so that the end user can have the best experience in retrieving pages and content. Underneath the covers, CloudFront caches the URL as a key so that if the URL is accessed again, it can be served immediately, or near-immediately.

Although static data is just that: static, it does not mean that it does not change. If the maintainer of the page decides to update any of the content, end users would still get the old data until the new changes have migrated across all edge servers. If there was a need to show new data without the worry of users seeing different pieces, a new method must be used.

As described previously, the URL of the pages and content are what is used in the cache. The best method for getting new data to the user is to lower the cache timeout in the created CloudFront distribution...