-
Notifications
You must be signed in to change notification settings - Fork 945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@remotion/lambda
: Allow configuring a VPC
#3881
@remotion/lambda
: Allow configuring a VPC
#3881
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dcc69da
to
5f19ecf
Compare
Thanks a lot for this! This was done super carefully, which I appreciate a lot! Does this already unlock additional functionality! Remotion Lambda only downloads via HTTP, or have you tricked it into doing something different? Or do you pass the internal endpoint as the I know the internal endpoint is interesting, and we might allow proxying S3 assets natively in the future. |
I'm just curious what exactly you are doing. |
@remotion/lambda
: Allow configuring a VPC
Indeed, @JonnyBurger , we do use internal endpoints as the |
Add VPC config support so remotion render lambda can download assets internally from the VPC.
With the VPC config option, the assets can be downloaded via an internal endpoint. That increases security and allows cost reduction. One clear use case is downloading assets from an S3 private bucket via an S3 VPC endpoint.