Switch S3 location for static data assets #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replace S3 location for static data assets to enable DevOps to remove real-time data from data archive (with data lifecycle policies that reduce our costs).
The Hacko-data-archive will get migrated to glacier as the data ages out - lower cost, slower retrieval - and it costs us every time one of the files gets called back to service.
The Hacko-cdn bucket will be considered a quick-and-dirty CDN and will keep its data in active rotation for typical web access.
If you'd prefer to use a standard web (http) retrieval approach instead of the
boto
library, we can turn on the static website hosting for the bucket as well.