aws-amplify / aws-amplify/amplify-cli
Hosting - custom caching in s3/cloudfront
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
It would be nice if there was a way to define custom s3 metadata for deployed projects.
Setting cache-control metadata in s3 gets passed through to cloud front and then on to the user. But it doesn't seem like there is an easy way to set the cache-control metadata during a deployment.
Maybe there could be a s3Headers.json file with something like:
`[
{files:"**/*.jpg", metaData:[{"Cache-Control":"max-age:100"}]},
{files:"**/*.js", metaData:[{"Cache-Control":"max-age:10", "other-header":"data"}]}
]`
Contributor guide
Research direction
The issue proposes an s3Headers.json file containing file patterns and S3 metadata such as Cache-Control. Start by tracing the CLI's hosting deployment path for S3 and CloudFront; done means matching deployed files receive the configured metadata during deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100