Sometimes with ffmpeg and seeking against MP4 files, it will generate an excessive amount of HTTP requests. This takes way too long and causes the Lambda to timeout.
Since the maintainers over at ffmpeg haven't fixed this yet, that means the only solution really is to cache the file on-disk first, and then run the ffmpeg operations against them.
However, inside Lambda, this is not possible as there is not enough storage space to allow for reasonably-sized videos.
Because of this, we should probably use Fargate instead of Lambda for the processing here, similar to some of my other CloudFormation processing packages.
Sometimes with
ffmpegand seeking against MP4 files, it will generate an excessive amount of HTTP requests. This takes way too long and causes the Lambda to timeout.Since the maintainers over at
ffmpeghaven't fixed this yet, that means the only solution really is to cache the file on-disk first, and then run theffmpegoperations against them.However, inside Lambda, this is not possible as there is not enough storage space to allow for reasonably-sized videos.
Because of this, we should probably use Fargate instead of Lambda for the processing here, similar to some of my other CloudFormation processing packages.