AWS Website: Next.js
Deploys a Next.js app to AWS with
AWS.Website.Nextjs — the OpenNext (@opennextjs/aws) serverless
topology with zero CDK or CloudFormation wiring: the SSR server runs on
a streaming Lambda Function URL, static assets (including prerendered
pages) deploy to S3 behind CloudFront, images are optimized by a
dedicated Lambda at /_next/image, and ISR revalidation flows through
an SQS FIFO queue plus a DynamoDB tag-cache table.
app/page.jsxis server-rendered in the Lambda on every request and reads theGREETINGenvironment value declared inalchemy.run.tsviaprocess.env.app/api/hello/route.tsis an app-router API route handler.- Everything under
public/deploys as static assets.
The integration packages must be installed in the project (the source provider is loaded dynamically at deploy time):
bun add -d @alchemy.run/frontend-frameworks @opennextjs/aws open-next.config.ts is the minimal default the AWS deploy target
generates when a project has none: the server uses the
aws-lambda-streaming wrapper so the emitted handler streams on the
Function URL (invokeMode: RESPONSE_STREAM).
Note
Running this example from inside the alchemy monorepo hits a known
OpenNext limitation: the repo's bun isolated installs store packages
behind node_modules/.bun symlinks, and OpenNext's file trace ships
the server's node_modules as symlinks that the Lambda zip flattens —
breaking store-sibling resolution (Cannot find module '@swc/helpers/...' at runtime). A standalone copy of this project
(plain bun install, hoisted node_modules) deploys and serves
correctly.
Deploy
bun run deploy Unchanged sources skip the OpenNext build entirely on subsequent
deploys — the input files are content-hashed (scoped by memo.include).
Dev
bun run dev Local dev is Next's own dev server (next dev, native HMR) — no cloud
resources are created.
Destroy
bun run destroy