Remotion Lambda Timeout

[bitter badge]

@tropic kraken please help with this

[tropic kraken]

I’m afraid I don’t have quite enough info to pinpoint the root cause. A few quick checks might help:

• Is your Lambda running in a VPC without NAT/Gateway? If so it won’t be able to fetch public S3 URLs—either remove the VPC or add a NAT.
• Does the function’s IAM role include s3:GetObject on your bucket/key?
• Is the MP4 publicly readable (or are you supplying a presigned URL)?
• Enable verbose proxy logs by setting DEBUG_PROXY=1 in your Lambda env and inspect CloudWatch for more clues.

If you’ve validated all of the above and still see the proxy timeout, the Remotion team can dive deeper—please reach out via their support channels.

[high inlet]

I checked this.

The IAM role used by the Lambda function has the necessary s3:GetObject permissions.

We’re not using a VPC for this Lambda function.

The S3 bucket allows public access, so the files should be reachable without authentication issues.

Given all that, we're still puzzled why one video loads fine and the other doesn't — especially since both files are in the same bucket and have similar access characteristics.

Any other ideas or things we might be missing?