The AWS Lambda package runs HyperFrames' distributed render primitives on AWS. It ships the Lambda handler, a Node client SDK, and an optional CDK construct for provisioning the render stack inside an adopter's AWS account.

npm install @hyperframes/aws-lambda

Use @hyperframes/aws-lambda when you need to:

• Render large compositions on AWS Lambda instead of one local machine
• Fan out plan, renderChunk, and assemble through Step Functions
• Store render inputs, intermediate chunks, and outputs in S3
• Drive renders from CI, a backend service, or a custom CLI
• Provision the render topology from a CDK app

Use a different package if you want to:

• Render locally or inside your own Node process - use the CLI or producer
• Run the same distributed model on Google Cloud - use gcp-cloud-run
• Build or edit composition HTML - use studio, sdk, or core

aws-cdk-lib and constructs are optional peer dependencies. SDK-only consumers do not need them unless they import from @hyperframes/aws-lambda/cdk.

The Lambda adapter wraps the distributed producer primitives behind one dispatch boundary:

The handler uses @sparticuz/chromium by default, with a build-time fallback for bundling chrome-headless-shell directly when needed.

After deploying the AWS resources, use the SDK from Node:

import { deploySite, getRenderProgress, renderToLambda } from "@hyperframes/aws-lambda/sdk";

const site = await deploySite({
  projectDir: "./my-composition",
  bucketName: "hyperframes-render-bucket",
});

const handle = await renderToLambda({
  siteHandle: site,
  planProtocol: "v2",
  bucketName: site.bucketName,
  stateMachineArn: "arn:aws:states:us-east-1:123456789012:stateMachine:hyperframes-render",
  config: {
    fps: 30,
    width: 1920,
    height: 1080,
    format: "mp4",
    chunkSize: 240,
    maxParallelChunks: 16,
    runtimeCap: "lambda",
  },
});

const progress = await getRenderProgress({ executionArn: handle.executionArn });
console.log(progress.status, progress.overallProgress, progress.costs.displayCost);

Plan v2 is recommended for new integrations because workers fetch manifest-selected content-addressed artifacts. For backwards compatibility, omitting planProtocol still selects v1; existing callers do not change behavior until they opt in.

renderToLambda() validates the distributed render config before starting the Step Functions execution, so invalid dimensions, formats, chunk sizes, or payload sizes fail synchronously.

import { App, Stack } from "aws-cdk-lib";
import { HyperframesRenderStack } from "@hyperframes/aws-lambda/cdk";

const app = new App();
const stack = new Stack(app, "VideoRender");

const render = new HyperframesRenderStack(stack, "HyperframesRender", {
  // reservedConcurrency: 8,
  // lambdaMemoryMb: 10240,
  // chromeSource: "sparticuz",
});

console.log(render.bucket.bucketName, render.stateMachine.stateMachineArn);

From the monorepo:

bun install
bun run --cwd packages/aws-lambda build:zip
bun run --cwd packages/aws-lambda verify:zip-size

The build stages Chromium, Puppeteer, FFmpeg, and the handler bundle into packages/aws-lambda/dist/handler.zip. The size verifier keeps the unzipped artifact below Lambda's deployment limit.