Taskforce.sh
  • Documentation
  • Getting started
    • Direct Redis Connection
    • Taskforce connector
  • Account
    • Settings
  • Connections
    • Queues
    • Jobs
    • Workers
  • Metrics
  • Monitoring
    • Enable notifications
      • Slack
      • Pagerduty
    • Connection monitor
    • Failed jobs monitor
    • Missing workers monitor
    • Max Memory monitor
    • Backlog Monitor
  • Alerts
  • Organizations
  • BullMQ Pro
    • Connector Pro
  • On Premises
    • AWS
      • Launch AWS AMI.
      • Create role with SSM permissions
      • Assign SSM Role
      • Configure your instance
        • Create a PostgreSQL instance
        • Configure Auth0
          • Configure API
        • Configure Mailgun
      • Setup loadbalancer
      • Setup route 53
      • Monitors
      • Upgrading
      • Troubleshooting
    • Docker
      • Docker registry
      • Environment variables
      • Docker compose
    • Using the taskforce connector
  • Security primer
  • Troubleshooting
Powered by GitBook
On this page
  • Requirements
  • Installation

Was this helpful?

  1. On Premises

AWS

PreviousOn PremisesNextLaunch AWS AMI.

Last updated 2 years ago

Was this helpful?

Requirements

The On-Premises deployment is a stateful service that only requires storing some environment variables in AWS System Manager. However, it requires some external services in order to work:

  • An AWS Application Load balancer with HTTPS enabled for your domain.

  • A PostgreSQL instance to use for your persistent data, you can provision one in AWS for less than 15$ a month.

  • An Auth0 application, is required to handle user authentication, the free version is perfectly fine unless you need more advanced features.

  • A Mailgun account is used to notify users via email, also the free version is enough.

Since the deployment is stateless, upgrading to a newer version does not require any special administration other than deploying the latest AMI image available in AWS Marketplace.

Currently, you can only configure one Taskforce.sh instance per region. If you for some reason require more instances per region please contact us.

Installation

Installing Taskforce.sh in AWS is pretty straightforward, but there are a few steps to follow. The instance has some dependencies and requirements that need to be fulfilled. Please follow the instructions on these pages in order to get your instance ready and running.

When the installation is completed you will get 2 services, a Configuration service running on port 8080 (see ), and the dashboard itself that runs on port 4200 (which only will work via HTTPS access due to Auth0 security constraints, see and ).

Configure your instance
Setup loadbalancer
Setup route 53