Automation Suite
2023.10
false
Banner background image
Automation Suite on Linux Installation Guide
Last updated Apr 19, 2024

Step 6: Configuring the DNS

The Automation Suite cluster is exposing multiple URLs to access the cluster management tools and the suite core functionality, all based on a common FQDN.

You must configure the DNS for the common FQDN and the subdomains specific to each tool as shown in the following table.

Application

Domain

Example URL

Automation Suite

fqdn

automationsuite.mycompany.com

Application Lifecycle Management (ALM)

alm.{{fqdn}}

alm.automationsuite.mycompany.com

Monitoring / Observability

monitoring.{{fqdn}}

monitoring.automationsuite.mycompany.com

Object Store

objectstore.{{fqdn}}

objectstore.automationsuite.mycompany.com

Docker Registry

registry.{{fqdn}}

registry.automationsuite.mycompany.com

Insights

insights.{{fqdn}}

insights.automationsuite.mycompany.com

Configuring DNS using public domain registrar

Add a A Record in Advanced DNS or Management section of your domain as shown in the following table:

Type

Host

Value

A Record (or CName)
automationsuite (or a subdomain to access Automation Suite)
  • For A Record: IP Address of Load Balancer
  • For CName: DNS name associated with Load Balancer
A Record (or CName)
*.automationsuite (or a subdomain to access Automation Suite)
  • For A Record: IP Address of Load Balancer
  • For CName: DNS name associated with Load Balancer

See the following example for the configuration:



Note: If the * wildcard is too generic, add a separate record or rule for the following subdomains: alm, monitoring, objectstore, registry, and insights.

Configuring the DNS in a multi-site deployment

Automation Suite multi-site deployments require that you configure the DNS for the common FQDN and the subdomains specific to each tool as shown in the following table:

Application

Domain

Example

Value

Primary Cluster FQDN

fqdn-primary

automationsuite-primary.mycompany.com

  • For A Record: the IP address of the primary cluster’s load balancer
  • For CName: the DNS name associated with the primary cluster’s load balancer

Secondary Cluster FQDN

fqdn-secondary

automationsuite-secondary.mycompany.com

  • For A Record: the IP address of the secondary cluster’s load balancer
  • For CName: the DNS name associated with the secondary cluster’s load balancer

Application Lifecycle Management

alm.{{fqdn-primary}}

alm.automationsuite-primary.mycompany.com

  • For A Record: the IP address of the primary cluster’s load balancer
  • For CName: the DNS name associated with the primary cluster’s load balancer

alm.{{fqdn-secondary}}

alm.automationsuite-secondary.mycompany.com

  • For A Record: the IP address of the secondary cluster’s load balancer
  • For CName: the DNS name associated with the secondary cluster’s load balancer

Monitoring

monitoring.{{fqdn-primary}}

monitoring.automationsuite-primary.mycompany.com

  • For A Record: the IP address of the primary cluster’s load balancer
  • For CName: the DNS name associated with the primary cluster’s load balancer

monitoring.{{fqdn-secondary}}

monitoring.automationsuite-secondary.mycompany.com

  • For A Record: the IP address of the secondary cluster’s load balancer
  • For CName: the DNS name associated with the secondary cluster’s load balancer

Registry (For offline only)

registry.{{fqdn-primary}}

registry.automationsuite-primary.mycompany.com

  • For A Record: the IP address of the primary cluster’s load balancer
  • For CName: the DNS name associated with the primary cluster’s load balancer

registry.{{fqdn-secondary}}

registry.automationsuite-secondary.mycompany.com

  • For A Record: the IP address of the secondary cluster’s load balancer
  • For CName: the DNS name associated with the secondary cluster’s load balancer

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.