At this point in the chapter, we have covered two ways of delivering static content. The first was a pattern that lets us deploy a sort of hybrid service in which some files remain on S3, while the bulk of the application would reside on the server itself. In the second pattern, we discussed removing the hybrid portion and hosting all of this from within S3 without the need for a server.

While these previous examples solve a very simple problem, they might not solve a real-world issue such as securing data that does not reside on the server itself, similar to the hybrid high availability pattern. We should try to solve a real-world issue with a real code-based solution. Let's imagine that we have some large files in an S3 bucket that should not be publicly accessible by default.

Instead of just serving out the content to any connection, we should secure these files somehow. One approach might be to use policies on the bucket itself, but that requires maintaining a policy...