Chapter 448: Customizing Lambda output destination
Core Idea
By default a render artifact is saved into the same S3 bucket as where the site is located under the key renders/${renderId}/out. {extension} (for example: renders/hy0k2siao8/out.
Key Concepts
- Customizing the output name
- Customizing the output bucket
- Saving to another cloud<AvailableFrom v="3.2.23" />
- Saving to another AWS region<AvailableFrom v="4.0.112"/>
- See also
Code Examples
const {bucketName, renderId} = await renderMediaOnLambda({
region: 'us-east-1',
functionName: 'remotion-render-bds9aab',
composition: 'MyVideo',
serveUrl: 'https://remotionlambda-qg35eyp1s1.s3.eu-central-1.amazonaws.com/sites/bf2jrbfkw',
inputProps: {},
codec: 'h264',
imageFormat: 'jpeg',
maxRetries: 1,
privacy: 'public',
outName: {
key: 'my-output',
bucketName: 'output-bucket',
},
});
- What it demonstrates: Usage pattern for Customizing Lambda output destination from the official docs.
Key Takeaways
- Understand customizing the output name when working with Customizing Lambda output destination.
- Understand customizing the output bucket when working with Customizing Lambda output destination.
- Understand saving to another cloud<availablefrom v="3.2.23" /> when working with Customizing Lambda output destination.
- Understand saving to another aws region<availablefrom v="4.0.112"/> when working with Customizing Lambda output destination.
- Understand see also when working with Customizing Lambda output destination.
Connects To
- api: related page in the Lambda (@remotion/lambda) section.
- Approuterwebhook: related page in the Lambda (@remotion/lambda) section.
- Authentication: related page in the Lambda (@remotion/lambda) section.