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.
| 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: the IP address of the machineFor 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 machineFor CName: the DNS name associated with the machine |
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, andinsights.
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