|The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply.
Custom domains for portals are only available to customers on Essential, Advanced, or Enterprise support.
By default, all portals have a set URL that uses the Appian environment name for the subdomain and
appianportals.com for the domain. For example, if an environment is called
insurecorp, the URLs for portals published from the environment will use
This works well for many use cases. However, some organizations prefer to have more control over the URLs for their portals. That's where custom domains come in.
Using a custom domain, you can configure your portal URLs to use a domain that you define. So the above example could use
web.insurecorp.com instead of
This page outlines how to configure a custom domain that all portals in your environment will use.
The hostname is how you define the URL to use for the portals in your environment. It should consist of a subdomain, a domain, and a top-level domain. For example, in
web.insurecorp.com, the subdomain is
web, the domain is
insurecorp, and the top-level domain is
When you choose a hostname, make sure it meets the following criteria:
mysites.insurecorp.com for your Appian environment and
myportals.insurecorp.com for your portals.
www is considered a subdomain.
Make sure the DNS infrastructure resolving your domain is publicly accessible. Otherwise, certificate signing will fail, and end users will be unable to access the portal.
If you have a Certification Authority Authorization (CAA) record configured for your domain, make sure it lists Amazon certificate authorities as authorized. Otherwise, certificate signing will fail.
Appian does not support wildcard certificates, meaning the certificate must not use wildcard characters in the hostname.
You can configure one custom domain per environment. Appian Support will work with you to create a certificate and configure your environment to use the domain.
Once configured, all portals published from the environment will use the custom domain.
To configure a custom domain for your portals:
The certificates are created and hosted in AWS Certificate Manager (ACM). They are signed by an Amazon certificate authority, and the private key cannot be exported from AWS.
Because the certificate is created and hosted in ACM, it will be automatically renewed if the following conditions are met:
If the certificate expires due to one of the criteria not being met, open a support case with Appian Support to create a new certificate.
Configuring a Custom Domain for Portals