How to deploy Hasura to AWS

Deploy Hasura GraphQL Engine on ECS Fargate with PostgreSQL on Amazon RDS in your AWS account through Ravion, including HTTPS, custom domains, and CI/CD.

Run Hasura on ECS Fargate behind an Application Load Balancer and place PostgreSQL in RDS.

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 Hasura app for Ravion ECS hosting.

CopiedCopy promptOpen in Cursor

Configure the deployment

Ravion provisions the network, compute, and database resources in your AWS account.

The Hasura GraphQL Engine publishes an official hasura/graphql-engine image that listens on port 8080. This example deploys that prebuilt image through build_source: image_registry; it does not build from your repository. The /healthz endpoint is used for the ALB health check.

ravion.yaml

project:
  givenId: hasura-app
  name: Hasura 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: hasura-production
      - givenId: database
        name: PostgreSQL
        type: rvn-rds
        version: 1.0.0
        input:
          network:
            moduleGivenIdRef: network
          name: hasura-production
          db_name: hasura
          username: hasuraadmin
          engine_major_version: "15"
      - givenId: cluster
        name: ECS cluster
        type: rvn-ecs-cluster
        version: 1.0.0
        input:
          network:
            moduleGivenIdRef: network
          name: hasura-production
      - givenId: web
        name: Hasura web service
        type: rvn-ecs-web
        version: 1.0.0
        input:
          cluster:
            moduleGivenIdRef: cluster
          name: hasura-production-web
          build_source: image_registry
          image_repository: hasura/graphql-engine
          container_port: 8080
          health_check_path: /healthz
          fargate_size:
            vcpu: 0.5
            memory_gb: 1

Set HASURA_GRAPHQL_DATABASE_URL, HASURA_GRAPHQL_ADMIN_SECRET, and any metadata settings through runtime variables or Secrets Manager. The module schema does not automatically map an RDS output into an ECS secret, so create that secret from the RDS outputs before applying the service.

Apply and connect your domain

ravion project create --given-id hasura-app --name "Hasura app"
ravion project config apply hasura-app --file ravion.yaml --dry-run
ravion project config apply hasura-app --file ravion.yaml

Follow custom domains to configure the ALB hostname.

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.