RemixSite

The RemixSite construct is a higher level CDK construct that makes it easy to create a Remix app. It provides a simple way to build and deploy the app to AWS:

The browser build and public static assets are deployed to an S3 Bucket, and served out from a CloudFront CDN for fast content delivery.
The app server is deployed to Lambda. You can deploy to Lambda@Edge instead if the edge flag is enabled. Read more about Single region vs Edge.
It enables you to configure custom domains for the website URL.
It also enable you to automatically set the environment variables for your Remix app directly from the outputs in your SST app.
It provides a simple interface to grant permissions for your app to access AWS resources.

Quick Start

If you are creating a new Remix app, run create-remix from the root of your SST app.
```
npx create-remix@latest
```
And select Remix App Server as the deployment target.
After the Remix app is created, your SST app structure should look like:
```
my-sst-app
├─ sst.config.ts
├─ services
├─ stacks
└─ my-remix-app     <-- new Remix app
   ├─ app
   ├─ public
   └─ remix.config.js
```
You can now jump to step 3 to complete the rest of the step.
If you have an existing Remix app, move the app to the root of your SST app. Your SST app structure should look like:
```
my-sst-app
├─ sst.config.ts
├─ services
├─ stacks
└─ my-remix-app     <-- your Remix app
   ├─ app
   ├─ public
   └─ remix.config.js
```
When you created your Remix app, you might've picked a different deployment target. We need to set the deploymen target to Remix App Server. To do that, make sure your remix.config.js contain the follow values.
```
module.exports = {
  ignoredRouteFiles: ["**/.*"],
  serverModuleFormat: "esm",
};
```
info
If you followed the Developer Blog or Jokes App tutorials on Remix's doc, it's likely you are using SQLite for database. SQLite databases cannot be deployed to a serverless environment. It is often used for local storage, and not recommended for modern web apps. It is recommended to use PostgreSQL, DynamoDB, or one of third party services like MongoDB for your database.
Go into your Remix app, and add the sst bind command to your Remix application's package.json. sst bind enables you to automatically set the environment variables for your Remix app directly from the outputs in your SST app.
Update the package.json scripts for your Remix application.
```
  "scripts": {
    "build": "remix build",
-   "dev": "remix dev",
+   "dev": "sst bind remix dev",
    "start": "remix-serve build"
  },
```

Add the RemixSite construct to an existing stack in your SST app. You can also create a new stack for the app.

import { RemixSite, StackContext } as sst from "sst/constructs";

export default function MyStack({ stack }: StackContext) {

  // ... existing constructs

  // Create the Remix site
  const site = new RemixSite(stack, "Site", {
    path: "my-remix-app/",
  });

  // Add the site's URL to stack output
  stack.addOutputs({
    URL: site.url || "localhost",
  });
}

When you are building your SST app, RemixSite will invoke npm build inside the Remix app directory. Make sure path is pointing to the your Remix app.

We also added the site's URL to the stack output. After the deploy succeeds, the URL will be printed out in the terminal.

Working locally

To work on your Remix app locally with SST:

Start SST in your project root.
```
npx sst dev
```
Then start your Remix app. This should run sst bind remix dev.
```
npm run dev
```

note

When running sst dev, SST does not deploy your Remix app. It's meant to be run locally.

Single region vs edge

There are two ways you can deploy the Remix app to your AWS account.

By default, the Remix app server is deployed to a single region defined in your sst.config.ts or passed in via the --region flag. Alternatively, you can choose to deploy to the edge. When deployed to the edge, loaders/actions are running on edge location that is physically closer to the end user. In this case, the app server is deployed to AWS Lambda@Edge.

You can enable edge like this:

const site = new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  edge: true,
});

Note that, in the case you have a centralized database, Edge locations are often far away from your database. If you are quering your database in your loaders/actions, you might experience much longer latency when deployed to the edge.

info

We recommend you to deploy to a single region when unsure.

Custom domains

You can configure the website with a custom domain hosted either on Route 53 or externally.

const site = new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: "my-app.com",
});

Note that visitors to the http:// URL will be redirected to the https:// URL.

You can also configure an alias domain to point to the main domain. For example, to setup www.my-app.com redirecting to my-app.com:

const site = new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: {
    domainName: "my-app.com",
    domainAlias: "www.my-app.com",
  },
});

Environment variables

The RemixSite construct allows you to set the environment variables in your Remix app based on outputs from other constructs in your SST app. So you don't have to hard code the config from your backend. Let's look at how.

To expose environment variables to your Remix application you should utilise the RemixSite construct environment configuration property rather than an .env file within your Remix application root.

