You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As aws-solutions-constructs has aws-cloudfront-X patterns, it would be good to have aws-cloudfront-mediastore pattern to implement AWS Elemental MediaStore container as an Amazon CloudFront distribution origin.
Use Case
An Amazon CloudFront distribution can have AWS Elemental MediaStore container as an origin, and this pattern would help to create an AWS CloudFormation template for live streaming solutions easily.
Proposed Solution
Users can use the existing AWS Elemental MediaStore container.
The pattern creates a new AWS Elemental MediaStore container if not using the existing one.
When creating a new container, it uses a user provided props. If no props are provided, it uses the default props.
The default props used by the pattern would contain aws:UserAgent to only allow the specific user agent, and the CloudFront is going to have that in the custom header.
The pattern creates a new Amazon CloudFront distribution, and it uses user provided props if there is any. Otherwise, it uses the default props.
Other
👋 I may be able to implement this feature request
⚠️ This feature might incur a breaking change
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered:
As aws-solutions-constructs has
aws-cloudfront-X
patterns, it would be good to haveaws-cloudfront-mediastore
pattern to implement AWS Elemental MediaStore container as an Amazon CloudFront distribution origin.Use Case
An Amazon CloudFront distribution can have AWS Elemental MediaStore container as an origin, and this pattern would help to create an AWS CloudFormation template for live streaming solutions easily.
Proposed Solution
aws:UserAgent
to only allow the specific user agent, and the CloudFront is going to have that in the custom header.Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: