The setup, I have videos being stored and served from S3. I also setup a cloudfront distribution to serve these same files. Now, I added the cloudfront cname to the site and the videos serve up just fine through cloudfront.

Here's the problem, when I add a pre-signed url to the config, the videos serve up from the S3 bucket URL instead of cloudfront URL. When I take the pre-signed path out of the config, the videos go back to serving from cloudfront. When the pre-signed path is setup, the urls to the videos do include the signed credentials.

I'd like the videos to serve from cloudfront and not the bucket directly.

What am I doing wrong here?

CommentFileSizeAuthor
#8 amazons3-support_cloudfront_signed_urls-1837920-7.patch4.75 KBchunty
#6 amazons3-support_cloudfront_signed_urls-1837920-6.patch3.63 KBpdrake

Comments

joaomachado’s picture

joaomachado commented

I seem to be having the same issue...I have images and files under two different content types set up. I too have the a CNAME set up (cdn.mysite.com) that works fine under images but content that has files for download they are served directly from S3. If I manually change the path to cdn.mysite.com/
before the 60 seconds runs out it will download and not download after the 60 seconds. I think the first step may be to find out why the CNAME is not being changed on all certain content.

Subscribing to this one...

barwonhack’s picture

barwonhack commented
Category: support » bug

Bump

j.branson’s picture

j.branson commented

Same things is happening for me. I'm not able to get the video file to download before or after my time out though when I manually replace the url with my cloudfront address. I get the no style formatting message from S3.

This is probably in the AmazonS3StreamWrapper.inc file if I had to bet. I've had to make a few changes in that file before. I'll take a peak later but I'm not sure if I'll be able to figure it out. Any suggestions here are quite welcome!

...at the same time I will note this: videos are huge files. As long as the non-profit I work with is paying for it, I know we won't be too terribly pained if we don't have to pay between 12 to 25 cents a Gig transfered for the large amount of internally housed videos we have. Also I suppose that through cloudfront it's possible to make the whole bucket signature access. This seems like a bit silly to do and I haven't wanted to put the time in to experiment with it yet, but it is an option.

Peace

barwonhack’s picture

barwonhack commented

Okay thanks. The alternative is to just change the cloudfront domain every now and then if the content keeps getting jacked.

haysuess’s picture

haysuess commented

I see the same thing. Luckily, I set up presigned URLs only for 1 directory, so it's fine for me, but it would be nice to have this fixed.

pdrake’s picture

pdrake commented
Title: Cloudfront CNAME and signed urls not working » Support Cloudfront signed URLs
Category: bug » feature
Status: Active » Needs review
StatusFileSize
new amazons3-support_cloudfront_signed_urls-1837920-6.patch3.63 KB

This happens because the signing code in the module currently only supports the S3 presigned urls method, not CloudFront URL signing. This patch adds support for CloudFront URL signing. Using this patch requires setting the cloudfront keypair settings on the AWS SDK UI module's configuration page.

chunty’s picture

chunty commented

I've extended this patch a little allow you lock down the signing a bit and use the IP address in the signed url that is generated but how do I submit this patch for review here?

chunty’s picture

chunty commented
Issue summary: View changes
StatusFileSize
new amazons3-support_cloudfront_signed_urls-1837920-7.patch4.75 KB

I've extended this patch to include the option to use the IP address in the policy as documented here: http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/privat...

Please ignore my comment at #7 asking how to upload it - I figured it out

justafish’s picture

justafish
she/her
Primary language English
Location London, UK
commented
Status: Needs review » Fixed

Fixed https://github.com/justafish/amazons3/commit/4b85704fba969f46382009c20aa...

j.branson’s picture

j.branson commented

Thank you!

chunty’s picture

chunty commented

@justafish

Have you rolled your changes into any of the versions on drupal.org or just github.

Thanks
Chris

justafish’s picture

justafish
she/her
Primary language English
Location London, UK
commented

They're the same repo. It's in the 1.0 release.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

fox_01’s picture

fox_01 commented

In Version 1.0 the help message says that cloufront signed url are not supported in he help of the field torrent url

A list of paths that should be delivered through a torrent url. Enter one value per line e.g. "mydir/*". Paths are relative to the Drupal file directory and use patterns as per preg_match. This won't work for CloudFront presigned URLs.

Is that just an old description or does the 1.0 not contain this patch?