How to deploy Next.js to AWS

Deploy a Next.js application on ECS Fargate behind an Application Load Balancer, or serve a static export from S3 and CloudFront.

Prerequisites

A Git repository containing your application and its production build command.
A Ravion account with your AWS account connected. Start free at Ravion signup.
The Ravion CLI installed and authenticated. See CLI installation.

The examples use my-org/my-app as a placeholder. Replace it with your repository before applying the config.

Set up this Next.js app for Ravion SSR or static hosting.

Open in Cursor

Configure the deployment

Deploy a Next.js App Router or Pages Router application on ECS Fargate behind an Application Load Balancer. Ravion provisions the network and compute resources in your AWS account. This example uses Railpack for the build. Use build_source: dockerfile instead when you need a custom Dockerfile. Set output: "standalone" in next.config.js or next.config.mjs. Next.js writes a self-contained server to .next/standalone/server.js. Copy public and .next/static into the standalone image as described in the Next.js deployment documentation.

ravion.yaml

project:
  givenId: nextjs-app
  name: Next.js app
environments:
  - givenId: production
    name: Production
    moduleInstances:
      - givenId: network
        name: Network
        type: rvn-aws-network
        version: 1.0.0
        input:
          aws_account_id: ravion-prod
          aws_region: us-east-1
          name: nextjs-production
      - givenId: cluster
        name: ECS cluster
        type: rvn-ecs-cluster
        version: 1.0.0
        input:
          network:
            moduleGivenIdRef: network
          name: nextjs-production
      - givenId: web
        name: Next.js web service
        type: rvn-ecs-web
        version: 1.0.0
        input:
          cluster:
            moduleGivenIdRef: cluster
          name: nextjs-production-web
          build_source: railpack
          source_repo: my-org/my-nextjs-app
          railpack_build_cmd: npm run build
          railpack_start_cmd: node .next/standalone/server.js
          container_port: 3000
          fargate_size:
            vcpu: 0.5
            memory_gb: 1

Set HOSTNAME=0.0.0.0 and use the ECS-provided PORT value in the server environment. The default Next.js server port is 3000.

Static export

For a fully static site, set output: "export" instead. Next.js writes the export to out, which you can serve from S3 and CloudFront.

ravion.yaml

project:
  givenId: nextjs-static
  name: Next.js static site
environments:
  - givenId: production
    name: Production
    moduleInstances:
      - givenId: static-site
        name: Next.js site
        type: rvn-aws-static
        version: 1.0.0
        input:
          aws_account_id: ravion-prod
          aws_region: us-east-1
          name: nextjs-static-production
          routing: filesystem
          build_source: railpack
          source_repo: my-org/my-nextjs-site
          output_directory: out
          railpack_build_cmd: npm run build

Static export does not run Next.js server features such as API routes, middleware, or server actions. Use public NEXT_PUBLIC_* values for browser configuration.

Apply and connect your domain

ravion project create --given-id nextjs-app --name "Next.js app"
ravion project config apply nextjs-app --file ravion.yaml --dry-run
ravion project config apply nextjs-app --file ravion.yaml

Follow custom domains to connect your Application Load Balancer hostname. For static export, connect the CloudFront hostname instead.

Next steps

Custom domains

Point a domain at your deployed service and manage its certificate.

Project config

Preview and apply Ravion configuration from source control.

Pipelines

Add approvals, migrations, and deployment automation.

Logs and metrics

Inspect deploy output and production health in Ravion.

​Prerequisites

​Configure the deployment

​Static export

​Apply and connect your domain

​Next steps