asteadman
Joined 11 years ago
Joined 11 years ago
I'd suggest https://aws.amazon.com/elastictranscoder/details/, its quite affordable and much easier than doing it yourself, assuming it does what you need.
From the research I've done, I'd suggest MPEG-DASH for reasonable cross-ish platform adaptive streaming without requiring fancy video servers. Your requirements and platforms might be different than mine though. Research is required.
I feel like something that simply 302'd the user to the most recently posted URL would make more intuitive sense, but with obvious drawbacks.
It's really only useful for a small list of file formats. Doesn't really do much for you if you primarily use s3 for binary data or static web hosting.
EDIT: in retrospect, the pricing means its probably not economically viable.
You can hook your lambda up to a cloudwatch scheduled event (http://docs.aws.amazon.com/AmazonCloudWatch/latest/events/Sc...). If you don't do much when this happens (like, you exit immediately), then you won't be charged much compute time. Can't find the reference to how often you should ping it to keep it warm, probably varies, IIRC hourly would be plenty.
As for the cold boot issue, I thought the standing solution was to have a "fast-exit" ping-like code-path within the lambda. Query it on a regular basis (you can even do it with a lambda scheduled-event). That way your lambda should be kept warm.