live-stream-on-aws

The live streaming solution you reference should allow the creation of MediaPackage with creating a CloudFront endpoint. Hopefully there was an option in the CloudFormation procedure to select this. You may want to partially run through the install and review the options during the MediaPackage section. If there is a choice to include the CloudFront endpoint with MediaPackage, then perhaps you can create a new live stream which includes CloudFront. The URL for the CF access will be included in the MediaPackage Endpoint information in the AWS console and via API. The original workflow can be removed by going to the CloudFormation service and removing that build out.

If the option to include CloudFront is not offered, you can create a CloudFront distribution from the AWS console, then use the existing MediaPackage endpoint(s) as the origin. This is a manual process and may require including different MediaPackage endpoints for each stream type of HLS, DASH, CMAF.

Thank you for your answer. I am creating live on node api. While creating the Media package endpoint most of the time the endpoint domain is the same, sometimes it is changing:

1. 0ef8937af0317fea.mediapackage.ap-northeast-2.amazonaws.com or
2. acee2b4c336e2e6f.mediapackage.ap-northeast-2.amazonaws.com most of the time this two endpoint hostnames are being created for my endpoint hls urls. I am concerned if another different endpoint hostname is created which is not added to cloud front as an origin! How can i control it.