CloudFront Signed URLs with Node.js

[@isaiaspereira2796]

Dude! Your content and explanation of the services you cover are phenomenal!!!!! :) Thank you much man!

[@santangelx1573]

Your content is great, the audio, video quality, explanation... I have no clue as to why you don't have 100k subs

[@videoideas.io_]

Can't believe this is free 🔥 Awesome work man!

[@lastbenchers019]

Bro bro bro your content is just toooo awesome

[@megapixel23]

Thank you, man! That's exactly what I was looking for :)

[@Sergio-ef5pz]

Thanks for an amazing content! One little critic, is that when the video begins, it's not clear that you're previewing a future segment of the video. At first I thought the video was glitched,

[@anu8928]

Awesome explanation! 🎉🎉

[@ifeody]

Thank you Sam! Love you!

[@sidthetech7623]

Saved my ass. Now I won't get the "Reinforced Shock Treatment" ... TY so much!

[@aussietramp]

Dude,you make me wanna leave my job since i'll never been as sharp as you..damn you!

[@SamMeechWard]

Just keep watching all my videos and commenting on them and become a channel member 🤗🤗🤗 Then you’ll be sharp

[@luismontero259]

Thanks dude, good tutorial, really helpful

[@gizataibassov6738]

thanks mate! this is well explained!

[@Sd-Bye]

great tutorial, I was having a lot of issues getting my private key import to work (maybe because I'm using AstroJS?). If anyone else is having issues try converting your key into base64 (cat private_key.pem | base64) then paste the output into your .env. Then parse the base64 with a buffer in your code (Buffer.from(, 'base64')

[@fahreziadha]

seeeshh!! u helping me! many thanks :D :D

[@hieudinhofficial]

Thank you, your video is so helpful to me to understand

[@yusstilllearning2749]

Great Content bro!! Thank you!! keep it up❤

[@techh4ck936]

Thanks for sharing awesome contents.

[@maazmunir7502]

Terrific video. Thanks for the help.

[@wickedknock9798]

This XML file does not appear to have any style information associated with it. The document tree is shown below.

[@fahadmahmood8656]

Great content. I am working on CMS in Laravel, how would signed URL effect the front end web because we want consistent study URL where singed or presigned url change the URL address on each request. I suppose we just have to use public URL access in such case. Am I missing anything? Should we consider cookies instead of signed URL?

[@paragbhide1695]

Big Fan of your videos!!!

[@otuleja]

This was perfect... thank you

[@emmabijmohun770]

Great vid, thank you!!

[@uwanxttesting]

I followed same approach, but in my case it's showing Access Denied

[@dmitrymatio]

How did you breakdown the url so quickly? What's the shortcut

[@SamMeechWard]

No shortcut, I’m magic

[@praveensequeira1525]

Hi, thank you for the great content. Have a quick qn. My understanding is that you showcased how we can use signed URLs to grant temporary access to the image i.e. no one can access the image even if they copied the URL from an authorized user's machine and used it after the expiry. Is it possible to also somehow provide access to only customers who have paid for the content, and not some random website visitor? I'm not sure if my question doesn't make perfect sense or has holes in the requirement, but glad to be corrected. thank you. Reference: Preventing Unauthorized Access: By requiring a valid signed URL to access a resource, CloudFront ensures that only users with the correct URL and authorization parameters can view or download the content. This effectively prevents hotlinking and unauthorized access.

[@pradyumnacharate1194]

Hello Sam..Thanks For share...how can I restrict signed url to be accessible only when request comes from my frontend domain? is their any way?because currently anyone can download that url easily.

[@EddieMao]

great video, thank you so much.

[@kapilkumar2204]

nicely explained

[@andreseungyeobsong4899]

your video rocks!!

[@rickshawty]

dude you are awesome!

[@KephaMisasa]

Daaang bro

[@san3724]

Awesome video!!

[@Foyzul]

Thanks 🎉

[@jasonvictor1798]

Great video. But how would you set this up for a subscription service where paid subscribers get premium content i.e. 4k videos?

[@MatttAt]

Is there a way to bypass these or generate keys or expiry extensions? Outside of their api, Google uses signed url's where you look at the ads being run by their advertisers. I bookmarked some of the advertiser pages and the links work for only a day or so.

[@ntsagar9]

I have one project that email signature I am using cloudfront sign url for s3 image and issue is once explire the url that email signature not working. You have any solution for this ?

[@rishabhmishra4093]

i tried this but when i access file conent through signed uRL returns access denied

[@ranicket]

Hmmm for some reason I'm getting 403 when loading images using the signedUrl.. any ideas, Sam?

[@fkszm3]

Thank you!

[@Sunil-e1d6b]

nice work

[@okeyshourovroy2769]

Please make a video on signed cookies

[@lambuitung6754]

very useful !!!

[@SamMeechWard]

Glad to hear that!

[@clearthinking5441]

But technically the bots can still download the files and build their own database? They just need to sign in to your website periodically?

[@ahmedalobed7382]

Hi Sam I saw and follow you previous video (Set up a CloudFront CDN for an S3 Bucket) But it was not work. whatever object in S3 i tried to access to it, it said (Access Denied) i spent a lot of times to see what is wrong with my Cloudfront, then i know that i must first to make my objects in S3 public for all the world so Cloudfront could access them. Amazon docs: By default, your Amazon S3 bucket and all the files in it are private-only the Amazon account that created the bucket has permission to read or write the files. If you want to allow anyone to access the files in your Amazon S3 bucket using CloudFront URLs, you must grant public read permissions to the objects. So now I am asking: what is the benefit of signed Cloudfront URLs if the object already must be public for all the world? and anyone could access this object directly from S3 bucket?

[@SamMeechWard]

They don't need to be public. Follow my videos exactly, I never make any of my objects in my S3 bucket public. They are private and can only be accessed when a signed url is generated by an IAM user that has that permission. With the CloudFront example, the only thing that can access the files in s3 is the cloudfront distribution. Nothing else can access them. Then you sign urls to allow some access to cloudfront.

[@babayaga6172]

Hi Sam you are actually doing amazing 🤩 But I have am wondering performance bottlenecks You are mapping on every document and generate a signed url Why should we genete url at each request if url is generated already for one day if a single user is keep refreshing page we are generating every time same url How to.handle this?

[@SamMeechWard]

The mapping is not processor intensive so you’ll be fine, but you could also store the url in a database or redis cache if you wanted to reuse the url

[@babayaga6172]

@@SamMeechWard Thanks ☺️

[@marcosveniciusubiali783]

Perfect

[@suneel1875]

mate I am getting this error: Error: error:0909006C:PEM routines:get_name:no start line please help

[@tayaward1733]

you've probably figured it out by now lol but i removed all new lines, so the it is an inline string and added after-----BEGIN PRIVATE KEY----- and before -----END PRIVATE KEY-----, so it looks something like this CLOUDFRONT_PRIVATE_KEY="-----BEGIN PRIVATE KEY----- abcd -----END PRIVATE KEY-----"