Skip to main content

Deploying ToolJet on Amazon ECS

info

You should setup a PostgreSQL database manually to be used by ToolJet.

Follow the steps below to deploy ToolJet on a ECS cluster.

  1. Setup a PostgreSQL database ToolJet uses a postgres database as the persistent storage for storing data related to users and apps.

  2. Create a target group and an application load balancer to route traffic onto ToolJet containers. You can reference AWS docs to set it up. Please note that ToolJet server exposes /api/health, which you can configure for health checks.

    note

    This setup follows the old AWS UI for ECS as some options are missing on the latest experience.

  3. Create task definition for deploying ToolJet app as a service on your preconfigured cluster.

    1. Select Fargate as launch type compatibility.

      select launch type compatibility
    2. Configure IAM roles and set operating system family as Linux

      task definition config
    3. Select task size to have 3GB of memory and 1vCpu

      task size config
    4. Click on add container to update container definitions

      add container button

      Within the add container form that is shown:

      • Specify your container name ex: tooljet-ce

      • Set the image you intend to deploy. ex: tooljet/tooljet-ce:v1.26.0

      • Update port mappings at container port 3000 for tcp protocol.

        container setup
      • Update container command field to be npm,run,start:prod.

        container command
      • Specify environmental values for the container. You'd want to make use of secrets to store sensitive information or credentials, kindly refer the AWS docs to set it up.

        container env setup
        note

        For the minimal setup, ToolJet requires: TOOLJET_HOST, PG_HOST, PG_DB, PG_USER, PG_PASSWORD, SECRET_KEY_BASE & LOCKBOX_MASTER_KEY keys in the secret.

        Read environment variables reference

  4. Create a service to run your task definition within your cluster.

    • Select launch type as Fargate.
    • Set operating system family as Linux
    • Select task definition family as the one created earlier. ex: tooljet-ce
    • Select the cluster and set the service name
    • You can set the number of tasks to start with as two
    • Rest of the values can be kept as defaultservice config
    • Click on next step to configure networking options
    • Select your designated VPC, Subnets and Security groups. Kindly ensure that the security group allows for inbound traffic to http port 3000 for the task.service security group config
    • Since migrations are run as a part of container boot, please specify health check grace period for 900 seconds.
    • Select the application loadbalancer option and set the target group name to the one we had created earlier. This will auto populate the health check endpoints.
info

The setup above is just a template. Feel free to update the task definition and configure parameters for resources and environment variables according to your needs.

  1. Verify if ToolJet is running by checking by checking the status of the tasks in the created service.

Creating default admin workspace and account

You can create a new revision of your existing task definition to have a one time task to seed with default admin.

  1. Create a new revision from your existing task definition. You can change task definition name to tooljet-seed-task
  2. Click on your existing container name to edit container.
  3. Change container command from npm,run,start:prod to npm,run,db:seed:prod
  4. Go back to your cluster dashboard and click on Run new task.run new task
  5. Configure your run task with the tooljet-seed-task for your cluster. It should look like:run task config
  6. Click on run task to have this task seed the database with user having following credentials:
    • email: dev@tooljet.io
    • password: password