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

Setup route 53

PreviousSetup loadbalancerNextMonitors

Last updated 3 years ago

Was this helpful?

The last step is to configure route 53 so that you can access your instance using your custom domain.

Create a new record

On your desired hosted zone create a new record. Remember that the record needs to match the ACM certificate that you assigned to your load balancer.

Choose record type A, and enable Alias, and choose Alias to Application Load Balancer. Finally choose the load balancer created in the previous step:

Create the record and then you can test it. However it can take up to 24 hours until the domain is available.