This page applies to Appian Cloud only. It may not reflect the differences with Appian Government Cloud.
Customers who are subscribed to Basic Support cannot use custom domains.
When Appian Cloud environments are created, they are assigned a subdomain under the
appiancloud.com domain. However, Appian Cloud customers can request to customize the Fully Qualified Domain Names (FQDN) of their environments to provide a personalized experience to end users.
This page outlines the steps required to change the FQDN of Appian Cloud environments to a custom domain.
An FQDN consists of three parts:
For example, in
prod-environment is the subdomain,
apps.mycorp is the domain, and
org is the TLD.
Valid domains and subdomains:
Appian Cloud environments use 3 FQDNs. By default, these are:
Only the main FQDN is visible to end users. You can choose to customize all three FQDNs, or the main FQDN by itself.
Your company domain is
mycorp.org and you have an environment called
production-acme currently using the
appiancloud.com domain, available at
production-acme.appiancloud.com. You want to customize this environment to use
mycorp.org so that end users can access the environment using the FQDN
You can decide to customize all 3 FQDNs:
When customizing a domain, the static, dynamic, and main FQDNs must be unique. You can use any valid FQDN configuration to customize the domain; each FQDN does not need to include the type, like static, dynamic, or main.
You can also opt to customize just the main FQDN of your environment. Appian Cloud will take care of handling the remaining two domains:
To renew your certificate, follow the renewal steps in Self-Service Certificate Management.
The static and dynamic domains are used for background web requests to support features such as the Document Viewer Component and Component Plug-ins. These domains are needed for security purposes. Review the Post Install Configurations for more details.
You do not need to change the subdomain portion of your environment's FQDN.
The subdomain portion of the environment FQDN must comply with the following requirements:
Requesting a Custom Domain