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

Was this helpful?

  1. On Premises
  2. AWS

Configure your instance

PreviousAssign SSM RoleNextCreate a PostgreSQL instance

Last updated 3 years ago

Was this helpful?

In order to configure your On-Premises instance you need to use the configuration tool that is available at your ec2 instance on port 8080.

To login you need to use the username admin and your instance id as the password. The instance id appears on your EC2 dashboard where the instance is running.

Note that if you access your instance directly from the instance domain, it will use standard HTTP instead of HTTPS. If you want an extra layer of security it is recommended to configure HTTPS by allocating a dedicated subdomain for the admin tool and AWS Certificate manager. These would be the same instructions as to configure the Taskforce.sh, check Setup loadbalancer and Setup route 53.

Once you login into the configuration tool you can setup all the necessary settings, starting with PostgreSQL. You must test the connection before you are allowed to save.

Due to a limitation in the current version, only "postgres" is allowed as the user, this will be improved in next versions.

When all the settings have been set and saved you can also see that they are stored in the Parameter Store: