s3-resizer: HTTPS problem

Hi!

I’ve got the resizing working, but Lambda is not working on HTTPS. I can reach my original (public) S3 image on https://[bucket].s3.eu-north-1.amazonaws.com/[image].jpg and http://[bucket].s3.eu-north-1.amazonaws.com/[image].jpg

And resized via Lambda on HTTP http://[bucket].s3-website.eu-north-1.amazonaws.com/300x300/[image].jpg But on on HTTPS https://[bucket].s3-website.eu-north-1.amazonaws.com/300x300/[image].jpg That just times out.

Though, when I have used Lambda over HTTP I can reach via HTTPS directly through S3.

Any ideas?

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 21 (9 by maintainers)

Commits related to this issue

Add CacheControl for fixing the bug on CloudFront There are 2 issues related to Cyclic redirect when using CloudFront https://github.com/sagidM/s3-resizer/issues/5 https://github.com/sagidM/s3-resize... — committed to sagidM/s3-resizer by kofon95 5 years ago

Most upvoted comments

Yes

First i followed this guide to point https to my S3 website https://medium.com/@channaly/how-to-host-static-website-with-https-using-amazon-s3-251434490c59

Then

I pointed the URL Variable to my https domain.
I uploaded the new zip, created a new release of Lambda and pointed “prod” to the new release.
Went to CloudFront -> chose my distribution -> Behaviours -> Edit. Here I could change Default TTL to 0.

subpublic on Nov 20, 2019

Wanted to add I ran into issues when configuring this for my Cloud Front distribution.

On your distribution origin domain name make sure you enter the S3 web Endpoint - not the S3 origin.

Otherwise you will receive access denied errors. See issue and resolution here: https://stackoverflow.com/questions/34060394/cloudfront-s3-website-the-specified-key-does-not-exist-when-an-implicit-ind/34065543#34065543

adskiremote on Dec 16, 2019

YAY! Changed the Default Cache TTL to 0, now everything works! (with the version you posted)

subpublic on Nov 20, 2019