- Newest
- Most votes
- Most comments
This sample solution comes somewhat close to what you want, and could be tweaked to fit your needs: https://github.com/aws-samples/cloudfront-authorization-at-edge
Currently it misses an upload feature you need, and also it misses the feature of having users only see/edit their own files. It would not require signed URLs because it relies on good old cookies for authentication.
However I do like to point out that generating signed URLs is in fact very quick, and usable for your purpose too. I doubt it would be too slow for hundreds of URLs even. Signing an (https) S3 URL using AWS credentials is quick--this does not need to invoke any AWS service over the wire, it's a cryptographic operation that runs locally on the client (in your browser's JavaScript in this case).
I hope that helps somewhat, I realize it's not the whole story. There's a lot to your question, it's quite a full blown application you're trying to build :)
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 8 months ago
Thanks. I did end up putting together a simple lambda@edge function that is similar to what you pointed to. I am uploading content by using presigned urls, but assume that using cookies with a lambda@edge function will be more performant for downloading content.