Imagine you have an API created using the Api construct, and you want to fetch data from the API. You'd pass the API's endpoint to your Remix app.

const api = new Api(stack, "Api", {
  // ...
});

new RemixSite(stack, "Site", {
  path: "path/to/site",
  environment: {
    API_URL: api.url,
  },
});

Then you can access the API's URL in your loaders/actions:

export async function loader() {
  console.log(process.env.API_URL);
}

info

Remix only supports server environment variables. If you are looking to access environment variables in your browser code, follow the Remix guide on browser environment variables.

In our example, you'd return ENV for the client from the root loader.

app/routes/index.tsx
export async function loader() {
  return json({
    ENV: {
      API_URL: process.env.API_URL,
    },
  });
}

Let's take look at what is happening behind the scene.

While deploying

On sst deploy, the Remix app server is deployed to a Lambda function, and the RemixSite's environment values are set as Lambda function environment variables. In this case, process.env.API_URL will be available at runtime.

If you enabled the edge option, the Remix app server will instead get deployed to a Lambda@Edge function. We have an issue here, AWS Lambda@Edge does not support runtime environment variables. To get around this limitation, we insert a snippet to the top of your app server:

const environment = "{{ _SST_FUNCTION_ENVIRONMENT_ }}";
process.env = { ...process.env, ...environment };

And at deploy time, after the referenced resources have been created, the API in this case, a CloudFormation custom resource will update the app server's code and replace the placeholder {{ _SST_FUNCTION_ENVIRONMENT_ }} with the actual value:

const environment = {
  API_URL: "https://ioe7hbv67f.execute-api.us-east-1.amazonaws.com",
};
process.env = { ...process.env, ...environment };

This will make process.env.API_URL available at runtime.

While developing

To use these values while developing, run sst dev to start the Live Lambda Development environment.

npx sst dev

Then in your Remix app to reference these variables, add the sst bind command.

package.json
"scripts": {
  "build": "remix build",
  "dev": "sst bind remix dev",
  "start": "remix-serve build"
},

Now you can start your Remix app as usual and it'll have the environment variables from your SST app.

npm run dev

There are a couple of things happening behind the scenes here:

The sst dev command generates a file with the values specified by the RemixSite construct's environment prop.
The sst bind CLI will traverse up the directories to look for the root of your SST app.
It'll then find the file that's generated in step 1.
It'll load these as environment variables before running the start command.

note

sst bind only works if the Remix app is located inside the SST app or inside one of its subdirectories. For example:

/
  sst.config.ts
  my-remix-app/

Using AWS services

SST makes it very easy for your RemixSite construct to access other resources in your AWS account. Imagine you have an S3 bucket created using the Bucket construct. You can bind it to your Remix app.

const bucket = new Bucket(stack, "Uploads");

const site = new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  bind: [bucket],
});

This will attach the necessary IAM permissions and allow your Remix app to access the bucket through the typesafe sst/node client.

import { Bucket } from "sst/node/bucket";

export async function loader() {
  console.log(Bucket.Uploads.bucketName);
}

You can read more about this over on the Resource Binding doc.

info

The sst/node client utilizes top-level await and requires the Remix server to be built using the esm output format. Ensure that `serverModuleFormat`` is set to esm in your remix.config.js.

Warming

Server functions may experience performance issues due to Lambda cold starts. SST helps mitigate this by creating an EventBridge scheduled rule to periodically invoke the server function.

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  warm: 20,
});

Setting warm to 20 keeps 20 server function instances active, invoking them every 5 minutes.

Note that warming is currently supported only in regional mode.

Cost

There are three components to the cost:

EventBridge scheduler: $0.00864

Requests cost — 8,640 invocations per month x $1/million = $0.00864

Warmer function: $0.145728288

Requests cost — 8,640 invocations per month x $0.2/million = $0.001728
Duration cost — 8,640 invocations per month x 1GB memory x 1s duration x $0.0000166667/GB-second = $0.144000288

Server function: $0.0161280288 per warmed instance

Requests cost — 8,640 invocations per month x $0.2/million = $0.001728
Duration cost — 8,640 invocations per month x 1GB memory x 100ms duration x $0.0000166667/GB-second = $0.0144000288

For example, keeping 50 instances of the server function warm will cost approximately $0.96 per month

$0.00864 + $0.145728288 + $0.0161280288 x 50 = $0.960769728

This cost estimate is based on the us-east-1 region pricing and does not consider any free tier benefits.

Examples

Configuring custom domains

You can configure the website with a custom domain hosted either on Route 53 or externally.

Using the basic config (Route 53 domains)

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: "my-app.com",
});

Redirect www to non-www (Route 53 domains)

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: {
    domainName: "my-app.com",
    domainAlias: "www.my-app.com",
  },
});

Configuring domains across stages (Route 53 domains)

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: {
    domainName:
      scope.stage === "prod" ? "my-app.com" : `${scope.stage}.my-app.com`,
    domainAlias: scope.stage === "prod" ? "www.my-app.com" : undefined,
  },
});

Configuring alternate domain names (Route 53 domains)

You can specify additional domain names for the site url. Note that the certificate for these names will not be automatically generated, so the certificate option must be specified. Also note that you need to manually create the Route 53 records for the alternate domain names.

import * as acm from "aws-cdk-lib/aws-certificatemanager";
import * as route53 from "aws-cdk-lib/aws-route53";
import * as route53Targets from "aws-cdk-lib/aws-route53-targets";

// Look up hosted zone
const hostedZone = route53.HostedZone.fromLookup(stack, "HostedZone", {
  domainName: "domain.com",
});

// Create a certificate with alternate domain names
const certificate = new acm.DnsValidatedCertificate(stack, "Certificate", {
  domainName: "foo.domain.com",
  hostedZone,
  region: "us-east-1",
  subjectAlternativeNames: ["bar.domain.com"],
});

// Create site
const site = new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: {
    domainName: "foo.domain.com",
    alternateNames: ["bar.domain.com"],
    cdk: {
      hostedZone,
      certificate,
    },
  },
});

// Create A and AAAA records for the alternate domain names
const recordProps = {
  recordName: "bar.domain.com",
  zone: hostedZone,
  target: route53.RecordTarget.fromAlias(
    new route53Targets.CloudFrontTarget(site.cdk.distribution)
  ),
};
new route53.ARecord(stack, "AlternateARecord", recordProps);
new route53.AaaaRecord(stack, "AlternateAAAARecord", recordProps);

Importing an existing certificate (Route 53 domains)

import { Certificate } from "aws-cdk-lib/aws-certificatemanager";

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: {
    domainName: "my-app.com",
    cdk: {
      certificate: Certificate.fromCertificateArn(stack, "MyCert", certArn),
    },
  },
});

Note that, the certificate needs be created in the us-east-1(N. Virginia) region as required by AWS CloudFront.

Specifying a hosted zone (Route 53 domains)

If you have multiple hosted zones for a given domain, you can choose the one you want to use to configure the domain.

import { HostedZone } from "aws-cdk-lib/aws-route53";

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: {
    domainName: "my-app.com",
    cdk: {
      hostedZone: HostedZone.fromHostedZoneAttributes(stack, "MyZone", {
        hostedZoneId,
        zoneName,
      }),
    },
  },
});

Configuring externally hosted domain

import { Certificate } from "aws-cdk-lib/aws-certificatemanager";

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  customDomain: {
    isExternalDomain: true,
    domainName: "my-app.com",
    cdk: {
      certificate: Certificate.fromCertificateArn(stack, "MyCert", certArn),
    },
  },
});

Note that the certificate needs be created in the us-east-1(N. Virginia) region as required by AWS CloudFront, and validated. After the Distribution has been created, create a CNAME DNS record for your domain name with the Distribution's URL as the value. Here are more details on configuring SSL Certificate on externally hosted domains.

Also note that you can also migrate externally hosted domains to Route 53 by following this guide.

Configuring server function

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  timeout: "5 seconds",
  memorySize: "2048 MB",
});

Advanced examples

Configuring VPC

Note that VPC is only supported when deploying to a single region.

import { Vpc, SubnetType } as ec2 from "aws-cdk-lib/aws-ec2";

// Create a VPC
const vpc = new Vpc(stack, "myVPC");

// Alternatively use an existing VPC
const vpc = Vpc.fromLookup(stack, "myVPC", { ... });

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  cdk: {
    server: {
      vpc,
      vpcSubnets: {
        subnetType: SubnetType.PRIVATE_WITH_NAT,
      }
    }
  }
});

Using an existing S3 Bucket

import * as s3 from "aws-cdk-lib/aws-s3";

new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  cdk: {
    bucket: s3.Bucket.fromBucketName(stack, "Bucket", "my-bucket"),
  },
});

Reusing CloudFront cache policies

CloudFront has a limit of 20 cache policies per AWS account. This is a hard limit, and cannot be increased. If you plan to deploy multiple Remix sites, you can have the constructs share the same cache policies by reusing them across sites.

import * as cdk from "aws-cdk-lib";
import * as cf from "aws-cdk-lib/aws-cloudfront";

const serverCachePolicy = new cf.CachePolicy(stack, "ServerCache", {
  queryStringBehavior: cf.CacheQueryStringBehavior.all(),
  headerBehavior: cf.CacheHeaderBehavior.none(),
  cookieBehavior: cf.CacheCookieBehavior.all(),
  defaultTtl: cdk.Duration.days(0),
  maxTtl: cdk.Duration.days(365),
  minTtl: cdk.Duration.days(0),
  enableAcceptEncodingBrotli: true,
  enableAcceptEncodingGzip: true,
});

new RemixSite(stack, "Site1", {
  path: "my-remix-app/",
  cdk: {
    serverCachePolicy,
  },
});

new RemixSite(stack, "Site2", {
  path: "another-remix-app/",
  cdk: {
    serverCachePolicy,
  },
});

Protecting server function behind API Gateway

When deployed to a single region, instead of sending the request to the server function directly, you can send the request to API Gateway and have API Gateway proxy the request to the server function. With this setup, you can use features like authorizers to protect the server function.

import { Fn } from "aws-cdk-lib";
import * as origins from "aws-cdk-lib/aws-cloudfront-origins";

// Create an API Gateway API
const api = new Api(stack, "Api");

// Configure the CloudFront distribution to route requests to the API endpoint
const site = new RemixSite(stack, "Site", {
  path: "my-remix-app/",
  cdk: {
    distribution: {
      defaultBehavior: {
        origin: new origins.HttpOrigin(Fn.parseDomainName(api.url)),
      },
    },
  },
});

// Configure the API Gateway to route all incoming requests to the site's SSR function
// Note: The site is not deployed when using the `sst dev` command
if (!app.local) {
  api.addRoutes(stack, {
    "ANY /{proxy+}": {
      type: "function",
      cdk: {
        function: site.cdk.function,
      },
    },
  });
}

Constructor

new RemixSite(scope, id, rawProps)

Parameters

scope Construct
id string
rawProps SsrSiteProps

Properties

An instance of RemixSite has the following properties.

customDomainUrl

Type : undefined | string

If the custom domain is enabled, this is the URL of the website with the custom domain.

id

Type : string

url

Type : undefined | string

The CloudFront URL of the website.

cdk

Type : undefined |

cdk.bucket

Type : Bucket

cdk.certificate

Type : undefined | ICertificate

cdk.distribution

Type : IDistribution

cdk.function

Type : undefined | IFunction | Function

cdk.hostedZone

Type : undefined | IHostedZone

The internally created CDK resources.

Methods

An instance of RemixSite has the following methods.

attachPermissions

attachPermissions(permissions)

Parameters

permissions Permissions

Attaches the given list of permissions to allow the server side rendering framework to access other AWS resources.

site.attachPermissions(["sns"]);

getConstructMetadata

getConstructMetadata()

Quick Start​

info

Working locally​

note

Single region vs edge​

info

Custom domains​

Environment variables​

info

While deploying​

While developing​

note

Using AWS services​

info

Warming​

Cost​

Examples​

Configuring custom domains​

Using the basic config (Route 53 domains)​

Redirect www to non-www (Route 53 domains)​

Configuring domains across stages (Route 53 domains)​

Configuring alternate domain names (Route 53 domains)​

Importing an existing certificate (Route 53 domains)​

Specifying a hosted zone (Route 53 domains)​

Configuring externally hosted domain​

Configuring server function​

Advanced examples​

Configuring VPC​

Using an existing S3 Bucket​

Reusing CloudFront cache policies​

Protecting server function behind API Gateway​

Constructor​

Properties​

customDomainUrl​

id​

url​

cdk​

cdk.bucket​

cdk.certificate​

cdk.distribution​

cdk.function​

cdk.hostedZone​

Methods​

attachPermissions​

getConstructMetadata​

Quick Start

Working locally

Single region vs edge

Custom domains

Environment variables

While deploying

While developing

Using AWS services

Warming

Cost

Examples

Configuring custom domains

Using the basic config (Route 53 domains)

Redirect www to non-www (Route 53 domains)

Configuring domains across stages (Route 53 domains)

Configuring alternate domain names (Route 53 domains)

Importing an existing certificate (Route 53 domains)

Specifying a hosted zone (Route 53 domains)

Configuring externally hosted domain

Configuring server function

Advanced examples

Configuring VPC

Using an existing S3 Bucket

Reusing CloudFront cache policies

Protecting server function behind API Gateway

Constructor

Properties

customDomainUrl

id

url

cdk

cdk.bucket

cdk.certificate

cdk.distribution

cdk.function

cdk.hostedZone

Methods

attachPermissions

getConstructMetadata