Just a small, simple feature to allow adding further origins and cache behaviors to the cloudfront distribution, for situations where there might be a separate bucket containing media or user generated data, with a corresponding path (and many other use-cases, really). So far you'd have to copy the entire Distribution resource to the serverless config and add the changes there, this should make it a bit more elegant.
Hot tip: use external files and reference them in the serverless.yml:
origins: ${file(./resources/customCloudfront.yml):Origins}
Just a small, simple feature to allow adding further origins and cache behaviors to the cloudfront distribution, for situations where there might be a separate bucket containing media or user generated data, with a corresponding path (and many other use-cases, really). So far you'd have to copy the entire Distribution resource to the serverless config and add the changes there, this should make it a bit more elegant. Hot tip: use external files and reference them in the serverless.yml:
origins: ${file(./resources/customCloudfront.yml):Origins}