Deploy →Edit this page

AWS Lambda

To deploy to AWS, use the built-in aws adapter. This adapter deploys your application as an AWS Lambda function with a CloudFront CDN distribution, using AWS SAM (Serverless Application Model) for infrastructure management.

You need the following tools installed:

brew install awscli aws-sam-cli

Then configure your AWS credentials:

aws configure

You'll need your AWS Access Key ID and Secret Access Key. You can create these in the AWS IAM Console under Users → Security credentials → Access keys.

No additional packages are needed — the adapter is built into @lazarv/react-server.

Add the adapter to your react-server.config.mjs file:

export default {
  adapter: "aws",
};

You can customize the adapter by passing options:

export default {
  adapter: [
    "aws",
    {
      name: "my-app",             // Application name (used in resource names)
      stackName: "my-app-stack",  // CloudFormation stack name
      runtime: "nodejs20.x",     // Lambda runtime (default: "nodejs20.x")
      memorySize: 1024,          // Lambda memory in MB (default: 1024)
      timeout: 30,               // Lambda timeout in seconds (default: 30)
      architecture: "arm64",     // Lambda architecture (default: "arm64")
      authType: "NONE",          // Function URL auth type (default: "NONE")
      environment: {             // Additional environment variables
        MY_API_KEY: "value",
      },
    },
  ],
};

Configuration Options

Build and deploy your application:

pnpm react-server build [root] --adapter aws
sam deploy --guided --stack-name my-app --capabilities CAPABILITY_IAM

Or use the --deploy flag to build and deploy in one step:

pnpm react-server build [root] --adapter aws --deploy

The first deployment uses --guided mode which prompts for configuration and saves it to samconfig.toml. Subsequent deployments use the saved configuration automatically.

The adapter creates the following AWS resources:

How it works

All requests flow through a single Lambda origin:

Viewer → CloudFront → Lambda
                       ├─ Static file? → Serve from disk with Cache-Control
                       └─ Dynamic?     → SSR via react-server

The Lambda handler includes all static files in its deployment package and serves them directly from the filesystem. Each response includes appropriate Cache-Control headers:

After the first request, CloudFront serves cached static files directly from the edge without invoking Lambda. The custom cache policy (DefaultTTL: 0, MinTTL: 0, MaxTTL: 31536000) defers entirely to the origin's Cache-Control headers.

Custom domain

To use a custom domain with your CloudFront distribution, extend the distribution config:

export default {
  adapter: [
    "aws",
    {
      cloudfront: {
        distributionConfig: {
          Aliases: ["www.example.com"],
          ViewerCertificate: {
            AcmCertificateArn: "arn:aws:acm:us-east-1:123456789:certificate/abc-123",
            SslSupportMethod: "sni-only",
            MinimumProtocolVersion: "TLSv1.2_2021",
          },
        },
      },
    },
  ],
};

Note: ACM certificates for CloudFront must be in the us-east-1 region.

Without CloudFront

To deploy without CloudFront (Lambda Function URL only):

export default {
  adapter: [
    "aws",
    {
      cloudfront: false,
    },
  ],
};

The adapter generates a template.json file in your project root. This is a standard AWS SAM template that can be customized via adapterOptions.template:

export default {
  adapter: [
    "aws",
    {
      template: (template) => {
        // Add a DynamoDB table
        template.Resources.MyTable = {
          Type: "AWS::DynamoDB::Table",
          Properties: {
            TableName: "my-table",
            AttributeDefinitions: [
              { AttributeName: "id", AttributeType: "S" },
            ],
            KeySchema: [
              { AttributeName: "id", KeyType: "HASH" },
            ],
            BillingMode: "PAY_PER_REQUEST",
          },
        };
        return template;
      },
    },
  ],
};

zsh: command not found: sam

Install the AWS SAM CLI:

brew install aws-sam-cli

zsh: command not found: aws

Install the AWS CLI:

brew install awscli

Error: Unable to locate credentials

Configure your AWS credentials:

aws configure

You'll need your Access Key ID, Secret Access Key, default region, and output format. Visit the AWS IAM Console to create access keys.

If you're using AWS SSO:

aws sso login --profile your-profile

Failed to create/update the stack ... ROLLBACK_COMPLETE

A previous deployment failed and CloudFormation is stuck. Delete the failed stack and try again:

sam delete --stack-name your-stack-name
sam deploy --guided --stack-name your-stack-name --capabilities CAPABILITY_IAM

Lambda cold starts

Cold starts are expected with Lambda functions. To minimize their impact:

You can add provisioned concurrency via the template override:

export default {
  adapter: [
    "aws",
    {
      template: (template) => {
        const fnKey = Object.keys(template.Resources).find(
          (k) => template.Resources[k].Type === "AWS::Serverless::Function"
        );
        if (fnKey) {
          template.Resources[fnKey].Properties.ProvisionedConcurrencyConfig = {
            ProvisionedConcurrentExecutions: 1,
          };
        }
        return template;
      },
    },
  ],
};

CloudFront cache invalidation

After redeploying, CloudFront may still serve stale cached content. Create an invalidation:

aws cloudfront create-invalidation \
  --distribution-id YOUR_DISTRIBUTION_ID \
  --paths "/*"

Build assets with content-hashed filenames (/assets/*, /client/*) don't need invalidation — new deployments generate new filenames automatically.

Note: For additional AWS-specific features like VPC configuration, IAM policies, or Lambda layers, use the functionProperties, resources, and template options. Refer to the AWS SAM documentation for the full template specification.

← Deploy: NetlifyDeploy: Bun →