Encoding 45-minute city council session videos exceeds practical La…

Question

Encoding 45-minute city council session videos exceeds practical Lambda maximum duration, yet ops only keeps raising the function timeout. What should the team do instead?

Accepted Answer

Move the long-running encode off Lambda to a more appropriate compute option such as containers or AWS Batch rather than treating timeout increases as the solution. — A 45-minute encode is a marathon; Lambda is built for sprints with a hard duration ceiling. Stop cranking timeout theater—park long batch video work on Batch or containers. Logs Insights will not render MP4s.

Answer

Keep increasing the Lambda timeout beyond the service maximum until a single invoke finishes the encode.

Answer

Perform the 45-minute encode inside an API Gateway mapping template with no worker compute.

Answer

Treat CloudWatch Logs Insights queries as the media encoder and skip dedicated compute.

Encoding 45-minute city council session videos exceeds practical Lambda maximum duration, yet ops only keeps raising the function timeout. What should the team do instead?

Short Explanation

Full Explanation