How to deploy Astro to AWS

Deploy your Astro static build to an S3 bucket behind 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 Astro app for Ravion static or SSR hosting.

Configure the deployment

The bucket and distribution stay in your AWS account, and Ravion versions each deployment. This example uses Railpack for the build. Use build_source: dockerfile instead when you need a custom Dockerfile. For a static Astro site, astro build writes to dist. Set routing to filesystem so generated paths resolve to their files.

ravion.yaml

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

Apply the config

Create the project

ravion project create --given-id astro-site --name "Astro site"

Preview and apply

ravion project config apply astro-site --file ravion.yaml --dry-run
ravion project config apply astro-site --file ravion.yaml

Astro variables prefixed with PUBLIC_ are exposed to browser code. Add them to build_environment_variables when they are required at build time. Keep server-only values out of a static build.

Custom domain

Use the CloudFront distribution hostname from the module outputs, then follow custom domains to add an ACM certificate and DNS record.

Astro SSR on ECS

For on-demand rendering, install @astrojs/node, set output: "server", and configure standalone mode. Astro writes the server entry to dist/server/entry.mjs; run it with Node on port 4321.

ravion.yaml

project:
  givenId: astro-ssr
  name: Astro SSR 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: astro-ssr-production
      - givenId: cluster
        name: ECS cluster
        type: rvn-ecs-cluster
        version: 1.0.0
        input:
          network:
            moduleGivenIdRef: network
          name: astro-ssr-production
      - givenId: web
        name: Astro SSR web service
        type: rvn-ecs-web
        version: 1.0.0
        input:
          cluster:
            moduleGivenIdRef: cluster
          name: astro-ssr-production-web
          build_source: railpack
          source_repo: my-org/my-astro-app
          railpack_build_cmd: npm run build
          railpack_start_cmd: node ./dist/server/entry.mjs
          container_port: 4321
          fargate_size:
            vcpu: 0.5
            memory_gb: 1

Set HOST=0.0.0.0 and PORT=4321 in the runtime environment. Use the ECS service’s Application Load Balancer hostname for your custom domain.

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

​Apply the config

​Custom domain

​Astro SSR on ECS

​Next steps