Forum Discussion

tattness's avatar
tattness
Binge Watcher
5 years ago
Solved

AWS Cloudfront and S3 configuration

In my last post I was configuring my channel's content and feed URL to be stored in AWS S3 and distributed through AWS Cloudfront. I created my S3 bucket and Cloudfront on February 15 and I received a notification that I've reached 100% of my Simple storage service. My channel has not been published yet and has only been tested by myself on my tv to ensure links are working and everything looks good. On that note I've been adding/deleting content to my bucket regularly, could that may have contributed to my usage being "eaten up"? Or is my channel not utilizing the proper access point in my Cloudfront. My original access point was to the S3 bucket itself, last night I created an access point of my JSON file in the bucket and changed my feed URL to that JSON access point. Any help is greatly appreciated.

 

 

  • Yes, that looks correct.  It should be the "Domain name" of the CloudFront distribution you defined.

12 Replies

  • tattness's avatar
    tattness
    Binge Watcher

    Baradanikto sorry to tag you but I saw you use AWS Cloudfront for your channel. Is your access point your actual JSON file or your S3 bucket?

    • Baradanikto's avatar
      Baradanikto
      Roku Guru

      Can you explain what you mean by "access point"?  Are you asking what I specify in the Roku developer portal?

      • tattness's avatar
        tattness
        Binge Watcher

        Hi Baradanikto, sorry what I meant was your origin domain name and path in AWS Cloudfront. In one of my images I attached I created 2 origin domain names in Cloudfront. The first was for the S3 bucket itself the other was for the JSON feed file itself in the S3 bucket. I understand for a feed URL it needs to point directly to the JSON file which I did and my content is showing up in my channel preview and I realized that the URL for the JSON file and the origin domain name and path is the same-  https://tattnesstv.s3.amazonaws.com/Tattness+TV.json. My concern is that when content is accessed from the channel it is fetching the content from the S3 bucket itself and not utilizing the Cloudfront as my usage dashboard is showing no usage from the Cloudfront but 100% from the S3 (see image)

        These are my two origin domain paths:


        I hope this makes sense. Thank you again.