Subscribe

UiPath Automation Suite

The UiPath Automation Suite Guide

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 need to configure the DNS for the common FQDN and the subdomains specific to each tool as shown in the following table.

ApplicationDomainExample URL
Automation Suitefqdnautomationsuite.mycompany.com
Application Lifecycle Management (ALM)alm.{{fqdn}}alm.automationsuite.mycompany.com
Monitoring / Observabilitymonitoring.{{fqdn}}monitoring.automationsuite.mycompany.com
Object Storeobjectstore.{{fqdn}}objectstore.automationsuite.mycompany.com
Docker Registryregistry.{{fqdn}}registry.automationsuite.mycompany.com
Insightsinsights.{{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:

TypeHostValue
A Record (or CName)automationsuite (or a subdomain to access Automation Suite) For A Record: the IP address of the machine

For CName: the DNS name associated with the machine
A Record (or CName)*.automationsuite (or a subdomain to access Automation Suite) For A Record: the IP address of the machine

For CName: the DNS name associated with the machine

See the following example for the configuration:

1041

📘

Note:

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

 

For test or evaluation deployments: Creating a private DNS zone


As a workaround, you can use a private domain for testing purposes only.

For an example, see Sample Azure infrastructure setup.

Updated 6 months ago


Configuring the DNS


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.