-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Pre-signed URLs #4
Comments
@fhickman No worries! I will add this to list of features to implement 😊 |
Closed because AWS S3 SDK only allows max of 1 week... See #14 |
@fhickman and @joshdholtz I was able to start getting around this by putting CloudFront in-front of the S3 bucket and using a private ACL. I then used Lambda@Edge to implement some kind of authentication in front if hitting the bucket (simple http-auth for now, but it could be made more complex) However, I am running into a new challenge, which is that the hostname is baked into the Any suggestions on how I might do that? |
It actually looks like #48 would fix my issues. Any reason that was never merged? |
Lots of our app distribution is for internal-only Enterprise-licensed builds.
For S3 buckets that we do not wish to make publicly readable, it would be great to generate the URLs within the .plist/.html using pre-signed URLs. You could supply a parameter for the expiration time of the URLs, or default it to 1 year.
(Sorry, if I knew a lick of Ruby I'd generate a PR myself. :) )
The text was updated successfully, but these errors were encountered: