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
  3. Configure your instance

Create a PostgreSQL instance

PreviousConfigure your instanceNextConfigure Auth0

Last updated 3 years ago

Was this helpful?

If you do not already have a PostgreSQL instance that you can reuse you must create a new one. For Taskforce.sh you can use the cheapest available which is the db.t3.micro instance (price between 15$ to 23$ depending on region).

Magnetic storage and 5Gb will also be enough:

Specify that we want to create a new security group for this instance:

In the Additional configuration you need to create an initial database:

Create your database, and now make sure that the security group you created has a inbound rule that gives access to the EC2 instance running Taskforce.sh: