- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello,
I understand you are trying to create a CloudFront distribution that directs traffic to an origin which is pointed to instagram.com, then caches instagram.com videos at the Content Delivery Network, to eliminate the necessity to send traffic to instagram.com again. I used the information you provided in the post to recreate the environment on my console. From what I am able to see, I am unable to use instagram.com as the origin for the CloudFront Distribution due to the origin’s privacy configurations. When I open the CloudFront distribution domain name, I am getting an error that says “Page couldn’t load” which implies that instagram.com cannot be used as an origin for a CF distribution.
A potential solution that can be used in this scenario is to utilize S3 and CloudFront to host the videos. Unfortunately, since CF cannot direct to instagram.com, the only way to access the videos through CloudFront is to download them and upload to an S3 Bucket. After uploading the videos, create a CloudFront Origin Access Identity to make sure viewers cannot bypass CloudFront to directly access the videos from S3. A CloudFront Distribution must be created afterward to serve, distribute, and cache the videos.
I hope this solution helped!
Documentation: Screenshot: Instagram Error via CloudFront Distribution: https://imgur.com/a/jHtJRB9 Tutorial: Hosting on-demand streaming video with Amazon S3, Amazon CloudFront, and Amazon Route 53: https://docs.aws.amazon.com/AmazonS3/latest/userguide/tutorial-s3-cloudfront-route53-video-streaming.html
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren